Law / Frameworks / NIST CSF 2.0

NIST Cybersecurity Framework

Below are its 106 controls in the framework's own order, and under each one the laws we track that bear on it. Each mapping is our reading that a law bears on a control, never a finding that running the control meets the law.

Where the law lands in the framework

79of 106 controls have law526laws189jurisdictions

GV.OC-01: no law we trackGV.OC-02: no law we trackGV.OC-03: 102 laws in 66 jurisdictionsGV.OC-03 102GV.OC-04: no law we trackGV.OC-05: no law we trackGV.RM-01: 1 law in 1 jurisdictionGV.RM-02: 3 laws in 3 jurisdictionsGV.RM-03: 1 law in 1 jurisdictionGV.RM-04: no law we trackGV.RM-05: 1 law in 1 jurisdictionGV.RM-06: 7 laws in 7 jurisdictionsGV.RM-07: no law we trackGV.RR-01: 34 laws in 28 jurisdictionsGV.RR-02: 32 laws in 25 jurisdictionsGV.RR-03: 2 laws in 2 jurisdictionsGV.RR-04: 7 laws in 7 jurisdictionsGV.PO-01: 73 laws in 55 jurisdictionsGV.PO-02: 4 laws in 4 jurisdictionsGV.OV-01: no law we trackGV.OV-02: 1 law in 1 jurisdictionGV.OV-03: 4 laws in 2 jurisdictionsGV.SC-01: 7 laws in 6 jurisdictionsGV.SC-02: no law we trackGV.SC-03: no law we trackGV.SC-04: no law we trackGV.SC-05: 55 laws in 50 jurisdictionsGV.SC-06: 15 laws in 13 jurisdictionsGV.SC-07: 16 laws in 11 jurisdictionsGV.SC-08: 1 law in 1 jurisdictionGV.SC-09: no law we trackGV.SC-10: 1 law in 1 jurisdictionID.AM-01: 1 law in 1 jurisdictionID.AM-02: 10 laws in 7 jurisdictionsID.AM-03: no law we trackID.AM-04: 2 laws in 2 jurisdictionsID.AM-05: 7 laws in 6 jurisdictionsID.AM-07: 6 laws in 6 jurisdictionsID.AM-08: 54 laws in 45 jurisdictionsID.RA-01: 7 laws in 4 jurisdictionsID.RA-02: no law we trackID.RA-03: 4 laws in 3 jurisdictionsID.RA-04: 4 laws in 3 jurisdictionsID.RA-05: 30 laws in 23 jurisdictionsID.RA-06: 44 laws in 36 jurisdictionsID.RA-07: 5 laws in 4 jurisdictionsID.RA-08: 9 laws in 7 jurisdictionsID.RA-09: 4 laws in 4 jurisdictionsID.RA-10: no law we trackID.IM-01: 26 laws in 18 jurisdictionsID.IM-02: 10 laws in 6 jurisdictionsID.IM-03: 3 laws in 1 jurisdictionID.IM-04: 25 laws in 19 jurisdictionsPR.AA-01: 2 laws in 2 jurisdictionsPR.AA-02: 1 law in 1 jurisdictionPR.AA-03: 10 laws in 6 jurisdictionsPR.AA-04: no law we trackPR.AA-05: 15 laws in 11 jurisdictionsPR.AA-06: 1 law in 1 jurisdictionPR.AT-01: 9 laws in 6 jurisdictionsPR.AT-02: 29 laws in 25 jurisdictionsPR.DS-01: 116 laws in 98 jurisdictionsPR.DS-01 116PR.DS-02: 9 laws in 8 jurisdictionsPR.DS-10: no law we trackPR.DS-11: 7 laws in 4 jurisdictionsPR.PS-01: 6 laws in 5 jurisdictionsPR.PS-02: 17 laws in 11 jurisdictionsPR.PS-03: 1 law in 1 jurisdictionPR.PS-04: 22 laws in 11 jurisdictionsPR.PS-05: 3 laws in 2 jurisdictionsPR.PS-06: 31 laws in 17 jurisdictionsPR.IR-01: 12 laws in 12 jurisdictionsPR.IR-02: no law we trackPR.IR-03: 15 laws in 11 jurisdictionsPR.IR-04: 2 laws in 1 jurisdictionDE.AE-02: 1 law in 1 jurisdictionDE.AE-03: no law we trackDE.AE-04: no law we trackDE.AE-06: no law we trackDE.AE-07: 1 law in 1 jurisdictionDE.AE-08: 1 law in 1 jurisdictionDE.CM-01: 6 laws in 5 jurisdictionsDE.CM-02: no law we trackDE.CM-03: 4 laws in 2 jurisdictionsDE.CM-06: 2 laws in 2 jurisdictionsDE.CM-09: 14 laws in 11 jurisdictionsRS.MA-01: 2 laws in 2 jurisdictionsRS.MA-02: 2 laws in 1 jurisdictionRS.MA-03: 9 laws in 5 jurisdictionsRS.MA-04: 1 law in 1 jurisdictionRS.MA-05: no law we trackRS.AN-03: 2 laws in 2 jurisdictionsRS.AN-06: 31 laws in 28 jurisdictionsRS.AN-07: 5 laws in 4 jurisdictionsRS.AN-08: 3 laws in 2 jurisdictionsRS.CO-02: 191 laws in 115 jurisdictionsRS.CO-02 191RS.CO-03: 55 laws in 40 jurisdictionsRS.MI-01: 7 laws in 7 jurisdictionsRS.MI-02: no law we trackRC.RP-01: no law we trackRC.RP-02: 2 laws in 2 jurisdictionsRC.RP-03: no law we trackRC.RP-04: no law we trackRC.RP-05: no law we trackRC.RP-06: 3 laws in 3 jurisdictionsRC.CO-03: 2 laws in 2 jurisdictionsRC.CO-04: 4 laws in 4 jurisdictionsOCRMRRPOOVSCAMRAIMAAATDSPSIRAECMMAANCOMIRPCOGVIDPRDERSRC

