Topic starter
06/07/2026 9:46 am
TL;DR: AI agents can book meetings, triage incidents, ship code, and approve purchases by chaining tool calls across apps, making the application itself the attack surface, according to Andromeda Security. The decisive gap is that governance must evaluate the human, agent, and action together in real time, because legacy role assignments and reactive controls cannot keep pace with agent execution.
Editorial analysis by NHI Mgmt Group, based on content published by Andromeda Security: “AI Agent Security: The Application Perimeter”.
Key questions
Q: What breaks when AI agents are not governed at runtime?
A: Without runtime governance, an agent can shift behaviour after provisioning and still execute actions that were never reviewed in context.
Q: Why do AI agents increase identity risk even when the login succeeds?
A: A successful login only proves that the agent reached the system.
Q: What are the signs that agentic access controls are failing?
A: The main signs are invisible tool use, delayed discovery of actions, and audit logs that explain an outcome only after it has already occurred.
Practitioner guidance
- Define the application perimeter Map each critical application to the specific tool surfaces an agent can invoke, then classify which tool combinations create unacceptable data or action exposure.
- Evaluate the full access triad Require every agentic access decision to include the human sponsor, the acting agent, and the intended action before the tool call is allowed.
- Replace static role logic with composable policy Use reusable policy rules that can express conditional approval, perpetual allowance, or denial for a tool call based on context and risk.
Bottom line: AI agents turn applications into governed tool surfaces, so the control boundary shifts from static identity records to live execution decisions.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
06/07/2026 10:03 am
Agentic governance fails when the application is treated as downstream of identity. The article correctly reframes the problem: in agentic systems, the application surface is where identity becomes operational. That means governance cannot stop at granting the agent access, because the real risk emerges when tool chaining turns one allowed action into many reachable actions. Practitioners should treat governed applications, not the agent alone, as the boundary that matters.
A few things that frame the scale:
- Gartner predicts that more than 50% of successful cyberattacks against AI agents through 2029 will exploit access control weaknesses.
A question worth separating out:
Q: Who should own policy governance for human, NHI, and agent access decisions?
A: Identity governance teams should own the policy model, with security architecture and application teams supporting enforcement and telemetry. The key is one consistent governance framework that covers human users, service identities, and AI agents without splitting rules across separate control planes.
👉 Read our full editorial: AI agent security needs an application perimeter, not just controls