Topic starter
06/09/2026 3:45 pm
TL;DR: AI agents turn model interaction into system action, so identity, permissions, tool access, and auditability become the centre of AI-SPM, according to LEVO. The practical shift is from static permission thinking to runtime control over tool chains, approvals, and evidence, because traditional workflow assumptions do not fully contain agent behaviour.
Editorial analysis by NHI Mgmt Group, based on content published by LEVO: “Agent Posture Management: The Missing Layer in AISPM and AI-SPM Programs”.
Key questions
Q: How should teams govern AI agent tool calls in real time?
A: Teams should govern AI agent tool calls with a runtime authorization layer that evaluates the principal, action, resource, and context on every request.
Q: Why do static permission models break down for AI agents?
A: Static permissions assume the risky part of access is known in advance, but agents can choose tools and sequence actions at runtime.
Q: What are the signs that agent posture controls are failing?
A: Look for unusual write volume, spikes in tool calls, repeated failures, and actions that occur without a clear approval trail.
Practitioner guidance
- Define separate identities for users, agents, and tools Make the actor chain explicit so every agent action can be traced back to the requesting user, the executing agent, and the target tool.
- Build a tool permission matrix Classify tools into read-only, low-impact write, and high-impact write tiers, then bind approvals and step-up checks to the highest-risk actions.
- Default agents to read-only access Treat write operations as exceptions that require explicit allowlisting and task-specific scope.
Bottom line: Agent posture management treats AI agents as governed identities whose tool use, permissions, and approvals must be controlled at runtime.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
06/09/2026 3:45 pm
Agent posture management is a control model for delegated action, not a model security add-on. Once an AI agent can retrieve data and write to systems, the security boundary shifts from prompt safety to action governance. That means the relevant question is not whether the model is well-behaved, but whether the agent can be trusted to act inside a bounded identity and permission envelope. Practitioners should treat agent posture as part of identity architecture, not a bolt-on AI control.
A few things that frame the scale:
- Systems with least-privileged AI access had a 17% incident rate vs 76% for over-privileged systems. Organisations failing to scope AI access properly are 4.5x more likely to experience a security incident, according to the 2026 Infrastructure Identity Survey.
- 97% of NHIs carry excessive privileges, increasing unauthorised access and broadening the attack surface, according to the Ultimate Guide to NHIs.
A question worth separating out:
Q: What should organisations do when an agent can make irreversible changes?
A: Require pre-authorization before the agent runs, not after the action is complete. Post-event monitoring can explain what happened, but it cannot prevent damage to code, data, or systems once the action has already executed. For irreversible work, the governance control has to happen before execution, with a clear owner attached to the decision.
👉 Read our full editorial: Agent posture management reframes AI security around identity and actions