Incident response plan: the six steps, and why you must test it

Many companies have an incident response plan. Few have ever tested it. A plan that has never been simulated often fails under pressure, exactly when there is the least time to think.

The six pillars of a solid plan

  1. Identification: who detects, with which tools, and at what alert thresholds?
  2. Containment: documented, tested procedures to isolate the network and stop the spread.
  3. Eradication: remove the threat without leaving a backdoor or a risk of reinfection.
  4. Recovery: restore cleanly from healthy, verified backups.
  5. Communication: a clear internal escalation chain, and your notification obligations (customers, partners, data-protection authority, insurer).
  6. Lessons learned: a structured review after the incident so the same mistakes are not repeated.

A written plan is not enough

The plan must be written, known to the people involved and simulated at least once a year. The simplest format is a tabletop exercise: the team meets, a scenario is presented (for example ransomware on a Friday evening) and everyone explains what they would do, who calls whom and which decisions must be made.

The questions this exercise brings up

  • Who decides to isolate a critical system, and how quickly?
  • Where are the backups, and do we know how to restore them?
  • Who speaks to customers, and what do we say?
  • Which emergency numbers and external contacts are at hand without network access?

Crisis management cannot be improvised at three in the morning. A half-day exercise already reveals most of the gaps.

Cybersecurity for businesses

An audit, staff awareness training or a backup plan: let’s talk about your situation.

See the service