Cross-Framework Mapping

OSFI B-13vsISO 22320:2018

See exactly how OSFI B-13 controls map to ISO 22320:2018. Pre-computed mappings, identified gaps, and coverage analysis.

14
Controls Mapped
0
Gaps Found
62%
Coverage

According to the TheArtOfService Compliance Knowledge Graph:

OSFI B-13 maps to ISO 22320:2018 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 14 of 14 mapped controls across 5 domains. Sign up to explore all 330K+ mappings across 718 frameworks.

Governance and Three Lines(4 mappings)

OSFIB13-1Governance, Risk Management, and Three Lines of Defense4 targets
ISO-22320-4.3Risk-based approach
ISO-22320-5.1General process requirements
ISO-22320-5.3Incident management structure (command)
ISO-22320-5.4Roles and responsibilities

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

OSFIB13-3Cyber Security: Identification, Protection, Detection, Response, Recovery3 targets
ISO-22320-5.2Incident management process
ISO-22320-BAnnex B: Incident management plan structure
ISO-22320-CAnnex C: Incident management task examples

Third-Party Risk Management(1 mappings)

OSFIB13-4Third-Party Risk Management and Cloud
ISO-22320-4.3Risk-based approach

Incident Reporting(3 mappings)

OSFIB13-7Incident Reporting to OSFI and Regulatory Coordination3 targets
ISO-22320-5.2Incident management process
ISO-22320-BAnnex B: Incident management plan structure
ISO-22320-CAnnex C: Incident management task examples

Metrics and Continuous Improvement(3 mappings)

OSFIB13-8Metrics, Monitoring, Continuous Improvement, Maturity3 targets
ISO-22320-5.2Incident management process
ISO-22320-BAnnex B: Incident management plan structure
ISO-22320-CAnnex C: Incident management task examples

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 ISO 22320:2018?

OSFI B-13 has 8 controls across its framework, while ISO 22320:2018 covers 37 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 ISO 22320:2018 equivalent.

How many controls map between OSFI B-13 and ISO 22320:2018?

Of 8 total OSFI B-13 controls, 5 map directly to ISO 22320:2018 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 ISO 22320:2018?

3 OSFI B-13 controls have no direct equivalent in ISO 22320:2018. 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 ISO 22320:2018?

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.