Law / Frameworks / Crosswalk / MIT mitigations to NIST AI RMF

The MIT AI Risk Mitigation Taxonomy, mapped to the NIST AI Risk Management Framework

18 of MIT mitigations' controls connect to 28 of NIST AI RMF's through 481 laws in 171 jurisdictions. Two controls connect when the same duties, in at least 2 laws we track, reach both. The connections are our own reading of the law; no framework publisher has reviewed or endorsed them.

From
MIT AI Risk Mitigation Taxonomy, preliminary taxonomy, July 2025, MIT AI Risk Initiative
To
NIST AI Risk Management Framework, version 1.0, January 2023 (NIST AI 100-1), National Institute of Standards and Technology
See also
NIST AI RMF to MIT mitigations, the other way · every pair in the crosswalk · law library as of

Download this mapping, with every law behind each connection: nist-ai-rmf--mit-ai-risk-mitigations.csv · nist-ai-rmf--mit-ai-risk-mitigations.json

MIT mitigationsNIST AI RMFLawsJurisdictionsWhere the laws stand
1.1Board Structure & Oversight GOVERN 1.1Legal and regulatory requirements involving AI are understood, managed, and documented. 38 20 28 in force, 9 not yet in force, 1 proposed
The 38 laws behind 1.1 and GOVERN 1.1

and 28 more, every one in the free file.

MAP 3.5Processes for human oversight are defined, assessed, and documented in accordance with... 25 18 17 in force, 8 not yet in force
The 25 laws behind 1.1 and MAP 3.5

and 15 more, every one in the free file.

MEASURE 2.4The functionality and behavior of the AI system and its components – as identified in... 22 11 12 in force, 10 not yet in force
The 22 laws behind 1.1 and MEASURE 2.4

and 12 more, every one in the free file.

GOVERN 1.4The risk management process and its outcomes are established through transparent... 17 12 11 in force, 6 not yet in force
The 17 laws behind 1.1 and GOVERN 1.4

and 7 more, every one in the free file.

MAP 2.3Scientific integrity and TEVV considerations are identified and documented, including... 12 9 8 in force, 4 not yet in force
The 12 laws behind 1.1 and MAP 2.3

and 2 more, every one in the free file.

