DPA 2018 vs PCICSO
Where they overlap, where they differ and which asks more, topic by topic, with their deadlines and fines side by side.
At a Glance
They differ on 1 of 1 topics. Each verdict names what it rests on; read the wording before relying on it.
- DPA 2018 Asks more on 0 topics Alone on 1 topic More detailed on 0 topics
- PCICSO Asks more on 0 topics Alone on 0 topics More detailed on 0 topics
| Topic | DPA 2018 | PCICSO | Verdict |
|---|---|---|---|
| Supervision and enforcement | |||
| Registration with authorities | DPA 2018: 1 | PCICSO: – | Only DPA 2018no specific requirement on the other side in the acts covered |
What This Covers
The obligations below are summarised from the acts listed here, grouped by topic. Where a side shows nothing on a topic, the acts covered have no specific requirement on it; an act not yet included, national guidance or a supervisor's expectations may still say more. Use it to see where the regimes differ, not as a compliance checklist.
Key Numbers
Incident reports go to
DPA 2018: Not in the acts covered
PCICSO: Commissioner of Critical Infrastructure (Computer-system Security)
First notice of an incident
DPA 2018: Not in the acts covered
PCICSO: As soon as practicable and within 48 hours of becoming aware; within 12 hours where the incident has disrupted, is disrupting or is likely to disrupt the core function of the critical infrastructure
Intermediate report
DPA 2018: Not in the acts covered
PCICSO: Written record within 48 hours of the notification, where it was not made in the specified form
Final report
DPA 2018: Not in the acts covered
PCICSO: Written report within 14 days of becoming aware
Supervision and enforcement
Registration with authorities
Only DPA 2018 no specific requirement on the other side in the acts covered
Pay the data protection charge
ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it. can be required by regulations to pay charges to the Commission and give it the information needed to work out the amount.
Nothing in the acts covered.
Requirements are summarised in plain words; the official text prevails. Verdicts compare what the acts covered state, not how a supervisor applies them. Most topics are cross-referenced to NIST CSF 2.0 and ISO/IEC 27001:2022.
More Comparisons
Subject to more than one?
We run one control set for both, without doing the work twice. Ask what that saves you.