Notifications
Clear all
Topic starter
18/08/2026 2:43 pm
TL;DR: Browser-level policy enforcement paired with Akamai ZTNA can reduce proxy-heavy SSE complexity while improving visibility into web and AI-tool access patterns, according to Seraphic. The identity implication is straightforward: when the browser becomes the control point, access governance must extend beyond network policy to session context, data handling, and risky prompt behaviour.
NHIMG editorial — based on content published by Seraphic: A New Chapter in Enterprise Security
Questions worth separating out
Q: How should security teams govern browser sessions used by AI agents?
A: Security teams should treat browser sessions used by AI agents as shared execution environments, not simple user logins.
Q: Why do unmanaged browsers create access governance gaps?
A: Unmanaged browsers can bypass the controls that organisations rely on for inspection, policy enforcement, and auditability.
Q: What do organisations get wrong about AI safety and access control?
A: Organisations often focus on model outputs while ignoring the privileges behind the model.
Practitioner guidance
- Map browser sessions to access-policy boundaries Identify which applications, SaaS tools, and AI services are now governed only after login and where browser-level enforcement is missing.
- Classify AI prompt and paste risks by data sensitivity Review which user workflows allow sensitive text, files, or credentials to move into third-party AI tools.
- Align ZTNA policy with session behaviour controls Make sure ZTNA decisions are not treated as the end of governance.
What's in the full article
Seraphic's full solution brief covers the operational detail this post intentionally leaves for the source:
- How the Secure Enterprise Browser and ZTNA policy are integrated across private apps, SaaS, and AI tools
- The specific enforcement model used to avoid proxies, endpoint agents, and TLS interception
- The vendor's operational framing for reducing infrastructure complexity and policy overlap
- The access-layer and browser-layer deployment scenarios the brief uses to justify the architecture
👉 Read Seraphic's solution brief on browser-level SSE and ZTNA integration →
Browser-level SSE and ZTNA integration: what it means for IAM teams?
Explore further
18/08/2026 3:26 pm
Browser governance is becoming an identity problem, not just a network problem. When access decisions are enforced at the browser layer, the control point moves closer to the human identity, device context, and application session. That is relevant to IAM because the browser now acts as the execution environment where authorised access can still become unsafe. Practitioners should treat browser policy as part of the access lifecycle, not an adjacent security feature.
A question worth separating out:
Q: What should teams do when browser policy and ZTNA overlap?
A: Teams should separate the functions but align the decisions. ZTNA should govern whether a user reaches the application, while browser policy should govern what they can do after access is granted. If those controls are not coordinated, users can pass the gate and still create data exposure or policy violations inside the session.
👉 Read our full editorial: Browser-level access control and SSE rework for AI-driven enterprise
