Kief Studio

What Happens in the First 24 Hours After a Data Breach

Protect

  • Published
  • Updated
  • 10 min read
A magenta ribbon narrowing to a bright point and fanning out, cover for a note on the first 24 hours after a data breach

TL;DR: The first 24 hours after a data breach decide how big it gets. Most breaches involve a person or an unpatched system, and many owners hear about it from a customer. In the first day: isolate affected systems without wiping them, reset credentials, call forensic help, preserve logs, and start the Massachusetts notice clock with a lawyer.

A data breach at a small business rarely looks like a movie. There is no skull on the screen and no countdown. It starts on an ordinary afternoon with a login page that looks right, or a server nobody patched, and the first sign is often a customer calling to ask about a strange email that came from you.

The businesses that come out of a data breach in decent shape are not the ones with the biggest budgets. They are the ones that knew who to call, did not wipe the evidence, and did the boring steps in the right order. This is that order, hour by hour, with what federal agencies and Massachusetts law actually say.

How does a data breach usually start?

With a person or a known hole, most of the time. Verizon's 2026 Data Breach Investigations Report found that the "Human element was present in 62% of breaches, a slight increase from the previous year's 60%." (Verizon 2026 DBIR Executive Summary (opens in a new tab)) That covers a stolen password, a convincing fake invoice, or someone sending a file to the wrong address.

The other big door is software nobody updated. The same report says "Exploitation of vulnerabilities is now the most common initial access vector for breaches. It has risen to 31%," while credential abuse is "down to 13%." It also found that "Only 26% of critical vulnerabilities" on CISA's Known Exploited Vulnerabilities list "were fully remediated by organizations in 2025." (Verizon 2026 DBIR Executive Summary (opens in a new tab))

Put those two facts side by side. Attackers are not inventing new tricks for a ten-person office. They use the password someone reused and the firewall update that has been waiting since spring. A data breach at a small business is usually a volume play, not a personal one.

Vendors matter too. Verizon reports that breaches with third-party involvement reached "48% of total breaches." Your payroll provider, your website host and your email platform are part of your attack surface whether you think about them or not.

What happens in the first hours of a data breach?

Person at a desk at night reviewing a list of user sign-ins on an administration console
The first job after a data breach is reading the sign-in history, not deleting it.

The first hour of a data breach: nothing seems wrong

Someone types a password into a fake login page, or a scanner finds an old plugin on your website. Nothing breaks. The page reloads, the person shrugs, and work goes on. That quiet is the problem. Nobody writes it down because nobody knows it happened.

The quiet hours of a data breach

An attacker with a working login does not need to break anything. They read the mailbox, look for invoices and customer lists, and set up a forwarding rule so they keep getting copies. If they found an unpatched server, they look for saved passwords and other machines they can reach. None of this sets off an alarm on a network where nobody reads the logs.

How most owners find out

Often from outside. A customer asks why you sent them new bank details. A vendor says your invoice looks odd. The website starts showing something you did not put there. IBM's 2025 Cost of a Data Breach study found that the average breach lifecycle, "the mean time to identify and contain a breach," dropped to "241 days," and credited the improvement to more organizations that "detected the breach internally." (IBM Newsroom, July 2025 (opens in a new tab)) Finding it yourself is faster than hearing it from a customer. That is the whole case for monitoring: the sooner a data breach is found, the less it costs.

What should you do in the first 24 hours after a data breach?

The Federal Trade Commission's guide for businesses opens with the instruction that matters most: "Move quickly to secure your systems and fix vulnerabilities that may have caused the breach." (FTC, Data Breach Response: A Guide for Business (opens in a new tab)) Here is how I break a data breach response into a first day.

Hour 0 to 1: stop the spread, keep the evidence

  1. Call your response people. The FTC says to "Mobilize your breach response team right away to prevent additional data loss." If you do not have a team, that is your IT provider, your insurer's breach line and a lawyer.
  2. Isolate, do not wipe. The FTC's wording: "Take all affected equipment offline immediately," but "don't turn any machines off until the forensic experts arrive." CISA's ransomware guide says the same thing in its own words: "Determine which systems were impacted, and immediately isolate them." (CISA #StopRansomware Guide (opens in a new tab)) Pull the network cable or disconnect Wi-Fi. A machine that is powered off may lose what was in memory.
  3. Write things down. Who noticed what, at what time, and what you clicked. Your notes become the data breach timeline your lawyer and insurer will ask for.

