Ahom Cybersecurity logo Ahom CybersecurityPlain-language security for people and small teams
Business Security

A One Page Incident Response Plan for a Small Team

A twelve person agency I worked with lost ninety minutes on a Friday evening because nobody knew who could change the hosting password.

A single printed response sheet pinned to an office wall beside a kettle, listing phone numbers and timed steps in three columns

A twelve person agency I worked with lost ninety minutes on a Friday evening because nobody knew who could change the hosting password. The incident itself was modest: one email account compromised, spotted at 17:40 by a client who received an odd invoice. The useful work took about twenty minutes. Everything else was three people texting each other to establish who had the login, whether the office manager was allowed to reset it, and whether anyone should ring the client back before the director had seen it.

They had a plan. It was fourteen pages long, written by a consultant in 2022, stored in a folder nobody could reach because the folder was in the compromised account. That is the ordinary version of this failure, and it is why I now tell small teams to write one page and put it somewhere that does not need a password.

The long template is the reason nobody has a plan

Search for an incident response template and you will find documents of thirty to sixty pages, modelled on frameworks written for organisations with a security team and a legal department. They are good documents. For a business under about fifty people they fail in a specific and predictable way.

They fail because an incident is a ten minute window in which a frightened person has to do the right thing. Nobody reads page nineteen at 17:40 on a Friday. In the four small businesses whose incidents I have helped review, the plan was opened during the event exactly once, and in that case the person skimmed the first page and closed it.

So the test for a plan is not completeness. It is whether the person who finds the problem, who is often the most junior person in the building, can read it in sixty seconds and take the first two actions without asking permission. Everything else can live in a longer document that gets read on a Tuesday.

A second reason the long version fails: it goes stale invisibly. Fourteen pages contain perhaps forty facts, and in a small company a quarter of those are wrong within a year. One page contains eight or nine facts and somebody notices when one changes.

Write these four things down before you write anything else

Most of the delay in a real incident comes from missing information rather than missing procedure. Four items cover almost all of it.

Who can authorise disruption, by name and mobile number, with a named deputy. Disruption means taking a site offline, locking an account, or sending an email to all customers. The deputy matters more than the primary, because incidents happen during holidays. At the agency, the director was at a wedding and nobody had decided whether that meant yes or no.

Where the credentials for critical systems live, and how to reach them without the systems. If your password vault is reached through a single sign on account and that account is the one compromised, you have a circular dependency. A printed emergency access sheet in a locked drawer is an unfashionable answer that works, and the safer version of it is described in the notes on leaving emergency access to your password vault.

Your legal clock. Under UK and EU data protection rules, a personal data breach that meets the risk threshold must be reported to the regulator within 72 hours of becoming aware of it, and affected individuals told without undue delay if the risk to them is high. In the United States it depends on your state and sector, and several windows are 30 days from discovery. Write your specific obligation on the page as a number, because at hour four nobody wants to read legislation.

Your insurer's requirement. If you hold cyber insurance, the policy almost certainly names a hotline and almost certainly says you must call before engaging your own incident responder. I have seen a claim reduced over this. The phone number belongs on the page next to the policy number.

The page itself

Here is the shape I suggest. Times are from the moment someone says something is wrong, and the owner column is the point of the whole exercise.

WindowWhat happensWho
First 5 minutesTell the named lead by phone, not email. Write down the time and what you saw.Whoever noticed
5 to 20 minutesDisconnect affected machines from the network. Do not power them off.Whoever is nearest
5 to 20 minutesForce a password reset and sign out all sessions on the affected accounts.Named lead or deputy
20 to 60 minutesCall the insurer hotline. Start a plain text log with timestamps.Named lead
1 to 4 hoursEstablish what data was reachable from the compromised account.Named lead plus owner of that system
Within 24 hoursDecide on regulator notification against the written threshold.Director, advised by the lead
Within 72 hoursNotify the regulator if required. Prepare customer wording.Director

Below the table, three blocks of contact details: internal people with mobile numbers, external parties including your insurer and your IT provider, and the regulator's reporting page. That is the page. Print it, put one copy on the wall near the kettle and one in the top drawer, and keep a photograph of it on two phones.

