Topic starter
17/08/2026 4:37 pm
TL;DR: Perplexity security is a shared-responsibility problem in which enterprise controls, consumer-tier usage, and Comet’s agentic browsing create different governance boundaries, according to WitnessAI. The gap is no longer model security alone, but visibility and enforcement at the interaction layer where prompts, account type, and authenticated actions determine exposure.
Editorial analysis by NHI Mgmt Group, based on content published by WitnessAI: “A guide to Perplexity security”.
Key questions
Q: What breaks when employees use personal and corporate AI accounts interchangeably?
A: Interchangeable account use breaks attribution, policy enforcement, and data handling assumptions.
Q: Why does agentic browsing increase security risk inside authenticated sessions?
A: Agentic browsing can act with the user’s current session context, so injected instructions or manipulated content may cause the agent to retrieve data or perform actions the human did not intend.
Q: What do security teams get wrong about AI governance reviews?
A: They often treat every use case as if it needs the same level of scrutiny.
Practitioner guidance
- Enforce tier-based AI access control Bind approved enterprise AI use to managed identities, separate personal accounts from corporate workflows, and block company data from consumer sessions.
- Verify retention and audit settings before rollout Confirm that enterprise tier settings for audit trails, data retention, file uploads, and sharing match the organisation’s data handling policy.
- Treat agentic browsing as privileged automation Scope Comet-style sessions with explicit permissions, monitored actions, and controls for authenticated access inside third-party services.
Bottom line: Perplexity security is not a single control problem because enterprise protections, personal-account usage, and agentic browsing each create different governance boundaries.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
17/08/2026 4:43 pm
Interaction-layer governance is now the control point that matters most for enterprise AI adoption. Perplexity illustrates a broader pattern in which written policy and provider controls are not enough unless the organisation can see prompts, responses, and account type at the moment of use. That is where identity governance meets AI governance, because the same employee can operate under different contractual and audit models in one workday. The practitioner conclusion is simple: policy without runtime observability does not govern AI use.
A question worth separating out:
Q: Who is accountable when employees use private AI for work tasks?
A: Accountability usually sits with the organisation that sets policy, the manager who approves the workflow, and the teams that control endpoint and identity settings. If no one defines approved use, the result is shadow AI with weak traceability. The right answer is explicit ownership, not assumed privacy.
👉 Read our full editorial: Perplexity security depends on tier controls and interaction-layer governance