Platform Platform
System
ConceptsEnginePolicy as codeDeclarationsSafe changeGatewaysIntegrationsObservabilityAdministrationSecurityHuman reviewAudit and evidenceData retentionSecrets and data classification
Controls
Registries and documentationAuthentication and authorizationInjection detectionData redactionCode fingerprintingRole and judge checksContent classificationSpend and loop limitsBusiness rules
Solutions Solutions
By what you do
Sell into the enterpriseControl the AI you run
By industry
Financial servicesDigital assetsInsuranceHealthcareLegalUser-generated content
By discipline
AI governanceTrust and safetyRisk and compliance
Cases Cases Embedded control planeSource-code leakTrading agents over MCPLive firehoseRefund assistant
Compare Compare LiteLLMNVIDIA NeMo GuardrailsOPAROOSTAgent Governance Toolkit
Resources Resources
Guides
Enterprise review questionsPrompt injectionAgent and control layerAgent architecturesDecision system mapAI control maturity model
Standards
Standards OWASP Agent Control StandardEU AI ActPMI AI standardNIST AI RMFERC-8004
Book a demo
Resources · Standards

The runtime controls and evidence behind the NIST AI RMF.

The NIST AI Risk Management Framework organizes AI risk into four functions: Govern, Map, Measure, and Manage. Swiftward gives you the enforced controls and the audit trail behind three of them at runtime — Govern, Measure, and Manage. The fourth, Map, is organizational work that stays with you.

Voluntary, and there is no certification

The AI RMF is a voluntary framework, not a standard you certify against. Anyone selling you "NIST AI RMF certified" is selling something that does not exist.

It gives you a shared language for AI risk that an auditor, a customer and a regulator all recognize.

Manage — acting on risk in production

This is where Swiftward sits. Every AI decision runs through one policy engine that allows, blocks, redacts, or routes it. Flagged cases go to a human review queue, and you declare in advance what happens if nobody answers in time. A bad policy rolls back by naming the previous version, and a failed event is kept so you can run it again. A rule can forward a decision to your SIEM over syslog. Manage is "respond, recover, and monitor," continuously.

Measure — assessing risk with evidence in hand

Before a control goes live, you backtest it on your own history to see what it would have changed, run it in shadow on live traffic, where it decides nothing, and then A/B it on a share of that traffic. Once it is live, every decision leaves a record, and you can account for any past decision on the exact policy version that was live. Measure is "assess, analyze, and track."

Govern — the enforced backbone

Govern is the policies, roles, accountability, and oversight that hold the other functions together. Swiftward provides the enforced, technical backbone for it:

  • policy as versioned code, with approvals;
  • layered RBAC and ABAC, with duties separated the way you declare them;
  • a tamper-evident audit trail of every change: who, when, and the before and after.

What stays with you is the organizational half — the accountability structure, the risk culture, the people and committees.

Map is yours to do

Map is establishing context, categorizing your AI system, and identifying its risks and impacts on people and rights. That is analysis your team and counsel do, usually before a control is written. Swiftward produces the runtime records — the decisions, the signals, the overrides — that feed your mapping and impact assessments with facts.

Generative and agentic AI

NIST extends the framework to generative systems through a dedicated profile, NIST AI 600-1 (July 2024). There is no NIST agentic profile; the agentic profile people cite is the Cloud Security Alliance's. Swiftward controls and records the runtime behavior of AI agents and the LLM calls behind them.

Related: AI governance · testing a change before it takes effect · the other standards
Book a demo