Who should be accountable for cloud identity governance when both developers and non-human identities need access?

Why This Matters for Security Teams

Cloud identity governance becomes difficult when developers need rapid delivery and non-human identities need machine-speed access to APIs, infrastructure, and data stores. The governance problem is not just who approves access, but who owns the policy boundary, who reviews exceptions, and who can revoke risky access without blocking the platform. Current guidance from the OWASP Non-Human Identity Top 10 and NHIMG research shows that over-privilege, weak lifecycle control, and hidden service accounts are recurring failure points, not edge cases.

For most organisations, the real risk is that human workflows and machine workflows are managed by the same process even though they age differently, fail differently, and require different audit evidence. Identity governance for developers can tolerate some delay and review; governance for NHIs often cannot, because the workload may be ephemeral, automated, and distributed across multiple systems. That is why joint ownership usually works better than a single team holding the whole burden. The Ultimate Guide to NHIs notes that NHIs outnumber human identities by 25x to 50x in modern enterprises, which changes the operating model materially.

In practice, many security teams encounter access sprawl only after a service account, pipeline token, or cloud role has already been used outside its intended boundary.

How It Works in Practice

The most workable model is shared governance with separated duties. Security usually defines policy, risk thresholds, and audit requirements. IAM or identity engineering implements lifecycle controls. Platform and infrastructure teams manage the delivery path so developers and workloads can obtain access quickly. Developers should not be asked to design the control model, but they do need usable request and approval flows that do not push them toward shadow credentials or long-lived tokens.

For NHIs, the governing principle is workload identity first, not shared secrets first. That means using cryptographic identity for the workload, then issuing access through short-lived credentials, scoped tokens, or federated trust where possible. The operational goal is to make access time-bound, task-bound, and revocable. NIST guidance in NIST Cybersecurity Framework 2.0 supports this kind of accountable governance by separating governance, protection, and recovery responsibilities, while NIST SP 800-53 Rev. 5 Security and Privacy Controls provides control language for access enforcement, logging, and review.

• Define a single policy owner for approval rules and exception criteria.
• Assign platform or IAM teams to implement delivery, rotation, and revocation.
• Require developers to request access through automation rather than shared manual handoffs.
• Use separate review cycles for human roles and non-human workloads.
• Track who approved, who implemented, and who can revoke every entitlement.

NHIMG’s Ultimate Guide to NHIs — Lifecycle Processes for Managing NHIs and the Top 10 NHI Issues both point to the same operational lesson: without clear lifecycle ownership, access review becomes a paper exercise and revocation lags behind reality. These controls tend to break down when access is embedded inside CI/CD pipelines with no central inventory and no reliable service-account ownership records.

Common Variations and Edge Cases

Tighter governance often increases delivery friction, so organisations must balance speed against accountability rather than pretending both happen automatically. There is no universal standard for who owns every cloud identity decision, but current guidance suggests a federated model works best: security sets the rules, IAM operationalises them, and platform teams embed them into workflows.

The main edge case is autonomous or semi-autonomous tooling. If an agent, build system, or automation pipeline can request access on its own, then approval cannot rely solely on static RBAC. In those environments, policy needs to be context-aware, with runtime checks, short-lived credentials, and explicit scope limits. This is where current NHI practice and agentic governance overlap. If the team also supports AI agents, the boundary should be even tighter, because the agent may chain tools, expand reach, or repeat requests faster than a human reviewer can detect. NHIMG’s Regulatory and Audit Perspectives section is useful here, especially where evidence of approval, usage, and revocation must be retained.

The practical answer is not to centralise every decision in security, but to make accountability explicit enough that no team can claim ownership only when access works and deny it when access fails.

Related resources from NHI Mgmt Group

• How should organisations secure privileged access, non-human identities, and secrets before an identity security conference or major programme rollout?
• How should security teams run access reviews for non-human identities?
• How should security teams govern non-human identities that have persistent access?
• How should security teams govern non-human identities in cloud environments?