Blog

What a Breach Really Costs, and What to Do in the First 24 Hours

Nobody plans for a bad day, but the first 24 hours of a security incident shape how much it costs and how long it lasts more than almost anything that comes after. This post explains, without drama, where the costs of a breach actually come from, and then walks through the first day hour by hour.

Where the costs come from

Headlines tend to focus on ransom demands. For a company of 50 to 250 people, the ransom, if there is one, is often not the largest cost. The bill usually comes from several directions at once:

Downtime. Lost sales, idle staff, overtime to catch up, late deliveries and missed deadlines. For many companies, this is the biggest line, and it grows every day systems are down.

Investigation. A forensic firm works out how the attacker got in, what they touched and whether they're still there. This is skilled, specialized work, and it's necessary before you can safely say the problem is over.

Recovery. Rebuilding computers and servers, restoring data from backups and replacing anything that can't be trusted. Good backups make this days; poor ones can make it weeks.

Legal advice and notification. If personal information was exposed, laws in every U.S. state require notifying affected people under certain conditions; the National Conference of State Legislatures keeps a summary of those laws. Requirements vary by state and by type of data, so you'll want a lawyer who specializes in this, often called a breach coach. There may also be obligations under contracts with customers, or industry rules such as those for payment cards.

Customer and reputation costs. Time spent reassuring customers, credit monitoring offered to affected people, and business that quietly goes elsewhere.

Fraud losses. If the incident involved a fake invoice or redirected payment, the money itself.

Cyber insurance can cover many of these costs, depending on your policy, but only if it's engaged properly from the start. That's why the first 24 hours matter so much.

Hour zero: noticing

Incidents rarely announce themselves clearly. It might be a ransom note on screens, or something quieter: a customer asking about an invoice you never sent, a strange mailbox rule, an alert from your security software, or a bank calling about a transfer.

The most important thing in the first minutes is that the person who notices tells someone right away, without fear of blame. A company where staff feel safe saying "I think I clicked something" finds out hours or days sooner.

Hours 1 to 2: contain and call

Pull out your one-page incident plan. If you don't have one, our post on the one-page plan shows how to write it, and this is the moment you'll wish you had.

Disconnect, don't destroy. Take affected computers off the network by unplugging the network cable or turning off Wi-Fi. Don't power them off or wipe them unless IT tells you to; that can destroy evidence the investigators need.

Call your IT provider's emergency line. Not the general helpdesk queue.

Call your cyber insurer's claim hotline. This is the step owners most often delay, and it's the one that matters most for coverage. Many policies expect prompt notice and give you access to a pre-arranged team of breach lawyers, forensic investigators and, if needed, negotiators. Some may not cover firms you hire on your own before calling. Read your policy, but in general, call early.

Call your bank if any money may be involved. Speed can be the difference between recovering a transfer and losing it.

Hours 2 to 6: get the right people in the room

The insurer's process usually starts with a call with a breach lawyer, who coordinates the response. Involving a lawyer early is common because it helps structure the investigation and the communications appropriately.

Inside the company, a small group should take charge: the person named in your plan as in charge, your IT lead or provider, a communications lead, and finance if money is involved. Everyone else should know who to send questions to.

Use a separate channel. If email may be compromised, don't use it to discuss the incident. Use phones or a messaging app on personal devices until IT confirms email is safe.

Start a written log. What happened, when, who did what and who was told. It sounds tedious; investigators, lawyers and insurers will all ask for it.

Hours 6 to 24: first decisions

By the end of the first day, with your advisers, you'll be working on several questions:

  • What's affected, and is the attacker still in? Forensics will start answering this; it may take longer than a day.
  • Can we operate? Which processes can run manually, and which systems can be restored from backups safely?
  • What do we tell staff? Usually a short, honest message: there's an incident, we're working on it, here's what to do and not do, and here's who to ask.
  • What do we tell customers, and when? Your lawyer will guide timing and wording, especially if personal information may be involved.
  • If there's a ransom demand, don't respond on your own. That decision involves your insurer, your lawyer and sometimes law enforcement, and there can be legal restrictions on payments.

What makes the first day go well

When I ran IT at a company of about 200 people, the incidents that stayed small had the same things in common: someone reported a problem quickly, the right phone numbers were already written down, backups had been tested recently, and nobody tried to handle it quietly alone. None of that was expensive. All of it had to be set up before the bad day.

What to do Monday morning

  1. Find your cyber policy's claim hotline and policy number, and put them where your leadership team can reach them without company email.
  2. Confirm your IT provider's after-hours emergency number, and that someone will answer it.
  3. Tell staff plainly that reporting a possible mistake quickly is always the right thing, and that they won't be punished for it.
  4. Write or update your one-page incident plan with the first-hour rules: disconnect, don't wipe, don't pay, call the insurer.
  5. Ask your broker what your policy covers for downtime, investigation, notification and fraud, and what it expects from you in the first 24 hours.

All essays