Identity collapses
The receiving system sees a privileged machine account, but loses the person whose request started the chain.
Governance questionCan every action still be attributed to an originating person and a named agent?

Most AI governance shipped in the last two years is a deck and a policy. Neither survives an enterprise security review, an ISO audit, or an EU supervisory authority asking for evidence. We build the operating system instead.
The Shape of the NIST AI RMF
NIST Functions
Govern · Map · Measure · Manage
Categories
Across the AI lifecycle
Subcategories
Each with an audit artifact
GenAI Risks
NIST AI 600-1 profile
Last reviewed August 2026. Regulatory dates change. This page is re-verified quarterly.
Frameworks
They do not overlap perfectly. They overlap meaningfully. Run them as one program.
Published by the US National Institute of Standards and Technology on January 26, 2023. Voluntary, non-prescriptive, and built around 4 functions, 19 categories, and roughly 72 subcategories. The framework tells you what to achieve. It deliberately does not tell you how. That gap is the work, and that gap is also why it has become the de facto standard for US enterprise procurement, federal-adjacent buyers, and any vendor questionnaire that mentions AI.
One thing to plan around: AI RMF 1.0 is currently under revision as part of the White House AI Action Plan. The four-function structure is stable and the subcategories are the working unit, so a program built on them will survive the revision. Sector profiles are where the near-term movement is. NIST released a concept note in April 2026 for an AI RMF Profile on Trustworthy AI in Critical Infrastructure, and a Cyber AI Profile is in draft.
Who needs it
Any company selling to US enterprise or federal-adjacent buyers. Any company whose security questionnaire from a customer references AI governance, model lineage, or automated decision-making. Treat the voluntary label as misleading: federal procurement, ISO 42001 audits, and enterprise vendor reviews all anchor to it.
Common gap
Treating Measure as a model performance exercise instead of a risk quantification exercise. The Playbook's suggested actions are the fastest route to closing this gap.
Think of it as a continuous operating loop, not a linear sequence. GOVERN is the permanent foundation. It is always on and infused through everything. MAP, MEASURE, and MANAGE cycle continuously throughout the AI system's lifecycle.
Culture, policies, accountability, oversight. The only function that spans the entire organization at all times. Enables the other three to be repeatable.
Scope and context. Identify which AI systems exist, who they affect, and what the risk landscape looks like before measuring anything.
Quantify and track. Use testing, evaluation, verification, and validation (TEVV) to assess identified risks with rigor. Not intuition.
Turn non-determinism into evidence. That's what TEVV is for.
Respond. Allocate resources to prioritized risks. Mitigate, transfer, avoid, or accept risk. Build incident response. Monitor continuously.
The key insight for your advisory practice: The framework is intentionally non-prescriptive. It tells organizations WHAT outcomes to achieve but rarely says HOW in concrete terms. That gap is exactly where a Sophizo engagement sits. We provide the implementation that translates NIST subcategories into board-ready procedures, controls, and KPIs.
Risk Lens
The 12 GenAI risks tell you what can go wrong. The 7 characteristics tell you what good looks like. Both anchor every Measure and Manage decision.
NIST AI 600-1 · Generative AI Profile · July 2024
Top three for B2B operators
Confidently stated, factually wrong output. The number one risk for enterprise copilots and customer-facing deployments. Requires TEVV baselines, confidence flagging, and human review gates.
Third-party models, APIs, datasets, and infrastructure introduce risk the deployer does not fully control. The most systemic and underappreciated category. Invisible until failure.
Workflow design risk, not a model risk. Automation bias, over-automation, anthropomorphism. No model-level control fixes this. Human-in-the-loop checkpoints and override mechanisms do. Most of your stack should stay deterministic software. A smaller layer is model judgment. A smaller layer still is human approval. The failure mode isn't using AI, it's not knowing which of the three a given decision belongs to.
All 12 categories
CBRN Information
Confabulation
Dangerous, Violent, or Hateful Content
Data Privacy
Environmental Impacts
Harmful Bias & Homogenization
Human-AI Configuration
Information Integrity
Information Security
Intellectual Property
Obscene, Degrading, or Abusive Content
Value Chain & Component Integration
NIST AI RMF, ISO/IEC 42001, and the EU AI Act are not three competing programs. They are one operating discipline with three compliance extensions. The right sequencing is the difference between framework fatigue and a program that compounds.
The four-function structure is the most flexible. It maps cleanly onto both EU AI Act obligations and ISO 42001 requirements without framework-specific constraints. This is your operating discipline.
The certifiable wrapper makes the program auditable and durable for enterprise sales and procurement. If you already hold ISO 27001, the shared Annex SL structure makes 42001 a meaningfully smaller lift.
Run every in-scope system through the Act's risk-tier categorization. The output tells you which systems require full high-risk compliance treatment. The Digital Omnibus moved high-risk obligations to December 2, 2027 for Annex III systems and August 2, 2028 for Annex I. The extra runway is real. The triage is not optional, because classification is what tells you which clock you are on.
Twelve GenAI risk categories. 200+ suggested actions. All mapped back to the four base functions. Treat it as a modular extension, not a separate program.
The framing that lands with CFOs and General Counsel: one foundational governance program with three compliance extensions. Not three separate programs competing for the same team bandwidth and the same budget line.
Agent-to-agent governance
Most governance evaluates one agent at a time: its instructions, tools, data, and permitted actions. When one agent delegates to another, authority crosses a new boundary. At machine speed, origin can disappear, access can widen, and work can travel onward without another approval.
The agent is not the only unit of risk. The handoff is too.
The receiving system sees a privileged machine account, but loses the person whose request started the chain.
Governance questionCan every action still be attributed to an originating person and a named agent?
A downstream agent inherits more access than its immediate task requires because authority was forwarded instead of narrowed.
Governance questionDoes authority become more limited at every handoff?
One compromised agent can reach other agents and systems through relationships the organization already trusts.
Governance questionCan delegation stop before a local failure becomes a system-wide one?
Seven checks at the boundary
A registration check is not enough. These questions belong at the moment an agent delegates work, calls a tool, or asks another system to act.
OriginWhich person or organization authorized the work?
AttributionWhich agent performed each action?
NarrowingDid permission become more limited at every handoff?
Human ceilingCould an agent do anything the originating person could not?
LifetimeIs access scoped to this task and short-lived?
Runtime checkWas authority checked when the action happened?
EvidenceCan the chain be stopped and reconstructed end to end?
Current State
The EU AI Act timeline changed in July 2026. Half the obligations moved. Half did not. Guides written before June are actively misleading.
Regulation (EU) 2026/1744, the Digital Omnibus on AI, was published in the Official Journal on July 24, 2026 and entered into force on July 27, 2026, six days before the original August 2 high-risk deadline. It deferred the heaviest compliance regime and left the most broadly applicable obligations exactly where they were. If your compliance calendar was built before June 2026, parts of it are wrong in both directions.
The delay is real and it is narrow. Article 50 reaches every customer-facing chatbot you run. That obligation is live today and most teams filed it under 2027.
United States
For a US B2B SaaS company, the binding obligations are state, not federal and not European.
More than 2,000 AI-related bills have been introduced across the states. A December 2025 executive order directed federal agencies to pursue preemption of state AI laws, and a Department of Justice AI Litigation Task Force was stood up in January 2026 to challenge them. The White House followed with a National Policy Framework for Artificial Intelligence on March 20, 2026, a set of non-binding legislative recommendations to Congress. No federal statute or court has preempted any state AI law. Until one does, the state patchwork is the operative rule set, and planning against its disappearance is speculation rather than strategy.
Intent-based statute. Bans deliberately developing or deploying AI to manipulate, unlawfully discriminate, or infringe rights. The broad high-risk impact assessment regime was cut from the final bill. Enforced by the Texas Attorney General.
Organizations substantially complying with the NIST AI RMF gain safe-harbor protection against enforcement. Documented RMF alignment is now a legal defense in Texas, not just good practice.
The 2024 Colorado AI Act (SB 24-205) was repealed and reenacted as SB 26-189, signed May 14, 2026, before it ever took effect. The replacement is a narrower automated decision-making transparency regime centered on consumer notices, adverse-outcome explanations, and human review rights. Substantive obligations start January 1, 2027. Note what did not survive: the original framework safe harbor for NIST AI RMF or ISO 42001 compliance is gone.
SB 53, the Transparency in Frontier Artificial Intelligence Act, targets developers training models above a compute threshold. AB 2013 requires training-data disclosure and applies far more broadly, to any generative AI developer making a system available in California. SB 942 adds content-provenance obligations for large-scale generative systems. CPPA automated decision-making regulations phase in through 2027 and beyond.
Illinois HB 3773 amended the Illinois Human Rights Act to cover AI in employment decisions, effective January 1, 2026. New York City Local Law 144 has required bias audits for automated employment decision tools since 2023. If your product touches hiring, promotion, or performance evaluation, you are already in scope somewhere.
The practical answer is not fifty compliance programs. It is one NIST-anchored operating discipline with jurisdictional overlays, re-checked quarterly.
Free Strategy Brief
A board-ready brief on operationalizing NIST AI RMF without hiring a binder writer.
How to translate four functions, 19 categories, and 12 GenAI risks into a 90-day execution plan your CFO and General Counsel will sign off on. Read it before your next AI risk committee meeting.
What is inside:
Tell us where to send it. Opens instantly in a new tab.
Operating System
If you can't show them what the agent did, they will never trust it. An audit trail isn't a compliance checkbox, it's the artifact that earns trust.
Build once. Maintain as discipline. Security, ISO, EU supervisory authority, LP, board: all read from the same evidence.
Every AI system in production, shadow AI included. Risk tier, owner, review cadence. Refreshed quarterly.
Two pages. What may be used, what data is off-limits, what review is required, who escalates. Two pages is the adoption ceiling.
One-page checklist every new AI vendor signs. Data, lineage, certifications, termination return. Kills shadow procurement.
Standing fifteen-minute slot. Inventory delta, incidents, top use cases. Builds board literacy without burning the agenda.
What happens when an AI system causes harm, leaks data, or fails oversight. Owner, classification, comms, regulator triggers. Tested in a tabletop.
Every autonomous decision, timestamped and traceable: what the agent saw, what it decided, and why. The record your security review, your board, and your own team need before they'll trust the output. This is no longer a nice-to-have. Singapore's IMDA published a Model AI Governance Framework for Agentic AI in January 2026, the first comprehensive governance framework built for autonomous agents, and it requires each agent to carry a verifiable digital identity and an audit trail of which agent acted under whose authorization.
Agentic Layer
No single standard governs autonomous agents yet. Four converging references now do most of the work, and none of them existed when your governance policy was written.
NIST AI Agent Standards Initiative. Launched by the Center for AI Standards and Innovation on February 17, 2026. Organized around industry-led standards, open-source protocol development, and security and identity research. The accompanying NCCoE concept paper covers agent authentication, authorization, auditing, non-repudiation, and prompt injection mitigation.
OWASP Top 10 for Agentic Applications 2026. Published December 10, 2025. The most operationally specific reference available, because it names attack mechanics rather than risk categories: goal hijacking, tool misuse, identity and privilege abuse, memory poisoning, cascading multi-agent failure.
Singapore IMDA Model AI Governance Framework for Agentic AI. January 2026. Verifiable agent identity and authorization audit trail as baseline requirements.
Berkeley CLTC Agentic AI Risk-Management Standards Profile. February 2026. The most comprehensive agentic risk taxonomy currently available, structured as an extension of the NIST AI RMF across Govern, Map, Measure, and Manage.
EU AI Act Article 14 on human oversight and Article 15 on accuracy, robustness, and cybersecurity apply directly to autonomous agents in high-risk domains. The obligation lands on the deployer, not the model vendor.
By Industry
The framework stack flexes by sector. HIPAA in healthcare. GLBA and FCRA in financial services. FERPA in education. Bar guidance in legal. C2PA for media. The operating discipline holds across all of them. See sector deep-dives
Engage
Three shapes. Different commitment. Same operating discipline.
Every engagement moves the same way: controlled environment, then shadow mode, then increasing autonomy, then production. Risk goes down at every step, which is why boards approve it.
2 to 4 weeks
Scored gap assessment across the three frameworks. Named bottleneck, prioritized roadmap, cost-to-green estimate.
Best for: Teams that need a baseline before they invest.
Scope a diagnosticMost chosen
90 days
The full six-artifact operating system. Inventory, policy, vendor framework, board cadence, incident runbook, agent action log.
Best for: Teams preparing for enterprise sales, an ISO audit, or a board review.
See the Governance AcceleratorOngoing retainer
Fractional AI governance ownership. Quarterly board reporting, vendor reviews, incident response, regulator-readiness.
Best for: Teams without the internal capacity to run governance as a discipline.
Talk to usDeeper Reading
Governance that people use
Every use case needs a named business owner, a technical operator, and a clear moment when a human can stop or override the work.
Drafting and retrieval. A person reviews before use; logging and source visibility are the default.
Prioritization and analysis. The system proposes; a named decision-maker accepts, changes, or rejects.
Customer or operational actions proceed only through explicit approval, with a reversible path.
High-consequence decisions require formal assessment, heightened controls, and executive sign-off before deployment.
The tier can change as evidence changes. Trust is reviewed, documented, and earned over time.
Book a 30-minute scoping call. We tell you which framework bites first, what 90 days looks like for your stack, and where security and privacy already do half the work.
Schedule Free CallGuidance, not legal advice. EU AI Act, NIST AI RMF, and ISO/IEC 42001 evolve. Regulatory timelines changed materially in 2026 and continue to move. ISO 42001 certification is issued by accredited certification bodies, not by Sophizo. Engage qualified legal counsel and a certification body for jurisdiction-specific work.
Keep exploring the frameworks and engagements connected to this topic.
Classify your B2B SaaS system correctly.
The risk framework scaled to lean teams.
A working register you can adopt today.
Where board-grade programs stand this year.
Clinical and commercial risk in regulated AI.
Compressed board-grade governance buildout.
Further reading