Human in the Loop
Also called HITL.
A design where a person reviews or approves an automated decision before it takes effect.
What it is
A control that places a human approval step between an automated recommendation and its action. In security automation it usually sits in front of anything disruptive or irreversible: isolating a server, disabling an account, deleting data or sending a message outside the company.
Why it matters
It lets teams automate the fast, repetitive parts of response while keeping judgment on the parts that can hurt the business. It is also the backstop when an AI component is wrong or manipulated.
In practice
A playbook enriches a phishing alert, finds every copy of the message, and prepares the purge. An analyst reviews the list and clicks approve before anything is deleted.
What to look for
- Approval records attached to disruptive automated actions.
- Approval steps that are always clicked through within seconds.
- Automations that skip review on certain alert sources.
Common mistake
Adding approvals to everything. Reviewers start rubber-stamping; reserve the step for actions where a mistake is costly.
In the field
Well-known tools where this shows up on the job. They are listed to show the landscape, not as a recommendation.
-
Splunk SOAR Commercial
Runs playbooks that enrich alerts and take response actions across tools.
-
Cortex XSOAR Commercial
Palo Alto Networks' SOAR platform with case management and playbooks.
-
Tines Commercial
Builds automated workflows that connect security tools without heavy code.
Read next
- SOAR: Automating and orchestrating response steps across security tools.
- Playbook: A documented, repeatable procedure for handling a scenario.
- Automated Response: Containment and cleanup actions that run on their own when a detection meets set conditions.
- Guardrails: Checks around a model that filter what goes in, what comes out, and what it is allowed to do.