Wadira: Find your way through Saudi data & privacy law.

Home › Guide › Incident and Breach Reporting Map

Incident and Breach Reporting Map

One incident can trigger several reporting duties. They are parallel duties: notifying SDAIA does not discharge NCA or sector reports, and the October 2026 draft's "without prejudice" wording keeps SDAIA notification separate from NCA and sector reports. Position as at 20 October 2026.

RegimeWhoTriggerToTimingStatus
PDPL Implementing Regulation (IR) Art 24 (current)ControllersIncident that may cause harmSDAIA (platform)72 hours from awarenessIn force
PDPL IR Art 24 (draft)ControllersAny breach, damage or unauthorised access, without prejudice to NCA dutiesSDAIA72 hoursDraft
PDPL IR Art 24(5)ControllersDamage to data or conflict with rightsData subjectsWithout undue delayIn force (unchanged in the draft)
NCA ECC-2:2024Government entities, critical national infrastructureCybersecurity incidentsNCANo hours set in ECCIn force
NCA NCNICC-1:2025Non-CNI private entities identified by the NCAIncident occursNCANo hours setIn force
NCA CCC-2:2024Cloud providersIncidents affecting tenantsTenantReal timeIn force
NCA NFCISIR (draft)All public and private entitiesActual or suspected incidentHaseen portalImmediate; 2, 12, 48 or 72-hour tiers for NCA requestsDraft
CST CCSPR v4 Art 3-3-8Cloud providersBreachCST and subscribersWithout undue delayIn force
Saudi Central Bank (SAMA) Cyber Security Framework 3.3.15 / BCMSAMA-regulated entitiesMedium or high incidentsSAMAImmediatelyIn force
CMA Cybersecurity GuidelinesCapital market institutionsIncidentCMAImmediately; report after recoveryIn force
Saudi Health Information Exchange (HIE) PoliciesHIE participantsBreachOfficer, then SeHE, then participants and individuals2 business days, then 2, 10 and 30 daysIn force (status of SeHE to verify)

Points to note


Content and register data licensed CC BY 4.0. Cite the live URL. Machine-readable register (JSON) · Markdown register · Content last verified: 2026-10-21