Back to all insights
Incident response9 min

The first 72 hours after a data breach: poor preparation creates a second incident

The first problem is the breach. The second is not knowing who must do what. GDPR uses a 72-hour window for supervisory notification where the breach is likely to create risk; preparation determines whether that window is used for evidence or confusion.

Incident response team reviewing a security event at night
01

The clock starts when the organization becomes aware

Notification does not wait for perfect certainty. Record the nature of the breach, approximate people and records, likely consequences and measures taken; provide missing information in phases where justified.

No log access, no data inventory or a slow processor response does not stop the clock. Preparation failures create late and inaccurate notification risk.

02

Preserve evidence while containing spread

Isolate affected systems without destroying logs or disk evidence. Rotate keys, evaluate sessions and investigate persistence. Record each step with time and owner.

Wiping everything may look decisive, but it can destroy the ability to determine scope and prove the response.

  • Name an incident commander
  • Preserve logs and evidence
  • Map affected data and people
  • Unite legal, technical and communication records
03

Regulator notice and user communication are different

A regulator notification addresses supervisory duties. Communication to affected individuals must be understandable and actionable—password reset, card monitoring or phishing precautions where relevant.

Overstating uncertain facts can be as damaging as hiding a known risk.

04

Write the 72-hour plan before the incident

Build contact lists, decision matrices, log retention, alternative channels and notification templates in advance. A plan never rehearsed usually fails under pressure.

Is your 72-hour plan ready?

Who declares an incident?

Can logs be reached outside office hours?

Is the processor and data inventory current?

Are regulator and user templates prepared?

Must every security event be reported?

No. Classification depends on whether personal data was breached and the resulting risk; technical and legal assessment should be combined.

What if details are incomplete after 72 hours?

An initial notification can use available facts and be completed in phases with reasons for delay.

Official sources and references

  1. EU General Data Protection Regulation – Articles 33 and 34
  2. Turkish DPA – Personal data breach notification

This is general technical information, not legal advice. Obtain advice from a qualified legal professional for your specific circumstances.

KEON REVIEW

Do not write the first-response plan on breach day.

We can prepare the incident workflow, ownership matrix, evidence list and 72-hour control for your systems.

Request a technical compliance review