Domain 7Security OperationsCORE

Incident Response & Management Lifecycle

NIST and ISO incident response lifecycle phases (Preparation, Detection & Analysis, Containment, Eradication, Recovery, Post-Incident Review), and CSIRT structures.

Domain: Domain 7: Security Operations•Updated: 2026-08-26
#Incident Response#NIST 800-61#Preparation#Detection#Containment#Eradication#Recovery#Lessons Learned

CISSP Domain 7: Incident Response & Management Lifecycle — Mindmap Review Study Guide

Incident Response — CISSP Domain 7 Study Material

═══════════════════════════════════

PART 1: MERMAID MINDMAP

═══════════════════════════════════

mindmap
  root((Incident Response))
    Key Definitions
      Event
      Incident
    IR Goals
    IR Frameworks
      NIST
      CSIRT
    Preparation
    Triage
      Detection
        SIEM
        IDS/IPS
        DLP
        Fire Detectors
        Fire Alarms
        Employee Reports
      Response
        IR Team Deployment
        Impact Assessment
        MTD
        BCP
        DRP
    Action and Investigation
      Mitigation
      Containment
      Reporting
        Dedicated Contact Person
        Stakeholders
    Recovery
      Return to Normal
      Remediation
        Root Cause Analysis
      Lessons Learned

═══════════════════════════════════

PART 2: TECHNICAL DEFINITIONS & CONCEPTS

═══════════════════════════════════

Key Definitions

Event — An observable occurrence in a system or network. Examples include someone logging in, a file being written to a drive, or someone scanning an external firewall. The vast majority of events are not of concern to security teams.

Incident — An event that negatively impacts the organization in some way. Examples include a server crashing, a password being brute forced, or an attacker getting through the firewall. Incidents are what IR teams care about and respond to.

IR Goals

Incident Response Goals — The overarching objectives of IR: detect incidents, provide an effective and efficient response to reduce organizational impact, maintain or restore business continuity, and defend against future attacks.

IR Frameworks

NIST — An authoritative source that defines incident response processes and frameworks.

CSIRT — An authoritative source that defines incident response processes and frameworks.

⚠️ EXAM TIP: Different frameworks (NIST, CSIRT, etc.) define slightly different numbers and names of steps, but all share the same underlying goals. Do not overly focus on exact step names—focus on the underlying goals instead.

Preparation

Preparation — The initial step before any incident occurs. Involves creating an incident response policy and procedures, identifying and training appropriate personnel, and putting monitoring capabilities in place.

Triage

Detection

Detection — The first and absolutely most important step in incident response. Without detection, the incident response process cannot be activated. This is where events are filtered to identify actual incidents.

⚠️ EXAM TIP: If asked on the exam to put the incident response process steps in order, always look for detection as the first step.

SIEM (Security Information and Event Management) — A system that collects and analyzes security events. Intrusion Detection Systems feed into SIEM to help identify incidents from the flood of events.

IDS/IPS (Intrusion Detection Systems / Intrusion Prevention Systems) — Tools used to detect (IDS) and prevent (IPS) intrusions. IDS feeds into SIEM for centralized analysis.

DLP (Data Loss Prevention) — A tool used to detect data exfiltration or unauthorized data movement incidents.

Fire Detectors — Building monitoring systems used to detect physical security incidents like fires.

Fire Alarms — A type of building monitoring system used for physical incident detection.

Employee Reports — A human-based method of incident detection where an employee reports a suspicious occurrence.

Response

Response — The step immediately following detection where the incident response team is activated and deployed to address the incident.

IR Team (Incident Response Team) — The team deployed to respond to an incident once it has been detected.

Impact Assessment — One of the first actions conducted by the IR team after deployment. Determines the severity of the incident and estimated recovery time. This assessment drives the rest of the response process.

MTD (Maximum Tolerable Downtime) — The maximum period of time a business process can be disrupted before the organization suffers unacceptable consequences. If the impact assessment determines MTD will be exceeded, the situation is escalated from an incident to a disaster.

BCP (Business Continuity Plan) — Plans enacted when a disaster is declared (when MTD is exceeded). Focuses on maintaining business operations during and after a disaster.

DRP (Disaster Recovery Plan) — Plans enacted when a disaster is declared (when MTD is exceeded). Focuses on restoring IT systems and infrastructure after a disaster.

Action and Investigation

Mitigation

Mitigation — The step where the team works to minimize damage and contain the incident. Examples include disconnecting systems from the network during a worm outbreak or activating fire suppression systems during a fire.

Containment — Used synonymously with mitigation in this context. The act of containing the incident to prevent further damage or spread.

Reporting

Reporting — Conducted throughout the entire incident response process, not just at one stage. There should be one dedicated contact person on the IR team responsible for reporting to all relevant stakeholders while the rest of the team stays focused on responding to the incident.

Dedicated Contact Person — A single person on the IR team assigned to handle all stakeholder communications. This allows the rest of the team to focus entirely on incident response without distraction.

Stakeholders — Parties that must be informed during an incident. Includes management, investors, regulators, customers, and the media.

Recovery

Return to Normal

Recovery (Return to Normal) — The step where the organization works on returning to business as usual. Examples include eradicating a worm and reconnecting systems to the network, or cleaning up after a fire (removing debris, installing new carpet, painting walls, moving in new furniture).

Remediation

Remediation — Begins in parallel with mitigation (not after recovery). Involves performing root cause analysis to determine how to prevent the issue from recurring (e.g., preventing continued worm spread or fire re-ignition). Continues through recovery and closure of the incident, leading into lessons learned.

Root Cause Analysis — Performed during remediation to determine the underlying cause of the incident and how to prevent it from happening again.

Lessons Learned

Lessons Learned — The post-incident step where the team reflects on what happened. Key questions include: How did this happen? How can we prevent it from happening again? Why did it happen to us?

Lessons Learned Goals — Improve processes and systems, teach people, prevent future incidents, and if incidents do occur, detect them more quickly and respond more effectively.