Context & tools
The material the work starts from: the sources, documents and tools a team already relies on.
TL;DR: AI governance in 2026 is built around NIST AI RMF (US, voluntary) and the EU AI Act (EU, binding), with ISO/IEC 42001 as the international certifiable standard. A credible programme has five named roles, five stages of maturity, and runs on three tooling layers; gateway, eval, and GRC overlay.
No serious 2026 AI governance programme is built from scratch. The mature pattern uses NIST AI RMF as the control anchor, layers EU AI Act for binding obligations, adds ISO 42001 for international certifiable evidence, and overlays sector-specific guidance where it applies.
Voluntary US framework structured around four functions: Govern, Map, Measure, Manage. AI RMF is the most-cited reference in 2026 corporate AI governance programmes. Anchors against the Companion AI RMF Generative AI Profile for LLM-specific risk.
Coverage: US-led, voluntary, broadly adopted by Fortune 1000
Deep dive →EU regulation that risk-tiers AI systems (unacceptable / high / limited / minimal) with binding obligations on high-risk systems. Articles 10-15 cover data governance, technical documentation, transparency, human oversight, accuracy + robustness + cybersecurity. Phased enforcement through 2027.
Coverage: Binding for any AI placed on the EU market. global reach
Deep dive →International standard for AI Management Systems (AIMS), first published 2023, adoption accelerating through 2026. Certifiable, audit-friendly, recognised as evidence of conformity under multiple regulators.
Coverage: International, certifiable
NIST companion profile for generative AI specifically: covers prompt injection, harmful content generation, intellectual property, and confabulation risks not addressed in the base AI RMF.
Coverage: US-led, focused on generative AI
Deep dive →HHS guidance on PHI handling when AI systems process it. Business Associate Agreements with model providers became standard practice in 2025. Zero Data Retention contracts are now the default expectation.
Coverage: US healthcare
Deep dive →Banking regulators (OCC, FRB), the SEC, the FDA, and DoD CMMC programmes have all issued AI-specific guidance through 2024-26. Most reference NIST AI RMF as the underlying control framework.
Coverage: US financial services, healthcare, defence
Govern, Map, Measure, Manage. The structure that almost every mature 2026 AI governance programme inherits, regardless of which other frameworks they overlay.
Org-wide AI policy, roles + responsibilities, risk appetite, decision rights, training, supplier oversight. The "who decides" layer.
Inventory every AI system in the org; what it does, what data it touches, who depends on it, what its risk tier is. Without an inventory you cannot govern.
Quantitative evaluation, and accuracy, bias, robustness, security, drift, cost. Measurement runs continuously, not just at procurement.
Risk treatment, incident response, change management, retirement. Treat AI like any other regulated information system.
Chief Risk Officer or delegate. Owns the AI risk register, board-level reporting, regulator engagement.
Operational owner of the governance programme. Maintains the inventory, runs the procurement gate, owns the policy library.
Owns prompt-injection defence, model jailbreak posture, training-data poisoning detection, supply chain integrity.
Owns PII handling, ZDR contracts with providers, cross-border transfer assessments (GDPR / SCCs), and data subject rights against AI systems.
Cross-functional review for high-risk use cases. Empowered to block deployments. Includes legal, risk, product, and external advisors.
Per-system accountable engineer. Maintains the model card, runs the eval harness, signs off on deployments and version bumps.
| Stage | Weeks | Deliverable |
|---|---|---|
| Stage 1. Inventory | 1-3 | Complete AI inventory with risk-tier labels for every system. Procurement gate established. |
| Stage 2, Policy + roles | 3-6 | AI policy library, RACI for AI decisions, board reporting cadence, training rolled out. |
| Stage 3: Controls | 6-12 | Eval harness, gateway-enforced policy (ZDR, model allowlist, per-team budgets), audit logging. |
| Stage 4; Conformity | 12-24 | Mapped NIST AI RMF / EU AI Act / ISO 42001 controls. Auditor-ready evidence binder. |
| Stage 5, and Continuous | Ongoing | Quarterly board reporting, automated drift + cost + bias monitoring, annual external audit. |
Layer 1. Gateway / policy plane. Enforces ZDR, model allowlists, per-team budgets, audit logging, and prompt injection / PII redaction at request time. Swfte, Portkey, TrueFoundry, LiteLLM are the major options. The gateway is where the governance programme actually lands in production traffic.
Layer 2, Eval + monitoring. Continuous quality, bias, robustness, and cost monitoring with a golden-dataset regression UI. Swfte ships this in-platform; LangSmith, Langfuse, Arize, and Galileo are standalone alternatives. Required evidence for any conformity claim.
Layer 3: GRC overlay. Policy library, mapping to frameworks, conformity reporting, supplier risk assessment. Credo AI, Holistic AI, Trustible, Saidot are the dedicated AI-GRC products. Often integrated with the existing enterprise GRC stack (ServiceNow GRC, OneTrust) rather than purchased standalone.
AI governance is the set of policies, roles, controls, and evidence-gathering that ensures an organisation's AI systems behave the way the organisation intends. within its risk appetite, in compliance with regulation, and aligned with its ethical principles. In 2026 it is built around NIST AI RMF (US, voluntary) and the EU AI Act (EU, binding), with ISO/IEC 42001 as the international certifiable standard.
Three reasons converged in 2024-26. Regulation became binding, the EU AI Act enforces from 2026 onwards with phased deadlines through 2027. AI systems became high-stakes: orgs are using LLMs for hiring, lending, medical triage, and customer-facing automation, where failures hit real people. Procurement bars rose; Fortune 500 buyers now require auditable AI governance from suppliers as a precondition of contracts.
AI ethics is the principle layer, and fairness, transparency, accountability, non-maleficence. AI governance is the operational layer that turns those principles into policies, controls, and evidence. Ethics committees set policy; governance programmes enforce it day to day.
Five stages. (1) Inventory every AI system in the org, risk-tier each one. (2) Stand up policy + roles + procurement gate. (3) Implement controls. eval harness, gateway-enforced ZDR, model allowlist, per-team budgets, audit logging. (4) Map controls to NIST AI RMF + EU AI Act + ISO 42001 for conformity. (5) Operate continuously with quarterly board reporting and annual external audit. Typical time from kickoff to a defensible programme: 12-24 months.
NIST AI Risk Management Framework (AI RMF 1.0 + Generative AI Profile) for the US-led control set. The EU AI Act for legal binding obligations on EU-market AI. ISO/IEC 42001 for international certifiable AI management. Sector-specific overlays from SEC, OCC, FDA, and DoD CMMC where relevant. Most mature programmes use NIST AI RMF as the anchor and overlay the others.
AI governance compliance is the demonstrable adherence of an AI governance programme to one or more external requirements, the EU AI Act for legal obligations, NIST AI RMF for voluntary alignment, ISO/IEC 42001 for certifiable evidence, plus sector regulators (SEC, OCC, FDA, HIPAA / OCR). Most large organisations now maintain an AI conformity binder with mapped controls and evidence per framework.
In 2026, the common pattern is a Chief AI Officer or VP of AI Governance reporting to a CRO, CISO, or General Counsel. Operationally the programme has at least 5 named roles: AI risk officer, AI governance lead, AI security lead, AI privacy lead, and an AI ethics committee. Each AI system also has a named model owner who signs off on deployments.
Below $500M revenue, a credible programme costs $300k-$1.5M/year all-in (people, tooling, audit). Above $5B revenue, $5M-$25M/year is typical, plus the operational cost of running the controls (gateway, eval, audit) which usually rolls into engineering spend. Most organisations under-invest by 2-4× in year 1 and end up rebuilding after a near-miss or regulator inquiry.
Three layers. (1) Gateway / policy plane: Swfte, Portkey, TrueFoundry enforce model allowlist, audit log, per-team budgets at request time. (2) Eval / monitoring; Swfte, LangSmith, Langfuse, Arize, Galileo run continuous quality + bias + drift monitoring. (3) GRC overlay. Credo AI, Holistic AI, Trustible, Saidot for policy library, mapping to frameworks, and conformity reporting.
Done badly, yes. Done well, it accelerates. because every team is operating against the same policy, the same eval harness, the same gateway, and the same budget envelope. The friction is upstream in the procurement gate; downstream the team ships faster because controls are baked in rather than retrofitted.
The EU AI Act entered into force 2024. Prohibited AI practices became enforceable 2025. General-purpose AI obligations began phased rollout 2025-26. High-risk AI obligations fully enforceable from 2027. Most non-EU organisations targeting EU customers are aiming for full conformity by mid-2026 to absorb the transition.
Swfte enforces model allowlists, per-team budgets, and audit logging at the gateway; the operational layer your governance programme runs on.
Free tier · OpenAI-compatible API · On-prem available
Working record / AI Governance
Walk through the working record for a proposed internal assistant. Illustrative authored example · snapshot · 7 September 2026. Supplied catalogue copy, not verified performance evidence; this preview does not execute a workflow.
A spatial explanation of the workflow.
Select a stage or scroll to explore.
The material the work starts from: the sources, documents and tools a team already relies on.
The reasoning step. A model reads the context that was gathered and proposes something a person can act on.
The limits set before the work runs — what is in scope, what is refused, and who is asked when it is unclear.
The sequence itself: the order of steps, the handoffs between them, and where a person is required.
How the result reaches the people who use it, and the conditions under which it is allowed to run.
What is kept afterwards so a reviewer can retrace the decision: inputs, choices, and the person accountable.
CONCEPTUAL WORKFLOW MODEL — NOT A DEPICTION OF SYSTEM ARCHITECTURE
Illustrative authored example · snapshot · 7 September 2026. Capabilities and figures require confirmation.