←Sukoon home
Live simulation

72-Hour Incident Response Clock

A tabletop exercise: the breach is detected, the clock starts. Complete each step before its deadline: contain, report to the cybercrime authority, notify the regulator and users.

GDPRPECAPDPB
72h
to GDPR Art. 33
T + 0h
Contain: isolate systems, revoke keys and sessions
Security Lead · Internal service level and Secure SDLC runbook
PENDING
T+1h
Assess scope, data categories and risk to individuals
DPO · GDPR Art. 33(3) content requirements
PENDING
T+4h
Report to the national cybercrime authority
Legal Counsel · PECA 2016 unauthorized access and data offences; internal 24-hour target
PENDING
T+24h
Notify the data protection authority
DPO · GDPR Art. 33, within 72 hours; draft PDPB, without undue delay
PENDING
T+72h
Notify affected users in plain language
Product Owner · GDPR Art. 34, where there is a high risk to rights and freedoms
PENDING
T+72h
Forensic report and root-cause analysis
Security Lead · Art. 33(5) documentation duty
PENDING
T+168h
Blameless post-mortem and control improvements
Engineering Manager · Secure SDLC feedback loop
PENDING
T+336h

Statutory: GDPR Art. 33 (72h) and Art. 34. Other deadlines are Sukoon's internal targets. The authority name and PECA reporting route should be confirmed with counsel before use (industry validation).