AI identity expansion is outpacing data security governance

At a glance

What this is: Netwrix's survey finds that AI-driven identity growth is widening the gap between access expansion and governance, with breach rates nearly four times higher where AI materially increases identities.

Why it matters: IAM, NHI, and data security teams need to treat AI-driven access growth as a governance problem, because the review and monitoring model many programmes use is already slower than the risk it is meant to contain.

By the numbers:

• 43% of organizations where AI significantly expanded identities reported a breach in the past 12 months, compared with 11% where AI had not materially changed access patterns.
• 76% of organizations do not fully govern or monitor non-human identities.
• 11% of organizations report full AI security readiness through continuous enforcement and monitoring.

Context

AI identity expansion means AI systems and workflows are creating or requiring access for more identities, including non-human identities, than the organisation can comfortably track. The governance problem is not merely volume. It is that access changes faster than the review, monitoring, and enforcement cycles most programmes still rely on.

Netwrix's survey of 2,317 IT and security professionals across 1,889 organizations in more than 60 industries suggests that readiness is lagging adoption. The article frames AI as a driver of identity sprawl, data exposure, and weaker breach resilience, which places the issue squarely in NHI governance and broader identity security.

The most important implication is that AI adoption now changes the identity estate itself. That moves the discussion from tool deployment to lifecycle control, monitoring discipline, and data access governance across human and non-human identities alike.

Key questions

Q: How should security teams govern AI readiness across identity systems?

A: They should define AI readiness as a control problem, not a rollout problem. That means linking identity governance, access review, device context, and audit evidence so AI tools and agents cannot operate outside approved boundaries. If the environment cannot answer who or what acted, on which system, and under which policy, it is not ready.

Q: Why do AI-driven attacks increase risk for identity and access management programmes?

A: They increase risk because they compress the time between exposure and impact. If attackers can move faster than normal review cycles, then standing privilege, exposed secrets, and weak revocation processes become more dangerous. IAM programmes must therefore focus on speed of detection, scope reduction, and verified offboarding, not just policy completeness.

Q: What are the signs that non-human identity governance is starting to slip?

A: Warning signs include reliance on manual upgrade paths, ad hoc secret handling, and fragmented access management across tools and environments. The article mentions caveats, dispatch limits, SSO support, and automated update channels, all of which point to the need for controlled operational discipline. When teams cannot explain how identities are provisioned, updated, and constrained, governance is already weaker than it should be.

Q: What is the difference between periodic access review and continuous AI audit?

A: Periodic access review checks whether a privilege is still justified after the fact, while continuous AI audit records access decisions and policy drift as they happen. For AI identities, that difference matters because privileges can change too quickly for retrospective review alone to be effective. Live evidence is needed to catch scope expansion before it becomes normalised.

Technical breakdown

How AI expands the identity attack surface

AI does not just add a new workload. It can create new service accounts, API credentials, delegated access paths, and data retrieval relationships that must all be governed as identities. The security issue is scale plus speed: each new access path increases the number of objects that need ownership, policy, monitoring, and removal. When AI systems interact with data at runtime, the identity estate becomes more dynamic than traditional joiner-mover-leaver processes were designed to handle.

Practical implication: Treat every AI-driven access path as an identity object with an owner, scope, expiry, and review trigger.

Why non-human identity governance becomes the bottleneck

Non-human identities are often the control gap behind AI adoption because they accumulate faster than teams inventory, classify, and monitor them. In practice, many organisations can name major human roles and applications, but not the full set of machine credentials, service accounts, tokens, and delegated permissions that AI workflows rely on. That leaves security teams with weak accountability and limited evidence when access needs to be reviewed or revoked.

Practical implication: Build a current inventory of all non-human identities tied to AI use cases and validate ownership before expanding access further.

Why continuous enforcement matters more than periodic review

Periodic access review assumes privileges remain stable long enough to be sampled and certified. AI-driven access patterns often change too quickly for that assumption to hold, especially when data access is created to support automated analysis or decisioning. Continuous enforcement closes the gap between issuance and misuse by checking access conditions in real time rather than waiting for the next review cycle. In a fast-changing identity environment, that difference determines whether governance is reactive or actually controlling exposure.

Practical implication: Shift high-risk AI access paths from calendar-based review to continuous policy enforcement and monitoring.

Threat narrative

Attacker objective: Exploit AI-expanded access paths to reach sensitive data faster than the organisation can detect, review, or contain the exposure.

1. Entry begins when AI adoption introduces additional identities and access paths into the environment, including non-human identities that may not be fully inventoried or governed.
2. Escalation occurs as these identities gain access to sensitive data faster than human-paced review cycles can track, expanding the available attack surface.
3. Impact follows when attackers exploit the expanded access footprint before governance and monitoring catch up, which the article says can happen in seconds.

