Skip to main content

Regulation map

NIST AI RMF, function by function.

Govern, Map, Measure and Manage, mapped to elan1 controls, for the procurement and security reviews that ask in NIST's terms. Free to read, no form.

Last reviewed
Access
Read free · no form
A lawyer takes a bound statute volume from black steel shelving in a skylit reading room

In short

The short answer.

What is the NIST AI Risk Management Framework?

The NIST AI Risk Management Framework, AI RMF 1.0 (NIST AI 100-1), released on 26 January 2023, is a voluntary, sector-neutral framework from the US National Institute of Standards and Technology. Its four functions, Govern, Map, Measure and Manage, give risk teams a shared vocabulary.

Applies to
Voluntary for any organisation. Indian enterprises meet it most often in procurement: global customers and parent companies increasingly ask suppliers to describe their AI controls in its terms.
Key dates
  1. 26 Jan 2023AI RMF 1.0 (NIST AI 100-1) released.
  2. 26 Jul 2024The Generative AI Profile (NIST AI 600-1) released.

Clause by clause

Each duty, and the control that answers it.

NIST AI RMF, clause by clause, mapped to elan1 controls, with the claim IDs behind each control
Clause, and what it askselan1 controlMapped toClaim IDs
Govern (function)A culture of risk management, with policies, accountability and roles. It is cross-cutting and informs the other three.Approval rules with named owners and review dates, held in elan1 Govern and changed on the record.
  • elan1 Govern
MapEstablish the context, purpose and potential impacts of an AI system, so risks can be identified.The readiness check and rule sheet capture each process's purpose, action types and who answers for them.
  • elan1 Govern
No claim ID
MeasureAnalyse, assess and track identified risks with quantitative and qualitative methods.Calibrated confidence in elan1 Decide, and refusal and expiry rates by agent and by rule.
  • elan1 Decide
  • elan1 Govern
ManagePrioritise risks and act on them, including responding to and recovering from incidents.Allow, ask a person or refuse before every action; one emergency stop for every agent; a record that supports incident response.
  • elan1 Govern

Mappings are drafts for your counsel and auditors. They are not certification, legal advice or regulator approval.

What this map does not claim.

  • Using the framework is voluntary and there is no NIST certification.

A note on names.

The framework's Govern function is an organisational practice. elan1 Govern is a product that decides individual agent actions. The product can supply evidence for the function; it does not replace it.

Questions

NIST AI RMF, plainly.

No. Using the framework is voluntary, and NIST does not certify organisations against it. Teams use it as a shared vocabulary for AI risk, and global buyers increasingly ask suppliers to describe their AI controls in its terms. A clear mapping can shorten security questionnaires and procurement reviews.

No. The framework's Govern function is an organisational practice: it builds a culture of risk management with policies, accountability and roles, and informs Map, Measure and Manage. elan1 Govern is a product that decides individual agent actions before they run. The product can supply evidence for the function; it does not replace it.

Agents that act close the gap between an output and a consequence, so three areas get harder. Govern needs a named person who can answer for each class of action. Measure is most useful as the pattern of approvals, refusals and expiries over time. Manage needs a way to supersede, disengage or deactivate agents, such as an emergency stop that works across all of them.

In India by default: AWS Mumbai, three availability zones, no US region. elan1 Run also runs in your data centre or on an appliance. Personal fields are masked before any model call.

No. Mappings are drafts for your counsel and auditors. They are not certification, legal advice or regulator approval. Each row names the clause or duty, what it asks, the elan1 control that answers it and, where one is assigned, the claim ID behind it, so your counsel and auditors can test each mapping against the receipts.

Start with one process.

Put one agent on the path. We'll show you the receipt.

  • Allowed · Approved by Asha R.
  • Held for CFO
  • Refused · rule 4.2
Illustrative data.

Add the next when it holds.

Approvals · Kolam ComponentsIllustrative
  • Allowed · Approved by Asha R.
  • Held for CFO
  • Refused · rule 4.2
RCPT-0042 · signed · chained
A product view with three decisions: allowed and approved by Asha R., held for the CFO, and refused under rule 4.2. Illustrative data.