Chapters0/54 ▾
- 1.Architecture & Log Sources0/5
- 2.Indicators of Malicious Activity0/5
- 3.Investigation Tools & Threat Hunting0/5
- 4.Process Improvement, Automation & AI0/5
- 5.Vulnerability Scanning Methods0/5
- 6.Analyzing Scan Output0/5
- 7.Prioritization, Mitigation & Controls0/5
- 8.Attack Frameworks & the Response Process0/5
- 9.Incident Response Techniques0/5
- 10.Vulnerability Reporting & Communication0/5
- 11.Incident Reporting & Metrics0/4
Chapter 4 · Lesson 1 of 5
Choosing what to automate in the SOC
1 min read
The exam sorts tasks into two groups. Steps that change nothing, such as looking up an address's reputation, finding the asset owner and criticality, pulling recent sign-in history, opening the case and collecting a copy of a message, are deterministic and safe to automate.
Steps that need judgment or can cause harm, such as setting a final disposition, raising severity, revoking sessions or isolating a host, should keep a human decision unless they run inside a scope that was approved in advance.
- Confidence branches: above the documented threshold a workflow may run a pre-approved action; below it, the workflow enriches the case and sends it to an analyst. It never closes a low-confidence case on its own.
- Blast radius: some actions are harmful even on a true positive. Isolating a virtualization host takes many services down, so critical assets are excluded from automatic containment and page an on-call analyst instead.
Example: a phishing workflow uses 75 as its documented high-confidence line, and a report scores 52. The workflow should attach the header analysis, URL verdicts and attachment results and queue the case for a person, not delete the message from every mailbox and not close the case.
A higher threshold or a staffed-hours schedule does not fix a damaging action; scoping it does.
Check yourself
1. Every alert in a team's queue requires the same three lookups before analysis begins: the source address reputation, the asset owner and business criticality, and the user's recent sign-in history. All three use data the team already holds. Which step is the strongest candidate for automation?
2. An orchestration workflow scores every reported phishing message, and the team's documented rule is that a score of 80 or above is high confidence and anything below 80 is low confidence. A reported message scores 41. What should the workflow do with it?
Facts checked 2026-11-15 · Sources: CompTIA CySA+ (CS0-004) certification page and exam objectives, NIST AI Risk Management Framework (AI RMF 1.0, NIST AI 100-1)
CompTIA CySA+ cheat sheet: every key fact on one page →