Respond to a data breach: a step-by-step guide for small business
What to do in the first hour, the first day and the weeks after a data breach: contain it, investigate, know who to notify and by when (including the 72-hour EU and UK rule), write the notice and learn from it.

A lost laptop, a phishing email that handed over a password, a spreadsheet sent to the wrong customer, a supplier that gets hacked: most data breaches begin as small, ordinary mistakes. What turns them into crises is what happens in the first hours, when nobody is sure who is in charge, whether to switch things off, or whom they have to tell.
This guide gives a small business a calm, practical plan for responding to a data breach. It follows guidance from the US Federal Trade Commission (FTC), the UK Information Commissioner's Office (ICO) and the European Commission, and it is general information, not legal advice. Breach rules vary by state, country and industry, so call a qualified attorney early.
What counts as a data breach?
The ICO describes a personal data breach as a security incident that affects the confidentiality, integrity or availability of personal data, and it can be accidental or deliberate. It covers more than theft: sending data to the wrong recipient, changing data without permission, or making data unavailable in a way that significantly harms people all qualify.
Common small business examples:
- A stolen or lost laptop or phone with customer data on it
- A staff account taken over after a phishing email
- Ransomware that locks or copies your files
- A misconfigured shared folder or website form that exposes records
- A supplier or software vendor that you rely on being breached
- An email with an attachment sent to the wrong person
The first hour: contain it
The FTC's breach guide stresses acting quickly and fixing the cause, noting that the only thing worse than a breach is repeated breaches. Its advice for stopping further loss includes:
- Take affected equipment offline right away, but leave machines powered on until forensic experts arrive so evidence is preserved.
- Change credentials and passwords for affected accounts. A stolen credential keeps the door open until it is changed.
- Secure physical areas involved, for example by locking them and changing access codes.
- Monitor entry and exit points, especially those used in the incident.
- Remove exposed information from the web if it was posted, and ask search engines to drop cached copies.
- Do not destroy evidence. Avoid wiping or rebuilding systems until investigators say it is safe.
Name one person to lead the response. The FTC suggests assembling a team that, depending on your size, may include IT, legal, operations, HR and communications. In a five-person firm that might be you, your IT contact and your attorney.
Hours 2 to 24: investigate and document
Bring in help
The FTC recommends hiring independent forensic investigators who can find the source and scope of a breach, capture images of affected systems and advise on remediation. It also recommends consulting counsel with privacy and data security experience, starting with your own attorney. Check whether your insurance policy covers breach response and whether the insurer must be notified first. Our guide to cybersecurity basics covers prevention that makes these calls less likely.
Write down what you know
Keep a running log with dates and times, who discovered it, what was affected, what you did and who you contacted. The ICO says organisations must record all breaches, including ones they decide not to report, covering the facts, the effects and the action taken. A good log also helps your lawyer and any regulator.
Questions to answer:
- What kind of data was involved (names, emails, payment details, health or ID numbers)?
- How many people are affected, and where do they live?
- Was the data encrypted?
- Is the weakness fixed, or could it happen again tomorrow?
- Did a supplier or contractor hold the data?
Who to tell, and by when
Notification is the part that worries owners most, because the rules depend on where your customers live. Treat this table as a map, not a rule book.
| Who | When | Source | |---|---|---| | Your attorney and insurer | Immediately | FTC guidance | | Local police or law enforcement | Promptly, especially where identity theft is possible | FTC guidance | | Data protection authority (EU or UK) | Within 72 hours of becoming aware, if the breach is likely to risk people's rights and freedoms | European Commission, ICO | | Affected individuals | Without undue delay if high risk (EU or UK); quickly under US state law | EC, ICO, FTC | | Other businesses whose data you hold, or institutions holding affected accounts | As soon as possible | FTC guidance | | Credit bureaus | If Social Security numbers were taken, or a large group is affected | FTC guidance |
United States
According to the FTC, all states, the District of Columbia, Puerto Rico and the Virgin Islands have breach notification laws, and federal or industry rules may also apply. The National Conference of State Legislatures also notes that private businesses must comply in every one of these jurisdictions. The laws typically define covered information, what counts as a breach, notice timing and method, and exemptions such as encrypted data, and they differ in the details, so check the laws of each state where affected people live. If health information is involved, ask your attorney about the FTC Health Breach Notification Rule and HIPAA.
California adds a legal incentive: the Attorney General says consumers can sue after certain breaches, with statutory damages that can reach $750 per incident after written notice and a 30-day chance to cure.
EU and UK
The European Commission says you must notify the supervisory authority within 72 hours of becoming aware of a breach that is likely to risk people's rights, and tell affected individuals when the risk is high. Encryption or other protections can make the risk unlikely, which can remove the need to tell individuals. The ICO adds that if you are late you must explain why, that you can report in phases when you cannot investigate fully in time, and that a report should include a description of the breach with approximate numbers, a contact point, the likely consequences and the measures taken. See the ICO's breach guide. If you are a processor handling data for others, you must report every breach to the controller.
Writing the notice to affected people
The FTC suggests telling people quickly so they can limit misuse, coordinating timing with law enforcement, naming one point person for information, and using letters, a web page and a toll-free number where useful. A clear notice usually covers:
- What happened, in plain words
- What information was involved
- What you are doing about it, including fixes and any free credit monitoring (the FTC suggests offering at least a year when financial data or Social Security numbers are exposed)
- What people can do, such as watching accounts, placing a fraud alert or credit freeze, and reporting misuse at IdentityTheft.gov
- How to reach you, and how you will and will not contact them, so scammers cannot imitate you
Do not downplay it or withhold details people need to protect themselves.
After the incident: fix and learn
- Close the gap. Fix the vulnerability, review what your vendors can access and confirm their fixes work.
- Review access. Remove accounts and permissions that are no longer needed. Our guide on roles and permissions explains least-privilege access.
- Turn on multi-factor sign-in if it was missing. See our MFA rollout plan.
- Restore from clean backups. Our guide to backing up business data explains how.
- Hold a short review: what failed, what worked, what changes.
- Keep less data. What you do not hold cannot be exposed. See data retention and deletion.
Common mistakes
- Waiting to be sure. The 72-hour clock in the EU and UK starts when you become aware, not when the investigation ends.
- Wiping systems too soon, which destroys evidence.
- Telling nobody internally. Staff need to know whom to alert, and quickly.
- Skipping the log. If you cannot show what you did and why, a regulator or insurer may doubt it.
- Over-sharing or under-sharing publicly. Both can cause harm. Coordinate wording with counsel.
- Forgetting suppliers and customers whose data you hold for them.
- No rehearsal. A plan nobody has read is not a plan.
A one-page breach plan to write this week
- Name a response lead and a backup.
- Write the phone numbers of your attorney, IT support, insurer and bank.
- List where personal data lives and who can access it.
- Agree who may speak to customers and the press.
- Prepare a template notice with the headings above.
- Practise once: pick a scenario and walk through it in thirty minutes.
Where WorkBOS fits
A breach plan is easier when you know where your customer information is and who has access to it. WorkBOS keeps contacts, projects, invoices and documents in one place, offers roles and permissions, and keeps an audit log of who did what, which helps when you are reconstructing events. It does not replace security tooling, forensic experts or legal advice. You can compare plans on the pricing page, and the docs and Academy explain how to set up access.
Frequently asked questions
Q: Do I have to report every breach? A: Not necessarily. Under EU and UK rules you report breaches likely to risk people's rights, though you should record all of them. US rules vary by state, and many depend on the type of data involved. Ask your attorney.
Q: What is the first thing I should do? A: Contain it: take affected systems offline without powering them off, change affected credentials, preserve evidence and bring in your response lead and attorney.
Q: When does the 72-hour deadline start? A: When you become aware of the breach. If you cannot finish investigating in time, the ICO says you can provide information in phases.
Q: Should I offer free credit monitoring? A: The FTC suggests offering at least one year of free credit monitoring or identity protection when financial information or Social Security numbers are exposed.
Q: Can I be sued after a breach? A: In some cases. California, for example, lets consumers sue after certain breaches, with statutory damages that can reach $750 per incident.
This is general information and not legal advice. Sources are linked in the text above: UK Information Commissioner's Office, California Attorney General, the European Commission and the FTC.
Run it all from one place
Projects, clients, finance, people and AI employees in one system. Start free, no card needed.
Start free →