Topic starter
02/08/2026 11:53 am
TL;DR: AI governance in security operations is shifting from ChatGPT-style usage controls to a three-layer model of outcome, judgment, and execution, according to Torq. The central governance problem is deciding where AI can act at machine speed and where human authority must remain non-negotiable, especially as MCP expands inter-system decision chains.
Editorial analysis by NHI Mgmt Group, based on content published by torq: “AI or Die: Where Human Authority Must Ultimately Sit”.
Key questions
Q: How should security teams decide which AI-driven SecOps actions can be automated?
A: Use a three-layer model.
Q: Why do MCP-based AI systems complicate access control and governance?
A: MCP-based systems complicate governance because they connect models to tools and data sources dynamically, often across multiple providers and environments.
Q: What breaks when AI automation is given broad SecOps access?
A: Broad access turns a useful assistant into an opaque operator.
Practitioner guidance
- Define decision boundaries by layer Classify each SecOps workflow as outcome, judgment, or execution, then prohibit machine-only authority in the judgment layer where business context drives the decision.
- Map AI handoffs across tool chains Inventory every AI-to-AI and AI-to-tool delegation path, including MCP-driven integrations, and require explicit approval gates where one action can trigger the next.
- Start with low-criticality workflows Begin AI use in repeatable triage, enrichment, and reversible containment tasks before widening authority into higher-impact decisions.
Bottom line: AI governance in SecOps fails when organisations treat learned judgment like ordinary automation and ignore the need for human context at key decision points.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
02/08/2026 1:02 pm
Outcome, judgment, and execution is the right governance model for SecOps AI: organisations keep failing when they treat AI as a single capability rather than a set of decision layers. Execution can be automated, but judgment remains a human function because business context cannot be reduced to telemetry. The practitioner lesson is to design AI control planes around decision type, not tool category.
A few things that frame the scale:
- Only 44% of organisations have implemented any policies to manage their AI agents, despite 92% agreeing that governing AI agents is critical to enterprise security, according to the 2026 Infrastructure Identity Survey.
- 76% of organisations cite shadow AI as a definite or probable problem, up from 61% in 2025, according to HiddenLayer's 2026 AI Threat Landscape Report.
A question worth separating out:
Q: Who is accountable when an AI agent causes a security incident?
A: Accountability should sit with the business owner, the system owner, and the security function together, because agent behaviour crosses operational boundaries. Organisations need a defined owner for approval, monitoring, and retirement, plus audit evidence that shows what the agent accessed and why.
👉 Read our full editorial: AI governance in SecOps needs human authority at the edge