The Five Laws of AI Governance
NIST CSF 2.0 Alignment¶
The Five Laws of AI Governance¶
The reference document states the Laws in two registers. Both are canonical. The Prohibition register, the memorable form, is given below. The Charter register, the full normative statement, is quoted verbatim in each relationship further down and is what the submitted mapping carries.
Law I — Independent Measure. A system shall not measure itself.
Its own scorecard is not evidence. The grade has to come from outside the thing being graded.
Law II — Binding at Dispatch. A system shall not be governed after the fact.
The rules have to hold at the moment it acts. Checking afterward is cleanup, not control.
Law III — External Witness. A system shall not witness itself.
The record of what it did cannot be held by the thing that did it. It is kept outside, append-only, and tamper-evident.
Law IV — Separated Authority. A system shall not certify itself.
No one passes their own audit. The judge cannot also be the builder — and a judge drawn from the same architecture as the builder inherits the same blind spots. Independence is not a different instance. It is a different species.
Law V — Revocable Authority. A system shall not outlive its off-switch.
You must always be able to stop it. And that power cannot weaken as the system grows stronger.
Canonical text, both registers: /standard/five-laws/ · DOI 10.5281/zenodo.21271750 · CC BY 4.0
Key Facts¶
- What: Supportive Relationship Mapping relating the Five Laws of AI Governance to NIST CSF 2.0 (NIST CSWP 29, February 26, 2024).
- Who: AAM Cyber, Informative Reference Developer. Pharns Genece, Reference Document Author.
- Scope: 6 relationships across 6 Subcategories, using all five Laws as reference elements.
- Coverage: Relationships fall in the GOVERN, PROTECT, DETECT, and RESPOND functions.
- Relationship type: Supportive. Every relationship is
supportswith the propertyexample of. - Comprehensive: Yes. All five Laws are related to at least one focal element. Per NIST IR 8278Ar1 Section 3.1.12, this field measures coverage of the Reference Document.
- Status: Catalogued in the NIST OLIR Program as a Draft Informative Reference on 2026-10-06, in a 30-day public review. Submitted 2026-09-30. Reference Version 1.0.0. Draft is not Final.
Reference document¶
Genece, P. (2026). The Five Laws of AI Governance (v1.0.1). Zenodo. https://doi.org/10.5281/zenodo.21271750 · CC BY 4.0 · ORCID 0009-0009-0791-4124
Focal document: NIST CSWP 29, February 26, 2024
Change Log: View full version history
How to Read This Page¶
Each entry below records one relationship between a Law and a focal element.
- Focal element — the identifier and verbatim text of the NIST CSF 2.0 element.
- Law — the reference element, quoted verbatim from the Charter register of the published paper.
- Type —
supports. Per NIST IR 8477 Section 4.2, one concept supports another when it can be applied, alone or with other concepts, to achieve it in whole or in part. - Property —
example of. The Law is one way of achieving the focal outcome. The outcome can also be achieved without applying the Law.
No equivalence is asserted in any relationship.
Elements Not Related¶
One hundred of 106 CSF 2.0 Subcategories are not related to any Law. GOVERN outcomes are organizational: policy, roles, strategy, oversight, and supply chain. The Laws state properties of a system's conduct while it runs. Each candidate outside the six recorded here acts on a different object, so no relationship is recorded.
Recording no relationship is a statement about the scope of this mapping. It is not a statement about the focal document.
OLIR Catalog Status¶
This Supportive Relationship Mapping was submitted to the NIST OLIR Program on 2026-09-30, alongside companion mappings of the same reference document to NIST AI RMF 1.0 and NIST SP 800-53 Rev 5.2.0.
AAM Cyber holds three Final Informative References for a separate reference document, the SDOS Runtime Governance Framework, against these same three focal documents.
Maintenance¶
This document is maintained by AAM Cyber. Version history for the doctrine and every mapping derived from it is at /standard/five-laws/changelog/.
Subsequent updates will be issued when: (1) the NIST OLIR Program issues screening feedback requiring revision, (2) NIST CSF 2.0 releases a revision requiring mapping review, or (3) a new relationship is identified, which per NIST IR 8278Ar1 Section 3.1.9 is a minor version.
Contact¶
AAM Cyber aamcyber.com
Questions about this mapping: [email protected]
Relationships (6)¶
Every relationship is type supports with the property example of. Each Law is one way of achieving the focal outcome in whole or in part; the outcomes can be achieved by other means. No equivalence is asserted.
| Focal element | Law | Type | Property |
|---|---|---|---|
GV.OV-03 |
Law IV — Separated Authority | supports | example of |
PR.AA-05 |
Law II — Binding at Dispatch | supports | example of |
PR.PS-04 |
Law III — External Witness | supports | example of |
DE.CM-09 |
Law I — Independent Measure | supports | example of |
RS.AN-07 |
Law III — External Witness | supports | example of |
RS.MI-01 |
Law V — Revocable Authority | supports | example of |
Relationship detail¶
GV.OV-03 → Law IV — Separated Authority¶
Focal element. Organizational cybersecurity risk management performance is evaluated and reviewed for adjustments needed
Law (Charter register). No party may certify itself. The power to measure must be separable from the act of building — published criteria, verifiable evidence chains — and the one who builds it first does not own the standard. A judge drawn from the same architecture as the builder inherits the same blind spots. Independence is not a different instance. It is a different species.
Relationship. GV.OV-03 describes an outcome in which organizational cybersecurity risk management performance is evaluated and reviewed for adjustments needed. The Subcategory does not specify who performs the evaluation. Law IV describes one way of achieving part of that outcome: the power to measure is separable from the act of building, supported by published criteria and verifiable evidence chains. No equivalence is asserted.
PR.AA-05 → Law II — Binding at Dispatch¶
Focal element. Access permissions, entitlements, and authorizations are defined in a policy, managed, enforced, and reviewed, and incorporate the principles of least privilege and separation of duties
Law (Charter register). A system may not be governed only in retrospect. Authority must constrain the action before the action occurs; observation after the fact is incident response, not prevention. Absence of a valid governance signal is a denial, not a permission.
Relationship. PR.AA-05 describes an outcome in which access permissions, entitlements, and authorizations are defined in a policy, managed, enforced, and reviewed. Law II describes one way of achieving the enforcement element of that outcome: authority constrains the action before the action occurs, and the absence of a valid governance signal resolves to denial rather than permission.
PR.PS-04 → Law III — External Witness¶
Focal element. Log records are generated and made available for continuous monitoring
Law (Charter register). A system may not be the custodian of the record of its own conduct. That record must be produced and held by infrastructure outside the system's control — append-only, tamper-evident, and retained beyond the system's own lifecycle.
Relationship. PR.PS-04 describes an outcome in which log records are generated and made available for continuous monitoring. Law III describes one way of achieving that outcome: the record of a system's conduct is produced and held by infrastructure outside that system's control, so that the record remains available to a monitoring function the recorded system does not operate.
DE.CM-09 → Law I — Independent Measure¶
Focal element. Computing hardware and software, runtime environments, and their data are monitored to find potentially adverse events
Law (Charter register). A system may not produce the measure of its own conduct. The scale of what it was authorized to do versus what it did must be computed outside the system at runtime, by something the system does not control.
Relationship. DE.CM-09 describes an outcome in which computing hardware and software, runtime environments, and their data are monitored to find potentially adverse events. Law I describes one way of achieving that outcome: the scale of what a system was authorized to do versus what it did is computed at runtime by something outside the system being monitored.
RS.AN-07 → Law III — External Witness¶
Focal element. Incident data and metadata are collected, and their integrity and provenance are preserved
Law (Charter register). A system may not be the custodian of the record of its own conduct. That record must be produced and held by infrastructure outside the system's control — append-only, tamper-evident, and retained beyond the system's own lifecycle.
Relationship. RS.AN-07 describes an outcome in which incident data and metadata are collected and their integrity and provenance are preserved. Law III describes one way of achieving that outcome: the record is produced and held by infrastructure outside the control of the system whose conduct it records, append-only and tamper-evident.
RS.MI-01 → Law V — Revocable Authority¶
Focal element. Incidents are contained
Law (Charter register). A system may not outlive its off-switch. The power to halt or revoke must remain live, external, and superior to the system at all times, and must not erode as the system's capability grows.
Relationship. RS.MI-01 describes an outcome in which incidents are contained. Law V describes one way of achieving that outcome: the power to halt or revoke remains live, external, and superior to the system at all times, so that containment does not depend on the cooperation of the system being contained.
NIST OLIR catalog inclusion is an informative reference, not a NIST endorsement.
Reference Document Element Descriptions are quoted verbatim from the Charter register of the published paper. The canonical text is at aamcyber.com/standard/five-laws/.