AML consumer data

Data breaches: the first 72 hours

An hour-by-hour plan for the first 72 hours of a data breach at an estate or letting agency: contain, assess, report to the regulator and tell clients.

Ava research teamPublished 6 min read

On this page
  1. Why agencies need a breach plan before they need it
  2. The legal clock in one paragraph
  3. Hours 0 to 4: contain
  4. Hours 4 to 24: assess the risk
  5. Hours 24 to 72: report and tell people
  6. Common agency breach scenarios
  7. After the first 72 hours
  8. Example: a phished lettings mailbox
  9. Build the plan now
  10. Frequently asked questions
  11. References

Key takeaways

  • A reportable breach must be notified to the regulator without undue delay and, where feasible, within 72 hours of becoming aware of it[1].
  • Where a breach is likely to result in a high risk to people, you must also tell them without undue delay, in clear and plain language[2].
  • Every breach must be documented, including ones you decide not to report[1].
  • Only 25% of UK businesses had a formal incident response plan in 2025/26, although 43% reported a breach or attack[3].

Why agencies need a breach plan before they need it

Breaches at agencies are rarely dramatic hacks. They are a tenancy agreement emailed to the wrong landlord, a negotiator's phone lost on a train with client WhatsApp threads, a phished mailbox forwarding messages to a stranger, or a filing box left in a vacant shop. Each one starts a legal clock the moment someone in the business becomes aware of it.

The numbers say most businesses will face something. In the 2025/26 government survey, 43% of UK businesses reported a cyber security breach or attack in the previous 12 months[3], and phishing was the most common type, affecting 38%[4]. Among businesses in the administration or real estate sector group, 83% said cyber security was a high priority[5]. Priority is not preparation, though: formal incident response plans were held by only 25% of businesses[3].

Incident response measures in UK businesses, 2025/26
Incident response measures in UK businesses, 2025/26Bar chart. Roles assigned to individuals: 39%; Guidance on who to notify: 34%; Guidance on when to report externally: 32%; Formal incident response plan: 25%.Roles assigned to individualsRoles assigned to individuals: 39%39%Guidance on who to notifyGuidance on who to notify: 34%34%Guidance on when to report externallyGuidance on when to report externally: 32%32%Formal incident response planFormal incident response plan: 25%25%Incident response measures in UK businesses, 2025/26Bar chart. Roles assigned to individuals: 39%; Guidance on who to notify: 34%; Guidance on when to report externally: 32%; Formal incident response plan: 25%.Roles assigned to individualsRoles assigned to individuals: 39%39%Guidance on who to notifyGuidance on who to notify: 34%34%Guidance on when to report externallyGuidance on when to report externally: 32%32%Formal incident response planFormal incident response plan: 25%25%

Source: Department for Science, Innovation and Technology (GOV.UK), 2026[3]

Show the data
ItemValue
Roles assigned to individuals39%
Guidance on who to notify34%
Guidance on when to report externally32%
Formal incident response plan25%

When a personal data breach occurs, the controller must notify the regulator without undue delay and, where feasible, not later than 72 hours after becoming aware of it, unless the breach is unlikely to result in a risk to people's rights and freedoms[1]. If you report later than 72 hours, you must give reasons for the delay. You can provide information in phases if you do not have it all at once[1]. Since 30 September 2026 the legislation names the regulator as the Information Commission, the successor to the ICO[1].

Aware means reasonably certain that a breach has happened, not the moment you finish investigating. A negotiator who realises on Friday evening that they emailed a tenant's referencing report to the wrong landlord has made the business aware on Friday evening.

Hours 0 to 4: contain

  1. Report internally at once

    Every member of staff should know one number or address for suspected breaches, and that reporting a mistake will not be punished; hiding one will.

  2. Stop the leak

    Recall or ask for deletion of a misdirected email, reset passwords on a compromised mailbox, remotely wipe a lost phone, and remove any forwarding rules a phisher has set up.

  3. Preserve evidence

    Do not delete the phishing email or wipe logs. Take screenshots, note times and keep the original messages for the investigation.

  4. Start the breach log

    Record when you became aware, who reported it, what happened and what you have done so far. Article 33 requires breaches to be documented in any case[1].

Hours 4 to 24: assess the risk

The decision to report turns on risk to people, not embarrassment to the agency. Work through the questions below with the compliance lead and, where needed, your IT provider.

Breach risk assessment for agencies (use with your own judgement and advice)
QuestionLower riskHigher risk
What data?Names and email addresses of applicantsPassports, bank details, referencing reports, health information
How many people?One or twoDozens or a whole mailbox
Who has it?A trusted recipient who confirms deletionUnknown attacker or a party in a dispute
Was it protected?Encrypted device with strong passwordUnencrypted laptop or open shared link
What harm could follow?Mild inconvenienceFraud, identity theft, distress, physical safety risk

Agency data skews towards the higher-risk column. Identity documents for money laundering checks, bank details for rent and completions, and referencing reports with employment and income details are exactly what fraudsters want. A phished mailbox is usually higher risk than it first appears, because attackers often watch for payment emails before acting.

