Notifications
Clear all
Topic starter
14/09/2026 10:10 am
TL;DR: Agentic browsers turn an employee’s authenticated session into an AI-driven action layer, expanding the attack surface for prompt injection, shadow AI, and unintended access across SaaS and internal systems, according to WitnessAI. The governance problem is not the browser itself but the collapse of assumptions that user sessions, approvals, and network controls can safely constrain runtime agent behaviour.
NHIMG editorial — based on content published by WitnessAI: Agentic browsers are a new class of software that puts an AI agent behind the corporate login
By the numbers:
- 78% of AI users bring their own tools to work.
- In IBM’s 2025 analysis, breaches with high levels of Shadow AI averaged USD 670,000 more than those with little or none.
- 96% of technology professionals identify AI agents as a growing security threat, and 66% believe this risk is immediate.
Questions worth separating out
Q: What breaks when agentic browsers can act inside a human session?
A: The browser stops being a passive interface and becomes a delegated actor with the user’s live privilege.
A: Block or tightly restrict them when you cannot verify runtime controls, approval workflows, auditability, and session-level inspection.
Q: How can security teams tell whether agentic browser governance is actually working?
A: Look for attributable audit trails, approved access scopes, visible policy enforcement on consequential actions, and discovery of unmanaged installs.
Practitioner guidance
- Restrict agentic browser deployment by default Limit use to approved pilots, high-trust groups, or tightly scoped environments while vendor controls and evidence are reviewed.
- Require intent-aware inspection of routed interactions Classify prompt and response traffic by purpose, not by keywords alone, and block or warn on consequential actions involving finance systems, credential vaults, or admin consoles.
- Build session-level audit trails for agent actions Capture who initiated the browser session, what content the agent processed, which tools or services were reached, and what actions were completed so accountability survives investigation.
What's in the full article
WitnessAI's full article covers the operational detail this post intentionally leaves for the source:
- Vendor control checks for Comet, including attestations, MDM support, browser policies, and security integrations.
- Step-by-step discovery patterns for identifying agentic sessions in network traffic and connected tool activity.
- Runtime guardrail examples for inspecting prompts, responses, and consequential actions before they reach users or systems.
- Practical guidance on restricting unmanaged installations and documenting policy enforcement for audit evidence.
👉 Read WitnessAI's analysis of agentic browser governance and runtime controls →
Agentic browsers: what do identity teams need to govern now?
Explore further
14/09/2026 10:11 am
Agentic browsers create an identity control problem, not just a browser-control problem. The key issue is that the AI agent operates under the employee’s authenticated identity while making runtime decisions inside the session. That collapses the old assumption that browser activity is simply a human action extended by software. For IAM teams, the practical conclusion is that delegated session behaviour now needs explicit governance, traceability, and approval boundaries.
A few things that frame the scale:
- 80% of organisations report their AI agents have already performed actions beyond their intended scope, including accessing unauthorised systems (39%), inappropriately sharing sensitive data (31%), and revealing access credentials (23%), according to AI Agents: The New Attack Surface.
- Only 52% of companies can track and audit the data their AI agents access, leaving 48% with a complete blind spot for compliance and breach investigation, according to AI Agents: The New Attack Surface.
A question worth separating out:
Q: What is the difference between an agentic browser and a browser with an AI sidebar?
A: A browser with an AI sidebar typically assists with content, while an agentic browser can take actions inside the authenticated session. That means the agent can operate with the employee’s permissions, touch connected systems, and create identity risk that is much closer to delegated access than passive assistance.
👉 Read our full editorial: Agentic browsers expose a new enterprise identity control gap
