Law / Frameworks / NIST CSF 2.0 / Detect
NIST CSF 2.0, DetectDE.CM-09
Computing hardware and software, runtime environments, and their data are monitored to find potentially adverse eventsNIST Cybersecurity Framework, version 2.0, February 2024 (NIST CSWP 29), DE.CM-09
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 .
- 14
- laws
- 11
- jurisdictions
- 0
- with court rulings behind them
- 3
- not yet in force
- 1
- proposed, not law
Related controls in other frameworks the same duties, in at least two laws we track, reach both
- NIST Privacy FrameworkPR.PO-P7 Response plans (Incident Response and Business Continuity) and recovery..., 3 laws
- NIST Privacy FrameworkPR.PO-P10 A vulnerability management plan is developed and implemented., 3 laws
- FINOS AIGFAIR-PREV-007 Legal and Contractual Frameworks for AI Systems, 14 laws
- FINOS AIGFAIR-PREV-008 Quality of Service (QoS) and DDoS Prevention for AI Systems, 14 laws
- FINOS AIGFAIR-PREV-012 Role-Based Access Control for AI Data, 14 laws
- 10 more in the FINOS AIGF
- ENISA NIS2 guidance2.1 Risk management framework, 12 laws
- ENISA NIS2 guidance3.1 Incident handling policy, 12 laws
- ENISA NIS2 guidance4.1 Business continuity and disaster recovery plan, 12 laws
- 10 more in the ENISA NIS2 guidance
A law in force is unmarked; the rest wear their state: not yet in force proposed
Sector security regimes
5 laws, 5 jurisdictions| Jurisdiction | Law | What it asks, as read here |
|---|---|---|
| OSFI Guideline B-13, Technology and Cyber Risk Management |
Maintain practices, capabilities, processes and tools to identify and assess cyber security weaknesses that external and insider threat actors could exploit, and design, implement and maintain multi-layer preventive controls and continuous security detection capabilities. |
|
| Digital Code, Book VI: Critical Installation Protection and Operator Security Controls |
Implement a qualified system for detecting events capable of affecting your information systems' security, if you operate a public electronic communications network or provide a public electronic communications service in Djibouti. The detection system, and any service provider you use to run it, must be qualified by the national cybersecurity authority. |
|
| Critical Infrastructure Cybersecurity Proclamation, Critical Infrastructure Owner Obligations from , in 8 months |
Formulate and implement your own cybersecurity program and cybersecurity framework consistent with the mandatory national cybersecurity frameworks the Administration issues, classify and protect your critical assets to the Administration's standard, create the cybersecurity organizational structure the national framework calls for, and establish and manage a center responsible for monitoring, reporting, and responding to cyberattacks. |
|
| Commission Implementing Regulation (EU) 2024/2690, Technical and Methodological Requirements for NIS2 Risk-Management Measures |
Establish and implement an incident handling policy, monitor and log activity on your network and information systems to detect events that could be incidents, assess suspicious events to determine whether they are incidents, and assess the existence of recurring incidents under Article 4 on a quarterly basis (points 3.1.1, 3.2.1, 3.4.1 and 3.4.2(b)). |
|
| New York Department of Financial Services Cybersecurity Regulation, Malicious Code Protection and Class A Company Monitoring Solutions |
If you are a Class A company as 23 NYCRR 500.1(d) defines it, implement an endpoint detection and response solution to monitor anomalous activity, including lateral movement, and a solution that centralizes logging and security event alerting, unless your Chief Information Security Officer has approved in writing the use of reasonably equivalent or more secure compensating controls. |
Vulnerability and incident reporting
4 laws, 4 jurisdictions| Jurisdiction | Law | What it asks, as read here |
|---|---|---|
| Data Security Law, Risk Monitoring and Incident Reporting Duty |
Strengthen risk monitoring of your data-processing activity, and on discovering a data-security defect, vulnerability, or other risk, immediately take remedial measures. |
|
| Cybersecurity Act 2025, Cybersecurity Incident Reporting Obligations |
Establish mechanisms and processes to promptly detect a cybersecurity threat, vulnerability, or incident affecting your critical information infrastructure. |
|
| FSM Cybersecurity Act 2025 (Bill), Critical Information Infrastructure Incident Reporting Clock proposed |
Establish mechanisms and processes to promptly detect a cybersecurity threat or incident affecting your critical information infrastructure. |
|
| 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. |
Security baseline statutes
3 laws, 3 jurisdictions| Jurisdiction | Law | What it asks, as read here |
|---|---|---|
| Digital Code, Livre IV: Digital Services Provider Security Obligations |
Implement systems qualified to detect events likely to affect the security of your own information systems; the qualification of the detection systems and of the service providers operating them is delivered by the Ministry responsible for digital affairs, the Agence Nationale de Cybersécurité having been consulted. |
|
| Law on Information and Its Protection, information-security duty |
Where the duty is triggered, maintain administrative, technical and organizational measures that: prevent unauthorized access to information and its transfer to a person without a right of access; detect an unauthorized access event in a timely manner; prevent adverse consequences from a breach of the access procedure; prevent disruption of the technical means used to process the information; permit immediate restoration of information altered or destroyed by unauthorized access; and continuously monitor the level of the information's protection. |
|
| Cybersecurity Law, Information System Classification and Protection Measures |
At level 3 or level 4, and not on the Prime Minister's list of information systems critical to national security, perform every Article 10(1) task and, without discretion, promulgate cybersecurity design-and-operation rules, apply management measures meeting national cybersecurity standards, back up and store data protecting the system's components, inspect and supervise compliance, monitor the system, and respond to and remedy incidents; file a dossier proposing your system's level and put it into operation only once that level is approved. |
AI risk obligations
1 law, 1 jurisdiction| Jurisdiction | Law | What it asks, as read here |
|---|---|---|
| AI Act, Article 15 (accuracy, robustness and cybersecurity) from , in 13 months |
Where appropriate to the risk, include measures to prevent, detect, respond to, resolve and control for data poisoning, model poisoning, adversarial examples or model evasion, confidentiality attacks and other model flaws. |
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 13 months |
Implement measures to detect and prevent cyber-attacks against vehicles of the type, support your monitoring of threats, vulnerabilities and cyber-attacks, and provide data forensic capability; mitigate threats and vulnerabilities that require a response within a reasonable timeframe, and monitor continually, including vehicles after first registration (paragraphs 7.3.7, 7.2.2.3 and 7.2.2.4). |
Full text of the NIST Cybersecurity Framework, public domain (a US government work). Every control of the framework.