Updated 12 May 2026 · Re-checked and republished 18 July 2026 · AgenticRail
EU AI Act, NIST AI RMF, ISO 42001: Three Frameworks, One Evidence Question
Three frameworks dominate AI governance in 2026: the EU AI Act (binding regulation, high-risk obligations from December 2027), NIST AI RMF 1.0 (voluntary US framework, widely adopted as enterprise baseline), and ISO/IEC 42001:2023 (international management system standard with certification path). Each specifies different obligations. All three converge on a requirement that agentic AI systems cannot meet with logging alone: evidence that oversight mechanisms were operational during deployment. A framework is an asserted safeguard — it says what must happen. What every framework leaves to the operator is proof that it did. This page compares the three factually, then maps what a pre-execution receipt chain can — and deliberately cannot — evidence for each. (The general version of that distinction — asserted, enforced, provable — is here.)
May 2026 — What's changed
→EU AI Act — high-risk enforcement December 2027. High-risk AI obligations apply from 2 December 2027, extended from 2 August 2026 by the Digital Omnibus on AI (May 2026). Agentic systems in Annex III sectors must satisfy Articles 9, 11, 12, and 14 or face penalties up to €35M.
→NIST — Critical Infrastructure Profile concept note (April 2026). NIST published a concept note for AI RMF Profile on Trustworthy AI in Critical Infrastructure, extending the core framework to energy, finance, healthcare, and transport operators. It follows the Generative AI Profile (NIST AI 600-1, July 2024). The direction is sector-specific, risk-tiered guidance — consistent with the EU AI Act's regulatory approach. The profile is in concept phase; a draft for public comment is expected later in 2026.
→ISO/IEC 42001 — Adoption accelerating. Certification bodies across the EU and UK report material upticks in ISO/IEC 42001 enquiries since Q1 2026, driven by organisations treating certification as evidence of conformity readiness ahead of the August EU AI Act deadline. ISO 42001 is not legally required, but certified organisations carry a stronger audit position.
Key takeaways
- EU AI Act is binding law — penalties up to €35M. High-risk AI deadline: 2 December 2027 (extended from 2 August 2026).
- NIST AI RMF is voluntary. No penalties, no deadline. Widely adopted as US enterprise baseline.
- ISO/IEC 42001 is voluntary with optional certification. Aligns with ISO 9001/27001 management system structures.
- All three require operational evidence of oversight — not just logs, but proof the controls ran before actions executed. This is why the deterministic vs probabilistic distinction matters at the regulatory level.
- One receipt chain produces evidence toward all three simultaneously. The evidence maps across frameworks; the obligations stay yours.
The three frameworks at a glance
Binding regulation
EU AI Act
Regulation 2024/1689 · European Union
Risk-based regulation classifying AI systems from unacceptable risk (banned) to minimal risk. High-risk AI — including agentic systems in hiring, lending, healthcare, law enforcement, and critical infrastructure — faces mandatory conformity assessment, technical documentation, CE marking, EU database registration, human oversight, and logging. High-risk obligations apply from 2 December 2027 (extended from 2 August 2026, Digital Omnibus May 2026).
Full text →
Voluntary framework
NIST AI RMF 1.0
AI Risk Management Framework · NIST, USA
Voluntary framework organising AI risk management across four functions: Govern (policies, culture), Map (context, risk identification), Measure (analysis, assessment), Manage (prioritisation, treatment). Adopted as baseline by US federal agencies and widely used in enterprise risk programmes globally. No certification mechanism; no legal deadline.
NIST AI →
Certifiable standard
ISO/IEC 42001:2023
AI Management Systems · ISO/IEC JTC 1/SC 42
International standard for AI management systems, structured like ISO 9001 (quality) and ISO 27001 (information security). Specifies requirements for establishing, implementing, maintaining, and continually improving an AI management system. Certification available via accredited bodies. Annex A includes 38 controls covering AI system design, data, operations, and incident management.
ISO standard →
Side-by-side comparison
| Property |
EU AI Act |
NIST AI RMF 1.0 |
ISO/IEC 42001 |
| Legal force |
Binding regulation (EU) |
Voluntary guidance |
Voluntary; certification available |
| Deadline |
Dec 2027 (high-risk AI) |
None |
None (certification-led) |
| Scope |
All AI placed on EU market; risk-tiered |
Any organisation using or developing AI |
Any organisation developing or using AI |
| Penalties |
Up to €35M or 7% global turnover |
None |
None (loss of certification) |
| Human oversight required |
Yes — Article 14 (mandatory) |
Yes — Manage 2.4 (recommended) |
Yes — Clause 6.1 (required for certification) |
| Logging / traceability |
Yes — Article 12 (mandatory) |
Yes — Measure 2.4 (recommended) |
Yes — Annex A.6.1.6 (control) |
| Technical documentation |
Yes — Article 11 + Annex IV (mandatory) |
Recommended (Map 5) |
Yes — Clause 8.4 (required for certification) |
| Incident reporting |
Yes — Article 73 (serious incidents) |
Recommended (Manage 4) |
Yes — Clause 10.1 |
| Conformity assessment |
Yes — third-party for most Annex III |
No |
Yes — independent certification |
| Agentic AI specific guidance |
Implicit via risk classification |
AI RMF Playbook (emerging) |
Not explicitly addressed |
How sequence enforcement maps to each framework
Sequence enforcement — evaluating each agent action against a defined policy before execution, issuing a cryptographic receipt on every authorised pass — is not specific to any one framework. It produces the class of evidence all three converge on: oversight points that are operational during deployment, logging that is tamper-evident, and proof that prerequisites were met before actions executed.
Framework requirement
Article 14: Human oversight measures — natural persons must be able to intervene or halt the system. Oversight must be effective (built into operation, not available as policy option).
What the receipt chain evidences
An enforcement gate does not satisfy Article 14 on its own — human oversight is an organisational measure, not a software feature. What the gate adds is the evidence layer oversight needs: every step requires authorisation before executing, an explicit HALT stops execution without relying on the model to comply, and each intervention point leaves a signed receipt. Whether oversight was exercised well is a question about people; whether it structurally could and did occur becomes provable.
Framework requirement
Article 12: Automatic log generation enabling post-market monitoring. Logs must be sufficient to determine the period of use, reference database used, and persons involved in verification.
What the receipt chain evidences
Every gate decision produces an Ed25519-signed receipt in tamper-evident, append-only storage, recording: step, sequence ID, decision, timestamp, payload hash, action type, and chain linkage (prev_receipt_hash). Sealed sequences are additionally copied to an independently held archive. Tampering breaks the chain detectably. Pre-action record — not post-action log.
Framework requirement
Article 11: Technical documentation demonstrating system operates as intended, including design logic, testing results, and risk management measures.
What the receipt chain evidences
The report endpoint generates a verifiable record for any sequence ID: the receipt chain with raw Ed25519 signatures and their exact signed bytes (so verification runs offline, in your own code), per-link hash-chain checks, and an independent-archive comparison for sealed sequences. It does not write your Article 11 documentation — it supplies the operational-evidence exhibits that documentation cites.
Framework requirement
Manage 2.4: Mechanisms are in place, and responsibilities assigned, to supersede, disengage, or deactivate AI systems that behave inconsistently with intended use.
What the receipt chain evidences
Gate access is controlled via API keys. Designated personnel can revoke keys, modify policy maps, or terminate sequences. The enforcement layer is separate from the model — human authority operates at the infrastructure level.
Framework requirement
Measure 2.4: The functionality and behaviour of the deployed AI system are monitored when in production.
What the receipt chain evidences
Gate statistics (total evaluations, ALLOW/DENY rates, HALT events, sequence completions) are recorded in KV and exposed via the dashboard. The receipt chain enables retrospective analysis of exactly which steps were blocked and why.
See the May 2026 updates section at the top for the NIST Critical Infrastructure Profile concept note and EU AI Act enforcement timeline.
Framework requirement
Clause 9.1: Monitoring, measurement, analysis, and evaluation — the organisation shall determine what needs to be monitored and measured and the methods for valid results.
What the receipt chain evidences
Gate decisions are the measurement points. Every ALLOW and DENY is recorded with full metadata. The receipt chain constitutes the continuous operational record that Clause 9.1 requires — produced automatically, not as a separate measurement exercise.
Framework requirement
Annex A, A.6.1.6: AI system operational logging — the organisation shall implement logging of AI system operations to an extent sufficient to enable the reconstruction of AI system behaviour.
What the receipt chain evidences
The receipt chain enables complete reconstruction of agent sequence behaviour: which steps ran, in what order, what the gate decided, at what time. The Ed25519 signatures make the reconstruction tamper-evident — any alteration is detectable.
Which framework applies to your agentic AI system?
Most organisations building agentic AI in 2026 will need to address at least two of these frameworks simultaneously:
- →EU market + high-risk sector: EU AI Act is mandatory. ISO/IEC 42001 certification provides a structured conformity path. NIST AI RMF aligns US operations.
- →US federal or regulated enterprise: NIST AI RMF is baseline. ISO/IEC 42001 provides certification. EU AI Act applies if EU market activity exists.
- →Global enterprise, any sector: ISO/IEC 42001 provides the management system foundation. EU AI Act applies to EU-facing deployments. NIST AI RMF fills voluntary gaps.
- →Agentic AI in any regulated context: All three frameworks require operational evidence that oversight mechanisms functioned during deployment. Sequence enforcement produces this evidence — one receipt chain, citable under all three.
- →Outside these jurisdictions (including Aotearoa NZ): none of the three binds directly — but local regulators ask the same underlying question: can you evidence that the safeguard ran? See the NZ health and NZ education briefs for that question on home ground.
The evidence layer is the same regardless of which framework you are working under. The receipt chain offered as Article 12 evidence is the same chain offered under ISO/IEC 42001 Annex A.6.1.6 and NIST AI RMF Measure 2.4 — build the evidence once, cite it three ways. The frameworks’ other obligations — risk management, documentation, and the oversight measures themselves — remain separate work that no receipt does for you.
Frequently asked questions
What is the difference between EU AI Act and NIST AI RMF?
The EU AI Act is binding EU law — mandatory for any AI placed on the EU market, with penalties up to €35M or 7% of global turnover and a compliance deadline of 2 December 2027 for high-risk AI (extended from 2 August 2026). NIST AI RMF 1.0 is a voluntary US framework with no penalties or legal deadlines. It organises risk management across four functions (Govern, Map, Measure, Manage) and is widely adopted as an enterprise baseline, particularly in US federal contexts.
Is ISO 42001 required for EU AI Act compliance?
No — ISO/IEC 42001 certification is not legally required for EU AI Act compliance. However, it provides a structured management system that can support the technical documentation and risk management evidence required under Articles 9 and 11. Many operators pursuing EU AI Act conformity assessment use ISO/IEC 42001 as a governance foundation alongside their notified body review.
What does EU AI Act Article 12 require for logging?
Article 12 requires that high-risk AI systems automatically generate logs enabling post-market monitoring. The logs must be sufficient to identify: the period of each use, the reference database against which output was verified, and the persons involved in the verification. In practice, logs an AI system writes about itself are weak evidence for exactly this purpose — an independent, tamper-evident record is what post-market monitoring can actually rely on.
When does the EU AI Act apply to agentic AI?
High-risk obligations apply from 2 December 2027 (extended from 2 August 2026, Digital Omnibus May 2026). Agentic AI systems operating in Annex III sectors — hiring, lending, healthcare triage, law enforcement, critical infrastructure — are classified as high-risk. These systems must satisfy Articles 9, 11, 12, and 14 by the deadline, including CE marking and EU database registration where required.
Can one approach satisfy EU AI Act, NIST, and ISO 42001 simultaneously?
One evidence layer can serve all three at once. All three frameworks ask for the same underlying capability: operational proof that oversight mechanisms functioned during deployment. Infrastructure-level sequence enforcement — gate-evaluating each agent action before execution and issuing a cryptographic receipt — produces a chain citable under EU AI Act Article 12, ISO/IEC 42001 Annex A.6.1.6, and NIST AI RMF Measure 2.4 simultaneously. What no single mechanism can do is satisfy any of these frameworks outright: risk management, technical documentation, and the oversight measures themselves remain organisational obligations. Evidence once; the obligations stay yours.
See it working
One receipt chain. Three frameworks’ evidence.
The receipt chain cited under EU AI Act Article 12 is the same chain cited under ISO/IEC 42001 Annex A.6.1.6 and NIST Measure 2.4. Run a demo sequence and generate the report yourself in 60 seconds — no signup required.