Topic starter
19/08/2026 4:08 pm
TL;DR: AI agent risk registers break when they are built around behaviour, because prompt changes, new MCP connections, and model upgrades make yesterday’s likelihood and impact ratings obsolete, according to ARMO. The durable unit is the agent surface, not the specific action, and runtime telemetry is now a prerequisite for usable governance.
Editorial analysis by NHI Mgmt Group, based on content published by ARMO: “AI Agents in the Cloud: A Risk Management Framework for Security Leaders”.
Key questions
Q: What breaks when AI agent risk registers are built around behaviour rows?
A: Behaviour rows break because the agent’s prompt, tool set, and model can change faster than the register can be rewritten.
Q: Why do AI agent risk scores become unreliable after tool or model changes?
A: They become unreliable because the score was often tied to a behaviour that no longer exists in the same form.
Q: How do security teams know if AI governance is working?
A: Look for evidence that access decisions are reviewable, permissions are revocable, and exceptions are not becoming permanent.
Practitioner guidance
- Map each AI agent to four stable surfaces Record Identity, Data, Tool, and Model columns for every production agent so changes can be updated by surface instead of rewriting behavioural entries.
- Build the register from runtime discovery Use observed processes, model endpoints, connections, and API patterns as the starting inventory rather than relying on declared CMDB entries.
- Replace subjective risk ratings with observable inputs Score likelihood using exposure, autonomy, and instrumentation gap, then score impact using identity blast radius, data sensitivity, tool capability, and model reach.
Bottom line: Behaviour-based risk registers age too quickly for AI agents because prompt, tool, and model changes can invalidate the original entry.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
19/08/2026 4:41 pm
Stable agent surfaces are the only durable unit of AI risk governance. Behaviour changes too quickly for a register row keyed to a single action to remain useful. When prompts, tools, and model versions shift independently, Identity, Data, Tool, and Model become the only surfaces that stay governable across the change cycle. The implication is that risk governance must stop pretending behaviour is the control boundary.
A few things that frame the scale:
- 70% of organisations grant AI systems more access than they would give a human employee performing the exact same job, according to the 2026 Infrastructure Identity Survey.
- 19% of organisations give AI systems dramatically more access than human employees, nearly one in five granting unrestricted privilege, according to the 2026 Infrastructure Identity Survey.
A question worth separating out:
Q: What is the difference between a CMDB entry and an AI agent risk register?
A: A CMDB entry describes what was declared, while an AI agent risk register should describe what is running and what surfaces it can reach. For AI agents, runtime scope matters more than static inventory because behaviour and connectivity change after deployment.
👉 Read our full editorial: AI agent risk registers need four stable surfaces, not behaviour rows