GOVERN 1.6Mechanisms are in place to inventory AI systems and are resourced according to... 7 6 6 in force, 1 not yet in force
The 7 laws behind 1.1 and GOVERN 1.6
GOVERN 2.1Roles and responsibilities and lines of communication related to mapping, measuring,... 7 6 7 in force
The 7 laws behind 1.1 and GOVERN 2.1
MEASURE 2.11Fairness and bias – as identified in the MAP function – are evaluated and results are... 6 5 4 in force, 2 not yet in force
The 6 laws behind 1.1 and MEASURE 2.11
GOVERN 2.3Executive leadership of the organization takes responsibility for decisions about... 4 4 4 in force
The 4 laws behind 1.1 and GOVERN 2.3
MEASURE 2.9The AI model is explained, validated, and documented, and AI system output is... 4 4 4 in force
The 4 laws behind 1.1 and MEASURE 2.9
MANAGE 2.4Mechanisms are in place and applied, and responsibilities are assigned and understood,... 4 3 4 in force
The 4 laws behind 1.1 and MANAGE 2.4
MAP 5.1Likelihood and magnitude of each identified impact (both potentially beneficial and... 3 3 3 in force
The 3 laws behind 1.1 and MAP 5.1
MAP 3.3Targeted application scope is specified and documented based on the system’s... 3 2 3 in force
The 3 laws behind 1.1 and MAP 3.3
MEASURE 2.7AI system security and resilience – as identified in the MAP function – are evaluated... 2 2 1 in force, 1 not yet in force
The 2 laws behind 1.1 and MEASURE 2.7
MEASURE 3.3Feedback processes for end users and impacted communities to report problems and... 2 2 2 in force
The 2 laws behind 1.1 and MEASURE 3.3
1.2Risk Management GOVERN 1.1Legal and regulatory requirements involving AI are understood, managed, and documented. 38 20 28 in force, 9 not yet in force, 1 proposed
The 38 laws behind 1.2 and GOVERN 1.1

and 28 more, every one in the free file.

MAP 3.5Processes for human oversight are defined, assessed, and documented in accordance with... 25 18 17 in force, 8 not yet in force
The 25 laws behind 1.2 and MAP 3.5

and 15 more, every one in the free file.

MEASURE 2.4The functionality and behavior of the AI system and its components – as identified in... 22 11 12 in force, 10 not yet in force
The 22 laws behind 1.2 and MEASURE 2.4

and 12 more, every one in the free file.

GOVERN 1.4The risk management process and its outcomes are established through transparent... 17 12 11 in force, 6 not yet in force
The 17 laws behind 1.2 and GOVERN 1.4

and 7 more, every one in the free file.

MAP 2.3Scientific integrity and TEVV considerations are identified and documented, including... 12 9 8 in force, 4 not yet in force
The 12 laws behind 1.2 and MAP 2.3

and 2 more, every one in the free file.

MAP 5.1Likelihood and magnitude of each identified impact (both potentially beneficial and... 11 10 5 in force, 1 not yet in force, 5 proposed
The 11 laws behind 1.2 and MAP 5.1

and 1 more, every one in the free file.

GOVERN 1.6Mechanisms are in place to inventory AI systems and are resourced according to... 7 6 6 in force, 1 not yet in force
The 7 laws behind 1.2 and GOVERN 1.6
GOVERN 2.1Roles and responsibilities and lines of communication related to mapping, measuring,... 7 6 7 in force
The 7 laws behind 1.2 and GOVERN 2.1
MANAGE 1.3Responses to the AI risks deemed high priority, as identified by the MAP function, are... 6 6 1 not yet in force, 5 proposed
The 6 laws behind 1.2 and MANAGE 1.3
MEASURE 2.11Fairness and bias – as identified in the MAP function – are evaluated and results are... 6 5 4 in force, 2 not yet in force
The 6 laws behind 1.2 and MEASURE 2.11
MEASURE 2.10Privacy risk of the AI system – as identified in the MAP function – is examined and documented. 5 5 3 in force, 2 not yet in force
The 5 laws behind 1.2 and MEASURE 2.10
GOVERN 2.3Executive leadership of the organization takes responsibility for decisions about... 4 4 4 in force
The 4 laws behind 1.2 and GOVERN 2.3
MEASURE 2.9The AI model is explained, validated, and documented, and AI system output is... 4 4 4 in force
The 4 laws behind 1.2 and MEASURE 2.9
MANAGE 2.4Mechanisms are in place and applied, and responsibilities are assigned and understood,... 4 3 4 in force
The 4 laws behind 1.2 and MANAGE 2.4
MAP 3.3Targeted application scope is specified and documented based on the system’s... 3 2 3 in force
The 3 laws behind 1.2 and MAP 3.3
GOVERN 4.2Organizational teams document the risks and potential impacts of the AI technology... 2 2 2 in force
The 2 laws behind 1.2 and GOVERN 4.2
MEASURE 2.7AI system security and resilience – as identified in the MAP function – are evaluated... 2 2 1 in force, 1 not yet in force
The 2 laws behind 1.2 and MEASURE 2.7
MEASURE 3.3Feedback processes for end users and impacted communities to report problems and... 2 2 2 in force
The 2 laws behind 1.2 and MEASURE 3.3
1.5Safety Decision Frameworks MAP 3.3Targeted application scope is specified and documented based on the system’s... 143 86 124 in force, 15 not yet in force, 1 blocked by a court, 3 proposed
The 143 laws behind 1.5 and MAP 3.3

and 133 more, every one in the free file.

1.7Societal Impact Assessment MAP 5.1Likelihood and magnitude of each identified impact (both potentially beneficial and... 9 8 3 in force, 1 not yet in force, 5 proposed
The 9 laws behind 1.7 and MAP 5.1
MANAGE 1.3Responses to the AI risks deemed high priority, as identified by the MAP function, are... 5 5 5 proposed
The 5 laws behind 1.7 and MANAGE 1.3
MEASURE 2.10Privacy risk of the AI system – as identified in the MAP function – is examined and documented. 4 4 3 in force, 1 not yet in force
The 4 laws behind 1.7 and MEASURE 2.10
2.1Model & Infrastructure Security MAP 4.1Approaches for mapping AI technology and legal risks of its components – including the... 145 107 142 in force, 3 not yet in force
The 145 laws behind 2.1 and MAP 4.1

and 135 more, every one in the free file.

MEASURE 2.6The AI system is evaluated regularly for safety risks – as identified in the MAP... 3 2 2 in force, 1 not yet in force
The 3 laws behind 2.1 and MEASURE 2.6
MEASURE 2.5The AI system to be deployed is demonstrated to be valid and reliable. Limitations of... 2 1 1 in force, 1 not yet in force
The 2 laws behind 2.1 and MEASURE 2.5
MEASURE 2.7AI system security and resilience – as identified in the MAP function – are evaluated... 2 1 1 in force, 1 not yet in force
The 2 laws behind 2.1 and MEASURE 2.7
2.3Model Safety Engineering MEASURE 2.6The AI system is evaluated regularly for safety risks – as identified in the MAP... 7 6 3 in force, 4 not yet in force
The 7 laws behind 2.3 and MEASURE 2.6
MAP 1.6System requirements (e.g., “the system shall respect the privacy of its users”) are... 4 4 1 in force, 3 not yet in force
The 4 laws behind 2.3 and MAP 1.6
MEASURE 2.8Risks associated with transparency and accountability – as identified in the MAP... 3 3 1 in force, 2 not yet in force
The 3 laws behind 2.3 and MEASURE 2.8
MAP 3.3Targeted application scope is specified and documented based on the system’s... 2 2 1 in force, 1 not yet in force
The 2 laws behind 2.3 and MAP 3.3
MEASURE 2.5The AI system to be deployed is demonstrated to be valid and reliable. Limitations of... 2 1 1 in force, 1 not yet in force
The 2 laws behind 2.3 and MEASURE 2.5
MEASURE 2.7AI system security and resilience – as identified in the MAP function – are evaluated... 2 1 1 in force, 1 not yet in force
The 2 laws behind 2.3 and MEASURE 2.7
2.4Content Safety Controls MEASURE 2.8Risks associated with transparency and accountability – as identified in the MAP... 43 33 30 in force, 8 not yet in force, 1 blocked by a court, 4 proposed
The 43 laws behind 2.4 and MEASURE 2.8

and 33 more, every one in the free file.

MAP 1.6System requirements (e.g., “the system shall respect the privacy of its users”) are... 4 4 1 in force, 3 not yet in force
The 4 laws behind 2.4 and MAP 1.6
MEASURE 2.6The AI system is evaluated regularly for safety risks – as identified in the MAP... 4 4 1 in force, 3 not yet in force
The 4 laws behind 2.4 and MEASURE 2.6
3.1Testing & Auditing MAP 5.1Likelihood and magnitude of each identified impact (both potentially beneficial and... 9 8 3 in force, 1 not yet in force, 5 proposed
The 9 laws behind 3.1 and MAP 5.1
MANAGE 1.3Responses to the AI risks deemed high priority, as identified by the MAP function, are... 5 5 5 proposed
The 5 laws behind 3.1 and MANAGE 1.3
MEASURE 2.10Privacy risk of the AI system – as identified in the MAP function – is examined and documented. 4 4 3 in force, 1 not yet in force
The 4 laws behind 3.1 and MEASURE 2.10
MEASURE 2.6The AI system is evaluated regularly for safety risks – as identified in the MAP... 3 2 2 in force, 1 not yet in force
The 3 laws behind 3.1 and MEASURE 2.6
MEASURE 2.5The AI system to be deployed is demonstrated to be valid and reliable. Limitations of... 2 1 1 in force, 1 not yet in force
The 2 laws behind 3.1 and MEASURE 2.5
MEASURE 2.7AI system security and resilience – as identified in the MAP function – are evaluated... 2 1 1 in force, 1 not yet in force
The 2 laws behind 3.1 and MEASURE 2.7
3.2Data Governance MAP 4.1Approaches for mapping AI technology and legal risks of its components – including the... 189 119 185 in force, 4 not yet in force
The 189 laws behind 3.2 and MAP 4.1

and 179 more, every one in the free file.

MAP 1.6System requirements (e.g., “the system shall respect the privacy of its users”) are... 6 5 5 in force, 1 not yet in force
The 6 laws behind 3.2 and MAP 1.6
MAP 3.5Processes for human oversight are defined, assessed, and documented in accordance with... 5 3 3 in force, 2 not yet in force
The 5 laws behind 3.2 and MAP 3.5
MEASURE 2.9The AI model is explained, validated, and documented, and AI system output is... 4 4 1 in force, 3 not yet in force
The 4 laws behind 3.2 and MEASURE 2.9
MEASURE 2.8Risks associated with transparency and accountability – as identified in the MAP... 2 2 1 in force, 1 not yet in force
The 2 laws behind 3.2 and MEASURE 2.8
MEASURE 2.10Privacy risk of the AI system – as identified in the MAP function – is examined and documented. 2 2 2 in force
The 2 laws behind 3.2 and MEASURE 2.10
MEASURE 3.3Feedback processes for end users and impacted communities to report problems and... 2 2 2 not yet in force
The 2 laws behind 3.2 and MEASURE 3.3
MAP 3.3Targeted application scope is specified and documented based on the system’s... 2 1 2 in force
The 2 laws behind 3.2 and MAP 3.3
3.3Access Management MAP 3.3Targeted application scope is specified and documented based on the system’s... 145 87 126 in force, 15 not yet in force, 1 blocked by a court, 3 proposed
The 145 laws behind 3.3 and MAP 3.3

and 135 more, every one in the free file.

MAP 3.5Processes for human oversight are defined, assessed, and documented in accordance with... 4 2 2 in force, 2 not yet in force
The 4 laws behind 3.3 and MAP 3.5
GOVERN 6.1Policies and procedures are in place that address AI risks associated with third-party... 2 2 1 in force, 1 not yet in force
The 2 laws behind 3.3 and GOVERN 6.1
3.5Post-deployment Monitoring GOVERN 1.1Legal and regulatory requirements involving AI are understood, managed, and documented. 38 20 28 in force, 9 not yet in force, 1 proposed
The 38 laws behind 3.5 and GOVERN 1.1

and 28 more, every one in the free file.

MAP 3.5Processes for human oversight are defined, assessed, and documented in accordance with... 25 18 17 in force, 8 not yet in force
The 25 laws behind 3.5 and MAP 3.5

and 15 more, every one in the free file.

MEASURE 2.4The functionality and behavior of the AI system and its components – as identified in... 22 11 12 in force, 10 not yet in force
The 22 laws behind 3.5 and MEASURE 2.4

and 12 more, every one in the free file.

GOVERN 1.4The risk management process and its outcomes are established through transparent... 17 12 11 in force, 6 not yet in force
The 17 laws behind 3.5 and GOVERN 1.4

and 7 more, every one in the free file.

MAP 2.3Scientific integrity and TEVV considerations are identified and documented, including... 12 9 8 in force, 4 not yet in force
The 12 laws behind 3.5 and MAP 2.3

and 2 more, every one in the free file.

GOVERN 1.6Mechanisms are in place to inventory AI systems and are resourced according to... 7 6 6 in force, 1 not yet in force
The 7 laws behind 3.5 and GOVERN 1.6
GOVERN 2.1Roles and responsibilities and lines of communication related to mapping, measuring,... 7 6 7 in force
The 7 laws behind 3.5 and GOVERN 2.1
MEASURE 2.11Fairness and bias – as identified in the MAP function – are evaluated and results are... 6 5 4 in force, 2 not yet in force
The 6 laws behind 3.5 and MEASURE 2.11
GOVERN 2.3Executive leadership of the organization takes responsibility for decisions about... 4 4 4 in force
The 4 laws behind 3.5 and GOVERN 2.3
MEASURE 2.9The AI model is explained, validated, and documented, and AI system output is... 4 4 4 in force
The 4 laws behind 3.5 and MEASURE 2.9
MANAGE 2.4Mechanisms are in place and applied, and responsibilities are assigned and understood,... 4 3 4 in force
The 4 laws behind 3.5 and MANAGE 2.4
MAP 5.1Likelihood and magnitude of each identified impact (both potentially beneficial and... 3 3 3 in force
The 3 laws behind 3.5 and MAP 5.1
MAP 3.3Targeted application scope is specified and documented based on the system’s... 3 2 3 in force
The 3 laws behind 3.5 and MAP 3.3
MEASURE 2.7AI system security and resilience – as identified in the MAP function – are evaluated... 2 2 1 in force, 1 not yet in force
The 2 laws behind 3.5 and MEASURE 2.7
MEASURE 3.3Feedback processes for end users and impacted communities to report problems and... 2 2 2 in force
The 2 laws behind 3.5 and MEASURE 3.3
3.6Incident Response & Recovery MEASURE 2.6The AI system is evaluated regularly for safety risks – as identified in the MAP... 3 2 2 in force, 1 not yet in force
The 3 laws behind 3.6 and MEASURE 2.6
MEASURE 2.5The AI system to be deployed is demonstrated to be valid and reliable. Limitations of... 2 1 1 in force, 1 not yet in force
The 2 laws behind 3.6 and MEASURE 2.5
MEASURE 2.7AI system security and resilience – as identified in the MAP function – are evaluated... 2 1 1 in force, 1 not yet in force
The 2 laws behind 3.6 and MEASURE 2.7
4.1System Documentation MEASURE 2.8Risks associated with transparency and accountability – as identified in the MAP... 64 43 40 in force, 12 not yet in force, 12 proposed
The 64 laws behind 4.1 and MEASURE 2.8

and 54 more, every one in the free file.

GOVERN 1.1Legal and regulatory requirements involving AI are understood, managed, and documented. 38 20 28 in force, 9 not yet in force, 1 proposed
The 38 laws behind 4.1 and GOVERN 1.1

and 28 more, every one in the free file.

MAP 3.5Processes for human oversight are defined, assessed, and documented in accordance with... 26 19 18 in force, 8 not yet in force
The 26 laws behind 4.1 and MAP 3.5

and 16 more, every one in the free file.

MEASURE 2.4The functionality and behavior of the AI system and its components – as identified in... 22 11 12 in force, 10 not yet in force
The 22 laws behind 4.1 and MEASURE 2.4

and 12 more, every one in the free file.

MAP 4.1Approaches for mapping AI technology and legal risks of its components – including the... 18 16 17 in force, 1 not yet in force
The 18 laws behind 4.1 and MAP 4.1

and 8 more, every one in the free file.

GOVERN 1.4The risk management process and its outcomes are established through transparent... 17 12 11 in force, 6 not yet in force
The 17 laws behind 4.1 and GOVERN 1.4

and 7 more, every one in the free file.

MAP 2.3Scientific integrity and TEVV considerations are identified and documented, including... 12 9 8 in force, 4 not yet in force
The 12 laws behind 4.1 and MAP 2.3

and 2 more, every one in the free file.

MEASURE 3.3Feedback processes for end users and impacted communities to report problems and... 10 10 3 in force, 1 not yet in force, 6 proposed
The 10 laws behind 4.1 and MEASURE 3.3
GOVERN 4.2Organizational teams document the risks and potential impacts of the AI technology... 8 6 4 in force, 3 not yet in force, 1 proposed
The 8 laws behind 4.1 and GOVERN 4.2
GOVERN 1.6Mechanisms are in place to inventory AI systems and are resourced according to... 7 6 6 in force, 1 not yet in force
The 7 laws behind 4.1 and GOVERN 1.6
GOVERN 2.1Roles and responsibilities and lines of communication related to mapping, measuring,... 7 6 7 in force
The 7 laws behind 4.1 and GOVERN 2.1
MEASURE 2.11Fairness and bias – as identified in the MAP function – are evaluated and results are... 6 5 4 in force, 2 not yet in force
The 6 laws behind 4.1 and MEASURE 2.11
MEASURE 2.9The AI model is explained, validated, and documented, and AI system output is... 5 5 5 in force
The 5 laws behind 4.1 and MEASURE 2.9
MAP 2.2Information about the AI system’s knowledge limits and how system output may be... 5 4 1 in force, 4 not yet in force
The 5 laws behind 4.1 and MAP 2.2
MAP 3.3Targeted application scope is specified and documented based on the system’s... 5 4 4 in force, 1 not yet in force
The 5 laws behind 4.1 and MAP 3.3
MANAGE 2.4Mechanisms are in place and applied, and responsibilities are assigned and understood,... 5 4 5 in force
The 5 laws behind 4.1 and MANAGE 2.4
GOVERN 2.3Executive leadership of the organization takes responsibility for decisions about... 4 4 4 in force
The 4 laws behind 4.1 and GOVERN 2.3
MAP 1.6System requirements (e.g., “the system shall respect the privacy of its users”) are... 4 4 3 in force, 1 not yet in force
The 4 laws behind 4.1 and MAP 1.6
MAP 5.1Likelihood and magnitude of each identified impact (both potentially beneficial and... 3 3 3 in force
The 3 laws behind 4.1 and MAP 5.1
MEASURE 2.6The AI system is evaluated regularly for safety risks – as identified in the MAP... 3 3 1 in force, 1 not yet in force, 1 proposed
The 3 laws behind 4.1 and MEASURE 2.6
MEASURE 2.5The AI system to be deployed is demonstrated to be valid and reliable. Limitations of... 2 2 2 in force
The 2 laws behind 4.1 and MEASURE 2.5
MEASURE 2.7AI system security and resilience – as identified in the MAP function – are evaluated... 2 2 1 in force, 1 not yet in force
The 2 laws behind 4.1 and MEASURE 2.7
MEASURE 2.10Privacy risk of the AI system – as identified in the MAP function – is examined and documented. 2 2 1 in force, 1 not yet in force
The 2 laws behind 4.1 and MEASURE 2.10
4.2Risk Disclosure MEASURE 2.8Risks associated with transparency and accountability – as identified in the MAP... 64 43 40 in force, 12 not yet in force, 12 proposed
The 64 laws behind 4.2 and MEASURE 2.8

and 54 more, every one in the free file.

GOVERN 1.1Legal and regulatory requirements involving AI are understood, managed, and documented. 18 12 13 in force, 4 not yet in force, 1 proposed
The 18 laws behind 4.2 and GOVERN 1.1

and 8 more, every one in the free file.

MEASURE 3.3Feedback processes for end users and impacted communities to report problems and... 10 10 3 in force, 1 not yet in force, 6 proposed
The 10 laws behind 4.2 and MEASURE 3.3
GOVERN 4.2Organizational teams document the risks and potential impacts of the AI technology... 10 7 6 in force, 3 not yet in force, 1 proposed
The 10 laws behind 4.2 and GOVERN 4.2
MANAGE 4.3Incidents and errors are communicated to relevant AI actors, including affected... 8 6 4 in force, 3 not yet in force, 1 proposed
The 8 laws behind 4.2 and MANAGE 4.3
MANAGE 4.1Post-deployment AI system monitoring plans are implemented, including mechanisms for... 5 5 5 in force
The 5 laws behind 4.2 and MANAGE 4.1
MAP 2.2Information about the AI system’s knowledge limits and how system output may be... 4 3 1 in force, 3 not yet in force
The 4 laws behind 4.2 and MAP 2.2
MAP 1.6System requirements (e.g., “the system shall respect the privacy of its users”) are... 3 3 2 in force, 1 not yet in force
The 3 laws behind 4.2 and MAP 1.6
MAP 3.3Targeted application scope is specified and documented based on the system’s... 3 3 2 in force, 1 not yet in force
The 3 laws behind 4.2 and MAP 3.3
GOVERN 4.3Organizational practices are in place to enable AI testing, identification of... 2 2 1 in force, 1 not yet in force
The 2 laws behind 4.2 and GOVERN 4.3
MAP 3.5Processes for human oversight are defined, assessed, and documented in accordance with... 2 2 2 in force
The 2 laws behind 4.2 and MAP 3.5
MEASURE 2.4The functionality and behavior of the AI system and its components – as identified in... 2 2 2 in force
The 2 laws behind 4.2 and MEASURE 2.4
MEASURE 2.6The AI system is evaluated regularly for safety risks – as identified in the MAP... 2 2 1 not yet in force, 1 proposed
The 2 laws behind 4.2 and MEASURE 2.6
MEASURE 2.9The AI model is explained, validated, and documented, and AI system output is... 2 2 2 in force
The 2 laws behind 4.2 and MEASURE 2.9
MANAGE 2.4Mechanisms are in place and applied, and responsibilities are assigned and understood,... 2 2 1 in force, 1 not yet in force
The 2 laws behind 4.2 and MANAGE 2.4
4.3Incident Reporting GOVERN 1.1Legal and regulatory requirements involving AI are understood, managed, and documented. 15 11 12 in force, 2 not yet in force, 1 proposed
The 15 laws behind 4.3 and GOVERN 1.1

and 5 more, every one in the free file.

MANAGE 4.3Incidents and errors are communicated to relevant AI actors, including affected... 9 7 5 in force, 3 not yet in force, 1 proposed
The 9 laws behind 4.3 and MANAGE 4.3
GOVERN 4.2Organizational teams document the risks and potential impacts of the AI technology... 8 6 5 in force, 3 not yet in force
The 8 laws behind 4.3 and GOVERN 4.2
MANAGE 4.1Post-deployment AI system monitoring plans are implemented, including mechanisms for... 6 6 6 in force
The 6 laws behind 4.3 and MANAGE 4.1
GOVERN 4.3Organizational practices are in place to enable AI testing, identification of... 2 2 1 in force, 1 not yet in force
The 2 laws behind 4.3 and GOVERN 4.3
4.4Governance Disclosure GOVERN 1.1Legal and regulatory requirements involving AI are understood, managed, and documented. 4 3 2 in force, 2 not yet in force
The 4 laws behind 4.4 and GOVERN 1.1
4.5Third-Party System Access GOVERN 1.1Legal and regulatory requirements involving AI are understood, managed, and documented. 15 11 12 in force, 2 not yet in force, 1 proposed
The 15 laws behind 4.5 and GOVERN 1.1

and 5 more, every one in the free file.

GOVERN 4.2Organizational teams document the risks and potential impacts of the AI technology... 8 6 5 in force, 3 not yet in force
The 8 laws behind 4.5 and GOVERN 4.2
MANAGE 4.3Incidents and errors are communicated to relevant AI actors, including affected... 8 6 4 in force, 3 not yet in force, 1 proposed
The 8 laws behind 4.5 and MANAGE 4.3
MANAGE 4.1Post-deployment AI system monitoring plans are implemented, including mechanisms for... 5 5 5 in force
The 5 laws behind 4.5 and MANAGE 4.1
GOVERN 4.3Organizational practices are in place to enable AI testing, identification of... 2 2 1 in force, 1 not yet in force
The 2 laws behind 4.5 and GOVERN 4.3
4.6User Rights & Recourse MEASURE 2.8Risks associated with transparency and accountability – as identified in the MAP... 84 52 56 in force, 15 not yet in force, 1 blocked by a court, 12 proposed
The 84 laws behind 4.6 and MEASURE 2.8

and 74 more, every one in the free file.

MEASURE 3.3Feedback processes for end users and impacted communities to report problems and... 10 10 2 in force, 2 not yet in force, 6 proposed
The 10 laws behind 4.6 and MEASURE 3.3
GOVERN 4.2Organizational teams document the risks and potential impacts of the AI technology... 8 6 4 in force, 3 not yet in force, 1 proposed
The 8 laws behind 4.6 and GOVERN 4.2
MAP 1.6System requirements (e.g., “the system shall respect the privacy of its users”) are... 6 6 3 in force, 3 not yet in force
The 6 laws behind 4.6 and MAP 1.6
MEASURE 2.6The AI system is evaluated regularly for safety risks – as identified in the MAP... 5 5 1 in force, 3 not yet in force, 1 proposed
The 5 laws behind 4.6 and MEASURE 2.6
MEASURE 2.9The AI model is explained, validated, and documented, and AI system output is... 5 5 2 in force, 3 not yet in force
The 5 laws behind 4.6 and MEASURE 2.9
MAP 2.2Information about the AI system’s knowledge limits and how system output may be... 4 3 1 in force, 3 not yet in force
The 4 laws behind 4.6 and MAP 2.2
MAP 3.3Targeted application scope is specified and documented based on the system’s... 3 3 1 in force, 2 not yet in force
The 3 laws behind 4.6 and MAP 3.3
MAP 3.5Processes for human oversight are defined, assessed, and documented in accordance with... 2 2 2 in force
The 2 laws behind 4.6 and MAP 3.5
Not connected to the NIST AI RMF: 5 of MIT mitigations' controls

No law we track reaches these

No duty in the laws we track reaches these controls.

  • 1.3 Conflict of Interest Protections
  • 1.4 Whistleblower Reporting & Protection
  • 1.6 Environmental Impact Management
  • 2.2 Model Alignment
  • 3.4 Staged Deployment

How these connections are drawn

Each requirement line in the laws we track is read against the framework for its subject (the AI, scraping and news aggregation laws against the NIST AI RMF, the privacy, communications and age assurance laws against the NIST Privacy Framework, the cybersecurity laws against the NIST CSF 2.0); laws on liability and content moderation are not read against any framework yet. A line reaches the MIT mitigations through a kind of duty its law carries, and only where that kind of duty also reaches, on that same line, the NIST framework for the line's own subject. Two controls connect when lines in at least 2 laws reach both. That says the same duties reach both; it does not say the two are alike, or that running either one does what a law asks.

Every duty line in the AI, scraping and news aggregation laws we track has been read against the framework for its subject.

Sources and licenses

MIT AI Risk Initiative (MIT FutureTech), AI Risk Mitigation Taxonomy. Data from the MIT AI Risk Initiative is licensed under CC BY 4.0. Cite as: Mapping AI Risk Mitigations: Evidence Scan & Draft Mitigation Taxonomy