Of these laws, 475 are in force, 30 not yet in force, and 21 proposed and not law.

11 of the 31 controls under Govern have no law we track under them.

  • in force
  • not yet in force
  • blocked by a court
  • proposed
  • no law we track
A bar's height is its number of laws. Select one to open the control.

Each requirement line of the cybersecurity laws we track was read on its own and mapped to the control it bears on most closely, and to a second or third only where the line has more than one limb. Lines of the AI, privacy and age assurance laws that reach a control in the NIST framework for their own subject were read against it as well, where their subject reaches into it, and count here wherever they land on a control.

Govern

20 of 31 controls with law

The organization's cybersecurity risk management strategy, expectations, and policy are established, communicated, and monitored

ControlWhat it saysLaws, by stateLawsJurisdictionsNot yet in forceProposed
GV.OCOrganizational Context: The circumstances - mission, stakeholder expectations, dependencies, and legal, regulatory, and contractual requirements - surrounding the organization's cybersecurity risk management decisions are understood
GV.OC-01 The organizational mission is understood and informs cybersecurity risk management no law we track no law we track
GV.OC-02 Internal and external stakeholders are understood, and their needs and expectations regarding cybersecurity risk management are understood and considered no law we track no law we track
GV.OC-03 Legal, regulatory, and contractual requirements regarding cybersecurity - including privacy and civil liberties obligations - are understood and managed 102 laws, 5 not yet in force, 5 proposed 102 66 5 5
GV.OC-04 Critical objectives, capabilities, and services that external stakeholders depend on or expect from the organization are understood and communicated no law we track no law we track
GV.OC-05 Outcomes, capabilities, and services that the organization depends on are understood and communicated no law we track no law we track
GV.RMRisk Management Strategy: The organization's priorities, constraints, risk tolerance and appetite statements, and assumptions are established, communicated, and used to support operational risk decisions
GV.RM-01 Risk management objectives are established and agreed to by organizational stakeholders 1 law 1 1 0 0
GV.RM-02 Risk appetite and risk tolerance statements are established, communicated, and maintained 3 laws 3 3 0 0
GV.RM-03 Cybersecurity risk management activities and outcomes are included in enterprise risk management processes 1 law 1 1 0 0
GV.RM-04 Strategic direction that describes appropriate risk response options is established and communicated no law we track no law we track
GV.RM-05 Lines of communication across the organization are established for cybersecurity risks, including risks from suppliers and other third parties 1 law 1 1 0 0
GV.RM-06 A standardized method for calculating, documenting, categorizing, and prioritizing cybersecurity risks is established and communicated 7 laws, 1 not yet in force 7 7 1 0
GV.RM-07 Strategic opportunities (i.e., positive risks) are characterized and are included in organizational cybersecurity risk discussions no law we track no law we track
GV.RRRoles, Responsibilities, and Authorities: Cybersecurity roles, responsibilities, and authorities to foster accountability, performance assessment, and continuous improvement are established and communicated
GV.RR-01 Organizational leadership is responsible and accountable for cybersecurity risk and fosters a culture that is risk-aware, ethical, and continually improving 34 laws, 1 not yet in force, 2 proposed 34 28 1 2
GV.RR-02 Roles, responsibilities, and authorities related to cybersecurity risk management are established, communicated, understood, and enforced 32 laws, 1 not yet in force, 2 proposed 32 25 1 2
GV.RR-03 Adequate resources are allocated commensurate with the cybersecurity risk strategy, roles, responsibilities, and policies 2 laws 2 2 0 0
GV.RR-04 Cybersecurity is included in human resources practices 7 laws, 1 not yet in force, 1 proposed 7 7 1 1
GV.POPolicy: Organizational cybersecurity policy is established, communicated, and enforced
GV.PO-01 Policy for managing cybersecurity risks is established based on organizational context, cybersecurity strategy, and priorities and is communicated and enforced 73 laws, 5 not yet in force, 1 proposed 73 55 5 1
GV.PO-02 Policy for managing cybersecurity risks is reviewed, updated, communicated, and enforced to reflect changes in requirements, threats, technology, and organizational mission 4 laws 4 4 0 0
GV.OVOversight: Results of organization-wide cybersecurity risk management activities and performance are used to inform, improve, and adjust the risk management strategy
GV.OV-01 Cybersecurity risk management strategy outcomes are reviewed to inform and adjust strategy and direction no law we track no law we track
GV.OV-02 The cybersecurity risk management strategy is reviewed and adjusted to ensure coverage of organizational requirements and risks 1 law 1 1 0 0
GV.OV-03 Organizational cybersecurity risk management performance is evaluated and reviewed for adjustments needed 4 laws, 1 not yet in force 4 2 1 0
GV.SCCybersecurity Supply Chain Risk Management: Cyber supply chain risk management processes are identified, established, managed, monitored, and improved by organizational stakeholders
GV.SC-01 A cybersecurity supply chain risk management program, strategy, objectives, policies, and processes are established and agreed to by organizational stakeholders 7 laws, 1 not yet in force 7 6 1 0
GV.SC-02 Cybersecurity roles and responsibilities for suppliers, customers, and partners are established, communicated, and coordinated internally and externally no law we track no law we track
GV.SC-03 Cybersecurity supply chain risk management is integrated into cybersecurity and enterprise risk management, risk assessment, and improvement processes no law we track no law we track
GV.SC-04 Suppliers are known and prioritized by criticality no law we track no law we track
GV.SC-05 Requirements to address cybersecurity risks in supply chains are established, prioritized, and integrated into contracts and other types of agreements with suppliers and other relevant third parties 55 laws, 4 not yet in force, 1 proposed 55 50 4 1
GV.SC-06 Planning and due diligence are performed to reduce risks before entering into formal supplier or other third-party relationships 15 laws, 1 proposed 15 13 0 1
GV.SC-07 The risks posed by a supplier, their products and services, and other third parties are understood, recorded, prioritized, assessed, responded to, and monitored over the course of the relationship 16 laws, 1 not yet in force 16 11 1 0
GV.SC-08 Relevant suppliers and other third parties are included in incident planning, response, and recovery activities 1 law 1 1 0 0
GV.SC-09 Supply chain security practices are integrated into cybersecurity and enterprise risk management programs, and their performance is monitored throughout the technology product and service life cycle no law we track no law we track
GV.SC-10 Cybersecurity supply chain risk management plans include provisions for activities that occur after the conclusion of a partnership or service agreement 1 law 1 1 0 0

