Law / Frameworks / NIST CSF 2.0 / Respond
NIST CSF 2.0, RespondRS.CO-02
Internal and external stakeholders are notified of incidentsNIST Cybersecurity Framework, version 2.0, February 2024 (NIST CSWP 29), RS.CO-02
We read each law below as bearing on this control. That does not mean the control, done well, meets the law: what each law asks is on its own page. Law library as of .
- 191
- laws
- 115
- jurisdictions
- 0
- with court rulings behind them
- 11
- not yet in force
- 10
- proposed, not law
Related controls in other frameworks the same duties, in at least two laws we track, reach both
- NIST Privacy FrameworkCM.AW-P7 Impacted individuals and organizations are notified about a privacy breach or event., 113 laws
- NIST Privacy FrameworkPR.PO-P7 Response plans (Incident Response and Business Continuity) and recovery..., 8 laws
- NIST Privacy FrameworkPR.PO-P10 A vulnerability management plan is developed and implemented., 4 laws
- FINOS AIGFAIR-DET-004 AI System Observability, 172 laws
- FINOS AIGFAIR-DET-021 Agent Decision Audit and Explainability, 141 laws
- FINOS AIGFAIR-DET-001 AI Data Leakage Prevention and Detection, 82 laws
- 6 more in the FINOS AIGF
- ENISA NIS2 guidance3.5 Incident response, 95 laws
- ENISA NIS2 guidance3.1 Incident handling policy, 94 laws
- ENISA NIS2 guidance3.4 Event assessment and classification, 92 laws
- 9 more in the ENISA NIS2 guidance
A law in force is unmarked; the rest wear their state: not yet in force proposed
Vulnerability and incident reporting
85 laws, 60 jurisdictions| Jurisdiction | Law | What it asks, as read here |
|---|---|---|
| Netz- und Informationssystemsicherheitsgesetz 2026 (NISG 2026), Significant-Incident Reporting Obligations |
Notify your competent sector-specific CSIRT, or, absent one, the national CSIRT, of every significant cybersecurity incident: an early warning within 24 hours of becoming aware, stating whether it is suspected to result from unlawful and culpable acts or to have cross-border effects. Follow with a fuller notification within 72 hours of becoming aware, updating the early warning with an initial evaluation of the incident's severity and impact and any indicators of compromise. +1 more |
|
| Cyber Security Act, Computer Emergency Response Team, Duty to Report a Cyber Incident |
Without delay after a cyber incident occurs, inform the National Computer Emergency Response Team the National Cyber Security Agency maintains; the Act names no fixed number of hours or days for this notification. |
|
| Loi du 26 avril 2024, Significant-Incident Notification Obligations |
Notify the national CSIRT of any significant incident without undue delay, following the arrangements set out in the protocol between the CSIRT and the National Crisis Centre. Submit an early warning within 24 hours of becoming aware of the significant incident, stating whether it is suspected to result from unlawful or malicious action and whether it may have a cross-border impact. +2 more |
|
| Cybersecurity Act, Incident and Cyber-Threat Reporting Obligations (Zakon za kibersigurnost, ZKS) |
Notify СЕРИКС of every significant incident on this clock: an early warning within 24 hours of detecting the significant incident, an incident notification within 72 hours of detecting it (24 hours if you are a trust service provider), an interim report on request, and a final report no later than one month after the incident notification (or, if you have not dealt with the incident by then, an interim report followed by a final report within one month after you have finished handling it) (Article 23(5)). State in your early warning, where applicable, whether the incident is suspected to result from unlawful or malicious acts and whether it could have a cross-border effect; update that assessment with an initial severity and impact evaluation in your 72-hour notification; and cover in your final report the incident's scope and impact, its likely cause, your mitigation measures, and any cross-border effect. +1 more |
|
| Data Security Law, Risk Monitoring and Incident Reporting Duty |
On an actual data-security incident, immediately take disposal measures, promptly notify affected users as provided, and report the incident to the competent authority; the statute states no numeric deadline, only immediacy and promptness. |
|
| National Cybersecurity Incident Reporting Measures |
Where the incident involves critical information infrastructure, report to your sector's protection-work department and to the public security organ within 1 hour of discovering or becoming aware of the incident. Where you are a department of a central or state organ, or a directly affiliated unit of one, report to your own department's cyberspace affairs unit within 2 hours of discovering or becoming aware of the incident. +2 more |
|
| Zakon o kibernetičkoj sigurnosti and Uredba o kibernetičkoj sigurnosti, Incident and Cyber-Threat Reporting Obligations |
Notify the competent CSIRT of every significant incident on this clock, set by the Cybersecurity Regulation rather than the Act itself: an early warning without delay and no later than 24 hours after becoming aware of it (24 hours also for a trust service provider's initial notification), an initial notification no later than 72 hours otherwise, an interim report if the CSIRT requests one, and a final report no later than 30 days after your initial notification, or, if the incident is still unresolved at that point, a progress report instead, repeated every 30 days once the incident has run past 60 days, followed by a final report within 30 days of your last progress report. Notify the recipients of your service, without delay and no later than 72 hours after you become aware of a significant incident likely to affect them, in a clear and easily verifiable way, and send them any details that were not yet known within 72 hours of sending that notice. Separately notify them of a serious cyber threat and of any protective measures or remedies they can take. |
|
| Resolución 105/2021, Reglamento sobre el Modelo de Actuación Nacional para la Respuesta a Incidentes de Ciberseguridad |
Report a cybersecurity incident to your immediate superior and to the Cuban Computer Incident Response Team (CuCERT), inside the Ministry of Communications' Oficina de Seguridad para las Redes Informáticas (OSRI), using the incident-report form the Reglamento's Annex III sets out. If you hold a private data network, ensure that a cybersecurity event or incident affecting it is recorded, classified and reported to CuCERT. +1 more |
|
| Security of Networks and Information Systems Law, Incident Notification Obligations |
Notify the Digital Security Authority without undue delay, and in any event within six (6) hours of becoming aware of a significant incident, with an early warning stating, where applicable, whether the incident is suspected to result from unlawful or malicious acts and whether it may have a cross-border impact. Follow with an incident notification within 72 hours of becoming aware, updating the early warning and giving an initial assessment of the incident's severity and impact, including any indicators of compromise where available. +2 more |
|
| Cybersecurity Act (Zákon o kybernetické bezpečnosti), Incident Notification |
If you are in the higher-obligations regime, notify NÚKIB no later than 24 hours after detecting a qualifying cybersecurity incident, with an initial report giving your identifying details, basic incident data, and whether you believe the incident was caused by an unlawful intervention or could have a cross-border impact. If you are in the lower-obligations regime, notify the Národní CERT on the same 24-hour clock instead, for a qualifying incident with significant impact on your service's provision. +4 more |
Show the other 75 laws
| Digital Code, Livre II: Trust Service Provider Security-Incident Notification |
Notify the Autorité Nationale de Certification Électronique, and where applicable other bodies concerned, within twenty four hours of becoming aware of it, of every breach of security or loss of integrity having a significant impact on the trust service provided or on the personal data it stores. Where the breach or loss of integrity is liable to harm a user of the service, notify that user as well, within twenty four hours. |
|
| Digital Code, Livre IV: General Cyberattack Cooperation and Incident-Reporting Duty |
Inform the Agence Nationale de Cybersécurité of every attack, intrusion or other penetration liable to impair the operation of another information system or network, so as to let the Agency take the measures necessary to address it, including isolating the affected system. |
|
| Act on Security and Preparedness in the Telecoms Sector (Lov om sikkerhed og beredskab i telesektoren), Significant Incident Notification |
Notify the Danish Agency for Societal Security and the CSIRT of every significant incident: an early warning without undue delay and within 24 hours of becoming aware of it, stating whether it is suspected to be caused by unlawful or malicious acts or could have a cross-border effect; an incident notification within 72 hours; an interim report when the authority asks; and a final report within one month of the incident notification, or, if the incident is still ongoing, a status report then and a final report within one month of the incident being handled (Sections 8(2) and 9(1)). Tell the recipients of your services, without undue delay and to the relevant extent, when a significant incident is likely to affect their service negatively, and tell recipients potentially affected by a significant cyber threat of any measures they can take in response (Section 11). |
|
| NIS 2-loven, Significant-Incident Reporting and Recipient-Notice Duties |
Notify your competent authority and Denmark's CSIRT of every significant incident, one that has caused or can cause serious operational disruption or financial loss for you, or has affected or can affect another person through significant physical or non-physical harm. Send an early warning without undue delay, and no later than 24 hours after becoming aware of the significant incident, stating whether it is suspected to result from an unlawful or malicious act and whether it may have a cross-border effect. +3 more |
|
| Digital Code, Book VII: National Health Data System Security Incident Reporting |
Report a serious information-system security incident to the cybersecurity authority without delay, if you access data in Djibouti's national health data system as a health professional, health establishment, health-insurance financing body, or other body accessing that system. |
|
| Küberturvalisuse seadus (KüTS), Duty to Notify of a Cyber Incident |
Submit an initial report to RIA without delay and no later than 24 hours after becoming aware of a cyber incident that has, or could reasonably be expected to have, a significant effect on your system's security or your service's continuity, unless you are a security authority. Follow with an incident report no later than 72 hours after becoming aware of the significant incident, updating the initial report, unless you are a trust service provider, in which case you submit it within 24 hours instead. +1 more |
|
| Computer Crime Proclamation, Duty to Report Computer Crime and Illegal Content |
Immediately notify the Information Network Security Agency (now the Information Network Security Administration) and report the crime to the police, and take appropriate measures. |
|
| Critical Infrastructure Cybersecurity Proclamation, Cyber Incident Reporting to National CERT from , in 8 months |
Notify the National Computer Emergency Response Center of a cyber incident within 48 hours of becoming aware of it, using the system the Administration establishes, and implement the mandatory recommendations or directions the Center provides within the time it sets. |
|
| Commission Delegated Regulation (EU) 2022/1645, External Reporting of Information Security Incidents and Vulnerabilities (IS.D.OR.230) |
Report to your competent authority any information security incident or vulnerability that may represent a significant risk to aviation safety; where it affects an aircraft or associated system or component, also report it to the design approval holder, and where it affects a system or constituent you use, to the organization responsible for its design (point IS.D.OR.230(b)). Submit a notification as soon as you know of the condition, and a report as soon as possible and not exceeding 72 hours from the time you know of it unless exceptional circumstances prevent this, in the form your competent authority defines (point IS.D.OR.230(c), points (1) and (2)). +1 more |
|
| Commission Delegated Regulation (EU) 2024/1366, Cybersecurity Network Code for Cross-Border Electricity Flows: Information Sharing on Cyber-Attacks and Threats |
Share relevant information related to a reportable cyber-attack with your CSIRTs and your competent authority without undue delay and no later than four hours of becoming aware that the incident is reportable; a cyber-attack is reportable when you assess its criticality as ranging from high to critical on the classification scale methodology under Article 37(8) (Article 38(3) and (4)). |
|
| Commission Implementing Regulation (EU) 2023/203, External Reporting of Information Security Incidents and Vulnerabilities in Aviation (IS.I.OR.230) |
Report to your competent authority any information security incident or vulnerability that may represent a significant risk to aviation safety; where it affects an aircraft or associated system or component, also report it to the design approval holder, and where it affects a system or constituent you use, to the organization responsible for its design (point IS.I.OR.230(b)). Submit a notification as soon as you know of the condition, and a report as soon as possible and not exceeding 72 hours from the time you know of it unless exceptional circumstances prevent this, in the form your competent authority defines (point IS.I.OR.230(c), points (1) and (2)). +1 more |
|
| Commission Implementing Regulation (EU) 2024/2690, Significant Incidents under NIS2 Article 23 |
Treat yourself as aware of a significant incident, for the clock Article 23(4) of Directive (EU) 2022/2555 sets, when after your initial assessment you have a reasonable degree of certainty that a significant incident has occurred (recital 31). |
|
| Cyber Resilience Act, Manufacturer Reporting Obligations |
Notify the CSIRT designated as coordinator for your main establishment and ENISA, through the single reporting platform, of any actively exploited vulnerability you become aware of in your product: an early warning within 24 hours of becoming aware, a vulnerability notification within 72 hours, and a final report no later than 14 days after a corrective or mitigating measure becomes available, the notification and the final report each unless the relevant information has already been provided. Notify the same recipients of any severe incident affecting the security of your product on the same 24-hour early warning and 72-hour incident notification clock, followed by a final report within one month of the incident notification; the incident notification and the final report each apply unless the relevant information has already been provided. For either an exploited vulnerability or a severe incident, give the CSIRT an intermediate report on relevant status updates if it asks for one. +1 more |
|
| DORA Technical Standards on the Standard Forms, Templates and Procedures for Reporting Major ICT-Related Incidents and Notifying Significant Cyber Threats |
Use the template in Annex I for the initial notification, the intermediate report and the final report, completing the data fields that correspond to the information that Articles 2, 3 and 4 of Delegated Regulation (EU) 2025/301 require for each report, follow the data glossary and instructions in Annex II, ensure that the information is complete and accurate, and give estimated values based on other available data and information where accurate data are not available for the initial notification or the intermediate report (Article 1). If you combine two or all of the reports in one submission, which Article 2 allows where regular activities have recovered or the root cause analysis has been completed, meet the time limits of Article 5 of Delegated Regulation (EU) 2025/301 for each report (Article 2). +4 more |
|
| DORA, Article 19 (reporting of major ICT-related incidents), with the time limits of Delegated Regulation (EU) 2025/301 |
Report a major ICT-related incident to the competent authority your sector's Union law designates under Article 46, the European Central Bank through your national supervisor if you are a credit institution classified as significant, using the templates referred to in Article 20, and submit an initial notification as early as possible and in any case within four hours of classifying the incident as major, and no later than 24 hours from becoming aware of it. Where classification as major comes later than that, submit the initial notification within four hours of the classification instead. +2 more |
|
| eIDAS Regulation, Article 19a(1)(b): Notification of Security Breaches and Disruptions by Non-Qualified Trust Service Providers |
Notify the supervisory body, the identifiable affected individuals, the public if it is of public interest and, where applicable, other relevant competent authorities of any security breach or disruption in the provision of the service, or in the implementation of the Article 19a(1), point (a), measures, that has a significant impact on the trust service provided or on the personal data maintained in it (Article 19a(1), point (b)). Make each notification without undue delay and in any case no later than 24 hours after you become aware of the security breach or disruption (Article 19a(1), point (b)). |
|
| European Health Data Space Regulation, Serious-Incident Reporting by Manufacturers of EHR Systems from , in 2.4 years |
It reaches you if you are the manufacturer of an EHR system placed on the market or put into service. Report any serious incident (Article 2, point (r)) involving the EHR system to the market surveillance authorities of the Member States where the serious incident occurred and of the Member States where the system is placed on the market or put into service, and include a description of the corrective action you have taken or envisage (Article 44(7)). Make the report immediately after you have established a causal link between the EHR system and the serious incident or the reasonable likelihood of such a link and, in any event, not later than three days after you become aware of the serious incident (Article 44(7)). |
|
| NIS2 Directive, Reporting Obligations |
Notify your CSIRT, or the competent authority where applicable, of any incident with a significant impact on the provision of your services: an early warning within 24 hours of becoming aware, an incident notification within 72 hours of becoming aware (24 hours if you are a trust service provider), an intermediate report on relevant status updates if your CSIRT or competent authority asks for one, and a final report no later than one month after the incident notification, or, for an incident still ongoing at that point, a progress report then and a final report within one month of its handling. Where appropriate, notify, without undue delay, the recipients of your services who a significant incident is likely to adversely affect, and communicate to recipients potentially affected by a significant cyber threat any measures or remedies they can take. |
|
| Kyberturvallisuuslaki, Significant-Incident Reporting Obligations |
Notify your supervisory authority without delay of a significant incident, one that has caused or could cause a serious service disruption or considerable financial loss to you, or that has affected or could affect another person with considerable material or immaterial damage. File an early notification within 24 hours of detecting the significant incident, stating whether it is suspected to result from an unlawful or hostile act and the likelihood of cross-border effects, and a follow-up notification within 72 hours of detection, both clocks running from detection rather than from each other; if you are a trust service provider whose trust services are affected, file your follow-up notification within 24 hours instead of 72. +1 more |
|
| Laki sosiaali- ja terveydenhuollon asiakastietojen käsittelystä, Reporting of Deviations in Information Systems and Wellbeing Applications and of Significant Information Security Disturbances |
Notify the Licensing and Supervisory Authority without delay of a significant information-security disturbance in the operating environments and networks you use that may significantly endanger the use of information systems or the provision of social and health care services; a pharmacy whose operations may be significantly endangered also notifies the Finnish Medicines Agency without delay (section 90). |
|
| Laki sähköisen viestinnän palveluista, Security Incident Notices by Telecommunications Operators |
If you are a telecommunications operator (teleyritys) providing a communications service in Finland, notify your subscribers and users without delay when a significant information-security breach, or another event that prevents the service from working or materially disturbs it, affects or threatens your service (Act 917/2014, section 274). If you provide a value-added service as a value-added service provider (lisäarvopalvelun tarjoaja), notify your users without delay of a significant information-security breach, or the threat of one, affecting your service (section 274). +2 more |
|
| Loi n° 2018-133 du 26 février 2018 (transposition NIS1), Incident Notification |
Declare to ANSSI, without delay after becoming aware of it, an incident affecting the networks and information systems necessary to provide your service, where the incident has or is likely to have a significant impact on the continuity of the service (an operator of essential services) or on the provision of the service in the European Union (a digital service provider). |
|
| Projet de loi Résilience des Infrastructures Critiques et Cybersécurité, Incident Notification (NIS2) proposed |
In the text the Sénat adopted, notify ANSSI without undue delay of any incident with an important impact on the provision of your services (one causing or liable to cause a severe operational disruption or financial loss for you, or considerable material, physical or non-material damage to another person), on a graduated clock: an initial notification within 24 hours of becoming aware of it, an intermediate notification within 72 hours of becoming aware of it updating the initial one and giving an initial assessment of severity and impact, a report on ANSSI's request, and a final report within one month of the intermediate notification, or, where the incident is not yet handled by then, a progress report within one month of the intermediate notification and a final report within one month of the incident being handled (Article 17). In the text the Assemblée nationale's special committee deposited (n° 1779-A0), the initial notification within 24 hours, the intermediate notification within 72 hours and the final report within one month would be the same, but an incident would count as important only where it caused or is liable to cause a severe operational disruption or significant financial losses for you, or considerable material, physical or non-material damage to another person. +1 more |
|
| Information and Communications Act, 2009, security of information and communications services (subscriber risk notification) |
Where a particular risk of a breach of the security of your services persists despite your safeguards, inform your subscribers of the risk and of the measures they may take to protect themselves. Identify in that notice any software or encryption technology available to the subscriber to protect the security of their communications. +1 more |
|
| BSI-Gesetz (BSIG), Incident Notification |
Notify the BSI's and the Bundesamt für Bevölkerungsschutz und Katastrophenhilfe's joint reporting office without delay, and in any event within 24 hours of becoming aware of a significant security incident, with an early warning stating whether the incident is suspected to be unlawful or malicious or to have cross-border effect. Follow with a full notification within 72 hours of becoming aware, confirming or updating the early warning and giving an initial assessment of the incident's severity and impact and, where available, indicators of compromise. +1 more |
|
| Cybersecurity Act, Duty to Report Cybersecurity Incident |
Report a cybersecurity incident to the relevant Sectoral Computer Emergency Response Team, or to the National Computer Emergency Response Team where the institution has no Sectoral team, within twenty-four hours after the incident is detected. |
|
| Law 5160/2024, Significant-Incident Reporting Obligations |
Notify the CSIRT of the National Cybersecurity Authority, without undue delay and in any case within 24 hours of becoming aware of a significant incident, with an early warning stating whether unlawful or malicious action is suspected and whether the incident may have cross-border effects. Follow within 72 hours of becoming aware of the significant incident with an incident notification updating the early warning and adding an initial assessment of its severity and effects. +2 more |
|
| Cybersecurity Act, Incident Notification and Cybersecurity Fine |
Notify the national cybersecurity incident-handling center (Nemzeti Kiberbiztonsági Intézet, the NKI) of a cyber threat, near-incident or cybersecurity incident affecting your electronic information system: an initial notification without undue delay and in any case within 24 hours of becoming aware, an event notification without undue delay and in any case within 72 hours of becoming aware that updates that report and assesses the incident's severity and impact, and a final report no later than one month after the event notification. If you are a trust service provider, notify the center of a cybersecurity incident affecting your trust services without undue delay and in any case within 24 hours of becoming aware of it, in place of the event notification (Decree 418/2024, Section 77(4)). |
|
| Notification of Serious Incidents and Risk to the National Cybersecurity Incident-Response Team |
Notify Iceland's national cybersecurity incident-response team as soon as may be about a serious incident or risk threatening the security of a network or information system; the Act sets no fixed hour-based clock of its own for this notification. State in the notification the number of affected users, the incident's duration, its geographic spread and scale, any outsourcing arrangement relied on, and any possible cross-border contagion effect. |
|
| Government Regulation on the Operation of Electronic Systems and Transactions, security-incident reporting duty |
Report the incident immediately, at the first opportunity, to law enforcement officials and the relevant Ministry or Agency; the Government Regulation states no numeric clock for this report, only immediacy. |
|
| European Union (NIS) Regulations 2018, Incident Notification |
Notify the State's CSIRT without delay and in any event not later than 72 hours after becoming aware of an incident with a significant impact on the continuity of your essential service, or a substantial impact on your digital service, including an incident affecting a third-party digital service provider you rely on. |
|
| National Cyber Security Bill, Incident Response Powers and Reporting Obligations proposed |
Notify the CSIRT without undue delay of any incident with a significant impact on the provision of your service: an early warning within 24 hours of becoming aware of it, an incident notification within 72 hours of becoming aware of it, an intermediate report on relevant status updates when the CSIRT requests one, and a final report not later than one month after submitting the incident notification (Head 15). If you are a trust service provider, notify the CSIRT of a significant incident affecting your trust services without undue delay and in any event within 24 hours of becoming aware of it, in place of the later incident notification (Head 15). +1 more |
|
| Decreto Legislativo 4 settembre 2024, n. 138 (Decreto NIS2), Incident Notification |
Notify CSIRT Italia without unjustified delay, and in any event within 24 hours of becoming aware of a significant incident, with a pre-notification stating, where possible, whether the incident appears unlawful or malicious and whether it may have a cross-border impact. Follow with a full notification within 72 hours of becoming aware, updating the pre-notification and giving an initial assessment of the incident's severity and impact and, where available, indicators of compromise. +1 more |
|
| Legge 28 giugno 2024, n. 90, Incident Notification and Vulnerability Remediation Duties |
If you are a central public administration, region, metropolitan city, large municipality or regional capital, urban or suburban public transport company, local health authority, or an in-house company providing IT, transport, wastewater or waste services for them, report any incident on the ACN taxonomy that affects your networks, information systems or IT services without delay and within 24 hours of learning of it, and make a complete notification within 72 hours of that moment (Law 90/2024, Article 1(1) and (2)). Make the report and the notification through the procedures on the ACN website (Article 1(2)). |
|
| Cyber Security Law No. 16 of 2019, Article 8 private-sector incident-reporting and Center-cooperation duty |
Adhere to the policies, standards, and controls the Center issues for the institution's own sector, provide the Center the information it needs to do its work, and inform the Center of any incident that threatens cybersecurity or the security of cyberspace, taking every step necessary to prevent or avoid it. |
|
| Computer Misuse and Cybercrimes Act, Reporting of Cyber Threat |
Immediately inform the National Computer and Cybercrimes Co-ordination Committee, established under section 4 of the Act, of an attack, intrusion, or other disruption to the functioning of another computer system or network, within twenty-four hours of the attack, intrusion, or disruption. Include in the report a summary of how the breach occurred, an estimate of the number of people affected, an assessment of the risk of harm to them, and an explanation of any circumstance that would delay or prevent telling them. |
|
| Cybersecurity Act 2026, Duty to Report a Cybersecurity Incident from a date not yet set |
When you are the subject of a cybersecurity incident or threat of one, gather information about it, assess the risk to your critical infrastructure, customers, suppliers and other stakeholders, take appropriate preventative, mitigating and remedial measures to limit that risk, and report all material information about a significant cybersecurity incident to the National CERT and any relevant Sectoral CERT within 24 hours after you detect it, in the form or manner the CERT prescribes. |
|
| Law No. 08/L-173 on Cyber Security, Incident Reporting and Enforcement |
As an operator of essential services, notify the Agency for Cyber Security immediately, and no later than 24 hours after becoming aware, of a cyber incident with a significant impact on system security or service continuity, and notify affected persons or the public within a reasonable time where individual notice is impractical. As a digital service provider, notify the Agency for Cyber Security immediately upon becoming aware of a cyber incident with a significant impact on the digital service you provide. |
|
| Digital Code, digital resilience incident notification |
Notify the sectoral regulator with jurisdiction over your sector no later than 72 hours after you discover the incident; if you notify later than that, explain the reason for the delay in the notice. If you process data as a processor for a record owner, notify that record owner of an incident within the period your contract sets, and in any event no later than 48 hours after you discover it. +1 more |
|
| Nacionālās kiberdrošības likums, Incident Notification |
Immediately take all action necessary to contain a detected cyber incident, immediately inform the competent cyber incident prevention institution (for most private-sector and civilian public-sector subjects, the Institute of Mathematics and Computer Science of the University of Latvia), and follow its instructions. For a significant cyber incident, electronically submit an early warning to the competent institution without delay and no later than within 24 hours. +1 more |
|
| Cyber-Sicherheitsgesetz (CSG), Incident Notification |
Notify the Stabsstelle Cyber-Sicherheit (Cyber Security Office) without delay, and in any event within 24 hours of becoming aware of a significant security incident, with an early warning stating, where relevant, whether the incident is suspected to result from unlawful or malicious acts or to have cross-border effect. Follow with a full notification within 72 hours of becoming aware, updating the early warning where relevant and giving an initial assessment of the incident's severity and impact and, where available, indicators of compromise. |
|
| Kibernetinio saugumo įstatymas (Law on Cyber Security), Incident Notification |
Notify NKSC of a significant cyber incident without delay and in any event within 24 hours of becoming aware of it. Follow within 72 hours of becoming aware with the incident's severity and impact assessment and any evidence of compromise; report a minor incident within 72 hours without a separate 24-hour early warning. |
|
| Loi du 5 mai 2026 relative à la cybersécurité (NIS2), Incident Notification |
Notify the competent authority, without undue delay, of any incident with a significant impact on the provision of your services: treat an incident as significant where it has caused or is capable of causing severe operational disruption or financial loss to you, or considerable material, physical or moral damage to another person. Submit an early warning within 24 hours of becoming aware of the significant incident, stating whether it is suspected to result from unlawful or malicious acts or could have cross-border effect. +3 more |
|
| Electronic Communications Networks and Services (General) Regulations, Security Incident Notification to the Malta Communications Authority |
Notify the Authority, the Malta Communications Authority, without undue delay of any security incident that has a significant impact on the operation of your networks or services (regulation 28(2)(a)). If you are a gateway operator, notify the Authority without undue delay of any failure or serious degradation of the connectivity you provide (regulation 28(2)(b)). |
|
| Gaming Authorisations and Compliance Directive, Notification of Information Security Breaches |
Notify the Authority forthwith, and in any case no later than three working days after the breach, of any breach of your information security that adversely affects the confidentiality of information relating to players (article 37(2)(c)). Notify the Authority on the same clock of any breach of your information security that precludes players from accessing their accounts for a period exceeding twelve hours (article 37(2)(d)). +1 more |
|
| Measures for a High Common Level of Cybersecurity across the European Union (Malta) Order, Significant-Incident Reporting to the National CSIRT |
Notify the national CSIRT, which article 8(1) establishes within the Malta Information Technology Agency, immediately of any incident that has a significant impact on the provision of your services; treat an incident as significant where it has caused or is capable of causing severe operational disruption of the service or financial loss for you, or considerable material or non-material damage to another person. Submit an early warning to the national CSIRT, without undue delay and in any event within 24 hours of becoming aware of the significant incident, stating where applicable whether it is suspected of being caused by unlawful or malicious acts or could have a cross-border impact. +3 more |
|
| Cybersecurity Act 2025, Cybersecurity Incident Reporting Obligations |
Immediately notify the Director and the CSIRT-MH (the Cyber Security Incident Response Team of the Marshall Islands) of a significant cybersecurity incident affecting your critical information infrastructure, of a significant incident on any interconnected computer system under your control, or of any other incident type the Director specifies by written order. |
|
| Law on Cyber Security, Cyber-Attack Notification Duty for Other Legal Persons |
On a cyber-attack or violation against your systems, notify the relevant center against cyber-attacks and violations, the Public center for a legal person outside the state information network and outside critical information infrastructure, and obtain assistance where necessary; the text states no numeric clock for this notice. |
|
| Law on Information Security, Cyber Threat and Incident Reporting |
Where a cyber threat or incident has no effect on the continuity of your service, report it once a month to the Cybersecurity Agency (Article 29). Where a cyber threat or incident could significantly affect the continuity of your service, submit an initial notification to the Cybersecurity Agency within 24 hours of becoming aware of it, on the prescribed form (Article 30). |
|
| Loi n° 05-20 relative à la cybersécurité, Digital Service Provider and Platform Operator Incident and Vulnerability Notification Duties |
Inform your clients of a vulnerability in your information systems, or of a breach that could affect them. When you detect an event that could affect the security of a client's information systems, inform the national cybersecurity authority of it without delay. +1 more |
|
| Cyberbeveiligingswet, Significant-Incident Reporting Obligations |
Give your CSIRT and competent authority an early warning without delay, or within 24 hours of becoming aware of a significant incident if immediate reporting is not possible, stating whether the incident is suspected to result from unlawful or malicious action and whether it may have cross-border effects. Follow with a notification, without delay or, if that is not possible, within 72 hours of becoming aware of the significant incident, updating the early warning with an initial assessment of the incident's severity and effects. If you provide a trust service and the incident affects its provision, file this notification without delay or, if that is not possible, within 24 hours of becoming aware of the incident instead. +1 more |
|
| New York Department of Financial Services Cybersecurity Regulation, Notices to the Superintendent |
Notify the Superintendent electronically, in the form set forth on the Department's website, as promptly as possible but no later than 72 hours after you determine that a Cybersecurity Incident has occurred at your organization, an affiliate, or a third-party service provider: an event that requires notice to a government or supervisory body, that has a reasonable likelihood of materially harming a material part of your normal operations, or that results in the deployment of ransomware within a material part of your information systems. Where you make an extortion payment in connection with a cybersecurity event, notify the Superintendent of the payment within 24 hours of making it, and within 30 days of the payment provide a written description of why the payment was necessary, the alternatives you considered, and the diligence you performed, including under Office of Foreign Assets Control rules. |
|
| Cybercrimes (Prohibition, Prevention, etc.) Act, 2015, as amended in 2024, Reporting of Cyber Threats to the National CERT |
Immediately inform the National Computer Emergency Response Team (CERT) Coordination Center, through your sectoral CERT or sectoral Security Operations Centre, of any attack, intrusion, or other disruption liable to hinder the functioning of another computer system or network. Report the incident to the National CERT within 72 hours of its detection. Failing to do so is itself an offence, punishable by denial of internet services and a mandatory fine of N2,000,000 payable into the National Cyber Security Fund. |
|
| Ustawa o krajowym systemie cyberbezpieczeństwa (KSC), Zgłaszanie Incydentów Poważnych |
Follow with a fuller notification within 72 hours of detection, a periodic report on the CSIRT's request, and a final report no later than one month after the 72-hour notification. If you provide a trust service, report a significant incident to the competent sectoral CSIRT without delay, and in any event within 24 hours of detecting it, as a notification (Article 11(1a)). +1 more |
|
| Regime Jurídico da Cibersegurança, Significant-Incident Reporting Obligations |
Notify the competent cybersecurity authority of any significant incident, weighing the number and share of users affected, the incident's duration, the severity of the service disruption and its economic and social impact. Submit an initial notification without undue delay and within 24 hours of concluding that a significant incident exists or may exist, and, where necessary, update it within 72 hours with an initial assessment of the incident's severity and impact; if the incident resolves within two hours of detection, submit only the end-of-impact notification below. |
|
| Ordonanța de urgență nr. 155/2024, Incident Notification |
Report to the national cybersecurity-incident-response team, without undue delay, any incident with a significant impact on the provision of your services, through the Platforma națională pentru raportarea incidentelor de securitate cibernetică (PNRISC). Submit an early warning within 24 hours of becoming aware of a significant incident, stating whether it is suspected unlawful, malicious, or cross-border in impact; follow with a fuller incident report within 72 hours giving an initial severity and impact assessment and any known indicators of compromise; submit an interim report if the CSIRT requests one; and submit a final report within one month of the 72-hour report, or a progress report followed by a final report if the incident is still ongoing at that point. +2 more |
|
| Law on Information Security, Incident Reporting Obligations |
Notify the single incident-reporting system, through the Ministry's or the Office for Information Security's website, of an incident that may significantly disrupt information security, without delay and at the latest within 24 hours of becoming aware of it. If you operate a banking or financial-market ICT system, send that notification to the National Bank of Serbia, and also to the Securities Commission if it supervises you; if you provide an electronic-communications or postal service, send it to the Regulatory Body for Electronic Communications and Postal Services instead. +2 more |
|
| Cyber Security and Crime Act, 2021, Reporting of Cyber Security Incidents |
Immediately inform the National Computer Security Incidence Response Team of an attack, intrusion, or other disruption liable to hinder the functioning of another computer system or network. Report the incident to the Team within 7 days of its occurrence even if you already gave the immediate notice section 53(1) requires; failing to do so, without reasonable excuse, is itself an offence distinct from any liability for the disruption reported. |
|
| Vyhláška NBÚ č. 226/2025 Z. z., Details of Cyber Security Reports |
If you are an essential service operator or another person who reports under Section 24 of Act 69/2018 on cyber security, report a serious cyber security incident with the particulars of Annex 2: your identity and contact data, the time of detection, a description of the incident and its consequences or expected scope, whether unlawful conduct may have caused it, whether it may have cross-border impact and the effect on trust services; the follow-up report adds updated information, the status of resolution and the measures taken. |
|
| Zákon o kybernetickej bezpečnosti (Cybersecurity Act), Incident and Vulnerability Notification |
Report without undue delay, and no later than 24 hours after becoming aware of it, an early warning of a significant cyber security incident, stating in particular whether it may have been caused by unlawful conduct or may have a cross-border effect. No later than 72 hours after becoming aware of it, report a notification updating and completing the early warning, in particular an initial assessment of the incident's severity and impact. +2 more |
|
| Zakon o informacijski varnosti (ZInfV-1), Significant-Incident Notification Obligations |
Give your competent CSIRT group an early warning without delay, at latest within 24 hours of detecting a significant incident, stating whether it is suspected to result from an unlawful or malicious act and whether it may have a cross-border effect. Follow with a full notification without delay, at latest within 72 hours, updating the early warning with an initial assessment of the incident's severity and impact and any available threat indicators, then an interim report if the CSIRT group asks for one, and a final report at latest one month after the 72-hour notification, or a progress report and a final report within one month of resolution if the incident is still ongoing at that point. +2 more |
|
| Information and Communications Network Act, Report on Computer Security Incidents |
Immediately report a computer security incident to the Minister of Science and ICT or to the Korea Internet and Security Agency upon discovering it; a report already made for the same incident under another statute satisfies this duty and need not be repeated. |
|
| Anteproyecto de Ley de Coordinación y Gobernanza de la Ciberseguridad, Incident Reporting Obligations proposed |
As drafted, the Anteproyecto would require you to notify the competent authority of a significant incident affecting the provision of your service, whether on your own networks or a third-party provider's. As drafted, the Anteproyecto would require you to send an early warning without undue delay, and in any event within 24 hours of becoming aware of a significant incident, to the competent authority through your reference CSIRT, stating, where applicable, whether the incident is suspected to result from an unlawful or malicious act or could have cross-border repercussions (Article 18(6)(a)). +1 more |
|
| Real Decreto-ley 12/2018, Incident Notification Obligation |
For a CRITICO-severity incident under the national notification instruction, notify immediately on becoming aware of it, follow up with an interim notification within 24 to 48 hours of the initial notification, and file a final notification within 20 days of the initial notification; for a MUY ALTO-severity incident, notify immediately on becoming aware of it, follow up within 72 hours of the initial notification, and file a final notification within 40 days of the initial notification; an ALTO-severity incident requires only an immediate initial notification (Real Decreto 43/2021, annex, section 6). |
|
| Cybersäkerhetslag, Incident Notification |
Inform the authority the government designates (in practice the CSIRT-enhet at Försvarets radioanstalt) of a significant incident as soon as you can, and no later than 24 hours after becoming aware of it. Follow with a formal incident notification to the same authority as soon as you can; if you provide a trust service, no later than 24 hours after becoming aware, and otherwise no later than 72 hours after becoming aware. +2 more |
|
| Cyber Security Management Act, Cyber Security Incident Reporting |
Notify the central competent authority in charge of the relevant sector as soon as the agency becomes aware of a cyber security incident. |
|
| Cybersecurity Act 2025, Duty to Report a Cybersecurity Incident from a date not yet set |
Within 24 hours of becoming aware of it, report to the Computer Emergency Response Team (CERT) a cybersecurity incident relating to the information systems of your designated critical infrastructure, an incident relating to any information system interconnected with or communicating with those systems, or any other cybersecurity incident or occurrence the Minister CPR has designated as requiring notification. File that report in the form the Minister CPR prescribes. |
|
| Cybersecurity Incident Reporting and Emergency Response |
Immediately inform the national contact point or your emergency response center of any cybersecurity incident or attack, and comply with the emergency measures either one orders. |
|
| Cybersecurity Law, Reporting and Cooperation Duties |
Report a detected vulnerability or cyber incident in the area of service provided to the Cybersecurity Directorate without delay; the Law's own text sets no numeric reporting clock. |
|
| Law on the Basic Principles of Ensuring Cybersecurity, CERT-UA Incident Notification Duty |
Inform CERT-UA immediately (невідкладно, without delay; the statute states no fixed hour clock) of a cybersecurity incident affecting your critical infrastructure object's communication or technological systems. |
|
| Computer-Security Incident Notification Requirements for Banking Organizations and Their Bank Service Providers |
If your organization is a banking organization, notify your primary federal banking regulator, the OCC, the Federal Reserve Board, or the FDIC, whichever supervises it, about a notification incident, as soon as possible and no later than 36 hours after your organization determines that a notification incident has occurred. A notification incident is the subset of computer-security incidents that has materially disrupted or degraded, or is reasonably likely to materially disrupt or degrade, your ability to serve customers, a business line, or an operation whose failure would threaten the financial stability of the United States, so a computer-security incident that falls short of that threshold does not by itself start this clock. If your organization is a bank service provider, notify at least one bank-designated point of contact at each affected banking organization customer as soon as possible after your organization determines that it has experienced a computer-security incident that has materially disrupted or degraded, or is reasonably likely to materially disrupt or degrade, covered services provided to that banking organization for a period of four hours or more. This duty carries a standard, as soon as possible, rather than a fixed number of hours to notify by, and that disruption threshold is what engages the duty rather than a period to notify within. |
|
| Cyber Incident Reporting for Critical Infrastructure Act of 2022 (CIRCIA) from a date not yet set |
Once the final rule takes effect, report a covered cyber incident to the Agency not later than 72 hours after your organization reasonably believes that the covered cyber incident has occurred. Once the final rule takes effect, report a ransom payment to the Agency not later than 24 hours after your organization makes the payment, even where the underlying ransomware attack is not itself a covered cyber incident. |
|
| Safeguarding Covered Defense Information and Cyber Incident Reporting (DFARS 252.204-7012) |
Rapidly report a cyber incident to the Department of Defense within 72 hours of discovering it, at the Department's DIBNet portal (dibnet.dod.mil), using a DoD-approved medium assurance certificate that you must obtain before you need to file a report. |
|
| SEC Cybersecurity Risk Management, Governance, and Incident Disclosure (Regulation S-K Item 106; Form 8-K Item 1.05) |
If your organization is an SEC reporting company, determine, without unreasonable delay after you discover a cybersecurity incident, whether the incident is material, and if it is, file a Form 8-K under Item 1.05 within four business days after you make that determination. If the information called for in Item 1.05 is not determined or is unavailable when you file, state that in the filing and file an amendment to the Form 8-K within four business days after you determine it or it becomes available. |
|
| Cybersecurity Law, Incident Response and Reporting Duties |
As the manager of an information system, connect its cybersecurity monitoring to the National Cybersecurity Centre of the Ministry of Public Security, or to the Ministry of National Defence's centre for a military system, and report a cybersecurity incident to that specialised force. As an enterprise providing a service on a telecommunications network, the Internet, or another value-added service in cyberspace in Vietnam, warn users of the cybersecurity risks in the service and give guidance on preventive measures, and keep an emergency response plan ready to address cybersecurity weaknesses, risks and incidents. +1 more |
Breach notification
74 laws, 72 jurisdictions| Jurisdiction | Law | What it asks, as read here |
|---|---|---|
| Law No. 124/2024, notification of a personal data breach |
Notify the Commissioner of a personal data breach as soon as possible and no later than 72 hours of becoming aware of the breach, unless the breach is unlikely to endanger the rights and freedoms of data subjects, and give the Commissioner your reasons for any later notification. As a processor, notify the controller immediately after becoming aware of any personal data breach. +2 more |
|
| Loi n° 18-07 relative à la protection des personnes physiques, notification des violations de données |
As a service provider, that is any public or private entity offering users the ability to communicate over a computer or telecommunications system, or any entity processing or storing data for that communication service, notify the ANPDP without delay of a personal-data breach occurring on a public electronic communications network. Notify the affected individual without delay of that same breach where it may harm their private life, unless the ANPDP finds you had already implemented appropriate protective measures. +3 more |
|
| LQPD, personal data breach notification |
Notify the Andorran Data Protection Agency of a personal data breach without undue delay and, where possible, within seventy-two hours of becoming aware of the breach, unless the breach is unlikely to result in a risk to the rights and freedoms of natural persons. Justify the reasons for the delay if notifying the Agency after that seventy-two-hour period. +3 more |
|
| Data Protection Act, 2019, personal data breach notification |
Notify a personal data breach to the Data Protection Commissioner without undue delay and, where feasible, not later than 72 hours after becoming aware of it, unless the breach is unlikely to result in a risk to the rights and freedoms of an individual, and give reasons for the delay if you notify later. Communicate a personal data breach likely to result in a high risk to the rights and freedoms of individuals to the affected data subject, in clear and plain language, without undue delay and, where feasible, not later than 72 hours after becoming aware of it. +2 more |
|
| Law of the Republic of Belarus On Personal Data Protection, notification of personal data protection violations |
Notify the National Center for Personal Data Protection immediately, and in any case no later than three working days after becoming aware of a violation of your personal data protection systems, under Article 16, unless the Center itself provides otherwise. |
|
| Data Protection Act 2021, personal data breach notification from a date not yet set |
Where feasible, notify the Data Protection Commissioner of a personal data breach within 72 hours of becoming aware of it, unless the breach is unlikely to risk a person's rights and freedoms. Where a personal data breach is likely to result in a high risk to a person's rights and freedoms, notify that person without undue delay and, where feasible, not later than 70 hours after becoming aware of it. |
|
| Loi n°2017-20 portant Code du Numérique en République du Bénin, Livre V, notification des ruptures de sécurité |
Notify the Autorité de Protection des Données Personnelles (APDP) and the affected person without delay of any security breach that has affected their personal data. As a processor, warn the controller without delay of any security breach affecting personal data you process on the controller's behalf. +1 more |
|
| Law on the Protection of Personal Data of Bosnia and Herzegovina, personal data breach notification |
Notify the Agency of a personal data breach without undue delay and, if possible, within 72 hours of becoming aware of the breach, giving the Agency the reasons for the delay where notice comes later. As a processor, notify the controller without undue delay after becoming aware of a personal data breach. +3 more |
|
| Data Protection Act, 2024, personal data breach notification |
Notify the Information and Data Protection Commission of a personal-data breach without undue delay and, where feasible, within 72 hours of becoming aware of it, unless the breach is unlikely to result in a risk to the affected person's rights and freedoms, and give reasons for any later notification. As a data processor, notify the data controller of a personal-data breach without undue delay after becoming aware of it. +1 more |
|
| LGPD, security incident notification |
Notify the ANPD and the affected data subjects of a security incident that may create relevant risk or harm to data subjects, within the reasonable period the ANPD sets by regulation, and state the reasons for the delay when the notice is not immediate. Describe in the notification the nature of the personal data affected, the data subjects involved, the technical and security measures used, the risks related to the incident, and the measures taken or planned to reverse or mitigate its effects. |
Show the other 64 laws
| Electronic Communications Act Articles 261в to 261д, Personal Data Breach Notification by Providers of Public Electronic Communications Services |
If you provide public electronic communications services, notify the KZLD within three days of establishing a personal data breach (Electronic Communications Act Article 261в, paragraph 1). Promptly notify the affected user or other person where the breach may adversely affect their personal data or privacy, unless you have shown the KZLD that appropriate technological protection measures were applied to the data concerned (Article 261в, paragraphs 2 and 3). +1 more |
|
| Law No. 133/V/2001 on the Protection of Personal Data, personal data breach notification |
Notify the CNPD of a personal data breach within 72 hours of becoming aware of it, unless the breach is unlikely to put individuals' rights, freedoms and guarantees at risk, and state the reasons for the delay if you notify later (Article 27(1) and (2)). Make the notification to the CNPD describe the nature of the breach, including where possible the categories and approximate number of data subjects affected, its likely consequences and the measures you have taken or propose, and keep it confidential (Article 27(3)). +2 more |
|
| California Data Breach Notification Law, as amended by SB 446 |
Notify affected California residents of a breach of their unencrypted personal information within 30 calendar days of discovery or notification. Notify the California Attorney General within 15 days of consumer notification when a breach affects more than 500 California residents. |
|
| Cambodia's Draft Law on Personal Data Protection, personal data breach notification proposed |
A data controller must notify the Ministry of Post and Telecommunications immediately, but no later than 72 hours of becoming aware of a personal data breach that may pose a risk to the data subject or another natural person, or give the Ministry valid reasons for any delay. A data controller must notify the affected data subject immediately upon becoming aware of a personal data breach that may pose a high risk to their rights and freedoms, unless the controller has already secured the data, has taken steps removing the high risk, or individual notice would be disproportionately burdensome, in which case a public notice serves instead. +1 more |
|
| Data Protection Act 2021 Revision, personal data breach notification |
Notify the Ombudsman and each affected data subject of a personal data breach without undue delay and no later than five days after you should, with the exercise of reasonable diligence, have been aware of it, describing the breach, its consequences, and the measures taken or recommended (section 16(1)). |
|
| Loi n°007/PR/2015, obligation de notification des violations de données à l'ANSICE |
Notify both ANSICE and the affected data subject, without delay, of any security breach affecting that person's personal data. |
|
| Ley 1581 de 2012, Security Breach Notification to the Authority |
As a data processor, notify the Superintendencia de Industria y Comercio under the same terms when a security code violation creates that risk; neither duty requires telling the affected data subject directly. |
|
| Breach of security re computerized data containing personal information |
Notify each affected Connecticut resident of a breach of security involving personal information without unreasonable delay and no later than 60 days after discovery, unless federal law requires a shorter time. Notify the Connecticut Attorney General of the breach not later than the time when you notify affected residents (section 36a-701b(b)(2)(A)). |
|
| Digital Code, Title III, personal data breach notification |
Notify the Data Protection Authority and the affected data subject without delay of any breach affecting personal data, describing the nature of the breach, the categories and approximate number of affected people and records where possible, a contact point, the likely consequences, and the measures taken or proposed to address it. As a processor, warn the controller without delay of any breach of security affecting personal data you process on the controller's behalf. +1 more |
|
| Consumer Security Breach Notification |
If your business conducts business in the District of Columbia and discovers a breach of the security of a system containing a District resident's personal information, notify each affected resident in the most expedient time possible and without unreasonable delay. If the breach affects 50 or more District residents, also give written notice to the Office of the Attorney General for the District of Columbia, no later than when you notify residents. |
|
| Digital Code, Book I: personal-data breach notification |
Notify the Commission Nationale de Protection des Données à Caractère Personnel of a personal-data breach without undue delay and, at the latest, within 72 hours of becoming aware of it, stating the reasons for any delay beyond that window. Tell the affected individual of the breach without undue delay, in clear and simple terms, where it is likely to result in a high risk to their rights and freedoms. +2 more |
|
| LOPDP, notificación de vulneración de seguridad |
Notify the Authority and the telecommunications regulator of a personal-data security breach as soon as possible and no later than five days after becoming aware of it. Notify the affected data subject within 3 days of learning of the risk, where the breach carries a risk to their fundamental rights and individual freedoms. +3 more |
|
| Egypt Personal Data Protection Law, Personal Data Infringement notification |
Notify the Personal Data Protection Center of any personal data breach within 72 hours of the breach, and notify immediately where the breach relates to national security protection concerns. |
|
| Ley para la Protección de Datos Personales, personal data breach notification |
Notify the Agencia de Ciberseguridad del Estado, the Fiscalia General de la Republica, and every affected data subject of a personal data breach within seventy two hours of becoming aware of it. Tell the Agencia de Ciberseguridad del Estado, in clear and simple language, the incident's nature, the personal data compromised, the immediate corrective actions taken, recommendations for the data subject, and where to learn more, and give the affected data subject the incident's nature, the data compromised, the recommendations, and where to learn more. |
|
| Personal Data Protection Proclamation, personal data breach notification |
Notify the Authority of a personal data breach within 72 hours of becoming aware of it, giving reasons for any delay. Communicate a personal data breach to the affected data subject within 72 hours of becoming aware of it, in clear language, describing the likely consequences, the contact point for more information and the measures taken to address it. +2 more |
|
| Commission Regulation on Personal Data Breach Notification by Electronic Communications Providers (Regulation (EU) No 611/2013) |
If you provide a publicly available electronic communications service, notify every personal data breach to the competent national authority (Article 2(1)), no later than 24 hours after its detection, where feasible, with the information set out in Annex I; detection is deemed to have taken place when you have acquired sufficient awareness that a security incident has occurred that led to personal data being compromised (Article 2(2)). Where the breach is likely to adversely affect the personal data or privacy of a subscriber or individual, also notify that subscriber or individual of the breach, in addition to notifying the competent national authority (Article 3(1)). +3 more |
|
| ePrivacy Directive, Article 4(3) to (5), Personal Data Breach Notification |
If you provide a publicly available electronic communications service and a personal data breach occurs, notify the breach to the competent national authority without undue delay (Article 4(3)). Where the breach is likely to adversely affect the personal data or privacy of a subscriber or individual, also notify that subscriber or individual of the breach without undue delay (Article 4(3)). +1 more |
|
| GDPR Articles 33-34, Breach Notification |
Notify the competent supervisory authority without undue delay, and within 72 hours where feasible, after becoming aware of a personal data breach affecting EU personal data, unless the breach is unlikely to risk individuals' rights and freedoms. |
|
| Law No. 025/2023, personal-data breach notification |
Notify the APDPVP without delay of a personal-data breach, describing its nature, the categories and approximate number of data subjects and records concerned where possible, the data protection officer's or another contact point's details, the likely consequences, and the measures taken or proposed to address it; the law sets no numeric deadline for this notice. Accompany a notification to the APDPVP with supporting evidence of the breach. +2 more |
|
| Personal Data Protection and Privacy Act, 2025, personal data breach notification from a date not yet set |
Notify the Information Commission of a personal data breach within 72 hours of becoming aware of the breach. Notify each affected data subject of a personal data breach without undue delay where the breach carries a high risk to their rights. |
|
| Data Protection Act, notification of security compromises |
Give the data subject enough information in the notification to take protective measures against the consequences of the breach, including the identity of the unauthorised person if known, and communicate it by registered mail, electronic mail, the website, media publication, or another manner the Commission directs. |
|
| Notification of Breaches of Personal Information |
If you hold a Guam resident's computerized personal information for another owner or licensee rather than for yourself, notify that owner or licensee as soon as practicable after discovering a breach. |
|
| Act C of 2003 on Electronic Communications, Section 156, Personal Data Breach Notification by Electronic Communications Providers |
If you provide a publicly available electronic communications service in Hungary, notify the National Media and Infocommunications Authority without delay when you detect a breach of subscriber personal data, meaning accidental or unlawful handling or processing of the personal data you transmit, store or otherwise handle in providing the service (Eht. section 156, paragraphs 2 and 3). Where a breach is likely to harm a subscriber's or another individual's personal data or privacy, also notify that person without undue delay, unless you satisfactorily show the Authority that you applied appropriate technical protection measures to the data affected (Eht. section 156, paragraph 5). |
|
| Personal Information Protection Act, data breach notification |
Notify affected Illinois residents of a data breach in the most expedient time possible and without unreasonable delay after discovering unauthorized acquisition of their computerized personal information, which includes unique biometric data used to authenticate an individual. Notify the Illinois Attorney General once a single breach requires you to notify more than 500 Illinois residents, in the most expedient time possible and without unreasonable delay, and in no event later than when you notify those residents. +4 more |
|
| GDPR Articles 33-34, Breach Notification in Ireland |
Notify the Data Protection Commission without undue delay, and within 72 hours where feasible, after becoming aware of a personal data breach affecting a person in Ireland, unless the breach is unlikely to risk their rights and freedoms. |
|
| Data Protection Act, 2020, reporting a contravention or security breach |
Report any security breach in respect of your operations which affects or may affect personal data, and any contravention of the data protection standards, to the Information Commissioner within 72 hours of becoming aware of the breach or contravention, in the prescribed form and manner. Notify the Information Commissioner without undue delay of any breach of your security measures which affects or may affect personal data. +2 more |
|
| Data Protection Act 2025, personal data breaches |
Notify the Digital Transformation Office of a personal data breach that has resulted in, or is likely to result in, significant harm to affected data subjects, as soon as practicable after becoming aware of the breach. Notify each affected data subject of that same harmful personal data breach as soon as practicable after becoming aware of the breach, or by public notification through widely used media where direct notification is not feasible or would involve disproportionate effort or expense. +2 more |
|
| Law No. 06/L-082 on Protection of Personal Data, personal data breach notification |
Notify the Agency for Information and Privacy of a personal data breach without delay and, where feasible, no later than seventy-two hours after becoming aware of the breach, unless the breach is unlikely to result in a risk to the rights and freedoms of natural persons. Give reasons for the delay if notifying the Agency after that seventy-two-hour period. +3 more |
|
| Law on Electronic Communications Article 74, Personal Data Breach Notification by Electronic Communications Providers |
If you provide public electronic communications networks or services, notify the State Data Protection Inspectorate without delay of a personal data security breach (Law on Electronic Communications Article 74, paragraph 4). Notify the subscriber, registered user or other person without delay where the breach may adversely affect the security of their data or their privacy, unless you prove to the Inspectorate that appropriate technical measures made the data inaccessible to unauthorized persons (Article 74, paragraphs 4 and 5). +1 more |
|
| Maldives Personal Data Protection Bill, personal data breach notification proposed |
A Controller must notify the Data Protection Authority within 72 hours of coming to know of, or reasonably believing in, a personal data breach involving special categories of personal data or data that could enable identity theft or fraud. |
|
| Maryland Personal Information Protection Act (MPIPA), breach notification |
Notify each affected Maryland individual as soon as reasonably practicable, and no later than 45 days after discovering or being notified of the breach, once you determine a likelihood that personal information has been or will be misused. If you maintain computerized data that you do not own or license, notify the owner or licensee of a breach as soon as reasonably practicable, and no later than 10 days after you discover or are notified of the breach (Com. Law 14-3504(c)). |
|
| Ley Federal de Protección de Datos Personales en Posesión de los Particulares, security-breach notice |
Notify the affected data subject immediately of the breach, occurring at any stage of processing personal data, that significantly affects their patrimonial or moral rights. |
|
| Moldova Law No. 195/2024, personal data breach notification |
Notify the National Centre for Personal Data Protection without undue delay, and within 72 hours where feasible, after becoming aware of a personal data breach affecting a person in Moldova, unless the breach is unlikely to risk their rights and freedoms. Communicate the breach to the affected data subject without undue delay where it is likely to result in a high risk to their rights and freedoms, in clear and plain language. +2 more |
|
| Loi sur la Protection des Données Personnelles, notification des violations de données |
Notify the Authority of a personal data breach as soon as possible and, where feasible, within 72 hours of becoming aware of the breach, unless it is unlikely to create a risk to the rights and freedoms of the persons concerned, and give the reasons for the delay when you notify later than that. Communicate a personal data breach to the affected person as soon as possible, in clear language, when it is likely to create a high risk to their rights and freedoms. +2 more |
|
| Telecommunicatiewet Article 11.3a, Personal Data Breach Notification by Electronic Communications Providers |
If you provide a public electronic communications service, notify the Autoriteit persoonsgegevens without delay of a security breach that adversely affects personal data processed in connection with the service in the European Union (Telecommunicatiewet Article 11.3a, paragraph 1). Notify the person whose personal data is concerned without delay where the breach is likely to have adverse effects on their privacy, unless the Autoriteit persoonsgegevens finds that appropriate technical protection measures made the data unintelligible to anyone without a right of access (Article 11.3a, paragraphs 2 and 5). |
|
| Security breach of personal information, notification |
Disclose a security breach of personal information to an affected Nevada resident in the most expedient time possible and without unreasonable delay. Nevada sets no fixed numeric deadline. |
|
| Ley No. 787, Ley de Protección de Datos Personales, security incident notice |
Where the personal data affected belong to a member of the National Police or the Army of Nicaragua, and the security measures the law requires fail or are not observed, immediately inform the affected institution of the breach. |
|
| Loi n° 2022-59, notification des violations de données |
Notify the HAPDP of a personal data breach without delay after becoming aware of it, and justify to the HAPDP any notification made outside that timeframe. Notify the affected person of a personal data breach as soon as possible when it is likely to create a high risk to their rights and freedoms; you need not notify the person where it is reasonable to believe the breach creates no such risk. +1 more |
|
| Nigeria Data Protection Act, 2023, data breach notification |
Notify the Commission of a personal data breach likely to result in a risk to individuals' rights and freedoms within 72 hours of becoming aware of it, describing the nature of the breach and, where feasible, the categories and approximate numbers of data subjects and records concerned. Notify affected data subjects immediately after becoming aware of a breach likely to result in a high risk to their rights and freedoms. +1 more |
|
| Identity Theft Protection Act, security breach notification |
Notify each affected North Carolina resident of a security breach involving their personal information without unreasonable delay, consistent with the legitimate needs of law enforcement. Notify the Consumer Protection Division of the North Carolina Attorney General's Office of every breach requiring notice to any affected person, not only breaches above the 1,000-person threshold. +1 more |
|
| Ontario | Personal Health Information Protection Act, 2004, breach notification by custodians and agents |
Notify the Commissioner at the first reasonable opportunity when the theft, loss or unauthorized use or disclosure meets a prescribed circumstance: reasonable grounds to believe the information was used or disclosed without authority by a person who knew or ought to have known that, reasonable grounds to believe it was stolen, further unauthorized use or disclosure after an initial incident, a pattern of similar incidents, a notice you must give a College, or your own determination that the incident is significant after weighing sensitivity, volume, the number of individuals and the number of custodians or agents responsible. |
| Ley 81 de 2019, personal data breach notification |
Notify the affected data subject as soon as possible after learning that their personal data was stolen without authorization or that its security was otherwise compromised. This Law sets no fixed number of hours or days for that notice and no duty to notify ANTAI of the breach. As an operator of a public communications network, tell affected data subjects about a particular breach of your network's security and the measures you are taking, again with no fixed period stated. |
|
| Ley N° 7593/2025, notificación de un incidente de seguridad from , in 12 months |
Notify the National Data Protection Agency, and the affected person where relevant, of a security incident within 72 hours of becoming aware of it. |
|
| Ley de Información al Ciudadano sobre la Seguridad de Bancos de Información (data breach notification) |
Notify affected Puerto Rico residents of a security breach of an information bank containing their personal information as expeditiously as possible. Report the breach to the Department of Consumer Affairs within ten non-extendable days of detecting it. +1 more |
|
| Law No. 29-2019, personal-data breach notification |
Notify the national commission of a personal-data breach without undue delay and, where possible, within 72 hours of becoming aware of it, unless the breach is not likely to create a risk to the rights and freedoms of natural persons. Communicate the breach to the affected data subject without undue delay, in clear and simple terms, where it is likely to create a high risk to their rights and freedoms. +2 more |
|
| Law 506/2004 Article 3, Personal Data Breach Notification by Electronic Communications Providers |
If you provide publicly available electronic communications services, notify the ANSPDCP without delay of a personal data security breach (Law 506/2004 Article 3, paragraph 6). Notify the subscriber or other person without delay where the breach could affect their personal data or private life, unless you have shown the ANSPDCP, to its satisfaction, that adequate technological protection measures were applied to the data concerned (Article 3, paragraphs 7 and 8). +1 more |
|
| Law relating to the Protection of Personal Data and Privacy, personal data breach notification |
Notify the supervisory authority of the breach within 48 hours of becoming aware of it. As a data processor, notify the data controller of the breach within 48 hours of becoming aware of it. +2 more |
|
| San Marino Law No. 171, personal data breach notification |
Notify the Data Protection Authority without undue delay, and within 72 hours where feasible, after becoming aware of a personal data breach affecting a person in San Marino, under Article 34. Communicate the breach to the affected data subject without undue delay where it is likely to result in a high risk to their rights and freedoms, in clear and plain language. +2 more |
|
| Law on Personal Data Protection, personal data breach notification |
Notify the Commissioner of a breach that may create risk to a person's rights and freedoms without undue delay, and within 72 hours of becoming aware of the breach where that is possible; give reasons for any delay beyond 72 hours. As a processor, notify the controller without undue delay after becoming aware of a breach. +2 more |
|
| Electronic Communications Act (ZEKom-2) Article 227, Personal Data Breach Notification by Providers of Public Communications Services |
If you provide public communications services, notify the Agency for Communication Networks and Services (AKOS) without delay of a personal data security breach (ZEKom-2 Article 227, paragraph 1). Notify the affected subscriber or individual without undue delay where the breach is likely to harm their personal data and privacy, unless you have satisfactorily shown the agency that appropriate technical protection measures were applied to the data concerned (Article 227, paragraphs 2 and 3). +1 more |
|
| Data Protection Act, 2023, personal data breach notification |
Notify the Data Protection Authority of a personal data breach that is likely to result in a risk to the rights and freedoms of individuals within 72 hours after becoming aware of it. Where you extend that deadline for the legitimate needs of law enforcement or to determine the scope of the breach, tell the Authority the grounds for the extension, with supporting evidence, before the original deadline expires. +2 more |
|
| Business data breach of security, notification statute |
Notify each affected South Carolina resident of a breach of security involving personal identifying information in the most expedient time possible and without unreasonable delay. Notify the Consumer Protection Division of the Department of Consumer Affairs and all nationwide consumer reporting agencies if you notify more than 1,000 persons of a breach at one time. |
|
| Draft Law on the Protection of Privacy and Personal Data, breach notification proposed |
Notify the Commissioner for Personal Data Protection of a breach relating to personal data without delay, and no later than 72 hours after becoming aware of the breach, unless the breach is unlikely to pose a risk to individuals' rights and freedoms; if you do not notify within 72 hours, state the reasons for the delay. Include in that notice, at minimum, the nature of the breach, the categories and approximate number of data subjects and records affected, your data protection officer's or another contact point's details, the likely consequences, and the measures taken or proposed to address the breach and mitigate its effects. +2 more |
|
| Law No. 12 of 2024 on Protection of Electronic Personal Data, personal data breach notification |
Notify the Authority immediately on becoming aware of the breach, and expect the Authority to immediately notify the competent authorities where the breach concerns national security matters. Notify the Authority within 72 hours of becoming aware of the breach, with a description of its nature, form and causes, the approximate number of records, persons and categories affected, the data protection officer's contact details, the breach's likely effects, the measures taken or proposed to address it, and documentation of the breach and the corrective action taken. +1 more |
|
| Privacy Act 2025, personal information breaches from a date not yet set |
Notify the Privacy Commission within 72 hours of becoming aware of a personal information breach that is likely to result in a risk to the rights and freedoms of individuals, describing its nature and, where possible, the categories and approximate numbers of data subjects and records concerned. As a data processor, notify the data controller or the data processor that engaged you within 72 hours of becoming aware of a personal information breach, and answer their information requests without undue delay. +1 more |
|
| Data Protection and Privacy Act, 2019, breach notification |
Publicise the breach in the manner the Authority specifies if it directs you to, where the Authority has grounds to believe publicity would protect an affected data subject. |
|
| Draft Law No. 8153, personal data breach notification proposed |
Notify the supervisory authority of a personal data breach within 72 hours of becoming aware of it. Include in that notification the nature of the breach, the number of affected individuals, the data types involved, the likely consequences, and the remedial measures taken. |
|
| UK GDPR Articles 33-34 and PECR, Breach Notification in the United Kingdom |
Notify the Information Commission without undue delay, and within 72 hours where feasible, after becoming aware of a personal data breach affecting a person in the United Kingdom, unless the breach is unlikely to risk their rights and freedoms. |
|
| HIPAA Breach Notification Rule |
Notify affected individuals without unreasonable delay and no later than 60 days after discovering a breach of unsecured protected health information. Notify the Secretary of Health and Human Services of a breach of unsecured protected health information involving 500 or more individuals contemporaneously with the notice to affected individuals. +3 more |
|
| Ley N° 19.670, personal data breach notification |
Notify the affected data subjects immediately and in detail on becoming aware of the breach, describing the measures adopted to address it. |
|
| Breach of personal information notification |
Notify the Virginia Office of the Attorney General and each affected Virginia resident of a breach of system security involving personal information without unreasonable delay after discovery. |
|
| Notice of security breaches involving personal information |
Notify affected Washington residents of a breach of unsecured personal information, including biometric identifiers, in the most expedient time possible and no more than 30 calendar days after discovery. Notify the Washington Attorney General of any breach affecting more than 500 Washington residents within 30 days after the breach was discovered. |
|
| Data Protection Act, 2021, notification of a security breach |
Notify the Data Protection Commissioner within 24 hours of the breach occurring: section 49(1) runs the period from the security breach itself, not from the moment you learn of it. Notify the affected data subject as soon as practicable of any security breach affecting their personal data. +1 more |
|
| Cyber and Data Protection Regulations 2024, security breach notification |
Report a personal data breach to the Authority within 24 hours of becoming aware of it, on Form DP3 in the Fourth Schedule. Inform the affected data subjects within 72 hours where the breach is likely to result in a high risk of adversely affecting individuals' rights and freedoms. |
Sector security regimes
19 laws, 17 jurisdictions| Jurisdiction | Law | What it asks, as read here |
|---|---|---|
| Law No. 25/2024, On Cybersecurity |
Report a significant or substantial cybersecurity incident to AKSK and the relevant CSIRTs, and inform the public or affected users where the incident reaches them; cooperate with AKSK and other operators in sharing cybersecurity threat, vulnerability and incident information. AKSK's own incident categorisation and log retention regulations set the reporting clock and severity thresholds that apply to your designated category. |
|
| Netz- und Informationssystemsicherheits-Verordnung (NISV 2026), Risk-Management Requirements and Significant-Incident Criteria |
Report an incident as significant under Section 35(1) of the NISG 2026 when it meets any of the nine criteria in Section 5(1), or when incidents that are not significant alone meet the repeat-incident test in Section 7 (at least two within six months, same apparent cause and effect, together meeting the financial-loss criterion). |
|
| Zakon o provedbi Uredbe (EU) 2022/2554, Competent Authorities, Incident Reporting and Fines for Financial Entities |
If you are a financial entity supervised by HANFA or the Croatian National Bank under Article 8 of the Act, report each significant ICT incident to HANFA (or to the Croatian National Bank, for the entities it supervises) and to the CSIRT (Article 14). Make those reports through the national platform for cyber threats and incidents set up under the cybersecurity law (Article 15). |
|
| Digital Code, Livre II: Trust Service Provider Security Risk-Management Duty |
Prevent and limit the consequences of security incidents, inform the parties concerned of the harmful effects of such incidents, and ensure the continuity of your services in the event of technical failures or cessation of activity. |
|
| Digital Code, Book II: Electronic Communications Network and Service Security |
Where a particular risk of a security breach exists, inform your users of the risk without delay, of any available remedy, and of its cost. As soon as you become aware of a security breach or integrity loss with a significant impact on your network's or service's operation, notify the cybersecurity authority and the telecoms regulator by registered letter with acknowledgement of receipt. No numeric clock is stated for this notice, unlike the 24-hour clock this jurisdiction's Digital Code sets for a trust service provider or the 72-hour clock it sets for a personal-data breach. |
|
| Act Amending the Financial Supervision Authority Act and Other Acts (DORA Implementation), Credit Institution ICT Risk and Incident Notification |
Notify the Financial Supervision Authority and the Information System Authority of a major ICT-related incident as DORA Article 19 provides, using the reporting forms and deadlines set under DORA Article 20, and, when you notify the Authority of a significant cyber threat under Article 19(2), send the notice to the Information System Authority at the same time (Section 92^4(1), (3) and (4)). |
|
| Commission Implementing Regulation (EU) 2024/2690, Technical and Methodological Requirements for NIS2 Risk-Management Measures |
Establish communication plans and procedures with your CSIRT or, where applicable, your competent authority for incident notification (point 3.5.3(a)). |
|
| DORA, Articles 5-16 (ICT Risk Management Framework) |
Have crisis communication plans that enable a responsible disclosure of, at least, major ICT-related incidents or vulnerabilities to clients and counterparts and to the public, communication policies for staff and external stakeholders, and at least one person tasked with implementing the communication strategy and fulfilling the public and media function (Article 14). |
|
| Payment Services Technical Standards on Strong Customer Authentication, Personalized Security Credentials and Common and Secure Open Standards of Communication |
For identification, rely on qualified certificates for electronic seals or for website authentication under Regulation (EU) No 910/2014 that include the additional attributes in Article 34(3) (Article 34). When exchanging data over the internet, apply secure encryption with strong and widely recognized encryption techniques throughout the communication session. If you issue card-based payment instruments or are an account information service provider or a payment initiation service provider, keep the access sessions offered by account servicing payment service providers as short as possible and terminate them as soon as the requested action is completed. Keep personalized security credentials and authentication codes unreadable, directly or indirectly, by any staff at any time, and inform the payment services user and the issuer of the credentials without undue delay of any loss of their confidentiality under your sphere of competence (Article 35). |
|
| Cybersecurity Act, Risk-Management Measures |
Report a cyber threat, near-incident or cybersecurity incident affecting your electronic information system to the competent cybersecurity incident-handling centre without delay, on the notification clock this jurisdiction's companion incident-notification row sets out. |
Show the other 9 laws
| Ministru kabineta noteikumi Nr. 397, Minimum Cybersecurity Requirements |
Enter each cyber incident in the cyber incident log within 24 hours of detecting it, assess its significance at once, and report a significant incident to the competent cyber incident prevention institution on the early warning, initial report, progress report, intermediate report and final report forms within the clocks of Article 34 of the Law (points 47, 117 and 119). |
|
| Banque du Liban Basic Circular No. 144 (Prevention of Electronic Criminal Acts) |
On learning that a customer has fallen victim to a financially-natured electronic crime, notify Lebanon's Special Investigation Commission of the relevant technical information and direct the customer to file a judicial complaint. |
|
| Malta DORA Regulations (S.L. 330.20) |
Send major ICT-related incident reports and any voluntary notifications of significant cyber threats to the Malta Financial Services Authority, the competent authority that receives them under DORA Article 19 (regulation 4(3)). |
|
| Cyberbeveiligingsbesluit, Security Measures and Incident Notification Details |
In the early warning of a significant incident, give the presumed start time of the incident and, where possible, a description of its nature and visible effects, an estimate of the recovery time and the measures you plan or have taken, and make the notification at the reporting point the Minister sets up (Articles 24 and 25). |
|
| Act of 25 June 2025 on Digital Operational Resilience of the Financial Sector, Supervision and Reporting Provisions |
Report a major ICT-related incident to the Komisja Nadzoru Finansowego with an initial notification, and submit the reports that DORA Article 19(4) requires (Article 18zg). |
|
| Lei n.º 73/2025, Digital Operational Resilience of the Financial Sector |
Report severe ICT-related incidents and any voluntary notification of a significant cyber threat to the competent authority Article 3 gives you: the Banco de Portugal where a credit institution distributes insurance or a credit or payment institution provides crowdfunding services, and otherwise the authority responsible for your prudential supervision (Article 3(2)(a) and (5)). |
|
| Somalia Cybersecurity Act (2026) proposed |
If the Law is enacted, a designated Critical Information Infrastructure operator would have to meet the cybersecurity standards the National Communications Authority sets and comply with its incident reporting obligations; the Authority's description does not state a reporting clock, a reporting threshold, or a penalty for a missed report. |
|
| Cybersäkerhetsförordning (2025:1507), Notification Channels and Supervisory Authorities |
Report incidents under chapter 2, sections 5 to 8 of the Act to the CSIRT unit (section 6 of the ordinance). |
|
| Cyber Security and Resilience (Network and Information Systems) Bill proposed |
If you operate an essential service other than a data center, give your designated competent authority an initial notification of an incident that has affected or is affecting the operation or security of the systems you rely on, and whose impact in the United Kingdom has been, is or is likely to be significant, within 24 hours of first being aware of it, and a full notification within 72 hours of that time, in writing and in the form and manner the authority determines, sending a copy to the computer security incident response team (the CSIRT) at the same time (new regulation 11). |
Product security requirements
7 laws, 7 jurisdictions| Jurisdiction | Law | What it asks, as read here |
|---|---|---|
| Loi n°2017-20 portant Code du Numérique en République du Bénin, Livre VI (cybersécurité), sécurité des réseaux et essai de vulnérabilité des produits |
Inform consumers of every vulnerability detected in that test, together with the solution recommended to remedy it. |
|
| Anatel Cybersecurity Requirements for CPE (Customer Premises Equipment) |
Maintain a public, Portuguese-language support page listing known vulnerabilities in your products together with their mitigations, and keep making corrected software or firmware available. |
|
| Cybersecurity Law, Network Product and Service Security Duties |
On discovering a security defect, vulnerability, or other risk in your product or service, immediately take remedial measures, notify affected users as provided, and report the defect or vulnerability to the competent authority; the statute states no numeric clock for this notice, only immediacy. |
|
| Digital Code, Livre IV: ICT Product and Service Vendor Security Certification |
Inform consumers of every vulnerability detected in your information and communication technology products and services, and of the solutions you have deployed to remedy them. |
|
| Cyber Resilience Act, Obligations of Open-Source Software Stewards from , in 13 months |
To the extent that you are involved in the development of products with digital elements, notify any actively exploited vulnerability contained in a product, of which you become aware, to the CSIRT designated as coordinator and to ENISA through the single reporting platform, as Article 14(1) requires of a manufacturer (Article 24(3)). To the extent that severe incidents having an impact on the security of products with digital elements affect the network and information systems you provide for the development of such products, notify the severe incident as Article 14(3) requires of a manufacturer, and inform the impacted users as Article 14(8) requires of a manufacturer (Article 24(3)). |
|
| Kyberkestävyyslaki, National Enforcement and Market Surveillance for the Cyber Resilience Act |
Report an actively exploited vulnerability in your product with digital elements, or a severe incident affecting its security, under the Regulation's own Article 14 clock; this Act does not restate the duty or its deadline. |
|
| Cyber Resilience Regulations, MDIA Designation under the Cyber Resilience Act |
Report an actively exploited vulnerability or a severe incident to ENISA's single reporting platform under the Regulation's own Article 14 and Article 16; from , regulation 10 of the Cyber Resilience Regulations, 2026 designates the national CSIRT as the CSIRT designated as coordinator for Regulation (EU) 2024/2847, which article 8(1) of the Measures for a High Common Level of Cybersecurity across the European Union (Malta) Order establishes within the Malta Information Technology Agency. |
Comprehensive regime
2 laws, 2 jurisdictions| Jurisdiction | Law | What it asks, as read here |
|---|---|---|
| Ley 149/2022, De Protección de Datos Personales, general regime |
Notify the competent authority of cybersecurity incidents affecting personal data held in a registry, file, archive, or database under your custody. |
|
| Act on the Protection of Personal Information, personal information of persons under 16 from a date not yet set |
Give the notice or public announcement of the purpose of use that Article 21 requires, and the notice of a data breach that Article 26(2) requires, to the legal representative of a person under 16 and not to the person (Article 40-2(1)). |
AI governance
1 law, 1 jurisdiction| Jurisdiction | Law | What it asks, as read here |
|---|---|---|
| Artificial Intelligence Risk Management and Security Act of 2026 proposed |
If you are a developer or provider of a frontier AI model, or an operator of critical infrastructure that uses an AI model to manage industrial control systems or other operational technologies, report any confirmed AI safety incident or AI security incident within 30 days of confirmation, and within 72 hours if the incident poses an imminent threat to national security, critical infrastructure or public safety. |
Cross border transfer
1 law, 1 jurisdiction| Jurisdiction | Law | What it asks, as read here |
|---|---|---|
| Resolución 58/2022 (MINCOM), security and localization rules for personal data in electronic form |
Notify the competent authorities of cybersecurity incidents affecting personal data in electronic form under your custody. |
Security baseline statutes
1 law, 1 jurisdiction| Jurisdiction | Law | What it asks, as read here |
|---|---|---|
| Tort Liability for Cybersecurity Programs, affirmative defense for a reasonable security program |
To claim the defense against a tort claim alleging that a failure to implement reasonable information security controls resulted in a data breach of personal information or restricted information, create, maintain, and comply with a written cybersecurity program containing administrative, technical, operational, and physical safeguards, designed to continually evaluate and mitigate reasonably anticipated threats, evaluate the maximum probable loss from a data breach at least annually, and communicate to affected parties the extent of any risk and steps to reduce damages once a breach is known to have occurred. |
Sensitive categories
1 law, 1 jurisdiction| Jurisdiction | Law | What it asks, as read here |
|---|---|---|
| Ontario | Personal Health Information Protection Act, 2004, electronic service providers and health information network providers |
If you are a health information network provider (you serve two or more custodians, primarily so that they can disclose personal health information to one another electronically), notify every applicable custodian at the first reasonable opportunity if you used, disclosed or disposed of the information outside those restrictions or an unauthorized person accessed it. |
Full text of the NIST Cybersecurity Framework, public domain (a US government work). Every control of the framework.