Identity tools need an operating system to close access blind spots

At a glance

What this is: Oak says the real identity problem is architectural fragmentation, not a lack of tools, because existing stacks cannot produce a complete, live view of who and what can access what.

Why it matters: This matters because IAM, IGA, PAM, and NHI programmes all depend on accurate access truth, and incomplete visibility leaves review, remediation, and least-privilege decisions structurally blind.

Context

Identity governance breaks when each control plane keeps its own model of access and none of them can reconcile the full estate. In that setup, the organisation can govern known human accounts but still miss service accounts, out-of-band entitlements, and AI agents that exist outside the central view.

The article frames an operating system for identity as the missing layer that connects systems, builds one live graph of access, and turns visibility into action. For practitioners, the question is no longer whether individual tools work, but whether the programme can reason over human, machine, and agent identities using the same source of truth.

Key questions

Q: What breaks when identity tools cannot see each other's access data?

A: Access reviews, privilege cleanup, and offboarding all become incomplete because each tool only sees local entitlements. Shadow admins, toxic combinations, and stale access survive when the organisation cannot correlate identity data across systems. The result is not just poor reporting. It is a blind spot in governance that attackers can exploit with legitimate credentials.

Q: Why do fragmented identities make AI access risk harder to govern?

A: Fragmented identities make AI risk harder to govern because assistants and copilots can only be limited as well as the user accounts they inherit. If one person has inconsistent permissions across systems, AI can surface or act on data from the most exposed account. That makes identity normalisation a prerequisite for safe AI adoption.

Q: How do security teams reduce blind spots between assigned access and actual reach?

A: They need runtime evidence, entitlement correlation, and relationship context in one view. That lets them see inherited access, direct application permissions, and unused privileges together, which is the only reliable way to shrink blast radius.

Q: How should organisations govern AI agents alongside human identity and device access?

A: Organisations should treat AI agents as a separate identity class with their own entitlement boundaries, logging expectations, and approval model. Human IAM controls often assume interactive sign-in and review cycles, which do not fit autonomous or programmatic access. The safer approach is to define actor-specific policy and verify which access paths can be delegated without expanding trust unnecessarily.

Technical breakdown

Why fragmented identity stacks lose access truth

An identity stack that spans IGA, PAM, CIEM, ITDR, directories, HR, and application-native entitlements only works if those sources can be normalised into one model. When they cannot, governance becomes partial by design: the IGA sees what it can correlate to a person, while service accounts, contractor access, direct app grants, and unmanaged agents remain outside the record. That is not merely a visibility problem. It means the policy layer is reasoning from incomplete evidence, so certification, least privilege, and remediation all start from a distorted baseline.

Practical implication: treat disconnected control planes as a governance defect, not a reporting issue.

How a live identity graph changes entitlement analysis

A live identity graph combines granted access, used access, and relationship context across human, machine, and AI agent identities. Instead of trusting role labels or static inventories, it infers effective reach from raw evidence such as activity logs, runtime usage, and resource-level entitlements. That matters because the meaningful risk is often the gap between what an identity has and what it actually needs. Once those relationships are visible, teams can identify inherited access, nested privilege, and hidden blast radius in a way periodic review cycles cannot.

Practical implication: build entitlement decisions on observed reach, not on the names of roles or groups.

Why agent identities require first-class governance

Agents are not a side case once they hold credentials and act on production systems. They create governance pressure because they inherit access, can be provisioned through builder credentials, and often lack a clear accountable owner in the catalogue. If the identity model treats them as just another workload or skips them entirely, the programme cannot sustain ownership, review, or closure when access changes. That is especially important where agent activity is frequent, delegated, and harder to map to a human operator after the fact.

Practical implication: register agent identities with ownership and review paths before they start touching production data.

NHI Mgmt Group analysis

Identity governance without a shared operating layer is not governance at all: It is a collection of partial control planes that each tell the truth about a different subset of access. Oak's core point is architectural: if the programme cannot correlate humans, service accounts, agents, and application-native grants into one model, then policy is always downstream of reality. Practitioners should treat that as a structural boundary, not a tooling inconvenience.