The log is the part people skip and the part that pays for itself. A plain text file with a line per action and a timestamp is what lets you answer the only hard question that comes later: when did you become aware. Written retrospectively from memory three weeks on, that answer is a guess, and a guess is a poor thing to give a regulator.

Two instincts to override

The first is pulling the power. Someone sees a ransomware note and switches the machine off at the wall, which feels decisive and destroys the memory contents that would have shown how the attacker got in. Unplug the network cable or turn off the wireless adapter instead. Isolate, do not shut down.

The second is tidying up. Deleting the phishing email, clearing the mailbox rules, wiping the machine and reinstalling. Every one of those actions removes evidence you may need to establish scope, and scope is what determines whether you have a notifiable breach or a bad afternoon. Screenshot first, export the message headers, then clean.

A third worth mentioning, which is less an instinct than a pattern: telling customers before you know anything. An email saying we may have had a security issue and are investigating creates a week of questions you cannot answer and often has to be corrected. Hold until you know which data and whose. The exception is active fraud against a specific client, as in the invoice case, where a phone call within the hour is the right thing to do.

Then test it, because an untested plan is a document rather than a capability. Twenty minutes, once a quarter, over coffee. Read a scenario out loud and ask who does what. The agency ran their first one in January and discovered their deputy had left the company in August, which is exactly the kind of thing that only surfaces when somebody asks. Two related gaps that the same exercise tends to expose are covered in the notes on offboarding an employee securely and on a backup plan that survives ransomware. More practical material for teams without an IT department sits in the business security section.

FAQ

Do we really need a written plan for a team of ten?

You need the one page. The value is not the document, it is having decided in advance who can lock an account without asking. That single decision is what turns a ninety minute scramble into a twenty minute response.

Who should be the named lead?

Whoever can be reached fastest and has authority to disrupt, which in a small company is often an operations person rather than the most technical person. Name a deputy with the same authority and make sure both are not on the same holiday.

When does the 72 hour clock start?

From when you become aware of a breach, not from when you finish investigating or from when it happened. That is why the timestamped log matters, and it is also why you should write the time down in the first five minutes while it is still accurate.

Should we pay a ransom?

That is a decision for the director with legal and insurer advice, not something to settle in the moment, and in several jurisdictions payment to sanctioned groups is itself unlawful. What your page should say is that the decision belongs to a named person and that nobody else opens a conversation with an attacker.

DN
Devika Nair

Priya writes about privacy and data protection for ordinary users and small teams, cutting through legal jargon to what actually matters.

More posts by Devika

More in Business Security

01doorganico 084goad 3hot8 4465456 after5internprogram ahandfulofblessings ahmadpc allodialresources annodex antiquesandperiodcollectibles aotc asianworldkashmir beedlectrics bloggertemplatefree bluefeatheragency bodyweightsolution campaign08blog carfixadvisor catstreetcollective cbstvsports cnfanspurchasing committeeof500yearsofdignityandresistance covertopsdjs cs-kaiyuangame cuestacomunicaciontotal cxoutlet dancebetgame deskgearhub destinyvillastay detectmagazine di33 diamondsteelbuildings donmo dyanadropship emarsysfinance emimattl escapechan eskitarih evautoplay everythingweddings-orlando farmzone feedviewerapp foxstudiosscratch gamevui123 gleasongrade greetingsday hacklabasu haskell iw-kaiyun jagoanproperti jilidskripsi joltbusinessfinance juegodepokergratis juegospucca kaeru-festival latestmehndidesigns lestanzediottaviano litemagazines localcommunityhero lustrsazan mariashebets menswheels newwebstechs1 nikkit ootheday oxigenvpn plurfitness prefetial probudgetcarpetcleaning psychicmrsmartin pyaten qvantor rejoignezlogis rexzbot riselayouts ruchin rwxqsgd5 sakaltime shibiaowang shop-bot skrtips spotlesshaven strcoding tetapatrium topselller uneplanteartificielle vipertechcr webtech1223411 wo-kygaming yamaha-mekar yeknava yoybuysheets zenunwa yamaha-mekar jilidskripsi ankertoto ankertoto ankertoto