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

PDPL 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 0 of 0 topics. Each verdict names what it rests on; read the wording before relying on it.

  • PDPL Asks more on 0 topics Alone on 0 topics More detailed on 0 topics
  • PCICSO Asks more on 0 topics Alone on 0 topics More detailed on 0 topics
Requirements per topic and verdict
Topic PDPLPCICSO Verdict

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

  • PDPL Royal Decree No. 6/2022; Ministerial Decision No. 34/2024 issuing the Executive Regulation Article 30 · 6 requirements

Status

Reviewed against the official texts.

Included

  • PCICSO Cap. 653, Laws of Hong Kong 5 requirements

Status

Reviewed against the official texts.

Key Numbers

Incident reports go to

PDPL: Ministry of Transport, Communications and Information Technology

PCICSO: Commissioner of Critical Infrastructure (Computer-system Security)

First notice of an incident

PDPL: 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

Incident notification

PDPL: Within 72 hours of becoming aware, where the breach may put the rights of data subjects at risk

PCICSO: Not in the acts covered

Intermediate report

PDPL: 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

PDPL: Not in the acts covered

PCICSO: Written report within 14 days of becoming aware

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.

Loading the form…