Identify

18 of 21 controls with law

The organization's current cybersecurity risks are understood

ControlWhat it saysLaws, by stateLawsJurisdictionsNot yet in forceProposed
ID.AMAsset Management: Assets (e.g., data, hardware, software, systems, facilities, services, people) that enable the organization to achieve business purposes are identified and managed consistent with their relative importance to organizational objectives and the organization's risk strategy
ID.AM-01 Inventories of hardware managed by the organization are maintained 1 law 1 1 0 0
ID.AM-02 Inventories of software, services, and systems managed by the organization are maintained 10 laws, 1 not yet in force 10 7 1 0
ID.AM-03 Representations of the organization's authorized network communication and internal and external network data flows are maintained no law we track no law we track
ID.AM-04 Inventories of services provided by suppliers are maintained 2 laws 2 2 0 0
ID.AM-05 Assets are prioritized based on classification, criticality, resources, and impact on the mission 7 laws, 1 not yet in force 7 6 1 0
ID.AM-07 Inventories of data and corresponding metadata for designated data types are maintained 6 laws, 1 proposed 6 6 0 1
ID.AM-08 Systems, hardware, software, services, and data are managed throughout their life cycles 54 laws, 2 not yet in force 54 45 2 0
ID.RARisk Assessment: The cybersecurity risk to the organization, assets, and individuals is understood by the organization
ID.RA-01 Vulnerabilities in assets are identified, validated, and recorded 7 laws 7 4 0 0
ID.RA-02 Cyber threat intelligence is received from information sharing forums and sources no law we track no law we track
ID.RA-03 Internal and external threats to the organization are identified and recorded 4 laws 4 3 0 0
ID.RA-04 Potential impacts and likelihoods of threats exploiting vulnerabilities are identified and recorded 4 laws 4 3 0 0
ID.RA-05 Threats, vulnerabilities, likelihoods, and impacts are used to understand inherent risk and inform risk response prioritization 30 laws, 3 not yet in force, 3 proposed 30 23 3 3
ID.RA-06 Risk responses are chosen, prioritized, planned, tracked, and communicated 44 laws, 5 proposed 44 36 0 5
ID.RA-07 Changes and exceptions are managed, assessed for risk impact, recorded, and tracked 5 laws, 1 not yet in force 5 4 1 0
ID.RA-08 Processes for receiving, analyzing, and responding to vulnerability disclosures are established 9 laws, 1 not yet in force 9 7 1 0
ID.RA-09 The authenticity and integrity of hardware and software are assessed prior to acquisition and use 4 laws, 1 not yet in force 4 4 1 0
ID.RA-10 Critical suppliers are assessed prior to acquisition no law we track no law we track
ID.IMImprovement: Improvements to organizational cybersecurity risk management processes, procedures and activities are identified across all CSF Functions
ID.IM-01 Improvements are identified from evaluations 26 laws, 2 not yet in force 26 18 2 0
ID.IM-02 Improvements are identified from security tests and exercises, including those done in coordination with suppliers and relevant third parties 10 laws 10 6 0 0
ID.IM-03 Improvements are identified from execution of operational processes, procedures, and activities 3 laws 3 1 0 0
ID.IM-04 Incident response plans and other cybersecurity plans that affect operations are established, communicated, maintained, and improved 25 laws, 1 not yet in force 25 19 1 0

