Topic starter
10/06/2026 10:55 pm
TL;DR: As AI agents move into production, the governance gap is no longer model output but runtime action: identity per instance, chain-of-custody audit, and external policy enforcement are all missing in most stacks, according to Cerbos. The critical failure is that current controls assume access can be reviewed after the fact, while agents make and execute decisions before review exists.
Editorial analysis by NHI Mgmt Group, based on content published by Cerbos: “Authorization for AI agents: What to build before the EU AI Act deadline”.
Key questions
Q: How should security teams govern AI agents that can take runtime response actions?
A: Treat them as privileged NHI workloads with explicit scope, short-lived authority, and full action logging.
Q: Why do AI agents need their own identity instead of borrowed human credentials?
A: AI agents need their own identity because borrowed human credentials destroy auditability, make revocation imprecise, and expand blast radius.
Q: What breaks when audit logs do not capture agent delegation and decision context?
A: You lose the ability to reconstruct how CUI moved through the workflow and who, or what, initiated each step.
Practitioner guidance
- Map every agent instance to a named sponsor Require a human owner for each agent lifecycle and make existence conditional on that owner’s employment or role status.
- Move authorization outside the agent loop Use a separate policy decision point for every agent-to-tool call so the agent cannot self-authorize access to tools or data.
- Bind audit to the full delegation chain Record the authorizing principal, original purpose, policy decision, and every delegated hop for each runtime action.
Bottom line: AI agent governance fails when organisations rely on model guardrails instead of runtime authorization at the tool boundary.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
This topic was modified 7 days ago by NHI Mgmt Group
12/06/2026 4:39 am
Runtime policy is the missing governance plane for AI agents: frameworks already describe what models may say, but they do not reliably govern what agents do at execution time. That gap becomes visible only when an agent can choose a tool, pass arguments, and execute without a separate authorization decision. The implication is that agent governance must move from content control to action control.
A few things that frame the scale:
- Only 44% of organisations have implemented any policies to manage their AI agents, despite 92% agreeing that governing AI agents is critical to enterprise security, according to the 2026 Infrastructure Identity Survey.
A question worth separating out:
Q: How do organisations know if AI agent governance is actually working?
A: Look for three signals: every production agent has a named owner, access decisions are enforced during runtime, and audit trails show when requests were allowed, denied, or escalated. If teams can only describe agent behaviour in hindsight, governance is still incomplete.
👉 Read our full editorial: Runtime policy for AI agents: the governance gap teams are missing
This post was modified 7 days ago by NHI Mgmt Group