Incident to report to a regulator?Incident to report? Intake Line

CER Denmark vs POPA

Where they overlap, where they differ and which asks more, topic by topic, with their deadlines and fines side by side.

CER DenmarkCritical entities identified by Member States

POPA

At a Glance

They differ on 5 of 5 topics. Each verdict names what it rests on; read the wording before relying on it.

  • CER Denmark Asks more on 0 topics Alone on 0 topics More detailed on 1 topic
  • POPA Asks more on 0 topics Alone on 4 topics More detailed on 0 topics
Requirements per topic and verdict
Topic CER DenmarkPOPA Verdict
Governance
Management accountability CER Denmark: – POPA: 1 Only POPAno specific requirement on the other side in the acts covered
Protection
Data security CER Denmark: – POPA: 1 Only POPAno specific requirement on the other side in the acts covered
Detection and response
Reporting to authorities CER Denmark: 3 POPA: 1 CER Denmark more detailedmore requirements on this, not necessarily stricter
Privacy and data protection
Lawful processing CER Denmark: – POPA: 2 Only POPAno specific requirement on the other side in the acts covered
Impact assessment CER Denmark: – POPA: 1 Only POPAno 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.

Included

  • CER Directive (EU) 2022/2557 of the European Parliament and of the Council of 14 December 2022 Articles 6, 8, 12 to 17, 21, 22 · 29 requirements

National requirements

None recorded yet, so the Directive is shown as it is. The national law may go further.

Status

Reviewed against the official texts.

Included

  • POPA Protection of Privacy Act, SA 2024, c P-28.5 6 requirements

Status

Reviewed against the official texts.

Key Numbers

Deadline

CER Denmark: By 17 July 2026 (Member States); Member State notifies within one month of identification (Member States); Within nine months of receiving the notification; Central authorities reply within 10 working days of receiving the request (Member States); Rules notified to the Commission by 17 October 2024 (Member States)

POPA: Not in the acts covered

How often

CER Denmark: List reviewed at least every four years (Member States); Whenever necessary, and at least every four years

POPA: Not in the acts covered

Threshold

CER Denmark: Actual or potential significant disruption of essential servicesEssential Service; Essential services to or in six or more Member States

POPA: Not in the acts covered

Goes to

CER Denmark: Competent authority

POPA: Not in the acts covered

Evidence to keep

CER Denmark: Resilience planIn critical infrastructure regulation, a document explaining how an organisation will protect and maintain services that society depends on, and restore them after disruption. It connects identified risks with practical safeguards, responsibilities and arrangements for prevention, response and recovery. The required contents, approval process and use of equivalent existing documents depend on the applicable national law. or equivalent documents; Information and evidence on the Article 13 measures (Critical entitiesA public or private entity that a Member State has identified under the CER Directive as belonging to a category in its Annex and providing an essential service. Risk-assessment and resilience duties are subject to Article 8, which excludes banking, financial-market-infrastructure and digital-infrastructure critical entities from specified CER provisions. NIS2 treats entities identified as critical under CER as essential entities. that are also entities under Directive (EU) 2022/2555)

POPA: Not in the acts covered

Incident reports go to

CER Denmark: Competent authority

POPA: Not in the acts covered

First notice of an incident

CER Denmark: Within 24 hours of becoming aware

POPA: Not in the acts covered

Final report

CER Denmark: Within one month of the initial notification, where relevant

POPA: Not in the acts covered

Deadline to have the measures in place

CER Denmark: 10 months after the date of the notification (Member States)

POPA: Not in the acts covered

External assessment or certification

CER Denmark: Audit by an independent and qualified auditor, where the authority requires evidence (Critical entitiesA public or private entity that a Member State has identified under the CER Directive as belonging to a category in its Annex and providing an essential service. Risk-assessment and resilience duties are subject to Article 8, which excludes banking, financial-market-infrastructure and digital-infrastructure critical entities from specified CER provisions. NIS2 treats entities identified as critical under CER as essential entities. that are also entities under Directive (EU) 2022/2555)

POPA: Not in the acts covered

Maximum fines

CER Denmark: Set by each Member State; effective, proportionate and dissuasive (Member States)

POPA: Not in the acts covered

Governance

Management accountability

Only POPA no specific requirement on the other side in the acts covered

NIST CSF 2.0 GV.RR, GV.OV · ISO/IEC 27001:2022 Clause 5.1, A.5.4

Nothing in the acts covered.

  • Privacy management program

    Establish and implement a documented privacy management program proportional to the volume and sensitivity of the personal information held, meeting the Ministerial Regulation (section 6: a privacy officer, policies and procedures, a security classification system, mandatory training and periodic review); give anyone who asks a copy within 30 business days.

    POPA, Section 25

Protection

Data security

Only POPA no specific requirement on the other side in the acts covered

NIST CSF 2.0 PR.DS · ISO/IEC 27001:2022 A.5.12, A.8.10 to A.8.12

Nothing in the acts covered.

  • Security arrangements

    Protect personal information with reasonable security arrangements against unauthorized access, collection, use, disclosure or destruction.

    POPA, Section 10(1)

Detection and response

Reporting to authorities

CER Denmark more detailed more requirements on this, not necessarily stricter

NIST CSF 2.0 RS.CO · ISO/IEC 27001:2022 A.5.5

  • Initial incident notification

    Notify the competent authority without undue delay of incidents that significantly disrupt, or could significantly disrupt, the provision of essential services. Send the initial notification within 24 hours of becoming aware of the incident, unless operationally unable to do so.

    CER, Article 15(1), first subparagraph · applies as in the Directive

  • Detailed incident report

    Where relevant, follow the initial notification with a detailed report within one month.

    CER, Article 15(1), first subparagraph · applies as in the Directive

  • Content of the notification

    Include any available information that lets the competent authority understand the nature, cause and possible consequences of the incident, including any cross-border impact. Notifying does not expose the entity to increased liability.

    CER, Article 15(2) · applies as in the Directive

  • Breach notification

    Notify the individual, the Commissioner and the Minister without unreasonable delay when an incident creates a real risk of significant harm; the notices are written and contain the information set by the Protection of Privacy (Ministerial) Regulation (section 4).

    POPA, Section 10(2)

Privacy and data protection

Lawful processing

Only POPA no specific requirement on the other side in the acts covered

NIST Privacy Framework CT.PO-P

Nothing in the acts covered.

  • Accuracy for decisions

    Make every reasonable effort to keep personal information used for decisions, including automated ones, accurate and complete, and keep it for at least one year after using it, or a shorter period agreed in writing by the individual, the public body and any body that approves its retention schedule.

    POPA, Section 6

  • No sale of personal information

    Never sell personal information.

    POPA, Section 11

Impact assessment

Only POPA no specific requirement on the other side in the acts covered

NIST Privacy Framework ID.RA-P

Nothing in the acts covered.

  • Privacy impact assessment

    Prepare a privacy impact assessment for a new or substantially changed practice, program, project or service involving personal information where a loss could cause significant harm or a submission factor applies, and submit it to the Commissioner where the information is highly sensitive, a significant share of the population is involved, data is matched between public bodies, the program is common or integrated, it uses innovative technology or the Commissioner asks (Ministerial Regulation, section 7).

    POPA, Section 26

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. 18 topics where all apply the Directive as it is are not shown.

Subject to more than one?

We run one control set for both, without doing the work twice. Ask what that saves you.

Loading the form…