Davis & Co All articles
Contracts & Risk

When the Laptop Goes Missing: A Boardroom Plan for the First Three Days of a Data Incident

Davis & Co
When the Laptop Goes Missing: A Boardroom Plan for the First Three Days of a Data Incident

Photo: business team incident response meeting laptop security UK office, via img.freepik.com

A missing laptop, a misdirected email or a ransomware message on a finance terminal can all start the same clock. Under the UK GDPR, where a personal data breach is likely to result in a risk to individuals' rights and freedoms, the Information Commissioner's Office must be notified without undue delay and, where feasible, within 72 hours of the organisation becoming aware of it. That period is not a deadline for completing a forensic investigation. It is a deadline for making, recording and acting on a considered decision.

For UK directors, the response is therefore as much a boardroom matter as a technical one. The company needs a short, workable plan that identifies who decides, who preserves evidence, who communicates and how the decision is recorded. The aim is not a perfect answer within three days. It is a defensible process that can withstand later scrutiny.

The clock starts with awareness, not certainty

A company becomes aware of a breach when it has a reasonable degree of certainty that a security incident has occurred and led to personal data being compromised. That does not require every fact to be established. Directors should resist two opposite errors: treating every alarm as a notifiable breach, and waiting for a complete picture before involving the right people.

The practical sequence is triage, containment, assessment and decision. The incident lead should establish what is known, what is not known and what immediate containment has been taken. Legal advice should be sought early where notification, contractual obligations or potential litigation are in view. Insurers should be contacted in line with policy requirements, and any processor involved should be required to provide its own account promptly.

Where notification to the ICO is required, it should be made on the basis of the information available at the time, with further details supplied later if necessary. Where the company decides that notification is not required, the reason should be recorded in the incident log. A silent decision is difficult to defend; a documented one is far easier to explain.

Assign roles before the incident, not during it

A small company does not need a large incident team, but it does need separate responsibilities. One person should act as incident lead, normally a senior director with authority to commit resources and make notification decisions. A deputy should be named in case that person is unavailable.

An evidence custodian should be responsible for preserving logs, devices, emails, access records and CCTV without altering them. This is not the same as the person investigating the cause. Containment should sit with an operations or IT lead who can isolate accounts, change credentials and block access. A communications lead should prepare internal and external messages, including customer and supplier contact where necessary. A board liaison should keep the rest of the directors informed and ensure that decisions are minuted.

In a very small business, one individual may hold more than one role. That is acceptable if the plan records the combination and the conflict. What is not acceptable is an unwritten assumption that 'IT will deal with it'. Data protection incidents frequently require commercial, contractual and regulatory judgments that sit beyond the IT function.

A one-page incident log

The incident log should be started at the first report and kept as a single controlled document. It should record facts, actions and decisions in chronological order. A simple format is often more useful than an elaborate template.

Field What to record
Time and date When the report was received and when each action was taken
Source Who reported the matter and how
Fact or allegation What is known, clearly separated from assumption
Action taken Containment, preservation, investigation or communication
Owner The named person responsible
Evidence location Where relevant logs, devices or correspondence are held
Decision Whether to notify, delay, escalate or take no further action, with reasons

The log should not be rewritten to look tidier after the event. Corrections should be added with a time and initials. Where a decision is taken not to notify the ICO, the log should state the assessment made and the information on which it was based. This is the record that will answer the question every regulator, insurer and customer will eventually ask: what did you know, when did you know it, and what did you do?

First 72 hours: a workable sequence

In the first four hours, the priority is to stop further loss and preserve evidence. The incident lead should convene a short call, confirm the roles and open the log. The operations lead should contain the incident without destroying records; for example, by disabling an account rather than wiping a device. The evidence custodian should secure relevant material and record who has access.

Between four and 24 hours, the company should establish the likely scope: whose data, what categories, how many individuals, and whether the data has been accessed, disclosed or lost. Legal and insurance contacts should be engaged. If notification looks likely, a draft ICO report should be prepared rather than waiting for a final conclusion.

Between 24 and 48 hours, the incident lead should make a notification decision, or record why it is being deferred. Communications should be prepared for staff, customers and processors as appropriate. If there is a high risk to individuals, they should be informed without undue delay. The board should receive a short factual update.

By the end of the 72-hour period, the company should either have notified the ICO or have a documented reason why not. The log should be up to date, further actions should be assigned, and a review date should be set. Notification is not the end of the matter; it is a milestone in an ongoing process.

A test scenario that exposes gaps

A useful rehearsal is a 90-minute tabletop exercise. The scenario: a finance director's laptop is stolen from a car outside a hotel in Birmingham. The laptop contains payroll records and customer bank details. The device is encrypted, but a shared password was written in a notebook in the same bag. Staff are unsure whether the notebook was taken.

The exercise should test five questions. Who calls the insurer? Who preserves access logs and CCTV requests? Who decides whether the ICO threshold is met? Who drafts the customer message if bank details may be at risk? Who informs the board and records the decision? The answers usually reveal that contact details are out of date, that no one has authority to approve notification, or that the company cannot quickly identify which customers are affected.

The output should be a short action list, not a score. Update the contact sheet, confirm who can authorise notification, test remote wiping and encryption, and check that processor contracts require prompt breach notification. Repeat the exercise annually or when key personnel change.

A data incident will never be convenient. The purpose of the plan is to make the first three days less improvised. Directors who assign roles, keep a contemporaneous log and rehearse the decision points will be in a far stronger position when the regulator, the insurer or the customer asks for an explanation.

All Articles

Related Articles

Who Still Holds the Keys? A Director’s Review of Shared Logins and Approval Rights

Who Still Holds the Keys? A Director’s Review of Shared Logins and Approval Rights

Small Print, Long Term: Regaining Control of Office Equipment Leases

Small Print, Long Term: Regaining Control of Office Equipment Leases

The Debt That Outlives the Company: A Creditor’s Guide to Strike-Off and Restoration

The Debt That Outlives the Company: A Creditor’s Guide to Strike-Off and Restoration