System requirements (e.g., “the system shall respect the privacy of its users”) are elicited from and understood by relevant AI actors. Design decisions take socio-technical implications into account to address AI risks. Requirements are elicited from the actors who will be affected and written down, and the design record shows socio-technical implications were weighed rather than only technical ones.
NIST AI Risk Management Framework (AI RMF 1.0) AIRMF-MP-1.6 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of NIST AI Risk Management Framework (AI RMF 1.0) your existing evidence covers. Hold EU AI Act and 48 of 72 NIST AI Risk Management Framework (AI RMF 1.0) controls already carry evidence.
Each report names every control your existing framework evidences, every one it does not, the reasoning behind each claim, and the claims that were argued against and rejected. 10 were rejected on the EU AI Act pair alone.
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.