Identity is the missing layer in the CIA triad for modern security

At a glance

What this is: NHI Mgmt Group's analysis, drawing on C1.ai's blog post: The CIA triad was built for a world with clear perimeters and known users, and modern cloud and AI environments make identity the missing control layer.

Why it matters: It matters because IAM, PAM, NHI and AI governance programmes now carry the responsibility for decisions the classic CIA model assumed were already settled upstream.

👉 Read C1.ai's analysis of why identity is the missing layer in modern security

Context

The CIA triad still describes core security outcomes, but it does not describe who or what is making access decisions in modern environments. Once applications, data and execution move across SaaS, cloud, APIs and AI agents, the old assumption that identity is already known stops holding.

That creates a governance gap for IAM teams. Confidentiality, integrity and availability remain relevant, but they now depend on actor identity, authorisation scope and lifecycle control across humans, workloads and autonomous systems.

C1.ai's argument is that the security model is now missing a layer above data protection. The question is no longer only whether information is protected, but whether the actor touching it exists, can be verified and should still be allowed to act.

Key questions

Q: What breaks when identity is treated as a secondary control beneath the CIA triad?

A: What breaks is the sequencing of trust. Teams may encrypt data, protect integrity, and maintain uptime while still allowing compromised credentials or over-privileged non-human identities to reach sensitive systems. The result is strong data protection on paper but weak governance over who can actually act on that data.

Q: Why do SaaS-heavy environments make identity governance harder than older perimeter-based models?

A: SaaS-heavy environments increase the number of access paths, endpoints, and collaborators that security teams must govern. The old perimeter no longer tells you what a user is actually doing inside applications. That makes continuous visibility, policy enforcement, and lifecycle control essential, especially where access is shared across teams and devices.

Q: How should security teams govern identity as a control plane?

A: Security teams should treat identity as the layer that decides who can act, how far authority travels, and what context makes an action legitimate. That means combining IAM, PAM, and NHI lifecycle controls with continuous evaluation, machine-readable policy, and delegation tracking. If identity is only provisioned and not governed, the rest of the stack is protecting decisions that were never validated.

Q: Should organisations add identity as a fourth pillar or redesign the security model entirely?

A: Adding identity as a fourth pillar is a useful step, but it does not fully solve the architectural problem if actor governance and data protection remain separated. Organisations should use it to force a redesign of access governance, lifecycle management and runtime authorisation, not just rename the framework.

Technical breakdown

Why the CIA triad assumes identity has already been solved

The CIA triad was designed around systems with clear network boundaries, known users and predictable access paths. Confidentiality, integrity and availability all depend on a prior decision about who is authorised, but the model never names that decision as a control layer. In practice, that worked when a human sat at a terminal behind a perimeter. In cloud, SaaS and machine-to-machine architectures, the requestor may be a service, workload or agent whose identity and context change continuously.

Practical implication: IAM teams should stop treating identity as a supporting input to CIA and treat it as a distinct governance layer.

How APIs and workloads shifted security from network trust to identity trust

Modern systems increasingly authenticate services to services rather than people to servers. That changes the security problem from defending an addressable boundary to validating a cryptographic identity and its authorisation for each request. Standards such as SPIFFE and OAuth reflect that shift because workloads now need verifiable identities, not just network placement. The operational consequence is that access control, token scope and runtime context matter more than where the traffic originated.

Practical implication: architecture reviews should focus on workload identity, token scope and per-request authorisation rather than perimeter location.

Why AI agents break the assumptions behind human-era security models

AI agents introduce actor types that can authenticate, delegate and act at machine speed without a human sitting in the loop for each decision. That breaks the old assumption that access can be reviewed after the fact using human-paced governance cycles. Once agents spawn sub-agents and inherit permissions, identity becomes a lifecycle problem, not a one-time login problem. The actor is dynamic, and the governance model must account for creation, delegation and removal, not just authentication.

Practical implication: identity governance for AI agents must include issuance, delegation and offboarding controls that are separate from human IAM processes.

Threat narrative

Attacker objective: The objective is to reach protected systems or data by exploiting identity assumptions that the CIA triad does not explicitly govern.

1. Entry occurs through a trusted credential, token or delegated identity rather than a perimeter breach, because the article's core point is that modern environments expose identity as the front door.
2. Escalation follows when the actor's privileges are accepted as valid even though the underlying identity was not governed as a first-class control layer.
3. Impact occurs when confidentiality, integrity and availability protections are bypassed through legitimate access paths, proving that the identity layer determines whether the other controls matter.

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

Identity is not a subcomponent of the CIA triad. It is a separate layer of governance above the properties the triad was built to protect. Confidentiality, integrity and availability describe what must be true about data, but identity determines who is allowed to affect that data in the first place. That difference matters because the modern attack surface is increasingly actor-driven rather than perimeter-driven. The practitioner conclusion is that actor governance now deserves its own architectural treatment, not just a supporting control.