Breaches seen in the wild

• Scania insurance portal breach 2025: An attacker used an external user login, likely stolen by infostealer malware, to take insurance claim documents from a Scania portal.

Read and download The State of NHI & AI Agent Breach Report 2026, covering 150+ breaches impacting Non-Human Identities including AI Agents.

NHI Mgmt Group analysis

AI identity expansion is really a governance compression problem: the more AI broadens access, the less useful human-paced review becomes as a control model. The article shows that breach rates rise where AI materially changes identity patterns, which means the programme risk is not just more access, but less time to govern it. Practitioners should read this as a lifecycle problem, not a tooling announcement.

Non-human identity governance is now a prerequisite for AI security readiness: the article's 76% figure shows that most organisations still do not fully govern or monitor the identities AI relies on. That gap matters because AI-driven access rarely stays inside a neat application boundary. The implication is that ownership, inventory, and revocation discipline for NHI must be treated as core security controls, not back-office hygiene.

Continuous enforcement is becoming the default control assumption: 11% full AI security readiness is not a maturity milestone, it is a warning that the current operating model is still the exception. Security teams should assume AI access will outpace scheduled review unless enforcement moves closer to issuance and runtime. That changes how identity programmes define evidence, accountability, and acceptable exposure.

Identity blast radius is now the right way to discuss AI risk: AI does not only increase the number of identities, it increases the speed at which those identities can connect data, permissions, and decisions. The article makes clear that the issue is blast radius, not just inventory size. Practitioners should focus on limiting what any AI-linked identity can reach at once.

The governance question is no longer whether AI will create identities, but whether the programme can see and constrain them quickly enough: identity security has moved into a state where stale assumptions about review cadence and static access no longer hold. This is where NHI, data security, and AI governance converge. The practical conclusion is that visibility, enforcement, and offboarding must be designed as one control chain.

From our research library:

• 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.
• Read next: Ultimate Guide to NHIs — Key Research and Survey Results

What this signals

Identity programmes built for human review cycles will underperform when AI starts creating and consuming access dynamically. The organisation does not need more certificate-style comfort; it needs control points that can evaluate access at the moment it is issued and used.

Continuous enforcement becomes the practical dividing line between AI readiness and AI theatre. If the control only works on a calendar, it will lose to systems that create access in real time.

According to the 2026 Infrastructure Identity Survey, organizations that describe themselves as confident in their AI deployment actually experience a 72% security incident rate, compared with 33% for those who remain cautious. That gap suggests confidence without governance discipline is a risk signal, not a maturity marker.

For practitioners

• Inventory AI-linked identities Map every service account, token, credential, and delegated permission used by AI workflows. Assign a named owner and tie each identity to a specific business purpose.
• Classify high-risk access paths Mark identities that can reach sensitive data, production systems, or privileged APIs so they receive tighter approval, monitoring, and revocation rules.
• Move from periodic review to continuous monitoring Use runtime enforcement for AI-driven access where privilege changes too quickly for quarterly certification to be meaningful.
• Define offboarding for AI access Require revocation steps for AI-related identities when a model, workflow, dataset, or vendor relationship is retired or changed.

Key takeaways

• AI adoption is changing the identity problem itself by multiplying the number and pace of access paths that security teams have to govern.
• The article's breach data and readiness figures point to a material gap between AI deployment and the control model most organisations still rely on.
• Practitioners should prioritise inventory, ownership, and continuous enforcement for AI-linked identities before expanding access further.

Key terms

• AI-driven identity expansion: AI-driven identity expansion is the growth in accounts, tokens, permissions, and delegated access created to support AI-enabled workflows. It matters because each new identity adds governance, monitoring, and revocation obligations, often faster than review cycles can handle. In practice, it is a scaling problem for identity security, not just an adoption trend.
• Non-Human Identity (NHI): A digital identity assigned to a non-human entity such as a software application, service account, API key, bot, machine, or AI agent that enables it to authenticate and interact with systems without direct human involvement. NHIs now outnumber human identities in most enterprises by 25 to 50 times.
• Continuous enforcement: Continuous enforcement means access rules, monitoring, and revocation are applied in near real time rather than during scheduled reviews. For AI and other non-human identities, it is the only model that matches how quickly identities can be created, changed, and abused. It turns security from periodic approval into ongoing control.
• Identity Blast Radius: The amount of damage a compromised identity can cause across systems, data, and infrastructure. In NHI environments, it is shaped by permissions, network reach, and administrative capability rather than by the credential alone. Reducing blast radius is a containment strategy that limits lateral movement and data exposure.

Deepen your knowledge

NHI governance, agentic AI identity, and machine identity lifecycle are core topics in our NHI Foundation Level course, the industry's only accredited NHI security programme. If you are building or maturing an IAM programme, it is worth exploring.