Hour 1 to 4: take the keys back

  1. Reset credentials. The FTC advises that you "update credentials and passwords of authorized users." Start with email, banking, payroll and any admin account. Reset from a clean device, not the one that may be compromised.
  2. Turn on multifactor authentication everywhere it is off. CISA puts it plainly: "Users who enable MFA are significantly less likely to get hacked." (CISA, More than a Password (opens in a new tab))
  3. Check for the attacker's leftovers. Mailbox forwarding rules, new admin users, new app connections and changed recovery phone numbers. These are how an attacker gets back in after you change the password, and they turn a contained data breach into a second one.

Hour 4 to 12: find the scope of the data breach

The FTC suggests you "Consider hiring independent forensic investigators to help you determine the source and scope of the breach." That is the question every later decision hangs on: which systems, which records, whose information, and over what dates. Do not guess in writing. "We are investigating" is a true sentence; "no customer data was affected" is not something to say until someone has checked.

This is where an incident response plan pays for itself. If you already know where customer data lives and which logs exist, a forensic team spends hours on the answer instead of days on the map.

Massachusetts law does not set a fixed number of hours. Chapter 93H says a business that owns or licenses personal information about a Massachusetts resident "shall provide notice, as soon as practicable and without unreasonable delay," once it "knows or has reason to know of a breach of security," and that notice goes "to the attorney general, the director of consumer affairs and business regulation and to such resident." (M.G.L. c. 93H, section 3 (opens in a new tab)) What counts as personal information, what the letter must say and what it must not say are set out in detail, and my wife Amelia, Kief Studio's co-founder and CEO, has written up the Massachusetts data breach notification requirements (opens in a new tab) step by step. Customers in other states bring their own rules; the FTC reminds businesses to "Check state and federal laws or regulations for any specific requirements for your business."

Two more calls belong in the first day. The FTC says "Notify law enforcement. Call your local police department immediately." CISA asks organizations to report cyber incidents "24/7 to [email protected] or 1-844-Say-CISA." (CISA (opens in a new tab)) Then tell your staff what to say and what not to say. One person answers customer questions. Everyone else points to that person.

What does a data breach cost?

The famous number is IBM's. Its 2026 Cost of a Data Breach Report puts "the global breach average" at "$4.99 million." (IBM Newsroom, July 2026 (opens in a new tab)) That average is drawn from the organizations IBM and the Ponemon Institute studied, and most are far larger than a Central Massachusetts shop. Do not read it as your bill. Read it as a list of the things that cost money: forensics, legal advice, notification letters, downtime and lost customers.

Ransomware is often how a data breach announces itself. Verizon reports that "Ransomware grew again to 48% of all breaches," that "69% of ransomware victims didn't pay," and that "The median amount of ransom paid" was "$139,875 in this year's reporting dataset." (Verizon 2026 DBIR Executive Summary (opens in a new tab)) Most victims refusing to pay tells you something useful: the ones who could restore from backups had a choice. I pulled the numbers for this state together in Massachusetts data breach statistics (opens in a new tab), and Amelia looked at what a data breach costs in Massachusetts (opens in a new tab) line by line.

The cost nobody prices well is time. Every hour spent finding a password, a vendor contract or a backup login during a data breach is an hour the attacker still has.

How do you prepare before a data breach happens?

NIST rewrote its incident response guidance in April 2025. SP 800-61 Revision 3 aims to help organizations "prepare for incident responses, reduce the number and impact of incidents that occur, and improve the efficiency and effectiveness of their incident detection, response, and recovery activities." (NIST SP 800-61 Rev. 3 (opens in a new tab)) For a small business, that comes down to a short list you can finish this month.

A one-page plan beats a binder

