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.
Editorial analysis by NHI Mgmt Group, based on content published by Seraphic: “Seraphic Enters Strategic Partnership with Akamai to Simplify SSE with Secure Enterprise Browsing”.
Key questions
Q: How should teams govern browser-level access when ZTNA and SSE are combined?
A: Treat the browser as a policy enforcement point rather than a passive client.
Q: Why does browser-based AI use increase third-party risk?
A: Because the browser is where users authenticate, consent, and connect services, so unmanaged AI adoption creates access paths before governance can review them.
Q: What breaks when SSE relies too heavily on proxy inspection?
A: Visibility becomes slower, more complex, and less aligned to the actual user session.
Practitioner guidance
- Map browser-level policy to the access lifecycle Define which decisions must be enforced in the browser, which belong in ZTNA, and which remain in downstream DLP or app controls.
- Inventory unmanaged browser paths Identify users, devices, and workflows that bypass proxy-heavy inspection so policy gaps are visible before migration decisions are made.
- Extend governance to AI-tool interactions Set controls for prompts, uploads, and third-party data sharing so AI use is covered by the same policy framework as SaaS access.
Bottom line: Browser-level SSE shifts enforcement closer to the session, which is where modern access and data-handling decisions are actually made.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
18/08/2026 3:26 pm
Browser governance is becoming the practical control boundary for modern enterprise access. When employees reach private apps, SaaS platforms, and AI tools from many devices, the browser holds the most actionable session context. Network-only models miss too much of the decision surface, so the control point has to move closer to where data is entered, moved, and disclosed. Practitioners should treat browser-level policy as a governance layer, not a tactical add-on.
A few things that frame the scale:
- 90% of IT leaders say properly managing NHIs is essential for a successful zero-trust implementation, according to the Ultimate Guide to NHIs.
- By 2029, 40% of enterprises that successfully implement zero trust within cloud service provider environments will rely on the advanced visibility and control capabilities offered by CNAPP solutions.
A question worth separating out:
Q: When should organisations re-evaluate their browser security architecture?
A: Re-evaluate it when users work across SaaS, private apps, and AI tools from many devices, because that is when browser context becomes central to both access control and data protection. If the browser is where work happens, the policy model must follow.
👉 Read our full editorial: Browser-level access control and SSE rework for AI-driven enterprise