Skip to main content

Overview

NIST defines a cybersecurity incident as an occurrence that actually or imminently jeopardizes, without lawful authority, the integrity, confidentiality, or availability of information or an information system, or that violates or imminently threatens to violate law, security policies, security procedures, or acceptable use policies. Incident response is how an organization handles such occurrences.

Earlier NIST guidance, SP 800-61 Revision 2, described a life cycle of preparation, detection and analysis, containment, eradication and recovery, and post-incident activity, and CISA's federal incident response playbook follows those phases. Containment aims to prevent further damage and reduce the immediate impact of the incident by removing the adversary's access. Eradication and recovery include reimaging or rebuilding affected systems, replacing compromised files with clean versions, installing patches, and resetting passwords on compromised accounts. Post-incident activities document the incident, harden the environment, and apply lessons learned to the handling of future incidents.

NIST SP 800-61 Revision 3, published in April 2025, proposes a model based on the six functions of the NIST Cybersecurity Framework (CSF) 2.0. Govern, identify, and protect help organizations prevent some incidents, prepare for those that occur, and reduce their impact; detect, respond, and recover cover discovering, containing, eradicating, and recovering from incidents. NIST gives the reason for the change. Incidents now occur frequently, cause far more damage, and often take weeks or months to recover from, so incident response is treated as a critical part of cybersecurity risk management integrated across the organization rather than a separate set of activities for a separate team.

Many roles take part. NIST lists leadership, incident handlers, technology professionals, legal experts, and public affairs staff. Leadership oversees incident response and may decide on high-impact actions such as shutting down or rebuilding critical services. Incident handlers verify that an incident has occurred, analyze data and evidence, limit damage, and restore operations. They may be on staff, on contract, for example through a security operations center outsourced to a managed security services provider, or available when needed from a parent organization, a business partner, or a law enforcement agency.

Similar Terms

3 terms

Frequently Asked Questions

What are the phases of incident response?→

CISA's federal playbook, following NIST SP 800-61 Revision 2, uses preparation, detection and analysis, containment, eradication and recovery, and post-incident activities. NIST SP 800-61 Revision 3 organizes incident response around the six CSF 2.0 functions: govern, identify, protect, detect, respond, and recover.

What is the goal of containment?→

Containment aims to prevent further damage and reduce the immediate impact of the incident by removing the adversary's access. CISA notes that the scenario drives the strategy: containing an active sophisticated adversary using fileless malware differs from containing ransomware.

What does an incident response policy include?→

According to NIST, most incident response policies include a statement of management commitment, purpose and objectives, scope, definitions of events and incidents, roles and authorities such as which roles may disconnect or shut down technology assets, guidelines for prioritizing incidents and estimating severity, and performance measures. Procedures based on the policy and plan can be tested or exercised periodically to verify their accuracy.

Who is involved in incident response?→

NIST lists leadership, incident handlers, technology professionals, legal experts, and public affairs and media relations staff, among others. Incident handlers can be on staff, on contract, or brought in when needed, and many organizations combine these approaches.

Related

Sources

Definitions follow the government and standards body sources listed above. This site is not affiliated with the agencies or organizations cited.