Protect

19 of 22 controls with law

Safeguards to manage the organization's cybersecurity risks are used

ControlWhat it saysLaws, by stateLawsJurisdictionsNot yet in forceProposed
PR.AAIdentity Management, Authentication, and Access Control: Access to physical and logical assets is limited to authorized users, services, and hardware and managed commensurate with the assessed risk of unauthorized access
PR.AA-01 Identities and credentials for authorized users, services, and hardware are managed by the organization 2 laws 2 2 0 0
PR.AA-02 Identities are proofed and bound to credentials based on the context of interactions 1 law 1 1 0 0
PR.AA-03 Users, services, and hardware are authenticated 10 laws, 1 not yet in force 10 6 1 0
PR.AA-04 Identity assertions are protected, conveyed, and verified no law we track no law we track
PR.AA-05 Access permissions, entitlements, and authorizations are defined in a policy, managed, enforced, and reviewed, and incorporate the principles of least privilege and separation of duties 15 laws 15 11 0 0
PR.AA-06 Physical access to assets is managed, monitored, and enforced commensurate with risk 1 law 1 1 0 0
PR.ATAwareness and Training: The organization's personnel are provided with cybersecurity awareness and training so that they can perform their cybersecurity-related tasks
PR.AT-01 Personnel are provided with awareness and training so that they possess the knowledge and skills to perform general tasks with cybersecurity risks in mind 9 laws 9 6 0 0
PR.AT-02 Individuals in specialized roles are provided with awareness and training so that they possess the knowledge and skills to perform relevant tasks with cybersecurity risks in mind 29 laws, 1 proposed 29 25 0 1
PR.DSData Security: Data are managed consistent with the organization's risk strategy to protect the confidentiality, integrity, and availability of information
PR.DS-01 The confidentiality, integrity, and availability of data-at-rest are protected 116 laws, 5 not yet in force, 4 proposed 116 98 5 4
PR.DS-02 The confidentiality, integrity, and availability of data-in-transit are protected 9 laws 9 8 0 0
PR.DS-10 The confidentiality, integrity, and availability of data-in-use are protected no law we track no law we track
PR.DS-11 Backups of data are created, protected, maintained, and tested 7 laws 7 4 0 0
PR.PSPlatform Security: The hardware, software (e.g., firmware, operating systems, applications), and services of physical and virtual platforms are managed consistent with the organization's risk strategy to protect their confidentiality, integrity, and availability
PR.PS-01 Configuration management practices are established and applied 6 laws 6 5 0 0
PR.PS-02 Software is maintained, replaced, and removed commensurate with risk 17 laws, 1 not yet in force 17 11 1 0
PR.PS-03 Hardware is maintained, replaced, and removed commensurate with risk 1 law 1 1 0 0
PR.PS-04 Log records are generated and made available for continuous monitoring 22 laws, 6 not yet in force 22 11 6 0
PR.PS-05 Installation and execution of unauthorized software are prevented 3 laws 3 2 0 0
PR.PS-06 Secure software development practices are integrated, and their performance is monitored throughout the software development life cycle 31 laws, 5 not yet in force 31 17 5 0
PR.IRTechnology Infrastructure Resilience: Security architectures are managed with the organization's risk strategy to protect asset confidentiality, integrity, and availability, and organizational resilience
PR.IR-01 Networks and environments are protected from unauthorized logical access and usage 12 laws 12 12 0 0
PR.IR-02 The organization's technology assets are protected from environmental threats no law we track no law we track
PR.IR-03 Mechanisms are implemented to achieve resilience requirements in normal and adverse situations 15 laws, 1 not yet in force 15 11 1 0
PR.IR-04 Adequate resource capacity to ensure availability is maintained 2 laws 2 1 0 0

