Automation, Incident Response & Investigations
Security+ SY0-701 · Security Operations
Automation and orchestration in security operations
Security teams face more alerts than humans can handle, and automation is how they keep up. Automation is the use of technology to perform repetitive security tasks without human involvement: automatically blocking a known malicious IP address, quarantining a suspicious file, or opening a ticket when an alert fires. Orchestration coordinates automated tasks across multiple tools into a single workflow: when the SIEM detects a phishing email, orchestration can automatically remove the email from all inboxes, block the sender's domain at the firewall, and create an incident ticket — all in one playbook. The platform that combines these is called SOAR (security orchestration, automation, and response).
The benefits are speed, consistency, and scale: automated responses happen in seconds, follow the same steps every time, and handle volumes no human team could. The exam also tests the risks: automation adds complexity, a misconfigured playbook can cause damage at scale (blocking legitimate traffic across the whole network), and automated systems can become a single point of failure. Common automation use cases include user provisioning and deprovisioning, ticket creation and routing, guard rails (automatically enforcing configuration standards), continuous integration and deployment (CI/CD) security checks, and resource provisioning. The exam's correct answer usually balances automation with human oversight: automate the routine, keep humans in the loop for judgment calls.
The incident response process
When an incident happens, the response follows a structured process. CompTIA's SY0-701 incident response phases are: preparation, detection, analysis, containment, eradication, recovery, and lessons learned. Preparation means having a plan, a trained team, and the right tools before anything goes wrong. Detection is recognizing that an incident has occurred, usually through alerts or reports. Analysis determines the scope: what was affected, how the attacker got in, and what data was touched. Containment stops the incident from spreading — isolating affected systems, blocking malicious IPs, disabling compromised accounts. Eradication removes the root cause: deleting the malware, closing the vulnerability, changing compromised credentials. Recovery restores systems to normal operation and verifies they are clean. Lessons learned is the post-incident review: what happened, what worked, what did not, and what will change.
The exam tests the order of these phases and the distinction between them. Containment is about stopping the spread; eradication is about removing the cause; recovery is about returning to normal. A common scenario: a team restores systems from backup (recovery) before removing the malware's persistence mechanism (eradication) — and the malware comes straight back. The correct sequence matters. Tabletop exercises are discussion-based walkthroughs of an incident scenario, used to test the plan without disrupting operations. Root cause analysis digs into why the incident happened, not just what happened. Threat hunting is the proactive search for hidden threats in the environment, using hypotheses about attacker behavior rather than waiting for alerts.
Digital forensics and chain of custody
When an incident may lead to legal action, evidence must be handled carefully. Digital forensics is the process of collecting, preserving, analyzing, and presenting digital evidence. The first rule is to preserve the evidence before investigating: create a forensic image (a bit-for-bit copy) of the affected disk and work from the copy, never from the original. Chain of custody is the documented record of who handled the evidence, when, and what they did with it — without an unbroken chain, evidence may be inadmissible in court. Order of volatility describes what to collect first: the most volatile data disappears fastest, so the order is CPU registers and cache, memory (RAM), temporary files and processes, disk storage, and finally remote logs and backups. Legal hold is an instruction to preserve all relevant data because litigation is expected. The exam also tests the difference between forensics (investigating after an incident, often for legal purposes) and incident response (stopping the incident and recovering).
Data sources for investigations
Objective 4.9 asks which data source answers a given investigative question. The main sources are: logs (firewall logs show network connections, authentication logs show who logged in and when, application logs show what users did, system logs show operating system events); packet captures (full recordings of network traffic, useful for seeing exactly what was sent); NetFlow data (summaries of network traffic, showing who talked to whom, when, and how much); metadata (data about data, such as a file's creation time, author, and location history); vulnerability scan results (showing which weaknesses existed); dashboards (visual summaries of security status); and threat intelligence (information about known attackers, indicators of compromise, and attack techniques). The exam gives a question — "which log shows whether the attacker logged in?" — and expects you to pick the right source: authentication logs for logins, firewall logs for network connections, packet captures for the content of traffic.
Communication and reporting during an incident
Technical response is only half of incident response; the other half is communication. The incident response plan must define who is notified, when, and by whom: internal stakeholders (executives, legal, HR, communications), external parties (customers, regulators, law enforcement), and the criteria for each notification. Some notifications are legally required and time-bound: under GDPR, a personal data breach must be reported to the supervisory authority within 72 hours of discovery, and under many US state laws, affected individuals must be notified without unreasonable delay. Public communication must be coordinated through a single spokesperson to avoid contradictory statements. Internally, the team needs a communication plan for the incident itself: a secure channel (not the compromised email system) for the response team to coordinate, regular status updates to management, and a clear escalation path when decisions exceed the team's authority. The exam tests the principle that communication failures — notifying the wrong people, notifying too late, or saying different things to different audiences — can turn a manageable incident into a crisis.
After the incident, the incident report documents the timeline, the scope, the actions taken, the root cause, and the lessons learned. This report serves multiple audiences: management needs the business impact, the security team needs the technical detail, auditors need evidence that the plan was followed, and regulators may need proof of compliance with notification requirements. A good report is factual, complete, and honest about what went wrong — including mistakes made during the response itself, because those are the lessons that prevent a repeat.
Exam traps to watch for
- Mixing up containment, eradication, and recovery. Containment stops the spread; eradication removes the cause; recovery returns systems to normal — in that order.
- Skipping the forensic image. Always work from a copy of the evidence, never from the original, and maintain the chain of custody.
- Forgetting the order of volatility. Collect the most volatile data first: memory before disk, disk before remote logs.
- Confusing automation with orchestration. Automation performs a single task without humans; orchestration coordinates many automated tasks across tools into one workflow.
Practice questions
Test yourself on this guide. Answers are checked instantly, with a full explanation for each question.
Q1.A security team discovers malware on a workstation. They immediately disconnect the workstation from the network so the malware cannot spread to other systems. Which incident response phase is this?
Explanation: Containment stops an incident from spreading — isolating the affected workstation prevents the malware from reaching other systems. Option C is wrong because eradication removes the root cause (deleting the malware and closing the vulnerability). Option B is wrong because recovery restores systems to normal operation after the threat is removed. Option D is wrong because lessons learned is the post-incident review.
Exam objective: SY0-701 Objective 4.8: Explain appropriate incident response activities
Q2.During an incident, a team restores affected servers from backup and returns them to service, but the attackers regain access within hours because the vulnerability they exploited was never closed. Which phase did the team skip?
Explanation: Eradication removes the root cause of the incident — in this case, closing the vulnerability the attackers exploited. The team jumped from containment to recovery without eradicating the cause, so the attackers simply came back through the same hole. Option A is wrong because preparation happens before an incident. Option D is wrong because the incident was detected. Option B is wrong because lessons learned happens after recovery.
Exam objective: SY0-701 Objective 4.8: Explain appropriate incident response activities
Q3.A company suspects an employee stole trade secrets. The security team needs to examine the employee's laptop in a way that preserves the evidence for possible legal action. What is the correct first step?
Explanation: Digital forensics requires preserving the evidence first: create a bit-for-bit forensic image of the drive and perform all analysis on the copy, so the original remains unaltered and the chain of custody is intact. Option D is wrong because powering on and searching the laptop changes its state and can destroy evidence. Option B is wrong because deleting the account is a containment action, not evidence preservation. Option C is wrong because reinstalling the operating system destroys the evidence.
Exam objective: SY0-701 Objective 4.8: Explain appropriate incident response activities
Q4.A forensic investigator is collecting evidence from a running server. According to the order of volatility, which data should be collected FIRST?
Explanation: The order of volatility says to collect the most volatile data first, because it disappears fastest. Memory (RAM) is lost the moment the system powers off, so it is collected before disk storage, remote logs, or backups. Option B is wrong because disk data persists after shutdown. Option D is wrong because remote logs are stored elsewhere and persist. Option C is wrong because backup tapes are the least volatile data of all.
Exam objective: SY0-701 Objective 4.8: Explain appropriate incident response activities
Q5.A company wants to automatically remove a phishing email from every employee's inbox, block the sender's domain at the firewall, and open an incident ticket — all triggered by a single SIEM alert. Which capability makes this possible?
Explanation: Orchestration coordinates automated tasks across multiple tools (email, firewall, ticketing) into a single workflow triggered by one event. Option B is wrong because automating a single task would handle only one of these three actions. Option D is wrong because manual response is slow and inconsistent compared with an automated workflow. Option A is wrong because vulnerability scanning finds weaknesses; it does not respond to phishing emails.
Exam objective: SY0-701 Objective 4.7: Explain the importance of automation and orchestration related to secure operations
Q6.An investigator wants to determine exactly what data an attacker sent to an external server during a breach. Which data source provides the full content of the network traffic?
Explanation: A packet capture records the full content of network traffic, so an investigator can see exactly what was transmitted. Option D is wrong because NetFlow provides summaries of traffic (who talked to whom, when, how much) but not the content. Option A is wrong because a vulnerability scan shows weaknesses, not traffic content. Option B is wrong because a dashboard shows summarized metrics, not the actual data sent.
Exam objective: SY0-701 Objective 4.9: Given a scenario, use data sources to support an investigation
Q7.A security team wants to test its incident response plan by walking through a ransomware scenario in a meeting, with each person describing what they would do at each step. No systems are touched. What is this called?
Explanation: A tabletop exercise is a discussion-based walkthrough of an incident scenario, used to test the response plan and team roles without disrupting operations. Option B is wrong because a penetration test actively attacks systems. Option C is wrong because a vulnerability scan checks for known weaknesses. Option A is wrong because a forensic investigation examines evidence after a real incident.
Exam objective: SY0-701 Objective 4.8: Explain appropriate incident response activities
Q8.After a security incident is resolved, the team holds a meeting to document what happened, what worked well, what failed, and what changes should be made to prevent a repeat. Which incident response phase is this?
Explanation: Lessons learned is the final incident response phase: a post-incident review that documents what happened, evaluates the response, and identifies improvements. Option B is wrong because analysis happens during the incident to determine its scope. Option A is wrong because containment stops the incident from spreading. Option D is wrong because recovery restores systems to normal operation.
Exam objective: SY0-701 Objective 4.8: Explain appropriate incident response activities