Security Operations, Incident Response & Investigations

CISSP CISSP · Security Operations

By Abu Anns · Last updated 20 November 2026Exam version: April 2024 outline (current until 15 April 2027)

Operations: where security meets reality

Domain 7 covers the day-to-day work of running a security program: monitoring for threats, responding to incidents, investigating what happened, and keeping systems patched and controlled. It is the largest operational domain, and the exam tests it as a management discipline — the questions are about process, priorities and judgement, not about operating specific tools. The central theme is that incidents are inevitable, and what matters is how quickly you detect them, how well you respond, and how thoroughly you learn from them.

Logging and monitoring

Effective operations depend on visibility, and visibility depends on logs. The exam expects you to know what should be logged (authentication events, privilege use, access to sensitive data, system and configuration changes, security tool alerts), how logs should be protected (centralised collection, restricted access, protection against tampering — ideally write-once or append-only storage, and time synchronisation via NTP so that events can be correlated across systems), and how long logs should be retained (driven by legal, regulatory and investigative needs — too short and you cannot investigate a breach discovered months later; too long and storage costs grow). A SIEM (Security Information and Event Management) system centralises logs from many sources, correlates events, and generates alerts based on rules or analytics. A SOAR (Security Orchestration, Automation and Response) platform goes further, automating response actions such as blocking an IP or isolating a host. The Security Operations Centre (SOC) is the team and facility that uses these tools, typically operating in tiers: Tier 1 triages alerts, Tier 2 investigates, Tier 3 handles advanced threats and threat hunting. The exam's key point about monitoring is that alert volume must be managed: a SOC drowning in false positives will miss real incidents, so tuning detection rules and prioritising alerts is as important as collecting the data.

The incident response lifecycle

