Law / Frameworks / NIST CSF 2.0 / Identify
NIST CSF 2.0, IdentifyID.RA-08
Processes for receiving, analyzing, and responding to vulnerability disclosures are establishedNIST Cybersecurity Framework, version 2.0, February 2024 (NIST CSWP 29), ID.RA-08
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 .
- 9
- laws
- 7
- jurisdictions
- 0
- with court rulings behind them
- 1
- not yet in force
Related controls in other frameworks the same duties, in at least two laws we track, reach both
- NIST Privacy FrameworkPR.PO-P10 A vulnerability management plan is developed and implemented., 9 laws
- FINOS AIGFAIR-PREV-007 Legal and Contractual Frameworks for AI Systems, 9 laws
- FINOS AIGFAIR-PREV-008 Quality of Service (QoS) and DDoS Prevention for AI Systems, 9 laws
- FINOS AIGFAIR-PREV-012 Role-Based Access Control for AI Data, 9 laws
- 4 more in the FINOS AIGF
- ENISA NIS2 guidance2.1 Risk management framework, 8 laws
- ENISA NIS2 guidance3.1 Incident handling policy, 8 laws
- ENISA NIS2 guidance4.1 Business continuity and disaster recovery plan, 8 laws
- 5 more in the ENISA NIS2 guidance
A law in force is unmarked; the rest wear their state: not yet in force
Product security requirements
6 laws, 5 jurisdictions| Jurisdiction | Law | What it asks, as read here |
|---|---|---|
| Security Standards for Smart Devices |
Publish a means for a security issue affecting the device to be reported to the manufacturer, and provide status updates on the resolution of a reported issue. |
|
| Anatel Cybersecurity Requirements for CPE (Customer Premises Equipment) |
Provide a dedicated, securely reachable channel, such as an HTTPS web form or a PGP-encrypted email address, for a customer, end user, or third party to report a security vulnerability, and publish a coordinated vulnerability-disclosure policy on your website covering how you want to be notified, what a reporter should expect, and your process's scope and limits. |
|
| Cyber Resilience Act, Essential Requirements and Manufacturer Obligations from , in 13 months |
From (Article 71(2)), when you identify a vulnerability in a component integrated in your product, including an open-source component, report the vulnerability to the person or entity manufacturing or maintaining the component and address and remediate it under the vulnerability handling requirements of Annex I, Part II. If you developed a software or hardware modification to address the vulnerability, share the relevant code or documentation with that person or entity, where appropriate in a machine-readable format (Article 13(6)). Put in place a coordinated vulnerability disclosure policy and a contact channel for reporting a vulnerability, and disclose the end date of the support period to the buyer at the time of purchase. |
|
| EUCC Certification Scheme, Vulnerability Management by the Holder of a Certificate |
It reaches you if you hold an EUCC certificate for an ICT product issued under the European Common Criteria-based cybersecurity certification scheme; Chapter VI applies to ICT products for which an EUCC certificate was issued (Article 32). Establish and maintain all necessary vulnerability management procedures in accordance with Chapter VI, supplemented where necessary by the procedures set out in EN ISO/IEC 30111 (Article 33(1)). Maintain and publish appropriate methods for receiving information on vulnerabilities related to your products from external sources, including users, certification bodies and security researchers (Article 33(2)). |
|
| Law 4961/2022 (Ν. 4961/2022), Chapter Γ' of Part B, Cybersecurity of Internet of Things Devices |
As a manufacturer, keep for each device a procedure for handling an incident or vulnerability that a user finds, documenting its nature, giving detailed instructions for dealing with it and listing mitigation measures (Article 39). |
|
| Product Security Requirements for Connectable Products |
Publish at least one point of contact for reporting a security issue affecting the product, in English, free of charge, without requiring the reporter's personal information, and state when the reporter will get an acknowledgment and status updates. |
Vulnerability and incident reporting
2 laws, 2 jurisdictions| Jurisdiction | Law | What it asks, as read here |
|---|---|---|
| Legge 28 giugno 2024, n. 90, Incident Notification and Vulnerability Remediation Duties |
If ACN notifies you of a specific vulnerability you are exposed to, as an entity in Article 1(1), a national cybersecurity perimeter entity or an electronic communications provider under Article 40(3) of the Electronic Communications Code, apply the remedies it indicates without delay and within 15 days of its notice, unless technical or organisational reasons you have promptly communicated to ACN prevent it (Article 2). |
|
| Nacionālās kiberdrošības likums, Coordinated Vulnerability Disclosure and Remediation |
Once the competent cyber incident prevention institution relays a substantiated report that a vulnerability exists in a system or network you operate, remediate it within the deadline the institution sets, no later than 90 days from when you received the information. Report your remediation progress to the institution as you go, and, if you cannot remediate within 90 days for objective reasons, request an extension, which the institution may grant up to a total of 180 days from the report's submission. |
Sector security regimes
1 law, 1 jurisdiction| Jurisdiction | Law | What it asks, as read here |
|---|---|---|
| Commission Implementing Regulation (EU) 2024/2690, Technical and Methodological Requirements for NIS2 Risk-Management Measures |
Address without undue delay the vulnerabilities you identify as critical to your operations, and lay down a procedure for disclosing vulnerabilities in accordance with the applicable national coordinated vulnerability disclosure policy (points 6.10.2(c) and (e)). |
Full text of the NIST Cybersecurity Framework, public domain (a US government work). Every control of the framework.