Law / Frameworks / NIST CSF 2.0 / Govern
NIST CSF 2.0, GovernGV.OV-03
Organizational cybersecurity risk management performance is evaluated and reviewed for adjustments neededNIST Cybersecurity Framework, version 2.0, February 2024 (NIST CSWP 29), GV.OV-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 .
- 4
- laws
- 2
- 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-P5 Protection processes are improved., 2 laws
A law in force is unmarked; the rest wear their state: not yet in force
Sector security regimes
3 laws, 2 jurisdictions| Jurisdiction | Law | What it asks, as read here |
|---|---|---|
| Decree on the Security Measures of a Provider of a Regulated Service in the Lower-Obligations Regime (Vyhláška č. 410/2025 Sb.) |
Keep an overview of the security measures you have introduced, will introduce with deadlines, priority and a responsible person, and have not introduced with reasons; update it and evaluate the measures' effectiveness at least once a year; keep each version for at least four years (Section 3(2)). |
|
| Commission Implementing Regulation (EU) 2024/2690, Technical and Methodological Requirements for NIS2 Risk-Management Measures |
Establish a policy and procedures to assess whether your cybersecurity risk-management measures are effectively implemented and maintained (point 7.1), offer your employees an awareness raising programme and give those whose roles require security skills regular training (points 8.1.2 and 8.2.1), and apply the Annex's requirements on cryptography, human resources security, access control, asset management, and environmental and physical security (points 9 to 13). |
|
| DORA, Articles 5-16 (ICT Risk Management Framework) |
Unless you are a microenterprise, assign responsibility for managing and overseeing ICT risk to a control function with an appropriate level of independence, keep ICT risk management, control and internal audit functions segregated, have the framework audited internally on a regular basis by auditors with sufficient knowledge, skills and expertise in ICT risk, and establish a formal follow-up process for critical ICT audit findings (Article 6(4), (6) and (7)). |
Product security requirements
1 law, 1 jurisdiction| Jurisdiction | Law | What it asks, as read here |
|---|---|---|
| L-Category Vehicles, Protection Against Cyberattacks Under UN Regulation No 155 (Annex XVIII to Delegated Regulation (EU) No 44/2014) from , in 14 months |
Report at least once a year, or more frequently if relevant, the outcome of your monitoring activities, including information on new cyber-attacks, and confirm that the mitigations implemented are still effective (paragraph 7.4.1). |
Full text of the NIST Cybersecurity Framework, public domain (a US government work). Every control of the framework.