Labs / Incident Response
Road 23 of 33
Incident Response
The six phases of handling a breach, each its own incident: the preparation done while nothing is wrong, confirming and scoping an intrusion, containing it without destroying evidence, eradicating the attacker's foothold, recovering the service in the right order, and turning the closed incident into a detection.
Start this roadFirst response: prepare, confirm, contain
Get ready, confirm an intrusion, and stop the bleeding.
- 01 Preparation: the three questions to answer before an incident While nothing is wrong, inventory the network, write down what normal looks like, and prove the login record is being kept.
- 02 Identification: is it a real incident, and how far does it reach? A rule flagged a spike of failed logins on the readings historian. Confirm whether anyone got in, scope the damage, and declare it.
- 03 Containment: stop the spread without destroying the evidence A compromised DMZ web server is reaching into the office network. Isolate it at the boundary to stop the spread while the box stays up.
Close it out: eradicate, recover, learn
Remove the foothold, restore safely, turn it into a defence.
- 01 Eradication: remove the foothold, not only the visible part The contained life-support controller is still compromised. Remove the implant, the cron that revives it, and the attacker's account, then prove it is clean.
- 02 Recovery: put it back safely, in the right order The cleaned broadcast server is offline. Confirm it is clean, rotate the guessed password, restore the page, and check a renewed attack would be seen.
- 03 Lessons learned: turn the incident into a defence The greenhouse-controller break-in is closed. Rebuild the timeline, name the root cause, and turn it into a detection that fires only on the real thing.