Topic starter
06/11/2026 6:39 pm
TL;DR: The market now needs runtime enforcement for enterprise AI agents, not just discovery or permissions, because control must be evaluated at execution time against organizational intent, according to Aizome’s analysis of SACR’s ARISE research. That assumption collapses the moment agents can act inside live workflows without human-paced review.
Editorial analysis by NHI Mgmt Group, based on content published by Aizome: “The Six ARISE Capabilities the SACR Report Points To - And How to Evaluate Whether a Vendor Has Them”.
Key questions
Q: How should security teams discover AI agents that were never formally deployed?
A: Use identity and telemetry correlation to look for agents that authenticate, retrieve secrets, assume roles, or call APIs without a matching onboarding record.
Q: When does runtime enforcement matter more than static permissions for AI agents?
A: Runtime enforcement matters whenever an agent can make contextual tool calls or change behavior after provisioning.
Q: Why do multi-agent workflows increase access control risk in production systems?
A: Multi-agent workflows increase risk because one request can fan out into many actions across tools, systems, and sub-agents before a human reviews the outcome.
Practitioner guidance
- Define machine-readable intent baselines Specify authorised systems, data types, and action scope in structured policy so runtime enforcement can evaluate behaviour without model interpretation.
- Place enforcement in the execution path Use controls that can allow, block, redact, pause, or narrow an agent action before completion, not just after logging.
- Track delegation across agent chains Preserve the originating authorization context across supervisor, worker, and sub-agent hops so scope cannot expand silently.
Bottom line: The core problem is not agent discovery but whether a control can evaluate and constrain an agent action while it is happening.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
06/11/2026 6:42 pm
ARISE is really a runtime governance pattern, not a category label. SACR’s framing matters because it separates discovery, intent capture, and inline enforcement into different architectural layers. That separation is the only way to evaluate whether an AI agent is doing what it was authorised to do at the moment it acts, not after the fact. Buyers that treat the label as the product category will misread inventory as control; practitioners should evaluate the enforcement path, not the taxonomy.
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.
- 69% of security leaders agree identity management must fundamentally shift to address agentic AI systems, according to the 2026 Infrastructure Identity Survey.
A question worth separating out:
Q: What should an AI agent audit trail include?
A: An audit trail should include who initiated the session, which agent executed it, what the agent was authorised to do, the exact tool calls made, the results returned, and whether a human approved the action. It should also preserve the delegation chain and time-bounded session context so the record is useful for incident response and compliance review.
👉 Read our full editorial: ARISE shifts AI agent governance from visibility to runtime enforcement