Topic starter
09/06/2026 11:23 pm
TL;DR: The average organisation now uses 16 AI apps, 17 AI browser extensions, and 17 AI OAuth integrations, most of them unapproved, as Shadow AI turns the browser into a trust hub that widens blast radius across connected SaaS, according to Push Security. Browser-layer governance, not app-by-app awareness, is now the control boundary.
Editorial analysis by NHI Mgmt Group, based on content published by Push Security: “What Push data reveals about the state of shadow AI”.
By the numbers:
- The average organisation has 16 unique AI apps in active use, according to Push Security.
- The average organisation has 17 unique AI browser extensions in active use, according to Push Security.
- The average organisation has 17 unique AI OAuth integrations connected into Google Workspace and Microsoft 365, according to Push Security.
Key questions
Q: What breaks when employees self-authorise AI tools in the browser without security review?
A: The control that breaks is governance by approval list.
Q: Why do OAuth integrations increase AI security risk?
A: OAuth turns access into a delegated relationship that can persist across applications and data sets.
Q: What are the signs that shadow AI controls are failing in practice?
A: Shadow AI controls are failing when sensitive data moves through copy-paste, uploads, or API calls outside sanctioned workflows, yet the organisation has no alerting or enforcement at the point of transfer.
Practitioner guidance
- Inventory AI usage by browser session Establish a baseline of which AI apps, extensions, and OAuth integrations employees are actually using, and tie each one back to the account and browser session that granted access.
- Allowlist browser extensions with explicit review Block unapproved AI browser extensions by default, then maintain a vetted allowlist for tools that have been assessed for permission scope, publisher identity, and update behaviour.
- Audit OAuth consent grants across the full SaaS estate Review AI-related consent grants in Google Workspace, Microsoft 365, and the broader SaaS estate, then remove dormant or forgotten integrations that still hold persistent tokens.
Bottom line: Shadow AI is expanding enterprise attack surface because employees are creating browser-level trust relationships that outgrow traditional app approval models.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
This topic was modified 1 day ago by NHI Mgmt Group
10/06/2026 1:42 am
Browser session governance is now an identity problem, not just a web usage problem. Shadow AI lives inside the browser, where users authenticate, consent, upload data, and connect systems in one place. That means the control boundary has shifted from application inventory to session-level identity and delegated access oversight. For IAM teams, this is a signal that browser telemetry belongs in the identity programme, not only in endpoint or web security workflows.
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 with nearly 1 in 4 for securing human identities.
A question worth separating out:
Q: How should teams reduce the blast radius of AI-driven SaaS access?
A: Teams should reduce blast radius by classifying every AI connection by the downstream systems it can reach, then removing unnecessary OAuth scopes and inactive grants. The goal is to limit how far a single compromised AI tool, extension, or user consent can travel across the SaaS estate.
👉 Read our full editorial: Shadow AI is expanding enterprise attack surface through browser trust
11/06/2026 12:47 am
Browser session governance is now an identity problem, not just a web usage problem. Shadow AI lives inside the browser, where users authenticate, consent, upload data, and connect systems in one place. That means the control boundary has shifted from application inventory to session-level identity and delegated access oversight. For IAM teams, this is a signal that browser telemetry belongs in the identity programme, not only in endpoint or web security workflows.
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 with nearly 1 in 4 for securing human identities.
A question worth separating out:
Q: How should teams reduce the blast radius of AI-driven SaaS access?
A: Teams should reduce blast radius by classifying every AI connection by the downstream systems it can reach, then removing unnecessary OAuth scopes and inactive grants. The goal is to limit how far a single compromised AI tool, extension, or user consent can travel across the SaaS estate.
👉 Read our full editorial: Shadow AI is expanding enterprise attack surface through browser trust
12/06/2026 2:21 am
Shadow AI is now a browser-governed identity problem, not an application inventory problem. The article shows that app approvals, extension permissions, and OAuth grants now happen inside the same user-controlled session. That collapses the old separation between software discovery and access governance. The implication is that programmes built only around sanctioned app lists are already behind the real control boundary.
A few things that frame the scale:
- Organisations that describe themselves as confident in their AI deployment actually experience a 72% security incident rate, compared to 33% for those who remain cautious, according to the 2026 Infrastructure Identity Survey.
- Only 13% of organisations feel extremely prepared for the reality of agentic AI despite the majority racing toward autonomous adoption, according to the 2026 Infrastructure Identity Survey.
A question worth separating out:
Q: How should security teams govern browser-based AI agents in SaaS environments?
A: Security teams should govern browser-based AI agents as runtime actors, not as ordinary users or static integrations. Give each agent a distinct identity, constrain what it can do in-session, and monitor browser, identity, and SaaS logs together. The key control is not just login validation, but continuous authorization of live actions.
👉 Read our full editorial: Shadow AI is expanding enterprise attack surface through browser trust
This post was modified 1 day ago by NHI Mgmt Group