Typical lifecycle
- Preparation.
- Identification and triage.
- Scoping and analysis.
- Containment.
- Eradication.
- Recovery.
- Lessons learned.
Follow a structured incident-response workflow from initial validation through containment, recovery and lessons learned.
Incident response is a controlled process. The analyst should preserve evidence, scope the activity, coordinate containment and document decisions according to authorized procedures.
Use this page after the daily quiz: learn the concept first, then follow the investigation workflow and examples.
During an incident, why should an analyst establish scope before making broad containment decisions when circumstances allow?
Quiz flow: introduce this topic briefly on social media, ask the question, reveal the answer, then send learners here for the detailed investigation.
Incident response moves from preparation and detection through analysis, containment, eradication, recovery, and lessons learned. The order and authority for actions depend on organizational policy, business impact, evidence needs, and incident scope.
Use the ransomware simulation to distinguish immediate containment from eradication and recovery. Preserve relevant evidence, coordinate with system owners, and validate backups and restored services before declaring recovery complete.
Continue practicing: open a fictional mission and test your reasoning against the simulated evidence.