Notifications
Clear all
Topic starter
09/06/2026 11:43 pm
TL;DR: LayerX is now available through AWS Security Hub’s Extended plan, giving AWS customers a consolidated way to deploy browser security, Shadow AI discovery, DLP, prompt-injection defense, and SaaS access governance through the console, according to LayerX Security. The real shift is that browser activity and AI use are being pulled into the same procurement and control plane as identity governance.
NHIMG editorial — what this means for NHI practitioners
Questions worth separating out
Q: How should security teams govern browser-based AI use in enterprise environments?
A: Security teams should govern browser-based AI use by combining discovery, policy, and identity context.
Q: Why do browser extensions and SaaS sessions create identity risk?
A: Browser extensions and SaaS sessions create identity risk because they operate inside the user’s authenticated context.
Q: What should organisations measure to know whether browser security is working?
A: Organisations should measure whether browser security reduces unmanaged AI usage, risky extension presence, and abnormal SaaS session behaviour.
Practitioner guidance
- Map the browser to your identity control plane Document which browser events should feed identity decisions, including account takeover signals, risky extension behaviour, and SaaS session anomalies.
- Classify and govern Shadow AI use Define which AI tools are sanctioned, which data types are prohibited in prompts, and what browser-based discovery signals trigger review.
- Assign clear ownership for SaaS and browser governance Separate procurement convenience from operating responsibility by naming the team that approves extensions, reviews session risk, and owns escalation when browser-mediated access is abnormal.
What's in the full announcement
LayerX Security's full post covers the operational detail this post intentionally leaves for the source:
- Console-based procurement flow inside AWS Security Hub Extended plan
- Guided onboarding path and support model for AWS Enterprise Support customers
- Browser and desktop use cases for Shadow AI discovery, DLP, and prompt-injection defense
- Granular SaaS access governance and extension-risk handling details
👉 Read LayerX Security's AWS Security Hub integration details for browser and AI security →
LayerX in AWS Security Hub - what changes for browser and AI security?
Explore further
10/06/2026 2:10 am
Browser security is becoming an identity control surface, not just an endpoint concern. When access to SaaS applications and AI tools happens through the browser, the browser starts carrying identity risk, policy enforcement, and session behaviour at the same time. That shifts governance from device-only thinking to a model where the session is part of the access decision. Practitioners should treat browser-mediated access as part of the identity plane, not a side channel.
A few things that frame the scale:
- 1 in 4 organisations are already investing in dedicated NHI security capabilities, with an additional 60% planning to do so within the next twelve months, according to The State of Non-Human Identity Security.
- Only 1.5 out of 10 organisations are highly confident in their ability to secure NHIs, compared to nearly 1 in 4 for securing human identities.
A question worth separating out:
Q: How does consolidated procurement affect security governance decisions?
A: Consolidated procurement can simplify deployment, but it should not change governance standards. Teams still need named owners, review cadences, and policy checks for access, logging, and escalation. The key decision is whether the buying path makes operational sense without weakening the control model already used for identity and SaaS governance.
👉 Read our full editorial: LayerX in AWS Security Hub: browser and AI governance implications
