Automation, Incident Response & Investigations

Security+ SY0-701 · Security Operations

By Abu Anns · Last updated 20 November 2026Exam version: SY0-701

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.

Advertisement

Exam traps to watch for

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?

Report an error

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?

Report an error

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?

Report an error

Q4.A forensic investigator is collecting evidence from a running server. According to the order of volatility, which data should be collected FIRST?

Report an error

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?

Report an error

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?

Report an error

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?

Report an error

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?

Report an error