Law / Frameworks / NIST AI RMF / Measure
NIST AI RMF, MeasureMEASURE 2.4
The functionality and behavior of the AI system and its components – as identified in the MAP function – are monitored when in production.NIST AI Risk Management Framework, version 1.0, January 2023 (NIST AI 100-1), MEASURE 2.4
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 .
- 27
- laws
- 16
- jurisdictions
- 0
- with court rulings behind them
- 10
- 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 AI 600-1GAI-RISK-07 Human-AI Configuration, 22 laws
- NIST AI 200-22.3 Apply & Measure, 22 laws
- NIST AI 200-24.3 Composing a TEVV Toolbox, 22 laws
- OWASP LLM Top 10LLM03:2026 Excessive Agency, 22 laws
- OWASP Agentic Top 10ASI09 Human-Agent Trust Exploitation, 22 laws
- MIT mitigations1.1 Board Structure & Oversight, 22 laws
- MIT mitigations1.2 Risk Management, 22 laws
- MIT mitigations3.5 Post-deployment Monitoring, 22 laws
- 2 more in the MIT mitigations
- NIST Privacy FrameworkCT.DM-P8 Audit/log records are determined, documented, implemented, and reviewed in..., 2 laws
- NIST CSF 2.0PR.PS-04 Log records are generated and made available for continuous monitoring, 8 laws
- FINOS AIGFAIR-PREV-005 System Acceptance Testing, 23 laws
- FINOS AIGFAIR-PREV-006 Data Quality & Classification/Sensitivity, 23 laws
- FINOS AIGFAIR-PREV-024 Human-in-the-Loop Action Approval Gate, 23 laws
- 3 more in the FINOS AIGF
- ETSI EN 304 2235.1.4-1 Capability for human oversight designed in and maintained., 22 laws
- ETSI EN 304 2235.2.1-1 Full inventory of assets, including their dependencies and connections., 22 laws
- ETSI EN 304 2235.2.4-1 Developers keep an audit trail of system design and post-deployment..., 22 laws
- 1 more in the ETSI EN 304 223
A law in force is unmarked; the rest wear their state: not yet in force proposed
AI sector rules
11 laws, 8 jurisdictions| Jurisdiction | Law | What it asks, as read here |
|---|---|---|
| OSFI Guideline E-23, Model Risk Management (2027) from , in 6 months |
You should have defined standards for model monitoring that cover frequency, scope and evaluation criteria by risk rating and model type, thresholds for breaches, contingency plans for model unavailability, deterioration or failure, and processes for AI/ML challenges such as autonomous decision making, autonomous re-parametrization and model drift. |
|
| Väärtpaberituru seadus Sections 82^15 and 82^16, Algorithmic Trading and Direct Electronic Access Controls |
Keep records of your algorithmic trading and, if you use high-frequency algorithmic trading technique, record precise, chronological data on every order submitted, cancelled and executed and every quotation made on a trading venue (section 82^15(11)). |
|
| EBA Guidelines on loan origination and monitoring (EBA/GL/2020/06), automated models and model governance |
Institutions should ensure that the performance of the model, including the validity and quality of its outputs, is continuously monitored and that appropriate remediation measures are taken in a timely manner in the case of detected issues (paragraph 53(f)). |
|
| MiFID II Algorithmic Trading Controls: Resilient Systems, Testing, Kill Functionality, Records and Notification (Article 17 and RTS 6) |
Monitor all trading activity that takes place through your trading systems, including your clients' trading, for signs of potential market manipulation with an automated surveillance system that generates alerts and reports, covers the full range of your trading activities and all orders you submit, is reviewed at least once a year, and can generate operable alerts at the beginning of the following trading day or, where manual processes are involved, at the end of the following trading day (Article 13(1) to (3), (6) and (7)). Monitor in real time, during the hours you are sending orders to trading venues, all algorithmic trading activity that takes place under your trading code, including that of your clients, for signs of disorderly trading, have the trader in charge of the algorithm and the risk management function or an independent risk control function carry out that monitoring, generate real-time alerts within five seconds after the relevant event, and take remedial action as soon as possible after an alert (Article 16(1), (2) and (5)). Continuously operate your post-trade controls, take appropriate action when one is triggered, keep complete, accurate and consistent records of trade and account information, and reconcile your own electronic trading logs with the information provided by trading venues, brokers, DEA providers, clearing members, central counterparties and data providers (Article 17(1) and (3)). +1 more |
|
| Central Bank of Jordan Artificial Intelligence Framework for the Banking Sector, Version 1.0 |
The CBJ expects you to review and validate AI data, models and decisions to detect and mitigate bias, to conduct periodic AI Impact Assessments proportional to risk, to validate and robustness-test models, and to monitor AI performance continuously at a level matched to the use case and risk (sections 2.5, 2.6, 5.2 and 5.3). The CBJ expects you to log and keep auditable all data, models, decisions, user prompts and authorized overrides, to store logs in a secure, tamper-evident manner, and to provide regulatory authorities with comprehensive audit reports on AI decision-making processes (sections 2.2 and 4.2). |
|
| Financial Services (Robotic and Artificial Intelligence Enabled Advisory Services) Rules 2021 |
Through your board, keep adequate policies, processes and controls so that your algorithms continue to perform as intended, a robust framework for designing, monitoring and testing them through periodic and random reviews, and competent officers to develop and review their methodologies even if that work is outsourced; do not outsource the key processes and management of your client-facing tools (clause 10). Keep, in addition to the records required by section 29 of the Financial Services Act, a copy of the advice given and the output of the investment, the client information relied on to generate the advice, and details of all algorithms and software you use (clause 12). |
|
| FSC Fintech Series Guidance Notes 4, responsible use of artificial intelligence in financial services |
The Commission advises you to establish procedures for monitoring AI systems and clear accountability for AI-related errors or malfunctions, and to run ongoing monitoring and evaluation of the ethical and societal impact of your AI systems. |
|
| Counter-Fraud Framework: fraud detection systems, machine learning and artificial intelligence |
Give the fraud detection systems the capability to monitor and report metrics and Management Information on data integrity, rule and scenario effectiveness such as the false positive rate, and operational performance (Section 5.2(j)). |
|
| Guidance Note on the Consumer Protection and Responsible Adoption and Use of Artificial Intelligence and Machine Learning by Licensed Financial Institutions in the U.A.E. |
Monitor AI continuously in accordance with the Model Management Standards, test automatic updates to AI tools before implementation, have mechanisms to detect, report and remediate performance issues, biases or unintended consequences before implementation and over time, and retain the clear and immediate ability, with human intervention, to cease use of an AI model, system, technology or application (Sections 6(a), 6(c), 6(d) and 6(f)). |
|
| Model Management Standards: governance, validation and monitoring of the models a bank uses to decide, including artificial intelligence models |
Monitor the performance of your models on a regular basis, present monitoring reports to the Model Oversight Committee at least every quarter, and follow a clear process in which that Committee decides whether to continue using a model with further monitoring or to suspend it and work on remediation (Sections 3.6.1, 3.6.4 and 3.6.7). |
Show the other 1 law
| Interagency Supervisory Guidance on Model Risk Management (2026 revision) |
Validate conceptual soundness, compare model outputs with real-world outcomes, and monitor model performance on an ongoing basis, considering adjustment, recalibration or redevelopment when performance deviates meaningfully from expectations. |
AI risk obligations
10 laws, 7 jurisdictions| Jurisdiction | Law | What it asks, as read here |
|---|---|---|
| Clinical Decision Support Systems Bias Mitigation Act (SB 503) from , in 7 weeks |
As a deployer, regularly monitor each such system and take reasonable and proportionate steps to mitigate the known or reasonably foreseeable risk of biased impacts |
|
| HB 26-1139 (2026), Use of Artificial Intelligence in Health Care from , in 7 weeks |
Periodically review the AI system to ensure its outcomes are accurate and reliable and that an individual's health data is not used beyond its intended or stated purpose |
|
| AI Act, Article 26(1) to (5) (deployer use, human oversight, input data and monitoring) from , in 13 months |
If you are the deployer of a high-risk AI system, monitor its operation on the basis of the provider's instructions for use, and inform the provider where relevant. |
|
| AI Act, Article 26(10) (post-remote biometric identification authorisation) from , in 13 months |
Document every use in the relevant police file, and make it available to the market surveillance authority and the national data protection authority on request, excluding sensitive operational data. |
|
| AI Act, Article 6(2) and Annex III, point 5(b) (creditworthiness and credit-scoring systems: provider duties) from , in 13 months |
Keep the logs the system automatically generates, to the extent they are under your control, as Article 19 requires. |
|
| AI Act, Article 72 (post-market monitoring by providers and post-market monitoring plan) from , in 13 months |
Have the system actively and systematically collect, document and analyze relevant data on the system's performance throughout its lifetime, whether provided by deployers or collected through other sources, so that you can evaluate its continuous compliance with the Chapter III, Section 2 requirements; where relevant, include an analysis of its interaction with other AI systems. This does not cover sensitive operational data of deployers that are law-enforcement authorities. |
|
| Decreto Legislativo 160/2026, After-the-Fact Facial Recognition Integrated in Video Surveillance (Art. 10) |
Allow access only to authorised persons, and record accesses and processing operations automatically in non-modifiable log files kept for five years (art. 10, comma 8). |
|
| Artificial Intelligence Bill, 2026, high-risk system obligations proposed |
Keep records of data inputs, training datasets, outputs and performance metrics for at least five years. |
|
| Digital Code, Chapter 23: AI system design and risk-management obligations |
An owner of such a heightened-risk system must meet the Cabinet of Ministers' risk-management, transparency, accuracy, reliability, data-quality and technical-documentation requirements, keep operating logs, and declare conformity in a signed digital document published on the owner's site before the system is deployed. |
|
| HB 820 / Ch. 747 (2025), Artificial Intelligence in Health Insurance Utilization Review |
Make the tool available for audit or compliance review by the Insurance Commissioner, and review its performance, use, and outcomes at least quarterly. |
AI governance
4 laws, 2 jurisdictions| Jurisdiction | Law | What it asks, as read here |
|---|---|---|
| Provisions on the Administration of Deep Synthesis Internet Information Services, Article 10 |
Strengthen your management of deep synthesis content: review your users' input data and synthesis output by technical or manual means, and record and retain the related network logs, if you provide a deep synthesis service. Build and maintain a feature database for identifying illegal and undesirable information, with entry standards, rules, and procedures. |
|
| AI Act, Article 12 (record-keeping) from , in 13 months |
Build automatic event logging into a high-risk AI system so it can record events over the system's lifetime, if you are its provider. Design the logging capability to support identifying an emerging risk or a substantial modification, post-market monitoring, and a deployer's monitoring of the system's operation. +1 more |
|
| AI Act, Article 19 (automatically generated logs) from , in 13 months |
Keep the logs your high-risk AI system automatically generates under Article 12, to the extent they are under your control, if you are its provider. |
|
| AI Act, Article 26(6) (deployer log-keeping) from , in 13 months |
Keep the logs your high-risk AI system automatically generates, to the extent they are under your control, if you are its deployer. |
AI prohibited practices
1 law, 1 jurisdiction| Jurisdiction | Law | What it asks, as read here |
|---|---|---|
| Decreto Legislativo 160/2026, Police Biometric AI: Dataset Labelling and Real-Time Remote Identification (Artt. 7-9, 13) |
Record each use automatically in non-modifiable log files and keep them for five years (art. 9, comma 2). |
Data subject rights
1 law, 1 jurisdiction| Jurisdiction | Law | What it asks, as read here |
|---|---|---|
| SPDP Norma General guaranteeing personal-data protection in the use of AI systems |
Maintain a record of processing activities and audit the AI system's operation in proportion to its level of risk. |
Full text of the NIST AI Risk Management Framework, public domain (a US government work). Every control of the framework.