Detect

7 of 11 controls with law

Possible cybersecurity attacks and compromises are found and analyzed

ControlWhat it saysLaws, by stateLawsJurisdictionsNot yet in forceProposed
DE.AEAdverse Event Analysis: Anomalies, indicators of compromise, and other potentially adverse events are analyzed to characterize the events and detect cybersecurity incidents
DE.AE-02 Potentially adverse events are analyzed to better understand associated activities 1 law 1 1 0 0
DE.AE-03 Information is correlated from multiple sources no law we track no law we track
DE.AE-04 The estimated impact and scope of adverse events are understood no law we track no law we track
DE.AE-06 Information on adverse events is provided to authorized staff and tools no law we track no law we track
DE.AE-07 Cyber threat intelligence and other contextual information are integrated into the analysis 1 law 1 1 0 0
DE.AE-08 Incidents are declared when adverse events meet the defined incident criteria 1 law 1 1 0 0
DE.CMContinuous Monitoring: Assets are monitored to find anomalies, indicators of compromise, and other potentially adverse events
DE.CM-01 Networks and network services are monitored to find potentially adverse events 6 laws 6 5 0 0
DE.CM-02 The physical environment is monitored to find potentially adverse events no law we track no law we track
DE.CM-03 Personnel activity and technology usage are monitored to find potentially adverse events 4 laws 4 2 0 0
DE.CM-06 External service provider activities and services are monitored to find potentially adverse events 2 laws 2 2 0 0
DE.CM-09 Computing hardware and software, runtime environments, and their data are monitored to find potentially adverse events 14 laws, 3 not yet in force, 1 proposed 14 11 3 1

