Incident and Data Breach Response Procedure

What we do when something goes wrong with security or personal data, including how quickly we tell clients and the Information Commissioner's Office, and how we learn from it.

1. Purpose and scope

This procedure explains how Carefully Coded Ltd detects, handles, reports and learns from information security incidents and personal data breaches. It applies to everyone who works for us and to all systems, devices, data and installed equipment covered by our Information Security Policy.

An incident is any event that has, or could have, harmed the confidentiality, integrity or availability of information or services. Examples include:

  • a lost or stolen laptop or phone;
  • a compromised account or password;
  • malware or ransomware on a device or server;
  • unauthorised access to a system, database or installed device;
  • client data sent to the wrong person;
  • a service outage caused by an attack or failure;
  • tampering with hardware installed on a client site.

A personal data breach is an incident that leads to the accidental or unlawful loss, destruction, change, disclosure of, or access to, personal data.

Where a client contract sets shorter notification timescales than this procedure, the contract takes precedence.

2. Notification commitments

Who we notify When Who sends it
The affected client (including any council) Within 24 hours of becoming aware of an incident affecting their data or services Tom Emmerson
The affected client: written root-cause report Within 10 working days of becoming aware of the incident Tom Emmerson
Information Commissioner's Office (ICO), where we are the controller Within 72 hours of becoming aware of a reportable personal data breach Tom Emmerson, Director
Affected individuals, where we are the controller Without undue delay, where the breach is likely to result in a high risk to them Tom Emmerson, Director
Police or Action Fraud Where a crime is suspected Tom Emmerson

Where we process personal data on a client's behalf (as a processor), we notify the client within 24 hours and support them in making any notification to the ICO or individuals. We do not notify the ICO on their behalf unless they ask us to in writing.

We will send the initial 24-hour notice even if we do not yet have full details, and follow up as we learn more.

3. Severity levels

Severity Description Examples Response
Critical Confirmed compromise of client data or services, or major loss of service Ransomware on a server holding client data; confirmed data breach; installed equipment taken over Start containment immediately, at any time of day. Notify client within 24 hours.
High Likely compromise, or serious risk to client data or services Stolen unencrypted device; compromised admin account; suspicious access to a production system Start containment the same day. Notify client within 24 hours if their data or services are affected.
Medium Limited impact, contained quickly, no confirmed loss of client data Lost encrypted laptop; phishing email clicked but no credentials entered; minor outage Respond within 1 working day. Assess whether client notification is needed.
Low Near miss or minor policy breach with no impact Suspicious email reported; screen left unlocked in the office Record and review within 5 working days.

If in doubt, we choose the higher severity.

4. Response phases

4.1 Detect and report

Anyone who suspects an incident must report it straight away to the director by email to tom@carefully.codes or by phone. Do not try to investigate alone and do not delete evidence. Clients, suppliers and members of the public can report incidents to the same contacts. Security vulnerabilities can also be reported as set out in our Vulnerability Management, Patching and Secure Development Policy.

The person receiving the report opens an entry in the incident log (see section 5) and records the time we became aware. This time starts all notification clocks.

4.2 Contain

We act quickly to stop further harm. Depending on the incident, this may include:

  • disconnecting affected devices from networks;
  • disabling compromised accounts and resetting passwords, keys and tokens;
  • remotely locking or wiping lost devices;
  • blocking malicious traffic or isolating affected services;
  • working with the client to secure installed equipment on their site.

We preserve evidence, such as logs and affected files, before making changes where it is safe to do so.

4.3 Assess

We work out what happened, which systems and data are affected, how many people may be affected, and the likely consequences. We set or revise the severity level and decide who must be notified.

4.4 Notify

We notify the parties in section 2 within the stated timescales. Each notification includes, as far as known:

  • what happened and when;
  • the data, systems or services affected;
  • the likely impact;
  • what we have done and plan to do;
  • a contact for further information.

ICO notifications follow the ICO's current reporting process. Our ICO registration number is ZB512909.

4.5 Recover

We restore affected systems and data from trusted sources, using our Business Continuity, Disaster Recovery and Backup Plan. We confirm systems are clean and secure before returning them to service, and monitor them closely afterwards.

4.6 Learn

Within 10 working days of becoming aware of an incident affecting a client, we send them a written root-cause report covering:

  • a timeline of events;
  • the root cause;
  • the impact;
  • actions taken;
  • actions to prevent it happening again, with owners and dates.

For every Critical or High incident we hold a recorded review, even if no client was affected. Actions are tracked to completion and lessons are reflected in our risk register, policies and training.

5. Incident log

We keep an incident log for every incident and near miss, whatever its severity. Each entry records:

  • the date and time we became aware, and who reported it;
  • a description and severity level;
  • systems, data and clients affected;
  • containment and recovery actions, with times;
  • notifications made, to whom and when, and the reason if we decided not to notify;
  • the root cause and follow-up actions.

The log is reviewed at every management review. It is kept for at least 6 years, or longer if set out in our Data Retention Policy. Clients may see entries relating to their data or services on request.

6. Key contacts

Contact Details
Incident lead Tom Emmerson, tom@carefully.codes
Data protection lead Tom Emmerson, Director, tom@carefully.codes
Deputy incident lead (if the director is unavailable) Another member of our team, nominated by the director
Information Commissioner's Office ico.org.uk, 0303 123 1113
National Cyber Security Centre (NCSC) ncsc.gov.uk (report a significant cyber incident)
Action Fraud actionfraud.police.uk, 0300 123 2040

Client-specific incident contacts are recorded in each client's project file.

8. Testing this procedure

We test this procedure at least every 12 months with a short desk-based exercise, such as a simulated ransomware or lost-device scenario. We record the date, scenario, findings and actions.

Organisation
Carefully Coded Ltd
Version
1.0
Owner
Tom Emmerson, Director
Effective from
19 November 2026
Next review
19 November 2027

Questions about this policy? Email info@carefully.codes.