Posted in Security Operations

Most incident response plans I review are beautifully formatted and have never been opened by the people…

Christian T. — Fractional CISO | Strategic Cyber, Technology & AI Advisor | Founder, Alvearium Associates

Most incident response plans I review are beautifully formatted and have never been opened by the people named in them. The contact list includes a CISO who left two years ago, a phone number that now reaches a pizza restaurant, and a recovery procedure that assumes the systems you need are still working.

A plan is not a capability. Capability is what happens at two in the morning when the author is on a beach and legal wants to know whether the regulator's clock has started.

Run a tabletop twice a year, make it slightly uncomfortable, and write down who decides what. Printing the plan also helps, since ransomware has a well documented dislike of paper.

When did your plan last meet a real decision?

5 reactions · 3 comments

Comments

Schomer: Spot on, Christian. A beautifully formatted plan is just a collection of assumptions until it meets an active exploit runtime. The industry spends millions drafting manual procedures for what to do after a system compromise occurs, completely ignoring the fact that if your security relies on human response times or out-of-date contact sheets at two in the morning, you've already lost the battle. T

Daniel O.: It is important to know the number of the closest pizza place before the incident :)

Victor Font: Christian, exactly. An incident response plan is a documented intention until someone demonstrates it works. I'd take the tabletop one step further: record who exercised decision authority, what information they had, where escalation failed, and which corrective actions were verified afterward. That evidence tells leadership whether the organization has genuine response capability or merely a well

Read and join the discussion on Cyberr