Discovering that personal data may have been lost, stolen or exposed is stressful. Perhaps a laptop has gone missing, an email went to the wrong person, or a member of staff clicked a link and now strange messages are coming from their mailbox. Your first thought is probably: what do I do now, and do I need to tell anyone?
This guide explains what to do in the first hours and days, how reporting a data breach to the ICO works for a small business, and how to get back on your feet.
First, what counts as a personal data breach?
Under UK GDPR, a personal data breach is any security incident that leads to the accidental or unlawful destruction, loss, alteration, unauthorised disclosure of, or access to, personal data. That is broader than many people expect. It is not only hackers. It can include:
- An email containing customer or pupil details sent to the wrong recipient
- A lost or stolen phone, laptop or USB stick that isn't encrypted
- A compromised Microsoft 365 account where an attacker could read emails
- Ransomware that encrypts files, even if nothing appears to have been copied
- Paper records left somewhere they shouldn't be
If personal data has been put at risk, treat it as a possible breach until you know otherwise.
The first few hours: contain the problem
Before you worry about paperwork, stop things getting worse. Speed matters, but so does staying calm.
- **Isolate affected devices.** If you suspect malware or ransomware, disconnect the machine from the network (unplug the cable or turn off Wi-Fi). Don't wipe or switch it off unless advised, as this can destroy useful evidence.
- **Secure compromised accounts.** Reset passwords, sign the user out of all sessions and make sure multi-factor authentication is switched on. Check for mailbox rules that forward or delete email, a common trick attackers use.
- **Recall or request deletion.** If data was sent to the wrong person, contact them, ask them to delete it and confirm in writing.
- **Block remote access** for missing devices if you have device management in place.
- **Bring in IT help** if you don't have the skills in-house. A good IT support provider can investigate what happened and what was accessed.
Start a record straight away
Write down what you know as you go: when the breach was discovered, who found it, what systems and data are involved, roughly how many people are affected and what actions you have taken. This log helps you make decisions, and you are legally required to keep a record of all personal data breaches, even ones you decide not to report.
Do you need to report it to the ICO?
You must report a breach to the Information Commissioner's Office within 72 hours of becoming aware of it, unless it is unlikely to result in a risk to people's rights and freedoms.
A few important points:
- **The clock starts when you become aware**, meaning when you have a reasonable degree of certainty that a breach has happened, not when it occurred.
- **72 hours means 72 hours.** Weekends and bank holidays count.
- **You don't need every answer before reporting.** If your investigation is ongoing, you can report what you know and provide more details later.
- **If you're late**, you should still report and explain the reason for the delay.
To judge the risk, think about the consequences for the individuals. Could they suffer financial loss, identity fraud, distress, discrimination or damage to their reputation? Health information, financial details, information about children or vulnerable adults, and passwords all tend to raise the risk. A single email with a business contact's name sent to a colleague's wrong address may be low risk; a spreadsheet of client bank details sent outside the organisation almost certainly is not.
If you're unsure, the ICO website has a self-assessment tool and guidance, and you can report through its online form or by phoning its helpline. When in genuine doubt, many organisations find it safer to report and explain their reasoning.
Telling the people affected
If the breach is likely to result in a high risk to individuals, you must also tell them without undue delay. Use plain language, explain what happened, what data was involved, what you're doing about it and what they can do to protect themselves, such as watching for phishing emails or changing passwords.
Other people you may need to tell
Depending on your organisation, think about:
- **Your cyber insurer**, who may have specific notification requirements and incident response support
- **Your bank**, if payment details or fraud are involved
- **The police**, via Action Fraud, if a crime such as hacking or fraud has occurred
- **The Charity Commission**, if you're a charity and the incident is serious
- **Your local authority, trust or regulator**, if you're a school or care provider with sector reporting obligations
- **Clients or partners**, if you process data on their behalf, as your contracts may require prompt notice
After the dust settles: learn and strengthen
Once the immediate crisis is over, look honestly at how it happened. Common lessons include:
- Turning on multi-factor authentication for every Microsoft 365 account
- Encrypting laptops and phones and managing them centrally
- Keeping software and devices patched and monitored
- Having reliable, tested cloud backups that ransomware can't reach
- Giving staff regular, practical training on phishing and handling data
- Writing a simple incident response plan so everyone knows who does what next time
The ICO looks favourably on organisations that respond quickly, are open about what went wrong and can show they've taken steps to prevent it happening again.
We're here to help
If you're dealing with a suspected breach right now, or want to make sure you're better prepared, Cloud 4 Sure can help. We support businesses, schools, charities and care providers across Sussex, Surrey, Hampshire and Kent with investigation, recovery and practical cyber-security. Get in touch with our team, or book a free IT health check to find the gaps before someone else does.
