DOMAIN 7 · Security Operations
Incident Response as Part of Cybersecurity Risk Management
Use the current NIST incident response model to connect preparation, detection, response, recovery, and continual improvement.
Use the current model deliberately
Section titled “Use the current model deliberately”NIST SP 800-61 Rev. 3, published in April 2025, supersedes Rev. 2. It frames incident response through the NIST Cybersecurity Framework 2.0 rather than simply reissuing the previous incident-handling guide. This distinction matters when comparing older learning material with current operational guidance.1
An effective response capability connects technical actions with business priorities, authority, communications, and recovery. Knowing a sequence of terms is useful, but the CISSP decision is often about who should act and which organizational outcome needs protection.
Distinguish preparation from response
Section titled “Distinguish preparation from response”| CSF 2.0 functions | Contribution |
|---|---|
| Govern, Identify, Protect | Broader risk-management activities that prepare the organization and can prevent or reduce incidents |
| Detect, Respond, Recover | Discovering and handling incidents and restoring affected assets and operations |
| Identify: Improvement | Feeding lessons into activities across the functions |
These functions are not a strict six-step incident checklist. Preparation supports response before an incident occurs, and improvement can happen throughout the work. Rev. 3 also maps the older phases to this model, so historical terminology can be understood without presenting it as the current model’s structure.1
Decide what requires a coordinated response
Section titled “Decide what requires a coordinated response”An alert is an observation requiring analysis, not automatically a confirmed incident. Teams need criteria for examining events, determining significance, declaring an incident, and escalating it. Prioritization should consider affected services, scope, likely impact, and available response capacity rather than the volume of alerts alone.1
Document who can make urgent decisions. The person investigating suspicious activity may need a business owner to authorize a disruptive containment action. A contact list that depends entirely on the affected identity or messaging service may be unusable precisely when it is needed.
Balance containment, evidence, and operations
Section titled “Balance containment, evidence, and operations”Containment limits further harm. Eradication addresses the causes or means of compromise. Recovery restores trustworthy operations. These concerns interact: immediately deleting an affected machine can remove valuable evidence, while delaying every containment decision until analysis is complete can allow further damage.
NIST’s response profile includes analysis, mitigation, reporting, communication, and recovery considerations. Organizations should establish decision criteria and coordination in advance, then record actions and their reasons during execution.1
Worked example: suspected account compromise
Section titled “Worked example: suspected account compromise”Consider a fictional service where a privileged account starts exporting customer records outside its usual pattern. The team preserves relevant logs, checks whether the activity is legitimate, and assesses the account’s reach. If it declares an incident, the authorized responder may revoke sessions and restrict credentials while investigating related systems.
The team records the decision, communicates through an available channel, and coordinates with the service owner before restoring access. It verifies that recovery does not simply re-enable the attacker’s route. Notification requirements are assessed against the actual contracts, jurisdictions, and facts; this example does not assume one universal reporting deadline.
Learn from the response
Section titled “Learn from the response”After immediate operations stabilize, examine why the activity was possible, what information was missing, and which decisions were delayed. Useful improvements might include narrower privileges, better log retention, a tested alternate contact channel, or clearer authority to revoke access.
Improvement should have owners and observable outcomes. Recording “provide more training” without identifying the affected decision or expected behavior makes it difficult to know whether the next response will improve. Rev. 3 explicitly treats lessons and improvement as inputs across cybersecurity risk management.1
Common misunderstandings
Section titled “Common misunderstandings”- “Response begins only after compromise is confirmed.” Preparation and event analysis already shape the outcome.
- “Recovery means putting the system back online.” Restored service must also be assessed for integrity and continuing compromise.
- “The technical team owns every decision.” Business, legal, communications, and external parties can have essential responsibilities.
Connect this topic
Section titled “Connect this topic”Access control explains privilege and revocation. Business continuity addresses service priorities, recovery requirements, and exercises that support the response.
References
Section titled “References”Footnotes
Section titled “Footnotes”Independent, unofficial study notes. Not endorsed or reviewed by ISC2. CISSP is a registered trademark of ISC2.
Editorial policy & attribution