The Invisible Playbook: Whatever You Have Is What You Have

Anyone trained in the NIST incident response lifecycle knows the activities involved in each stage. Many organizations use this framework to model their cyber emergency response and assess their preparedness for an unlikely event. On a whiteboard, the framework looks clean and ready to execute. However, the moment the second alarm goes off, the phones start ringing, and outside messages start pouring in about a potential breach or attack, that neat plan melts away. An emergency does not create weaknesses, because it simply reveals them.

When an incident hits, the outcome is mostly decided by what was done beforehand, such as who is on the team, what is documented and backed up, and what has actually been tested. Your response and critical thinking matter, but you can only work with what you already have. When the internet drops, a server will not start, the document repository goes offline, and the contact list is out of date, the team cannot prompt or Google its way out of the dark. In a crisis, only the basics and the habits built beforehand are left.

The idea we will follow in this article is simple, which is to prepare first, and then, when things get loud, get back to four basics, which are to know what you have, write down the events in sequence, follow one lead at a time and know when to pivot, and say it plainly. The good news is that these basics are simple, cheap and learnable, which means any team can start building them today.

Know What You Have Before It Vanishes.

Clarity, resources and help do not exist during an emergency, and when help does come later, it comes with a significant cost. In the middle of an incident there is no time to hire, train or learn a new tool, so whatever you have is what you work with. The most unglamorous part of the whole effort is the preparation.

Hire the right people and develop them, and make sure more than one person can do each critical job. Think about the scenarios where these experts are stuck on vacation, or cannot reach the operations center because transport has failed.

Keep the technology portfolio lean, the architecture simple and everything baselined, because every extra component and system is one more thing to defend and explain. Keep insurance policy conditions, regulatory notification rules, playbooks, policies and standards current and accessible, because outdated documents are the worst of all, since they feel secure and look like help.

Test everything on a periodic schedule, including recovery from backups, execution of playbooks by someone who is not a subject matter expert (SME), and out of band communication. On backups, the number of copies matters less than the medium, because when everything goes down the copy you can read without the network is the one that helps, and the cloud is useful only if it is reachable.

SMEs these days are useful only as long as a search engine or an AI assistant is available to answer for them, so what happens when the internet and mobile networks are down?

Write It Down and stamp the time.

During an incident, information arrives in erratic bursts from outside callers, help desks, chat channels, and other sources. With a lean crew, there is no time to verify, validate, and vet every signal on arrival, so you must document it right away because anything not documented did not happen, and people will either forget the information received, remember their own version of events, or chase a rabbit hole while neglecting new information.

Logging the noise will help the team pivot when the mind fatigues inside a rabbit hole trap, and months later these exact paper trails can help get cyber insurance claims paid and protect the enterprise in a courtroom.

With that being said, keeping accurate records of who, what and when in the midst of an incident is the hardest job, and whoever keeps it up at hour six has to be careful to record what is confirmed as confirmed and what is only reported as unverified.

Follow One Lead at a Time and Put a Clock on It

Clarity is a rare commodity during an incident, and it rarely exists. What exists is the leads and logs, and the rare skill is choosing which one to follow, when to stop digging and when to pivot, which is easier when each lead has a time limit. There are two traps while chasing a lead, one is to follow it to the end and get trapped in a hole without pivoting, and the other is to trust all the information that comes in without a second look.

In real emergencies nobody will coach you from the sideline, and this muscle memory of receiving a lead, tailoring it to the big picture, choosing which one to follow, recording the outcome and knowing when to pivot is built long before the crisis starts. Every one of us is capable of getting stuck in a trap and getting out of it, so what is your rule for leaving a rabbit hole?

Say It Plainly, Clearly and Consistently

When IT, law enforcement, finance, legal and executive teams are at the same table, the same word can carry a completely different meaning. “Backup” to an engineer means an offline restore medium, and to law enforcement it means patrol cars arriving with sirens. A simple, shared and unified language goes a long way, and the medium in which it is conveyed carries significant weight.

Using one medium repeatedly will reduce the effectiveness of the message, and each medium such as chat, email, a live press conference, a recorded message and others has a very different style of message delivery, so keep the message consistent across them and test each one.

Get these four basics right, and what is left is how you carry yourself while the crisis is still going on. At the end of the day your habits are your invisible playbook.

Detached Compassion

Once you go through a crisis dispassionately, you will recognize that compassion and detachment are actually complementary to each other. You will feel compassion for the people carrying the weight and keep enough distance to respond to a threat. They don’t conflict, and together they keep you clear enough to act while still caring about the outcome. Not all emergencies are the same, but the common thread is the habits you build during quiet times, and in the end your habits are your invisible playbook.