Incident response is an organized way to identify, manage, and learn from incidents. An event is something observable, such as a login or system error. An incident disrupts or could damage an organization; a security incident compromises security, as a data breach or malware infection might. Because defenses cannot eliminate every risk, a prepared response helps limit damage and restore operations. section 5.7 section 5.0
The incident response lifecycle has four connected phases:
- Preparation: strengthen defenses, create a plan, and train the people who will use it. section 5.3.1
- Detection and analysis: identify, investigate, and classify a possible security incident. section 5.7
- Containment, eradication, and recovery: limit the damage, remove the threat, and restore systems. section 5.7 section 5.9
- Post-incident activity: review what happened and use the findings to improve plans, training, and detection. section 5.3
An incident response plan makes these actions coordinated and repeatable. It assigns roles and a chain of command, sets communication arrangements, and includes procedures for different incidents. Those procedures may be written as playbooks: predefined steps and decisions that help responders act without starting from scratch during a crisis. A Security Operations Center (SOC) commonly brings together the people who monitor threats and carry out the response. section 5.3.1 section 5.4 section 5.5
A reported phishing email
A procedure might tell an employee not to open links or attachments, to preserve the email, and to report it. IT may handle the initial report while the cybersecurity team analyzes it and coordinates the response. Clear handoffs help the right people act consistently. section 4.2.4