Picture a hypothetical: a dental office in Westborough with eight staff, a practice management system and a shared mailbox. Its whole data breach plan could fit on one page taped inside a cabinet:

  1. Who to call, in order: IT provider, insurer's breach line, lawyer, the practice owner. Phone numbers, not just email, because email may be the thing that is down.
  2. Where the data lives: patient records, billing, email, backups. One line each, with who has admin access.
  3. How to isolate: which switch, which cable, which account to disable first.
  4. Where the logs are: and how long they are kept.
  5. Who speaks: one person for patients, one for staff.

Close the doors attackers actually use

  • Multifactor authentication on email, banking, payroll and remote access. It is the cheapest control on this list.
  • Patch what is on CISA's known exploited list first. If only about a quarter of those flaws get fully fixed, closing yours puts you ahead of most targets.
  • Backups that live somewhere an attacker cannot delete. We wrote up the 3-2-1 backup rule in practice for small offices, and the difference between RTO and RPO tells you how much downtime and data loss you can live with.
  • Someone reading the signals. Logs nobody reads are not detection. Threat detection means a person or a system watching for the signs above and acting on them.
  • Train for the email that looks right. Amelia's piece on business email compromise (opens in a new tab) is a good one to hand to staff.

Then rehearse once. Sit down for an hour, pick a scenario such as "the office manager's mailbox was taken over on Friday," and walk the page. You will find the missing phone number before you need it.

Frequently asked questions

What is the first thing to do after a data breach?

Call your response people and isolate affected systems from the network without turning them off. The FTC says to take affected equipment offline but leave machines on until forensic experts arrive.

Should I turn off a computer that was hacked?

Disconnect it from the network, but do not power it off unless a forensic expert tells you to. Shutting down can erase evidence of what the attacker did.

How fast do I have to report a data breach in Massachusetts?

Chapter 93H says notice must go out as soon as practicable and without unreasonable delay, to the Attorney General, the Office of Consumer Affairs and Business Regulation and affected residents. Talk with a lawyer the same day.

How do most data breaches start?

Verizon's 2026 report found a human element in 62% of breaches, and exploited vulnerabilities were the most common way in at 31%. Stolen passwords and unpatched systems cover most small business cases.

Should a small business pay a ransom?

That is a decision for you, your lawyer and your insurer. Verizon found 69% of ransomware victims in its data did not pay. Tested backups are what give you that choice.

Do I need an incident response plan if I only have a few employees?

Yes, but it can be one page: who to call, where your data lives, how to isolate a machine, where logs are kept and who speaks for the business.

This article is general information, not legal advice. Kief Studio is not a law firm, and reading it does not create an attorney-client relationship. Laws and regulations change, so check the current text and talk with a licensed Massachusetts attorney about your situation.

Where we fit

Kief Studio is in Shrewsbury, and our threat detection and response work is built for the first day of a data breach before it happens. We inventory what you run, collect and correlate the signals that matter, and write the response path for each alert: who acts, what they check, what they do. During an incident we follow that path: contain, investigate, fix and report, and afterward we change the detection so the same thing is caught sooner. 3am is a retainer, not a default.

For the systems we build and host, managed security monitoring means we harden hosts before they go live, keep them patched, watch the signals and report what changed in plain language. Security is included on what we host. If you want to know what an attacker could reach today, a penetration test proves it with written authorization and a retest after the fix.

First conversation is free. No commitment.

Tell us what your first 24 hours would look like

Related articles

  1. Protect

    The Rise of Agentic Malware: Protecting Your Data Before It Thinks for You

    Agentic malware asks an AI model what to do mid attack. The documented cases from 2025, what is still hype, and six practical defenses for a small business.

    Brian Gagne

  2. Protect

    Small Business Backup in Central Massachusetts: The 3-2-1 Rule in Practice

    Small business backup for Central MA: the 3-2-1 rule, immutable and offline copies, what to back up beyond files, retention, testing restores and keys.

    Brian Gagne

  3. Protect

    Voice-Activated Browsing: The Real Risks of Talking to an AI Browser

    Voice-activated browsing risks, per research and regulators: inaudible commands, cloned voices, prompt injection, stored recordings, and a one-hour fix list.

    Brian Gagne