Cross-Framework Mapping

OSFI B-13vsNIST AI Risk Management Framework (AI RMF 1.0)

See exactly how OSFI B-13 controls map to NIST AI Risk Management Framework (AI RMF 1.0). Pre-computed mappings, identified gaps, and coverage analysis.

12
Controls Mapped
0
Gaps Found
62%
Coverage

According to the TheArtOfService Compliance Knowledge Graph:

OSFI B-13 maps to NIST AI Risk Management Framework (AI RMF 1.0) with 62% coverage across 5 directly mapped controls. Analysis of 8 OSFI B-13 controls identifies 3 compliance gaps — primarily concentrated in Assurance and Audit.

Source: TheArtOfService Knowledge Graph | 8 controls analysed | 718 frameworks | 330K+ cross-framework mappings

Control Mappings

Showing 12 of 12 mapped controls across 5 domains. Sign up to explore all 330K+ mappings across 718 frameworks.

Governance and Three Lines(3 mappings)

OSFIB13-1Governance, Risk Management, and Three Lines of Defense3 targets
AIRMF-GOV-01AI Risk Management Policies
AIRMF-MAN-01AI Risk Treatment
AIRMF-MEA-01AI Performance Metrics

Cyber Security (5 NIST CSF Functions)(3 mappings)

OSFIB13-3Cyber Security: Identification, Protection, Detection, Response, Recovery3 targets
AIRMF-MAN-03AI Incident Response
NIST-AI600-MGT-1Content Provenance Implementation
NIST-AI600-MGT-4Incident Response for GAI

Third-Party Risk Management(2 mappings)

OSFIB13-4Third-Party Risk Management and Cloud2 targets
AIRMF-GOV-01AI Risk Management Policies
AIRMF-MAN-01AI Risk Treatment

Incident Reporting(2 mappings)

OSFIB13-7Incident Reporting to OSFI and Regulatory Coordination2 targets
AIRMF-MAN-03AI Incident Response
NIST-AI600-MGT-4Incident Response for GAI

Metrics and Continuous Improvement(2 mappings)

OSFIB13-8Metrics, Monitoring, Continuous Improvement, Maturity2 targets
AIRMF-MAN-03AI Incident Response
NIST-AI600-MGT-4Incident Response for GAI

Stop Paying Consultants to Read Spreadsheets

AI-powered compliance intelligence across 718 frameworks — at a fraction of consulting costs.

$0/forever

Free

  • 718 framework browser
  • Cross-framework mappings (330K+)
  • 824 compliance assessments
  • 3 AI queries & searches per day
Get Started Free
Recommended
$49/month

Professional

  • Unlimited AI Compliance Advisory
  • Unlimited full-text search
  • Framework self-assessment
  • PDF, Excel & CSV exports
Start 7-Day Free Trial →

What are the key differences between OSFI B-13 and NIST AI Risk Management Framework (AI RMF 1.0)?

OSFI B-13 has 8 controls across its framework, while NIST AI Risk Management Framework (AI RMF 1.0) covers 52 controls. Direct mapping analysis identifies 5 overlapping controls (62% coverage). The frameworks diverge most significantly in Assurance and Audit, where 1 OSFI B-13 controls have no direct NIST AI Risk Management Framework (AI RMF 1.0) equivalent.

How many controls map between OSFI B-13 and NIST AI Risk Management Framework (AI RMF 1.0)?

Of 8 total OSFI B-13 controls, 5 map directly to NIST AI Risk Management Framework (AI RMF 1.0) controls — representing 62% coverage. The remaining 3 controls represent compliance gaps requiring additional documentation or compensating controls to satisfy both frameworks simultaneously.

What are the compliance gaps when mapping OSFI B-13 to NIST AI Risk Management Framework (AI RMF 1.0)?

3 OSFI B-13 controls have no direct equivalent in NIST AI Risk Management Framework (AI RMF 1.0). The highest concentration of gaps is in Assurance and Audit with 1 unmapped controls. These gaps represent areas where additional controls, policies, or documentation must be created to achieve compliance with both frameworks.

Which control domains have the most gaps between OSFI B-13 and NIST AI Risk Management Framework (AI RMF 1.0)?

The domain with the highest gap count is Assurance and Audit (1 gaps). Export the full domain-by-domain gap breakdown via the Professional tier to generate a prioritised remediation roadmap.

This platform provides educational compliance tools, not legal, regulatory, or professional compliance advice. Cross-framework mappings are AI-assisted interpretations and do not reproduce or replace official standards. Framework names and trademarks belong to their respective owners. Consult qualified professionals for your specific compliance requirements. See our Terms of Service.