Respond

11 of 13 controls with law

Actions regarding a detected cybersecurity incident are taken

ControlWhat it saysLaws, by stateLawsJurisdictionsNot yet in forceProposed
RS.MAIncident Management: Responses to detected cybersecurity incidents are managed
RS.MA-01 The incident response plan is executed in coordination with relevant third parties once an incident is declared 2 laws 2 2 0 0
RS.MA-02 Incident reports are triaged and validated 2 laws 2 1 0 0
RS.MA-03 Incidents are categorized and prioritized 9 laws 9 5 0 0
RS.MA-04 Incidents are escalated or elevated as needed 1 law 1 1 0 0
RS.MA-05 The criteria for initiating incident recovery are applied no law we track no law we track
RS.ANIncident Analysis: Investigations are conducted to ensure effective response and support forensics and recovery activities
RS.AN-03 Analysis is performed to establish what has taken place during an incident and the root cause of the incident 2 laws 2 2 0 0
RS.AN-06 Actions performed during an investigation are recorded, and the records' integrity and provenance are preserved 31 laws, 1 proposed 31 28 0 1
RS.AN-07 Incident data and metadata are collected, and their integrity and provenance are preserved 5 laws, 1 not yet in force 5 4 1 0
RS.AN-08 An incident's magnitude is estimated and validated 3 laws 3 2 0 0
RS.COIncident Response Reporting and Communication: Response activities are coordinated with internal and external stakeholders as required by laws, regulations, or policies
RS.CO-02 Internal and external stakeholders are notified of incidents 191 laws, 11 not yet in force, 10 proposed 191 115 11 10
RS.CO-03 Information is shared with designated internal and external stakeholders 55 laws, 3 not yet in force, 3 proposed 55 40 3 3
RS.MIIncident Mitigation: Activities are performed to prevent expansion of an event and mitigate its effects
RS.MI-01 Incidents are contained 7 laws, 2 not yet in force 7 7 2 0
RS.MI-02 Incidents are eradicated no law we track no law we track

Recover

4 of 8 controls with law

Assets and operations affected by a cybersecurity incident are restored

ControlWhat it saysLaws, by stateLawsJurisdictionsNot yet in forceProposed
RC.RPIncident Recovery Plan Execution: Restoration activities are performed to ensure operational availability of systems and services affected by cybersecurity incidents
RC.RP-01 The recovery portion of the incident response plan is executed once initiated from the incident response process no law we track no law we track
RC.RP-02 Recovery actions are selected, scoped, prioritized, and performed 2 laws 2 2 0 0
RC.RP-03 The integrity of backups and other restoration assets is verified before using them for restoration no law we track no law we track
RC.RP-04 Critical mission functions and cybersecurity risk management are considered to establish post-incident operational norms no law we track no law we track
RC.RP-05 The integrity of restored assets is verified, systems and services are restored, and normal operating status is confirmed no law we track no law we track
RC.RP-06 The end of incident recovery is declared based on criteria, and incident-related documentation is completed 3 laws 3 3 0 0
RC.COIncident Recovery Communication: Restoration activities are coordinated with internal and external parties
RC.CO-03 Recovery activities and progress in restoring operational capabilities are communicated to designated internal and external stakeholders 2 laws 2 2 0 0
RC.CO-04 Public updates on incident recovery are shared using approved methods and messaging 4 laws 4 4 0 0

Cybersecurity duties with no home in NIST CSF 2.0

36 lines in 18 laws

Each line below was read against CSF 2.0 and recorded as having no control to sit under.

Product security requirements 8

JurisdictionLawThe duty, as read
China Cybersecurity Law, Network Product and Service Security Duties

Where your product or service collects user information, disclose that collection and obtain consent, and where personal information is involved, also follow this Law's and the Personal Information Protection Law's personal-information rules, already this jurisdiction's privacy row.

Czech Republic Cybersecurity Act (Zákon o kybernetické bezpečnosti), Cybersecurity Certification: Authorisation, Suspension and Offences