Hours 24 to 72: report and tell people

If the breach is reportable, notify the regulator within the 72-hour window. The notification should describe what happened, including where possible the categories and approximate numbers of people and records; give a contact point; describe likely consequences; and describe what you have done or will do to address it[1]. If you are still investigating, report what you know and follow up.

Where the breach is likely to result in a high risk to people, you must also tell them without undue delay, in clear and plain language, including the contact point, likely consequences and the measures taken[2]. For agencies, that often means calling the affected landlords or tenants first and following up in writing, so they can act quickly, for example by watching their bank accounts or refusing unexpected payment requests.

Example (fictional) client message: "On Tuesday an email containing your referencing report was sent in error to another landlord. They have confirmed in writing that they deleted it. The report included your employment details and bank sort code but not your full account number. We recommend you treat any unexpected request for payment or personal details with caution, and call us on our office number if anything concerns you. We have reported this to the Information Commission and changed our process so referencing reports can only be sent from the CRM."

Common agency breach scenarios

  • Misdirected email: the most common. Ask the recipient to delete and confirm in writing; assess whether the content was sensitive enough to report.
  • Phished mailbox: reset credentials, check forwarding rules and sent items, warn clients whose payment emails may have been read, and assume reportable until shown otherwise.
  • Lost or stolen device: wipe remotely, check encryption, and list what client data was on it, including messaging apps.
  • Ransomware: isolate machines, call your IT provider and insurer, and treat it as a likely reportable breach even if data was only encrypted.
  • Paper files: lost inventory reports or ID copies left in a vacant property or bin; retrieve, assess and log.

After the first 72 hours

Containment and reporting are only half the work. Within a fortnight, hold a short review: what happened, why the controls did not stop it, and what will change. Then make the change. Misdirected emails usually call for address autocomplete to be switched off for external domains, or for sensitive documents to be sent only through the CRM. Phishing usually calls for two-step login and a rule that payment details are never changed on the strength of an email.

External reporting deserves thought too. Among businesses that identified breaches or attacks, only 40% reported their most disruptive breach outside the organisation[3]. Where fraud is involved, report to your bank and to Action Fraud as well as to the data protection regulator, and tell your insurer early. Our guide to bank detail change fraud covers payment-related breaches in more depth.

Example: a phished lettings mailbox

Example (fictional): on Monday morning a property manager notices replies to emails she never sent. IT finds that her mailbox was accessed after she entered her password on a fake login page on Friday, and that a rule has been forwarding emails containing the word invoice to an outside address. The agency becomes aware on Monday at 9.15am.

In this example, by noon the password is reset, the rule deleted and two-step login switched on for every mailbox. By the end of Monday the agency has listed the landlords and contractors whose emails were forwarded. On Tuesday it calls each landlord to warn them not to act on any email about changed bank details, and files a report with the regulator, explaining what is known and what is still being checked. A follow-up report on Thursday confirms that no payments were diverted. The breach log, call notes and reports are kept together for the file.

Build the plan now

  1. Name the breach lead and a deputy, with out-of-hours contact details.
  2. Write a one-page procedure covering contain, assess, report and tell, with the 72-hour clock on it.
  3. Prepare templates for the regulator notification and for client messages.
  4. Keep a contact list for your IT provider, insurer, bank and solicitor.
  5. Run a 30-minute exercise once a year using a realistic scenario such as a phished mailbox.
  6. Connect the plan to your Cyber Essentials controls so prevention and response reinforce each other.

Frequently asked questions

Do we have to report every breach?

No. You must notify the regulator unless the breach is unlikely to result in a risk to people's rights and freedoms, but you must document every breach, including the ones you do not report[1].

When does the 72-hour clock start?

When the business becomes aware of the breach, meaning reasonably sure it has happened[1]. Weekends count, so the plan must work out of hours.

Must we tell the affected tenants or landlords?

Yes, without undue delay, where the breach is likely to result in a high risk to them, using clear and plain language[2].

What if we do not have all the facts within 72 hours?

Report what you know and add information in phases without undue further delay[1]. If you report after 72 hours, explain why.

References

  1. legislation.gov.uk (The National Archives) (2016). UK GDPR Article 33: Notification of a personal data breach (opens in a new tab) ↑

  2. legislation.gov.uk (The National Archives) (2016). UK GDPR Article 34: Communication of a personal data breach to the data subject (opens in a new tab) ↑

  3. Department for Science, Innovation and Technology (GOV.UK) (2026). Cyber security breaches survey 2025/2026 (opens in a new tab) ↑

  4. Department for Science, Innovation and Technology (GOV.UK) (2026). Cyber security breaches survey 2025/2026 (opens in a new tab) ↑

  5. Department for Science, Innovation and Technology (GOV.UK) (2026). Cyber security breaches survey 2025/2026 (opens in a new tab) ↑

Book a demo

See Ava handle your calls.

Book a short demo. We’ll walk through your calls and workflow, and agree what Ava should take care of.

Book a demo