TL;DR: Autonomous AI agents compress human response time, making alerting alone too slow to stop harmful steps, according to Codenotary. Runtime governance has to decide at execution time, or agents can move data and invoke APIs before review catches up.
Editorial analysis by NHI Mgmt Group, based on content published by Codenotary: “AI Agents Need Runtime Security, Not Just Detection”.
Key questions
Q: Why do detection-only controls fail against autonomous AI agents?
A: Because autonomous agents can complete harmful steps before a human ever sees the alert.
Q: What are the signs that an AI agent access model is becoming too permissive?
A: Warning signs include agents routinely reaching data outside their intended task, repeated approval exceptions, broad retrieval paths across unrelated systems, and outputs that expose information the user did not explicitly need.
Q: How should security teams govern agentic AI as it moves into production?
A: Security teams should govern agentic AI as a class of non-human identity, not as a generic application feature.
Practitioner guidance
- Define runtime authorisation for agent actions Require each high-risk agent action to be evaluated against identity, permission scope, destination and data sensitivity before execution continues.
- Instrument execution graphs for multi-agent workflows Record task delegation, tool invocation, data handoff and downstream agent triggers so you can see how one compromise can spread.
- Scope permissions to the task, not the agent Remove standing write access where possible and grant only the smallest permission set needed for the current action or session.
Bottom line: Autonomous AI agents compress the time available for human response, which makes alerting alone an inadequate control model.
Glossary terms: Runtime Security, Agentic workflow, Proportional Intervention, Execution Graph
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
Runtime governance is becoming the security control plane for autonomous agents. The article describes a world where decisions happen faster than SOC workflows can absorb them, which means post-event detection no longer protects the business. That shifts the governing question from whether an alert fired to whether the action should have been allowed in the first place. For identity teams, that is the same structural change seen when standing privilege gives way to task-scoped authority.
A few things that frame the scale:
- 53% of security leaders expect AI to run major portions of their infrastructure autonomously within the next three years, 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: Should teams use selective containment or full shutdown when an agent is suspicious?
A: Selective containment is usually the better first move when the evidence points to one action, one destination or one agent. Revoking a single permission, isolating one workflow or pausing for human approval reduces blast radius while preserving legitimate work.
👉 Read our full editorial: Runtime security is overtaking detection for autonomous AI agents