Do not misuse the mark or label of a European cybersecurity certification scheme, a European cybersecurity certificate or an EU declaration of conformity, and do not forge or alter any of them (Section 61(1)(a) and (b)).

European Union Ecodesign Regulation for Smartphones and Tablets, Operating System Updates

Make functionality updates available to the user at the latest 6 months after the corresponding release (Annex II, point (6)(d) or (5)(d)).

For a smartphone or a slate tablet, where a functionality update you provide shows a negative impact on device performance, modify the released operating system to ensure at least the same performance as before the update, within a reasonable period of time, free of charge and without causing significant inconvenience to the end-user, unless the end-user gave explicit consent to the negative impact before the update (Annex II, Part B point (6)(f), Part D point (5)(f)).

European Union European Health Data Space Regulation, Essential Requirements for the Harmonised Software Components of EHR Systems from , in 2.4 years

Provide, where the EHR system is designed to store or intermediate personal electronic health data, an interface enabling access to that data in the European electronic health record exchange format and the ability to receive it in that format; where it is designed to provide access to such data, be able to receive it in that format; and where it includes a functionality for entering structured data, enable entry with sufficient granularity to provide the entered data in that format (Annex II, points 2.1 to 2.4).

Do not include in the harmonised software components features that prohibit, restrict or place an undue burden on authorized access, sharing or use of personal electronic health data for permitted purposes, or on authorized export of that data for the purpose of replacing the EHR system by another product (Annex II, points 2.5 and 2.6).

European Union General Product Safety Regulation, Cybersecurity Features and Software Changes in Assessing a Consumer Product's Safety

It reaches you if you are a manufacturer that places on the EU market a product intended for consumers, or likely to be used by them, including a product interconnected to other items: ensure it is a safe product, designed and manufactured in accordance with the general safety requirement (Articles 3, point (1), 5 and 9(1)).

Take into account, where required by the nature of the product, its evolving, learning and predictive functionalities (point (h)) and the effect of non-embedded items that are meant to determine, change or complete the way the product works (point (c)).

European Union In Vitro Diagnostic Medical Devices Regulation, Software Development, Information Security and IT Security Information Requirements

Where the software is intended to be used in combination with mobile computing platforms, design and manufacture it taking into account the specific features of the mobile platform and the external factors related to their use (section 16.3).

Include those minimum requirements in the instructions for use of a device that incorporates electronic programmable systems, including software, or of software that is a device in itself (section 20.4.1, point (ah)).

European Union Medical Devices Regulation, Software Development, Information Security and IT Security Information Requirements

Where the software is intended to be used in combination with mobile computing platforms, design and manufacture it taking into account the specific features of the mobile platform and the external factors related to their use (section 17.3).

Include those minimum requirements in the instructions for use of a device that incorporates electronic programmable systems, including software, or of software that is a device in itself (section 23.4, point (ab)).

Hungary 2024. évi LXIX. törvény, National Cybersecurity Certification Schemes

If you design or run a national cybersecurity certification scheme for ICT products, services or processes in Hungary, make the scheme meet the Section 38 security objectives, including protection of data across the life cycle, identification and documentation of known dependencies and vulnerabilities, security by default and by design, up-to-date software and hardware, and mechanisms for secure updating (Section 38).

Sector security regimes 8

JurisdictionLawThe duty, as read
Burundi Loi n° 1/10, Articles 3, 4(3) and 14: security-of-service duty and diligence penalty for network operators and service providers

Maintain an operational management center for your critical infrastructure on Burundian national territory.

European Union Payment Services Technical Standards on Strong Customer Authentication, Personalized Security Credentials and Common and Secure Open Standards of Communication

If you are an account servicing payment service provider, give account information service providers the same information from designated payment accounts and associated payment transactions that you make available to the user when the user requests it directly, excluding sensitive payment data, give payment initiation service providers immediately after receipt of the payment order the same information on the initiation and execution of the transaction, confirm immediately upon request in a simple yes or no format whether the amount necessary for a payment transaction is available, and notify the other provider of the reason for an unexpected event or error (Article 36(1) and (2)). If you are an account information service provider, prevent access to information other than from designated payment accounts and associated payment transactions in accordance with the user's explicit consent, and access the information only when the user is actively requesting it or otherwise no more than four times in a 24-hour period unless the account servicing payment service provider agrees a higher frequency with you, with the user's consent (Article 36(3) and (5)). If you are a payment initiation service provider, give the account servicing payment service provider the same information as requested from the user when initiating the payment transaction directly (Article 36(4)).

