Law / Frameworks / NIST CSF 2.0 / Respond
NIST CSF 2.0, RespondRS.CO-03
Information is shared with designated internal and external stakeholdersNIST Cybersecurity Framework, version 2.0, February 2024 (NIST CSWP 29), RS.CO-03
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 .
- 55
- laws
- 40
- jurisdictions
- 0
- with court rulings behind them
- 3
- not yet in force
- 3
- 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., 6 laws
- FINOS AIGFAIR-DET-004 AI System Observability, 47 laws
- FINOS AIGFAIR-DET-021 Agent Decision Audit and Explainability, 45 laws
- FINOS AIGFAIR-DET-001 AI Data Leakage Prevention and Detection, 2 laws
- ENISA NIS2 guidance3.1 Incident handling policy, 44 laws
- ENISA NIS2 guidance3.4 Event assessment and classification, 44 laws
- ENISA NIS2 guidance3.5 Incident response, 44 laws
- 2 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
46 laws, 34 jurisdictions| Jurisdiction | Law | What it asks, as read here |
|---|---|---|
| Netz- und Informationssystemsicherheitsgesetz 2026 (NISG 2026), Significant-Incident Reporting Obligations |
Submit an interim report on request, and a final report no later than one month after the 72-hour notification, or, if the incident is still ongoing at that point, a progress report followed by a final report no later than one month after you have finished handling the incident (Section 34(2)). |
|
| Loi du 26 avril 2024, Significant-Incident Notification Obligations |
Submit an interim report if the national CSIRT or the competent sectoral authority asks for one, and a final report no later than one month after the incident notification, describing the incident in detail, its severity and impact, the likely threat or root cause, the mitigation measures applied and in progress, and any cross-border impact. If the incident is still ongoing when the final report falls due, submit a progress report at that point, followed by a final report within one month of the final handling of the incident (Article 35, paragraph 1, point 5). |
|
| Zakon o kibernetičkoj sigurnosti and Uredba o kibernetičkoj sigurnosti, Incident and Cyber-Threat Reporting Obligations |
Submit an interim report to the CSIRT when it requests one, within the period the CSIRT sets, of no less than 48 hours and no more than seven days from receipt of the request. |
|
| Digital Code, Livre IV: General Cyberattack Cooperation and Incident-Reporting Duty |
Cooperate in detecting cyberattacks in accordance with the applicable legal and regulatory provisions. |
|
| NIS 2-loven, Significant-Incident Reporting and Recipient-Notice Duties |
Submit an interim report if your CSIRT asks for one, and a final report no later than one month after your notification, describing the incident in detail, its severity and impact, the likely threat or root cause, mitigating measures applied and under way, and any cross-border effects. If the incident is still ongoing at that point, submit a status report instead and the final report within one month of the incident being handled. |
|
| Küberturvalisuse seadus (KüTS), Duty to Notify of a Cyber Incident |
Submit an interim report if RIA asks for one, and a final report within one month of the incident report, or, if the incident is still unresolved at that point, treat that report as interim and submit a further final report within one month of resolution. |
|
| Critical Infrastructure Cybersecurity Proclamation, Cyber Incident Reporting to National CERT from , in 8 months |
Provide the National Computer Emergency Response Center the information it requests and cooperate appropriately with its activities when it is responding to a cyberattack. |
|
| Commission Delegated Regulation (EU) 2022/1645, External Reporting of Information Security Incidents and Vulnerabilities (IS.D.OR.230) |
Submit a follow-up report on the actions you have taken or intend to take to recover and to prevent similar incidents as soon as those actions are identified (point IS.D.OR.230(c), point (3)). |
|
| Commission Delegated Regulation (EU) 2024/1366, Cybersecurity Network Code for Cross-Border Electricity Flows: Information Sharing on Cyber-Attacks and Threats |
Provide your CSIRTs without undue delay with any information related to a reportable cyber threat that may have a cross-border effect (Article 38(6)). When you share information under Article 38, specify that it is submitted pursuant to the Regulation, which kind of information it is, and, for a reportable cyber-attack, its level on the classification scale with the information leading to that classification (Article 38(7)). |
|
| Commission Implementing Regulation (EU) 2023/203, External Reporting of Information Security Incidents and Vulnerabilities in Aviation (IS.I.OR.230) |
Submit a follow-up report on the actions you have taken or intend to take to recover and to prevent similar incidents as soon as those actions are identified (point IS.I.OR.230(c), point (3)). |
Show the other 36 laws
| DORA Technical Standards on the Standard Forms, Templates and Procedures for Reporting Major ICT-Related Incidents and Notifying Significant Cyber Threats |
When you submit an intermediate or a final report, use the Annex I template to submit all required information and update, where applicable, the information that you provided earlier (Article 1(4)). If you notify a significant cyber threat to your competent authority under Article 19(2) of Regulation (EU) 2022/2554, use the template in Annex III, follow the data glossary and instructions in Annex IV, and ensure that the information is complete and accurate (Article 8). |
|
| DORA, Article 19 (reporting of major ICT-related incidents), with the time limits of Delegated Regulation (EU) 2025/301 |
Submit an intermediate report within 72 hours of the initial notification, and submit an updated intermediate report without undue delay and in any case when you have recovered regular activities. Submit a final report no later than one month after the intermediate report, or your latest updated one, once you know the root cause and the actual impact figures. |
|
| EUCC Certification Scheme, Vulnerability Impact Analysis Report and Disclosure |
Transmit the report to the certification body or the national cybersecurity certification authority, in accordance with Article 56(8) of Regulation (EU) 2019/881, without undue delay (Article 35(4)). Upon withdrawal of the certificate, disclose and register any publicly known and remediated vulnerability in the ICT product on the European vulnerability database established under Article 12 of Directive (EU) 2022/2555, or on the other online repositories referred to in Article 55(1), point (d), of Regulation (EU) 2019/881 (Article 39). |
|
| Kyberturvallisuuslaki, Significant-Incident Reporting Obligations |
Provide an interim report on the authority's request, or within one month of your follow-up notification if the incident is long-running, and a final report within one month of the follow-up notification, or within one month of the incident's resolution if it is still ongoing at that point, describing the incident, its likely root cause, mitigation measures taken, and any cross-border effects. |
|
| Laki sosiaali- ja terveydenhuollon asiakastietojen käsittelystä, Reporting of Deviations in Information Systems and Wellbeing Applications and of Significant Information Security Disturbances |
If a deviation in an information system or wellbeing application may cause a significant risk to client or patient safety or to information security, notify the Licensing and Supervisory Authority (Lupa- ja valvontavirasto); if you are a pharmacy and the deviation may put your operations at significant risk, also notify the Finnish Medicines Agency (section 90). |
|
| BSI-Gesetz (BSIG), Incident Notification |
Submit an intermediate report on the BSI's request, and a final report within one month of the 72-hour notification, or, if the incident is still ongoing at that point, a progress report followed by a final report once you have finished handling it. |
|
| Law 5160/2024, Significant-Incident Reporting Obligations |
Submit an interim report if the National Cybersecurity Authority requests one. Submit a final report no later than one month after the 72-hour notification, describing the incident in detail, its severity and effects, the likely threat or root cause, mitigating measures applied, and any cross-border impact; if the incident is still ongoing at that point, submit a progress report instead and the final report within one month of its resolution. |
|
| Cybersecurity Act, Incident Notification and Cybersecurity Fine |
Submit an interim status report if the center asks for one, and, if the incident is still ongoing when the final report is due, a report on the results achieved so far followed by a final report within one month after you have finished handling the incident (Decree 418/2024, Section 77(1)). |
|
| CERT-In Cyber Security Directions, Incident Reporting, Logging and Time Synchronisation |
Enable logs of all your ICT systems and retain them securely, within Indian jurisdiction, on a rolling 180-day basis, and provide them to CERT-In together with an incident report or when CERT-In orders or directs you to. |
|
| European Union (NIS) Regulations 2018, Incident Notification |
Notify the CSIRT again as soon as practicable once the incident has been resolved, and in any event not later than 72 hours after that time (Regulations 18(9) and (10), 22(10) and (11)). |
|
| National Cyber Security Bill, Incident Response Powers and Reporting Obligations proposed |
Where the incident is still ongoing when the final report falls due, submit a progress report at that time and a final report within one month of handling the incident (Head 15). |
|
| Decreto Legislativo 4 settembre 2024, n. 138 (Decreto NIS2), Incident Notification |
Submit an intermediate report on CSIRT Italia's request, and a final report within one month of the notification (or, for an incident still ongoing at that point, a monthly progress report and a final report within one month of the incident's resolution). |
|
| Cybersecurity Act 2026, Duty to Report a Cybersecurity Incident from a date not yet set |
Provide any further information the National CERT or a Sectoral CERT requests about the incident, and allow either CERT to access your network and information infrastructure to analyse the incident, detect other threats, identify vulnerabilities, and advise on preventative, mitigating or remedial measures. |
|
| Nacionālās kiberdrošības likums, Coordinated Vulnerability Disclosure and Remediation |
Where you discover a vulnerability in a subject's information system or electronic communications network, report it to the competent institution within five working days; you may report anonymously and ask that your identity be kept confidential. |
|
| Nacionālās kiberdrošības likums, Incident Notification |
Within one month of the initial report, submit a final report on the incident's resolution, or, if it is still unresolved at that point, a progress report followed by a final report once you have resolved it; submit an intermediate report if the competent institution requests one. |
|
| Cyber-Sicherheitsgesetz (CSG), Incident Notification |
Submit an intermediate report on the Stabsstelle Cyber-Sicherheit's request, and a final report within one month of the 72-hour notification, describing the incident's severity and impact in detail, the likely threat or root cause, and the mitigation measures taken. If the incident is still ongoing when the final report falls due, submit a progress report at that point and a final report within one month of the incident being dealt with (Article 6(2)(e)). |
|
| Loi du 20 décembre 2024, Cybersecurity Certification Authority and Vulnerability Notices |
If you hold a European cybersecurity certificate, issue an EU declaration of conformity, or are a conformity assessment body, inform ILNAS in writing within 72 hours of learning of a vulnerability or irregularity that may affect compliance with the security requirements linked to the certification of a product, service or process (Loi du 20 décembre 2024, Article 5(2)). |
|
| Loi du 5 mai 2026 relative à la cybersécurité (NIS2), Incident Notification |
Submit an intermediate report if a CSIRT or the competent authority requests one, and a final report within one month of the 72-hour notification, or, if the incident is still ongoing at that point, a progress report followed by a final report within one month of the handling of the incident (Article 14, paragraph 4). |
|
| Electronic Communications Networks and Services (General) Regulations, Security Incident Notification to the Malta Communications Authority |
Where there is a particular and significant threat of a security incident, inform the users who may be potentially affected of any possible protective measures or remedies they can take and, where appropriate, of the threat itself (regulation 28(7)). |
|
| Measures for a High Common Level of Cybersecurity across the European Union (Malta) Order, Significant-Incident Reporting to the National CSIRT |
Submit an intermediate report on relevant status updates if the national CSIRT asks for one, and a final report not later than one month after the incident notification, covering a detailed description of the incident, its likely root cause, the mitigation applied and any cross-border impact; if the incident is still ongoing then, send a progress report at that point and a final report within one month of handling it. |
|
| FSM Cybersecurity Act 2025 (Bill), Critical Information Infrastructure Incident Reporting Clock proposed |
For an ongoing significant cybersecurity incident, submit a progress report to the Secretary of Justice and the CERT-FSM within 30 days of the notification, and a final report within 30 days of the handling of the incident (Section 412(2)(d)). |
|
| Law on Information Security, Cyber Threat and Incident Reporting |
For an incident the Agency rates medium, submit a first report within 72 hours of your initial notification, a further report without delay on any new development, continuing reports every 72 hours while the incident lasts, and a final report within 30 days of resolving it (Article 33). For an incident the Agency rates high, follow the same reporting sequence on a tighter clock: continuing reports every 24 hours while the incident lasts (Article 34). |
|
| Cyberbeveiligingswet, Significant-Incident Reporting Obligations |
Submit an interim report if your CSIRT or competent authority asks for one. Submit a final report no later than one month after your notification, describing the incident in detail, its severity and effects, the likely threat or root cause, mitigating measures applied, and any cross-border effects; if the incident is still ongoing at that point, submit a progress report instead and the final report within one month of resolution. |
|
| New York Department of Financial Services Cybersecurity Regulation, Notices to the Superintendent |
Promptly provide the Superintendent any information requested about a reported incident, and continue updating the Superintendent with material changes or new information previously unavailable; the regulation states no separate numbered clock for either duty. 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. |
|
| Ustawa o krajowym systemie cyberbezpieczeństwa (KSC), Zgłaszanie Incydentów Poważnych |
If the handling of a significant incident has not ended when the final report falls due, submit a progress report on the handling to the competent sectoral CSIRT, and submit the final report no later than one month after the handling of the incident ends (Article 12b). |
|
| Regime Jurídico da Cibersegurança, Significant-Incident Reporting Obligations |
Submit a final report within 30 working days of your end-of-impact notification, describing the incident, its impact, the mitigating measures you took and any residual impact still present, and submit an interim report if the competent authority asks for one; if the incident is still ongoing when the final report falls due, submit that interim report at the authority's request every week until you submit the final report (Article 44(1) and (3)). |
|
| Ordonanța de urgență nr. 155/2024, Incident Notification |
Report to the national cybersecurity-incident-response team any information that lets it establish a cross-border impact of the incident, without undue delay and in any event within 6 hours of becoming aware of that information (Article 15(3)). |
|
| Law on Information Security, Incident Reporting Obligations |
While the incident continues, submit a status report to the single incident-reporting system every three days for a medium-level incident, or every 24 hours for a high or very high-level incident. Submit a final report within 15 days after the incident ends, covering its type, cause, duration, scope of impact, any cross-border effect, and the steps you took to remedy it. +1 more |
|
| Vyhláška NBÚ č. 226/2025 Z. z., Details of Cyber Security Reports |
When you report a significant cyber threat, a near miss or a vulnerability, give the particulars of Annex 3: the type, description, possible impact and time of discovery of what you report and, for a vulnerability, the ICT product, ICT service or operational technology concerned and its manufacturer or provider where you know it. |
|
| Zákon o kybernetickej bezpečnosti (Cybersecurity Act), Incident and Vulnerability Notification |
On the CSIRT unit's request, report updated or other requested information about how the incident is progressing. No later than one month after the 72-hour notification, report a final report describing the incident, its severity and impact, the threat type or probable root cause, the mitigating measures taken and under way, and any cross-border impact. +2 more |
|
| Anteproyecto de Ley de Coordinación y Gobernanza de la Ciberseguridad, Incident Reporting Obligations proposed |
As drafted, the Anteproyecto would require you to submit an interim report when your reference CSIRT or the competent authority asks for one, and a final report within one month of submitting 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 (Article 18(6)(c) to (e)). As drafted, the Anteproyecto would require you to communicate to the recipients of your service, as soon as possible, a significant cyberthreat that could affect them and any mitigating measures they can take. |
|
| Cybersäkerhetslag, Incident Notification |
On the authority's request, submit an interim report with relevant status updates on the significant incident. No later than one month after your incident notification, submit a final report; if the significant incident is still ongoing at that point, submit a progress report instead and a final report within one month after you have resolved it. |
|
| Cybersecurity Law, Reporting and Cooperation Duties |
Provide the Cybersecurity Directorate promptly with any data, information, document, hardware, software, or other contribution it requests in connection with its duties. |
|
| Cyber Incident Reporting for Critical Infrastructure Act of 2022 (CIRCIA) from a date not yet set |
Once the final rule takes effect, promptly submit an update to a previously submitted covered cyber incident report whenever substantial new or different information becomes available or a ransom payment is later made, continuing until your organization notifies the Agency that the incident has concluded and been fully mitigated and resolved, and preserve data relevant to the incident or payment under the procedures the final rule establishes. |
|
| Safeguarding Covered Defense Information and Cyber Incident Reporting (DFARS 252.204-7012) |
Submit any malicious software you isolate in connection with a reported incident to the Department of Defense Cyber Crime Center, following that Center's instructions, and never send it to the contracting officer. |
|
| Law on Cybersecurity, cybersecurity incident notification duty |
If you investigate the incident yourself because you hold the resources and technical means to do so, report the results to the State Security Service. |
Breach notification
3 laws, 3 jurisdictions| Jurisdiction | Law | What it asks, as read here |
|---|---|---|
| Personal Information Protection Act, data breach notification |
If you are a State agency and you determine who perpetrated a breach, report that to the General Assembly within 5 days after the determination, unless the report would jeopardize the security of Illinois residents or compromise a security investigation. |
|
| Law 506/2004 Article 3, Personal Data Breach Notification by Electronic Communications Providers |
Inform subscribers of the risk and its possible consequences where a breach of data security creates a risk (Article 3, paragraph 5). |
|
| Cyber and Data Protection Regulations 2024, security breach notification |
Answer the Authority's information request about a data breach within 14 days of that request, and cooperate with its enquiries or investigations. |
Sector security regimes
3 laws, 3 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. |
|
| BRH Circulaire 126, Information Security Rules for Financial Institutions |
Keep your security committee systematically informed of incidents capable of compromising information security and of the measures taken to address them. |
|
| Lei n.º 73/2025, Digital Operational Resilience of the Financial Sector |
If you make a voluntary notification of a significant cyber threat under DORA Article 19(2), also send it on the standard templates to the national CSIRTs (Article 5). |
Product security requirements
2 laws, 2 jurisdictions| Jurisdiction | Law | What it asks, as read here |
|---|---|---|
| Cybersecurity Act (Zákon o kybernetické bezpečnosti), Cybersecurity Certification: Authorisation, Suspension and Offences |
As a holder of a European cybersecurity certificate, inform the conformity assessment bodies concerned of any vulnerabilities or irregularities found later (Section 61(2)). |
|
| EUCC Certification Scheme, Vulnerability Management by the Holder of a Certificate |
When a potential vulnerability impacts a composite product, inform the holders of dependent EUCC certificates (Article 33(4)). In response to a reasonable request by the certification body that issued the certificate, transmit all relevant information about potential vulnerabilities to that certification body (Article 33(5)). |
Comprehensive regime
1 law, 1 jurisdiction| Jurisdiction | Law | What it asks, as read here |
|---|---|---|
| Ley N° 18.331, Personal Data Protection and Habeas Data Law |
If you operate a public communications network or offer an electronic communications service, secure the network and the service, and tell subscribers about any particular risk of a security breach and the measures to take. |
Full text of the NIST Cybersecurity Framework, public domain (a US government work). Every control of the framework.