TL;DR: Security orchestration is shifting from task automation to governed delegation, with recovery time, KRIs and human approval gates defining where AI can help, according to Safe Security. Orchestration now has to stop automation where consequence and accountability begin.
Editorial analysis by NHI Mgmt Group, based on content published by Safe Security: “Gartner UK from the Practitioner’s Seat: Everyone Wants to Be an Orchestrator. Now What?”.
Key questions
Q: Why do recovery targets need to be tied to business value rather than workshop estimates?
A: Because recovery time is really a loss-tolerance question.
Q: What breaks when automation expands without clear risk indicators?
A: Automation starts moving faster than governance can evaluate it.
Q: How do security teams know a workflow is ready for automation?
A: A workflow is ready when the team can define it clearly, measure its current performance, analyse its failure points, and show that exceptions are rare and understood.
Practitioner guidance
- Define automation boundaries by consequence Classify security workflows by business impact, then allow AI or agents only where failure is low-risk and reversible.
- Keep human approval on consequential actions Require human review for privilege changes, recovery decisions and any workflow that can alter business exposure.
- Model recovery targets against business loss Tie RTO and related resilience decisions to value chains, downtime tolerance and financial exposure instead of workshop estimates.
Bottom line: Security orchestration is shifting from task automation to governed delegation, which makes consequence and accountability the key design variables.
Glossary terms: Security orchestration, Recovery Time Objective, Key Risk Indicator, Human-in-the-Loop (HITL)
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
Orchestration is becoming the control plane for delegated security work. The article's real signal is that security teams are no longer just automating repetitive tasks, they are deciding which decisions can safely be delegated to AI, agents and APIs. That makes orchestration an identity and privilege problem as much as an operations problem, because every delegated action still depends on scoped authority and accountable execution. The practitioner conclusion is simple: treat orchestration as a governed delegation model, not a convenience layer.
A question worth separating out:
Q: Who should own the decisions that sit between automation and governance?
A: The most effective programs assign that role to an orchestrator function that can translate policy into operating boundaries. That owner should understand security operations, business impact and exception handling, because the job is not to automate everything. It is to decide what can be delegated and what must remain under accountable human control.
👉 Read our full editorial: Orchestration in security programs is shifting from tasks to decisions