The real exposure is the gap between granted access and used access: Static entitlement records routinely overstate or misstate what identities can actually do, especially when privileges are inherited through groups, roles, or builder credentials. A live graph changes the conversation from who is assigned what to what can be reached right now. That is the basis for least privilege that can survive modern sprawl.

Agents make the identity model collapse visible: The moment an AI agent can hold credentials and act repeatedly, the old assumption that every non-human identity has a clear owner and a stable administrative lifecycle stops holding. That assumption was designed for application accounts and conventional workloads, not for actor sets that can multiply quickly and operate across systems. The implication is that identity governance now has to account for autonomous behaviour as a governance class, not just a technical integration problem.

Access review is no longer the primary control when review data is incomplete: Certification works only when the system being reviewed is already visible and stable enough to inspect. Where service accounts, direct app entitlements, and agents sit outside the catalogue, the review becomes a ritual over an incomplete dataset. The practical conclusion is that governance has to move toward evidence collection and entitlement reconciliation before certification can be trusted.

Identity programmes need a control layer that can act, not just report: The market has spent years stacking point tools on top of a fragmented model, then expecting the review process to close the loop manually. That does not scale when AI expands both the number of identities and the rate at which access changes. The next useful architecture is one that can identify root cause, normalise truth, and drive remediation from the same graph.

From our research library:

• 69% of security leaders agree identity management must fundamentally shift to address agentic AI systems, according to the 2026 Infrastructure Identity Survey.
• Read next: Identity Security Programme Guide

What this signals

Identity operating layer: The market is moving toward a model where governance starts with a unified identity graph rather than with another point control. For programmes built around periodic reviews, the practical shift is toward continuous reconciliation of granted access and effective reach across human, machine, and agent identities.

AI agents turn visibility into a lifecycle problem: Once an agent can hold credentials and act continuously, the question is no longer only whether it exists, but who owns it, how it is reviewed, and when its access is retired. That pushes lifecycle governance into the same operational plane as access control.

69% of security leaders agree identity management must fundamentally shift to address agentic AI systems, according to the 2026 Infrastructure Identity Survey. That signals a broad recognition that existing IAM patterns do not scale cleanly into agent-driven estates.

For practitioners

• Map your actual control boundary Inventory which identities each current platform can truly see, then compare that with service accounts, direct application entitlements, and any AI agent accounts that exist outside the central catalogue.
• Reconcile granted access with observed use Use runtime evidence, activity logs, and resource-level entitlements to identify where assigned privileges exceed what identities actually use, especially for inherited or nested access.
• Assign owners to every agent identity Require accountable ownership, lifecycle status, and review responsibility for each agent before it is allowed to hold credentials or reach production systems.
• Reduce blind spots in application-native access Target entitlements granted directly in applications and other out-of-band pathways so they are reconciled into the governance model instead of remaining invisible.

Key takeaways

• Identity governance fails when each platform sees only its own slice of access and cannot reconcile the full estate into one operational model.
• The article's core evidence is architectural rather than anecdotal: hidden service accounts, direct app grants, and AI agents can sit outside review even in well-run environments.
• Practitioners should move from periodic certification alone to a model that correlates runtime evidence, ownership, and lifecycle status before access can be trusted.

Key terms

• Identity Graph: An identity graph is a relationship map that connects identities, assets, data, and permissions so teams can see how access actually flows. In NHI programmes, it helps explain which agent is related to which owner, which system, and which policy boundary.
• Effective reach: The real set of systems, resources, and environments an identity can actually influence, not just the permissions listed on paper. For non-human identities, effective reach often matters more than granted access because unused or cross-environment privilege still expands attack surface and operational risk.
• App-native Entitlement: An app-native entitlement is a role, permission, token, or integration grant created directly inside the application rather than through the central identity plane. These entitlements are often the hardest to govern because they live where work happens, not where identity teams usually look.
• Agent Identity: An agent identity is the set of attributes, credentials and permissions assigned to an autonomous software entity. It is treated as a non-human identity because it can authenticate, act on systems and accumulate access over time, which creates governance, audit and lifecycle obligations similar to other production identities.

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 responsible for identity security strategy or NHI governance in your organisation, it is worth exploring.