Topic starter
14/08/2026 6:34 pm
TL;DR: Enterprise AI risk has shifted from data leakage in chat to uncontrolled agent actions, including exfiltration, destructive changes, and policy bypass, because most security stacks still lack session-level visibility into what agents actually do, according to Island. That makes runtime governance, not prompt review, the decisive control boundary.
Editorial analysis by NHI Mgmt Group, based on content published by Island: “AI Protect: Governing What Agents Do, Not Just What They're Told”.
Key questions
Q: What breaks when AI governance only monitors prompts and outputs?
A: Prompt and output monitoring misses the moment where the real risk occurs, which is execution.
Q: Why do session-level controls matter for AI agent risk?
A: Because one isolated event rarely shows the full behaviour.
Q: What signals show that an AI agent is operating outside its intended purpose?
A: Look for mismatches across identity, data, model behaviour, posture, and environment.
Practitioner guidance
- Govern the action layer Define policy around specific agent actions such as file transfer, command execution, and database modification rather than around prompts or outputs alone.
- Reconstruct the full agent session Correlate browser, endpoint, network, and API events into one session record so that tool use, resource access, and responses are analysed together.
- Differentiate agent identity from user identity Track which identity the agent acted under, which user requested the task, and where delegated access expanded the effective blast radius.
Bottom line: AI agents change the security problem from content moderation to action governance because the harmful event happens when the tool call executes.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
14/08/2026 6:41 pm
Action-level control is now the governing unit for AI agents. The article shows that prompt review is too early and output review is too late when an agent can call tools, move files, and execute commands mid-session. That makes the action itself the control boundary, because the material security decision happens at the point of execution. Practitioners should treat agent actions as governed events, not passive outputs.
A few things that frame the scale:
- Only 5.7% of organisations have full visibility into their service accounts, according to the Ultimate Guide to NHIs.
A question worth separating out:
Q: How should security teams respond when an AI agent attempts a risky action?
A: They should interrupt the action before it becomes permanent, explain the denial in terms the agent can use, and log the event for review. If the workflow can continue safely, the agent should be redirected into a permitted path rather than simply shut down.
👉 Read our full editorial: AI agent governance now depends on action-level control