Techbanq

Cybersecurity · incident readiness

An incident plan is a claim until it has been rehearsed

Every response plan claims that people will know their roles, that decisions will be made quickly, that evidence will survive the response and that the right words will reach customers and regulators. A readiness assessment tests each claim while the stakes are theoretical — through a rehearsed scenario, a decision authority map and an honest look at what is actually prepared.

Enterprise delivery credentials

  • ISO

    ISO/IEC 27001

    ISO/IEC 27001 certified

Certifications & registrations

The method

How we test whether your incident plan would survive contact

The assessment moves from what the plan says, to who may decide, to how people actually behave, to whether the evidence would survive. Each step produces something usable on its own.

STAGE 01

Read the plan against the estate

Does the document name systems that still exist, roles that are actually filled, tools that are actually licensed, and contacts who still work here. Most plans fail this quiet audit before any scenario is needed. A list of the plan's claims, each marked verified or broken.

STAGE 02

Map who may decide what

For each drastic action — isolating a production system, taking the payment flow down, notifying a regulator, engaging counsel — who decides, who deputises when they are asleep or on leave, and is that written anywhere. A decision authority matrix with names and deputies.

STAGE 03

Run the tabletop

A scenario written for your estate, played in real time with the people who would hold the roles, with injects that force the awkward moments: the missing deputy, the journalist calling, the backup that might be infected. The observed gaps between what the plan says and what the room did.

STAGE 04

Check the evidence path

Could your team, tonight, capture memory from a suspect host, image a disk, and export the relevant logs — without trampling the evidence in the process — and is there a place to put the copies and a record of who touched them. An evidence-handling readiness verdict with its fixes.

The authority gap

Isolating production at two in the morning is a question of authority

The technical act of containing an intrusion is often minutes of work — an account disabled, a host cut off, a route withdrawn. What consumes the first hours of real incidents is the question of permission: the engineer who sees the problem is rarely the person entitled to take the revenue system offline, and the person entitled is asleep, travelling, or unsure whether this is their call. So the intrusion runs on while the organisation telephones its own hierarchy. The gap is invisible in the plan, because plans describe roles, and it is fatal in the event, because events are decided in minutes.

The repair is unglamorous and effective: decide the authorities in daylight. For each drastic action, name who decides, name who deputises at night and during leave, and — where the risk justifies it — pre-delegate: agree in advance that under defined conditions the on-call engineer may isolate first and report immediately after. Organisations resist writing this down because it feels like planning for failure; in practice it is the difference between a response measured in minutes and one measured in phone calls.

Prepared in advance

The documents a ready organisation writes before it needs them

None of these can be written well at three in the morning with an incident running. All of them can be written calmly this month.

01

Communication templates with blanks to fill

Holding statements for customers, notices for staff, notification drafts for regulators and partners — composed calmly in advance and reviewed by counsel, so that under pressure the work is filling in facts rather than finding words.

02

A contact tree that survives the directory being down

The incident may live inside the very systems that hold your contacts, so the tree exists offline, includes out-of-band channels agreed with each person, and assumes corporate email might be the compromised platform.

03

A decision authority matrix with named deputies

For each drastic action, the decider, the deputy and the conditions for pre-delegated action — the one-page answer to the question that otherwise costs the response its first hours.

Our role

What the readiness assessment delivers and what your leadership decides

  1. 01

    A rehearsal, not an ambush

    The tabletop is designed to surface gaps in the plan, not to embarrass the people in the room; findings are about documents, authorities and preparation, and the exercise is one a team wants to run again.

  2. 02

    Fixes ranked by what an incident punishes first

    The report orders its findings by the damage each gap would do in the first hours of a real event — authority gaps and evidence handling typically before document polish — so the next quarter's effort lands where it matters.

  3. 03

    An exercise your team can rerun

    The scenario, the injects and the facilitation notes stay with you, so readiness becomes a habit rehearsed on your own schedule rather than an event that happened once.

Which scenarios worry you most, how much authority to pre-delegate, and what risk appetite the rehearsal assumes are leadership's calls; we build the exercise around them and report what the room revealed, plainly.

Common questions

What buyers ask

Who should sit in the room for a tabletop exercise?+

The people who would actually hold the roles, not their most available substitutes. That means the incident lead, the engineers who would do the containment, whoever owns communications, a legal or compliance voice, and — for at least part of the session — the executive who would make the drastic calls, because the most valuable minutes of most tabletops are the ones where an executive discovers a decision is theirs. Sending deputies to the rehearsal while principals plan to appear only at the real thing inverts the logic of rehearsal: the performance gets the practised cast, and the premiere gets the understudies.

Our incident response plan passed an audit — is a rehearsal still worth running?+

Yes, because an audit and a rehearsal test different things. An audit checks that the document exists, covers the expected topics and is approved; it is a review of the plan as text. A rehearsal tests the plan as behaviour: whether the named people know they are named, whether the deputy knows the threshold for acting, whether the contact tree works when the directory is down, whether anyone can actually produce a forensic image tonight. We regularly rehearse plans that passed audits and watch them fail in the first half hour — not because the document was wrong, but because a plan is a claim about people, and text cannot verify people.

What does evidence-handling readiness mean before any incident exists?+

That the capability exists before the need does, because forensic evidence is destroyed by ordinary response actions unless someone is prepared. Concretely: the tools to capture volatile memory and image disks are installed and licensed, someone on each shift has practised using them, prepared storage exists for the copies, and a simple chain-of-custody record — who collected what, when, and who has touched it since — is ready to fill in. Without this, the instinctive first acts of a response, rebooting and reimaging, quietly erase what an investigation, an insurer or a court would later need. The assessment checks each element by asking your team to actually do it, not to describe it.

Book the first rehearsal

A scoping call that chooses the scenario your first tabletop should rehearse and identifies who needs to be in the room for it to count.

What happens next

  1. 1We reply within one business day.
  2. 2A 30-minute scoping call with a senior consultant.
  3. 3A written proposal with scope, team, and timeline.

Or reach us directly

By submitting this form you agree to our Terms of Use and Privacy Policy.