Initialising secure session0%
PITOWINGS — Secure Everywhere

Incident Response

How to Build an Incident Response Plan and Run a Tabletop Exercise That Is Actually Useful

The worst time to decide who is in charge of a breach is during the breach.

PWPITOWINGS Research9 min read

Every serious incident we respond to has the same early pattern: people unsure who can make decisions, who to call, whether to switch systems off and what they are legally obliged to report. A short, rehearsed plan removes those questions before the pressure arrives.

What the plan must answer

  • Who leads? A named incident lead and deputy, with authority to take systems offline.
  • How bad is it? Simple severity levels with examples, so everyone escalates the same way.
  • Who do we call? Internal contacts, incident response provider, legal counsel, insurer, out-of-hours numbers.
  • How do we talk? A backup channel that does not depend on company email or chat.
  • What do we preserve? Logs, disk and memory images, and a timeline, before cleaning anything.
  • Who must we notify, and when? Regulators and customers under CERT-In directions, DPDP, GDPR, SEC or sector rules.

Running a tabletop exercise

StepDetail
Pick a realistic scenarioRansomware on Friday night, a supplier's email compromised, a cloud key leaked
Invite the real decision-makersLeadership, IT, legal, communications, finance, not only the security team
Add injectsA journalist calls, backups fail, the attacker emails staff, the regulator asks questions
Time-box decisionsForce choices with incomplete information, as in a real incident
Write it downCapture gaps, owners and deadlines; update the plan within two weeks
A plan nobody has rehearsed is a document. A plan you have rehearsed is a capability.

Rehearse before it is real

Our incident responders facilitate tabletop exercises built on real attack patterns, and are on call if it happens for real.

See incident response

Frequently asked questions

What should an incident response plan include?

Roles and decision authority, severity levels, contact lists, backup communication channels, evidence preservation steps and regulatory notification requirements.

How often should we run a tabletop exercise?

At least once a year, and after major changes in systems, leadership or regulations. Many organisations run them every six months.

What is the first step when a cyber incident happens?

Contain without destroying evidence: isolate affected systems from the network but keep them powered on, preserve logs and contact your incident response team.

PW

PITOWINGS Research

OSCP, CEH and ECES certified testers, SOC analysts and certified forensic investigators at PITOWINGS.

Talk to us
All articles