The CIA triad fails as a complete security model because it assumes the actor has already been verified. That assumption held in terminal-and-perimeter environments, but it collapses when access is distributed across SaaS, APIs, workloads and agents. The result is not just more identity risk, but a structural blind spot in how security programmes are scoped. Practitioners should read this as a governance boundary problem, not merely an implementation gap.

Adding identity as a fourth pillar is directionally correct, but it still understates the change in security architecture. Identity is not another property of information. It is a property of actors, and actors have lifecycles, delegation chains and authorisation context. That means IAM, PAM and NHI governance are no longer adjacent to security architecture; they are part of the control plane. The practitioner conclusion is that security governance has to span both data and actor layers.

AI agents make the missing-layer problem impossible to ignore because they turn identity from a login event into a runtime decision system. When agents authenticate hundreds of times per minute and spawn sub-agents, the old assumption that access persists long enough to be reviewed no longer holds. This is where NHI governance and agentic oversight converge. The practitioner conclusion is that lifecycle and authorisation controls must be designed for actors that create, inherit and shed privileges dynamically.

Identity blast radius is now the more useful way to think about breach exposure than traditional perimeter strength. Once credentials, tokens and delegated access define the path into systems, the question becomes how far a compromised actor can move before governance catches up. That shifts prioritisation toward lifecycle control, token scope and privilege boundaries. The practitioner conclusion is to measure security by actor reach, not just by data protection posture.

What this signals

Actor governance is becoming the missing operating layer in security programmes. Once access decisions are made by humans, services and agents across different runtime contexts, the old perimeter-based mental model stops being useful. IAM leads should expect more pressure to unify identity, privilege and lifecycle governance across every actor type rather than manage them as separate workstreams.

Identity now defines security blast radius. If a compromised actor can move through SaaS, APIs and cloud workloads before the organisation detects it, then the real question is how far that actor can travel with valid authority. That pushes programme design toward token scope, delegation boundaries and rapid offboarding rather than perimeter assumptions.

The CIA triad still matters, but it no longer explains where control actually lives. Security teams should prepare for a governance shift in which actor identity, not network location, becomes the primary trust variable for access, auditability and accountability.

For practitioners

• Map identity as a separate control layer Document where your security architecture currently assumes identity is solved upstream, then mark every place where confidentiality, integrity or availability decisions depend on actor verification.
• Rebuild controls around actor lifecycles Define how human users, service accounts and AI agents are created, authorised, reviewed and removed, with explicit ownership for each lifecycle path.
• Review workload and API trust paths Inventory the services, APIs and workloads that authenticate to each other and confirm that tokens, scopes and renewal rules match actual runtime behaviour.
• Treat AI agents as governed identities Require delegated authority, approval boundaries and offboarding criteria for any agent that can take actions without human intervention.
• Reassess PAM and recertification timing Check whether privileged access reviews happen often enough to matter in cloud and agentic environments where access can be created and consumed quickly.

Key takeaways

• The article argues that the CIA triad was built for environments where identity was already settled, which is no longer true in cloud, SaaS and AI-driven estates.
• Its core evidence is that modern access decisions increasingly hinge on actor identity, delegation and lifecycle, not just on protecting data properties.
• For practitioners, the implication is to treat identity as a separate governance layer and redesign access controls around the actor, not the perimeter.

Key terms

• Actor governance: The discipline of governing who or what can act on systems, data, and services, including how that authority is issued, verified, limited, and removed. It is broader than authentication because it covers lifecycle, delegation, and the scope of action for both human and non-human identities.
• Identity layer: An identity layer is the shared policy and trust model that sits across applications and data sources. It connects authentication, claims, access rules, and revocation into one control plane so organisations can enforce consistent decisions across fragmented environments.
• Delegated Authority Model: A delegated authority model defines who is allowed to approve, review, or execute control-related decisions across the enterprise. It helps ensure requests reach the correct responsible party, especially when control owners, managers, and process owners sit in different teams, regions, or systems.
• 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.

What's in the full article

C1.ai's full blog covers the argument this post intentionally leaves at the architecture level:

• The historical progression from Bell-LaPadula and Biba to the CIA triad, including why that lineage matters for modern governance
• The article's five-step account of how cloud, SaaS, APIs, remote work and AI agents eroded perimeter-based security assumptions
• The breach examples used to support the identity-first argument, including Midnight Blizzard, Change Healthcare, Snowflake, Okta and PowerSchool
• The author's case for treating identity as a separate layer rather than only a fourth pillar inside the existing model

👉 C1.ai's full blog expands the argument with breach examples and the case for identity as a separate layer.

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.