Notifications
Clear all
Topic starter
10/06/2026 12:02 am
TL;DR: Microsoft says 80% of Fortune 500 companies now run active AI agents, the average enterprise has about 1,200 unofficial AI applications, and 86% report no visibility into AI data flows, underscoring a fast-growing identity gap according to Microsoft’s February 2026 security report. Existing IAM and NHI controls can govern permissions, but they cannot explain session-level behaviour when agents act inside their approved scope.
NHIMG editorial — based on content published by AuthMind: Ahead of the Breach, Part 3 of 3, The Identity Imperative
By the numbers:
- 80% of Fortune 500 companies now have active AI agents operating within their environments.
- The average enterprise has approximately 1,200 unofficial AI applications in use.
- 86% of organizations report no visibility into their AI data flows.
Questions worth separating out
Q: How should security teams govern AI agent identity risk in enterprise environments?
A: Security teams should govern AI agents as non-human identities with additional session-level observability.
Q: Why do AI agents complicate existing IAM and NHI controls?
A: AI agents complicate IAM and NHI controls because they can act legitimately inside granted permissions while still behaving unsafely.
Q: What breaks when organisations rely only on provisioning records for AI agents?
A: What breaks is the assumption that the official catalog reflects the real attack surface.
Practitioner guidance
- Build a complete agent inventory Discover AI agents at the authentication layer, not only through approved provisioning workflows, so shadow agents and unofficial integrations enter scope before they become persistent access paths.
- Baseline session behaviour for each agent Track which resources an agent touches, in what sequence, and from what context, then flag deviations from the expected pattern as a possible sign of prompt injection or scope drift.
- Separate entitlement governance from behavioural monitoring Use NHI controls to manage credentials and permissions, but add a distinct observability layer that proves whether the agent’s live session stayed within its intended task boundary.
What's in the full article
AuthMind's full research covers the operational detail this post intentionally leaves for the source:
- Session telemetry design patterns for identifying AI agent behaviour across enterprise applications
- The article’s vendor-specific explanation of how identity observability differs from standard NHI governance
- Practical examples of detecting prompt-driven deviation at the session level in live environments
- Implementation detail on inventorying shadow AI through authentication instrumentation
👉 Read AuthMind's analysis of AI agent identity risk and identity observability →
AI agent identity risk and the governance gap teams are missing?
Explore further
10/06/2026 2:39 am
AI agent identity risk exposes a governance blind spot, not just a tooling gap. The central issue is that existing identity programmes were built to manage access at provisioning time, while AI agents create risk at session time. That means the programme can look compliant on paper while still missing the actual behaviour that matters. Practitioners should treat agent behaviour as a separate identity control plane, not a side effect of NHI management.
A few things that frame the scale:
- 91.6% of secrets remain valid five days after the targeted organisation is notified, showing a critical gap in remediation procedures, according to the Ultimate Guide to NHIs.
- Only 5.7% of organisations have full visibility into their service accounts, which shows how often identity programmes still fail at discovery before control.
A question worth separating out:
Q: Who is accountable when an AI agent acts outside its intended scope?
A: Accountability usually sits with the organisation that provisioned, approved, or failed to monitor the agent. For governance purposes, the question is not whether the agent had credentials, but whether the team had visibility into the session and defined ownership for the identity’s behaviour. Without that, accountability becomes ambiguous after the fact.
👉 Read our full editorial: AI agent identity risk is outpacing enterprise IAM controls