The incident response lifecycle is the backbone of Domain 7, and the exam tests its phases in order. NIST SP 800-61 defines four phases: Preparation (building the IR plan, the team, the tools, and the playbooks before anything happens), Detection and Analysis (identifying that an incident has occurred, determining its scope and severity, and prioritising the response), Containment, Eradication and Recovery (stopping the spread, removing the cause, and restoring systems to normal operation), and Post-Incident Activity (lessons learned, updating the plan, and improving controls). The exam often presents a scenario mid-incident and asks what to do next — the answer follows the phase order. Two distinctions matter within the lifecycle: containment (stopping the incident from spreading, which may be short-term, such as isolating a host, or long-term, such as blocking an attacker's infrastructure) versus eradication (removing the root cause, such as deleting malware or closing the exploited vulnerability) — eradicating before containing is a classic mistake, because the attacker can simply re-enter through the still-open path. And recovery must be verified: restoring from a clean backup and confirming the system is clean before returning it to service.

Phase (NIST SP 800-61)Key activities
1. PreparationIR plan, team, tools, playbooks, training, exercises
2. Detection & AnalysisIdentify the incident, determine scope and severity, prioritise
3. Containment, Eradication & RecoveryStop the spread, remove the cause, restore verified-clean systems
4. Post-Incident ActivityLessons learned, update plans and controls, report

Incident handling priorities

When an incident occurs, the exam expects a specific order of priorities. People first: if anyone's safety is at risk, that comes before systems or data. Contain the incident to prevent further damage. Preserve evidence — do not destroy forensic artefacts in the rush to recover. Notify the appropriate parties: internal management, legal counsel, law enforcement where required, regulators within their deadlines, and affected individuals where the law requires it. Recover systems in priority order, guided by the business impact analysis. The exam also tests incident classification and severity: not every event is an incident (an event is any observable occurrence; an incident is an event that compromises or threatens to compromise security), and severity determines the response urgency and who must be notified. Communication during an incident is a distinct discipline: a single spokesperson, factual statements, no speculation, and a clear record of what was said and when. The exam's most common trap is the impulse to fix things before preserving evidence — rebooting a compromised server destroys volatile memory evidence, and reimaging a disk destroys forensic artefacts.

Digital forensics

When an incident may lead to legal proceedings, the investigation must follow forensic principles. The order of volatility determines what to collect first: the most volatile evidence disappears fastest, so the order is generally CPU registers and cache, RAM, network state, running processes, disk, and finally backups and archival media. The exam's formulation is often: collect RAM before disk, because RAM is lost when the system powers off. Chain of custody is the documented record of who handled evidence, when, and what they did with it — without an unbroken chain, evidence may be inadmissible in court. Forensic imaging creates a bit-for-bit copy of a disk (using a write blocker to prevent any modification of the original), and the copy is verified with a hash (MD5 or SHA-256) so that any later alteration can be detected. Investigators work on the copy, never on the original. The exam also covers legal holds (preserving evidence when litigation is anticipated), admissibility (evidence must be relevant, authentic, and obtained legally), and the distinction between forensic investigation (for legal purposes, with strict procedures) and incident analysis (for operational purposes, which can be less formal). The exam's key forensic facts: never work on the original evidence, always hash the image, and always document the chain of custody.

Patch and vulnerability management

Patch management is the operational discipline of keeping systems current: identifying available patches, testing them, deploying them, and verifying the deployment. The exam's framing is risk-based: patches should be prioritised by the severity of the vulnerability and the exposure of the system, not applied in the order they arrive. Critical patches for internet-facing systems go first; low-severity patches for isolated systems can wait for the next maintenance window. Change management governs the process: every change (including patches) should be requested, assessed for impact and risk, approved, tested, scheduled, implemented, and reviewed. Emergency changes follow an expedited path but still require documentation and retrospective review. The exam tests the tension between speed and safety: an untested patch can break a production system, but an unpatched critical vulnerability can be exploited within hours of disclosure. The correct answer usually involves a risk-based middle path — test critical patches quickly in a representative environment, deploy to a pilot group, then roll out broadly, with a rollback plan ready.

Change and configuration management

Configuration management ensures systems are built and maintained to a known, secure baseline: hardening guides (such as the CIS Benchmarks), standard images, and configuration monitoring to detect drift. Change management ensures that changes to that baseline are controlled. The exam tests the elements of a change management process: a change request, impact assessment, approval by a Change Advisory Board (CAB) or equivalent, testing, scheduling, implementation, and post-implementation review. Unauthorised changes — whether well-intentioned or malicious — are a major source of incidents and audit findings. The exam also covers version control and rollback: every change should be reversible, and the rollback procedure should be tested before the change is made.

Exam mindset for security operations

Operations questions reward process discipline: follow the incident response phases in order, preserve evidence before fixing things, contain before eradicating, and prioritise patches by risk. When a scenario describes a crisis, the correct answer is usually the one that follows the plan — not the one that acts fastest or most aggressively.

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 SOC analyst detects malware on a workstation that is communicating with an external command-and-control server. What is the FIRST action the analyst should take?

Report an error

Q2.A forensic investigator arrives at the scene of a suspected data theft. The suspect computer is powered on and running. According to the order of volatility, what should the investigator collect FIRST?

Report an error

Q3.A company suffers a ransomware attack that encrypts file servers. The incident response team has contained the attack and identified the entry point. Before restoring systems, what is the MOST important step?

Report an error

Q4.A forensic investigator creates a bit-for-bit copy of a suspect hard drive. Which TWO practices are essential to ensure the copy is admissible as evidence?

Report an error

Q5.A critical vulnerability with a public exploit is disclosed for a widely used web server. The vendor releases a patch the same day. The organisation’s standard change process takes two weeks. What is the BEST course of action?

Report an error

Q6.A SOC receives 10,000 alerts per day, of which fewer than 1% are genuine incidents. Analysts are missing real attacks because they cannot review every alert. What is the BEST improvement?

Report an error

Q7.During an incident, a manager asks the response team to "just fix it and worry about the paperwork later". The team is concerned about preserving evidence for a possible legal case. What should the team do?

Report an error

Q8.An organisation’s incident response plan has not been tested in three years. A tabletop exercise is proposed. What is the PRIMARY value of the tabletop exercise?

Report an error