Finland Laki sähköisen viestinnän palveluista, Domain Name Registration Data of Registries and Registrars

Collect and maintain domain registration data that includes the data NIS 2 Directive Article 28(2) lists, and keep and publish policies and procedures that ensure the database is accurate and correct (section 172 c).

Publish the registration data that is not personal data without undue delay after a domain is registered, and answer a lawful and duly reasoned request for access to the other registration data without undue delay and within 72 hours of receiving it (section 172 d).

+1 more
France Loi n° 2022-309 du 3 mars 2022 (loi Cyberscore), Cybersecurity Audit and Disclosure Duty

Present the audit result to the consumer in a legible, clear and comprehensible form, with a colour-coded presentation, in the conditions a joint ministerial order fixes.

Latvia Financial Market Digital Operational Resilience Law, DORA Provisions

Inform Latvijas Banka of all material changes, including any circumstance that may adversely affect your further operation, and of changes in the information you gave it (Article 9).

Sweden Lag (2024:1278), DORA Supplementary Provisions

Pay the annual fee that funds the Finansinspektionen's work under DORA and the Act (chapter 1, section 3).

United States Sarbanes-Oxley Act section 302: certification of periodic reports by the principal executive and principal financial officers

Include the certifications as an exhibit to each annual and quarterly report, in the form the report's exhibit requirements specify, with each certifying officer signing personally: a certification may not be signed on an officer's behalf under a power of attorney or other form of confirming authority.

Have each signing officer certify that he or she has reviewed the report; that, based on his or her knowledge, the report contains no untrue statement of a material fact and omits no material fact necessary to make the statements, in light of the circumstances under which they were made, not misleading; and that the financial statements and other financial information in the report fairly present in all material respects the financial condition and results of operations of the issuer.

+3 more
United States Sarbanes-Oxley Act title IV: management's report on internal control over financial reporting and the auditor's attestation

Maintain internal control over financial reporting: a process designed by or under the supervision of your principal executive and principal financial officers, and effected by your board of directors, management and other personnel, to provide reasonable assurance regarding the reliability of financial reporting and the preparation of financial statements for external purposes in accordance with generally accepted accounting principles, including policies and procedures that pertain to the maintenance of records that in reasonable detail accurately and fairly reflect your transactions and dispositions of assets.

Maintain disclosure controls and procedures, and have management evaluate their effectiveness, with the participation of your principal executive and principal financial officers, as of the end of each fiscal quarter (each fiscal year for a foreign private issuer; for a registered investment company, within the 90-day period before the filing date of each report requiring certification under Rule 30a-2).

+6 more

Security baseline statutes 1

JurisdictionLawThe duty, as read
India Information Technology Act, Compensation for Failure to Protect Data, and Sensitive Personal Data or Information Rules, Reasonable Security Practices

Obtain the data provider's written consent, by letter, fax, or email, before collecting their sensitive personal data or information, let them decline or withdraw that consent, publish a privacy policy on your website, and designate a Grievance Officer who must resolve a complaint within one month.

Vulnerability and incident reporting 1

JurisdictionLawThe duty, as read
India CERT-In Cyber Security Directions, Incident Reporting, Logging and Time Synchronisation

If your own service is itself a data centre, a virtual private server provider, a cloud service provider, a virtual private network service, or a virtual asset (crypto) service provider, a narrower and heavier duty also applies: register and retain specified customer KYC information and financial-transaction records for five years. That narrower bound-party class is not one this profile's declared activities can identify on their own, so confirm applicability directly against the text if this describes your service.

Where the law and the framework part

27 of the 106 controls have no law we track under them.

36 requirement lines were read as having no control in this framework to sit under; they are listed above.

The framework's text

Full text of the NIST Cybersecurity Framework, public domain (a US government work).

Read it from the publisher: nvlpubs.nist.gov