NIST AI RMF 1.0
Rendered when the buyer ticks "NIST AI RMF". The register cites 5 of its 72 clauses, behind 6 findings: decides alone under a listed use, decides with review, no reviewer named, no benchmark evidence on the entity's own cases, decides alone, or decides a listed use, with no impact assessment recorded, concentration on one tool, retest longer than the reporting cycle, and on the obligation rows of every line it reaches.
Requirement text in our own words, read clause by clause from the published standards: our statement of each clause, not the instrument verbatim. Source framework: NIST AI RMF 1.0. What it attaches to a line: the NIST AI RMF regime page.
Clauses cited
5 of 72AI RMF MP-3.5 Processes for human oversight are defined, assessed, and documented in accordance with organizational policies from the GOVERN functionProcesses for human oversight are defined, assessed, and documented in accordance with organizational policies from GOVERN function. Oversight is designed for the specific configuration, assessed for whether it is exercisable in practice, and consistent with the governing policy rather than invented per project.
Common gap: Oversight designed at a volume the reviewer cannot sustain
Source framework: NIST AI RMF 1.0
AI RMF MS-2.3 AI system performance or assurance criteria are measured qualitatively or quantitatively and demonstrated for conditions similar to deployment settings, and measures are documentedAI system performance or assurance criteria are measured qualitatively or quantitatively and demonstrated for conditions similar to deployment setting(s). Measures are documented. Performance is demonstrated under conditions resembling deployment rather than only on held-out test data, and the measures are recorded.
Common gap: Performance demonstrated only in silico on a static test set
Source framework: NIST AI RMF 1.0
AI RMF MS-2.5 The AI system to be deployed is demonstrated to be valid and reliable, and limitations of the generalizability beyond the conditions under which the technology was developed are documentedThe AI system to be deployed is demonstrated to be valid and reliable. Limitations of the generalizability beyond the conditions under which the technology was developed are documented. Validity and reliability are demonstrated before deployment, and the boundary beyond which the demonstration does not carry is written down.
Common gap: Validity claimed from training performance rather than independent validation
Source framework: NIST AI RMF 1.0
AI RMF MN-3.1 AI risks and benefits from third-party resources are regularly monitored, and risk controls are applied and documentedAI risks and benefits from third-party resources are regularly monitored, and risk controls are applied and documented. Third-party data, model, software and hardware dependencies are monitored on an ongoing basis, not assessed once at procurement, and the controls applied are recorded.
Common gap: Third parties assessed at onboarding and not monitored afterwards
Source framework: NIST AI RMF 1.0
AI RMF MN-1.1 A determination is made as to whether the AI system achieves its intended purpose and stated objectives and whether its development or deployment should proceedA determination is made as to whether the AI system achieves its intended purpose and stated objectives and whether its development or deployment should proceed. A recorded determination weighs measured risk against benefit and decides whether to proceed, so that not proceeding remains an available and evidenced outcome.
Common gap: Determination recorded as approval with no evidence weighed
Source framework: NIST AI RMF 1.0
See which clauses your list engages
Paste the list and every line names the clauses behind it, filtered to the regimes that apply to you. Eight lines free, no account.
Build my decision register