Self-assessment

Score yourself

Answer each question honestly. Yes = 2, Partly = 1, No = 0. Keep a running total.

Your score

0/ 24

0 of 12 answered

Not scored yet

The definition

0 / 6

01 Is "what counts as a personal data breach" defined in writing, with triage and classification criteria?

02 Would a breach surfacing anywhere, security monitoring, a vendor's call, a customer's complaint, the press, route into one playbook?

03 Can you name, in minutes, which systems hold the personal data a given incident touches? The [record of processing](/enterprises/focus-areas/record-of-processing-and-dpia) should answer this.

The clocks

0 / 6

04 For each kind of incident you could have, do you know which clocks start: the Board, the six-hour national incident direction, your sector regulator?

05 Is there a regulator register: which authority gets what, in which format, on which clock?

06 Where a cyber insurance policy exists, are its notification conditions written into the plan? The [cyber insurance page](/resources/cyber-insurance) covers what to check.

The people

0 / 6

07 Are the notification templates drafted in advance: the Board intimation, the detailed report, the notice to affected people?

08 Is it written down, by name with deputies, who classifies, who approves notifying the Board, who approves telling affected people, who speaks externally?

09 Would those approvals actually work at 2 AM?

The practice

0 / 6

10 Do contracts oblige processors and vendors holding your data to tell you fast when they have an incident?

11 Does the plan reach partners holding your data, not only your own systems?

12 Have you run at least one tabletop drill, recorded it, and closed what it exposed?

Readiness bands for this self-assessment
Score Where you stand What to do next
0 to 8ExposedYour first breach would be handled by improvisation. Draft the templates and name the decision owners this quarter.
9 to 16HalfwayThe plan exists on paper. The gaps are usually partner reach and approval paths that fail out of hours.
17 to 21Strong baseDrill it. A tabletop with the real team is the only way to find what the paper hides.
22 to 24LeadingKeep the regulator register and templates current, and drill again after any organisational change.

Any single "No" is a named gap, whatever the total says. Nothing leaves your browser.

What the law expects

When a personal data breach occurs, you must notify the Data Protection Board and every affected person without delay. The Rules structure this as an initial intimation followed by a detailed report: the facts, the consequences and the mitigation.

In parallel, other clocks run. The national incident-reporting directions require cyber incidents to be reported within six hours. Sectoral regulators, banking, securities, insurance, impose their own reporting duties and formats for the entities they regulate. One incident can mean three or four notifications on different clocks, in different formats, to different authorities.

The framework: four moves

Move 1: Define and detect. Write the triage and classification criteria, so the first hour is spent executing, not debating definitions. Fix the detection sources: security monitoring, a vendor's call, a customer's complaint, the press. Each source needs a route into the playbook.

Move 2: Name the decision owners. Who classifies, who approves a Board notification, who approves telling affected people, who speaks externally. By name, with deputies, reachable out of hours.

Move 3: Draft the pack. Templates for the Board intimation, the detailed report and the notice to affected people, drafted now, not mid-crisis. Keep a regulator register: authority, format and clock per incident type. Extend the plan to processors and vendors who hold your data, including their contractual duty to tell you fast. Where a cyber insurance policy exists, write its notification conditions into the plan.

Move 4: Drill, record, fix. Run tabletop exercises with synthetic scenarios, record each exercise as evidence, and track every finding to closure.

Template: the breach readiness pack

The regulator register:

Incident typeAuthorityWhat is sentThe clockOwner
Example: personal data breachData Protection BoardInitial intimation, then detailed reportWithout delayDPO
Example: cyber incidentNational incident-reporting directionIncident reportSix hoursCISO

The incident record, one per event: what happened, when detected, classification, clocks started, notifications sent with times, approvers, and the evidence.

The downloadable file carries both sheets with a column guide.

What good looks like at the end

You should have: a playbook with named owners, drafted notification templates, a current regulator register, partner notification duties in contracts, and at least one completed tabletop with its findings closed.

The live test: pick a synthetic scenario, say a vendor reports a leaked database extract containing customer records, and walk it through the playbook with the real team. Time how long until the classification is agreed, the Board intimation is ready, and the decision owners have signed. Then fix what took too long.

Where enterprises go wrong

  • One assumed universal clock when several different ones apply.
  • External notices drafted from scratch mid-crisis.
  • Learning from the tabletop that nobody knows who approves a Board notification.
  • A playbook that covers your own systems but not the partners holding your data.
  • Treating the breach plan as a security document. Containment is security work; notification, evidence and communication are the privacy work, and both must happen at once. The security controls page covers the containment side.

The decisions to make

  • In-house response or a retained breach response service you can call.
  • How breach classification interacts with the security incident process you already run.
  • Drill frequency, and who participates.
  • How the plan reaches partners, and what their contracts oblige them to do.

Next step

Governing vendors and partners, because half your breach risk sits outside your walls. If you need help with any of this, write to us and we will help.