Notifications
Clear all
Topic starter
27/08/2026 2:11 pm
TL;DR: Security operations need controlled autonomy, not brittle SOAR scripts or unchecked AI agents, according to Mate. The central lesson is that agentic systems must reason and pivot inside governed boundaries, because access review cadences assume decisions persist long enough to be manually validated.
NHIMG editorial — based on content published by Mate: the role of Gamebooks in AI agent security operations
Questions worth separating out
Q: What breaks when AI agents are trusted to police their own boundaries?
A: The containment model breaks because the agent cannot be relied on to know whether the environment is truly isolated.
Q: Why do controlled AI agents matter in security operations?
A: Controlled AI agents matter because security work needs both machine speed and policy discipline.
Q: How do organisations keep AI security workflows auditable?
A: Log who initiated the action, what data the model used, what output it produced, and whether any downstream action was taken.
Practitioner guidance
- Define investigation intent before tool choice Write down the evidence required, escalation thresholds, and stop conditions before mapping any agent to product-specific APIs or workflow steps.
- Separate capability design from execution permissions Treat capabilities as reusable security tasks and constrain the underlying flows with typed inputs, typed outputs, and least-privilege access to systems.
- Preserve decision rationale in structured context Store why a decision was made, what conditions supported it, and how confidence should be interpreted so later agent actions inherit governed context.
What's in the full article
Mate's full article covers the operational detail this post intentionally leaves for the source:
- How Gamebooks are structured as versioned investigation procedures across real systems and data sources.
- How the Security Context Graph preserves analyst reasoning, confidence, and investigation history over time.
- How Flows enforce typed inputs, permissions, and rate limits while agents continue to pivot dynamically.
- How teams can translate existing SOAR playbooks into reusable investigative intent without rewriting the whole stack.
👉 Read Mate's analysis of controlled autonomy for AI security agents →
AI agents in security ops: how do you keep autonomy bounded?
Explore further
27/08/2026 2:12 pm
Controlled autonomy is the right design goal for security agents, not full scriptability or unconstrained agency. Mate’s core argument is that security operations need AI agents that can reason and pivot, but only inside defined investigation boundaries. That is the same governance problem now emerging across NHI and agentic AI programmes: if the system can act, then authority has to be bounded by intent, scope, and escalation rules. The practitioner conclusion is that agentic security controls should be designed around constrained decision space, not blind automation.
A few things that frame the scale:
- Only 1.5 out of 10 organisations are highly confident in their ability to secure NHIs, compared to nearly 1 in 4 for securing human identities, according to The State of Non-Human Identity Security.
- Lack of credential rotation is cited as the top cause of NHI-related attacks by 45% of organisations, according to The State of Non-Human Identity Security.
A question worth separating out:
Q: Should organisations let AI agents take containment actions automatically?
A: Only with tightly bounded use cases and strong preconditions. Containment actions can have business impact, so the safer model is human approval for high-risk steps, machine assistance for evidence gathering, and clear rollback procedures if the agent misclassifies a case or lacks context.
👉 Read our full editorial: Controlled autonomy for AI agents in security operations
