Cross-Framework Mapping

ISO/IEC 27003:2017vsOwn Risk and Solvency Assessment (ORSA) - NAIC Model Act

See exactly how ISO/IEC 27003:2017 controls map to Own Risk and Solvency Assessment (ORSA) - NAIC Model Act. Pre-computed mappings, identified gaps, and coverage analysis.

6
Controls Mapped
66
Gaps Found
6%
Coverage

According to the TheArtOfService Compliance Knowledge Graph:

ISO/IEC 27003:2017 maps to Own Risk and Solvency Assessment (ORSA) - NAIC Model Act with 6% coverage across 4 directly mapped controls. Analysis of 72 ISO/IEC 27003:2017 controls identifies 68 compliance gaps — primarily concentrated in Support (Clause 7).

Source: TheArtOfService Knowledge Graph | 72 controls analysed | 706 frameworks | 324K+ cross-framework mappings

Control Mappings

Showing 6 of 6 mapped controls across 2 domains. Sign up to explore all 324K+ mappings across 706 frameworks.

Operation (Clause 8)(4 mappings)

AS9100D-8.1Operational Planning and Control
ORSA-S1ORSA Manual Section 1: Description of Insurer's Risk Management Framework
ISO27003-8.2Information Security Risk Assessment2 targets
ORSA-S1ORSA Manual Section 1: Description of Insurer's Risk Management Framework
ORSA-S2ORSA Manual Section 2: Insurer's Assessment of Risk Exposure
ISO27003-8.3Information Security Risk Treatment
ORSA-S1ORSA Manual Section 1: Description of Insurer's Risk Management Framework

Planning (Clause 6)(2 mappings)

ISO27003-6.1Actions to Address Risks and Opportunities2 targets
ORSA-S1ORSA Manual Section 1: Description of Insurer's Risk Management Framework
ORSA-S2ORSA Manual Section 2: Insurer's Assessment of Risk Exposure

Related Comparisons

Other ISO/IEC 27003:2017 comparisons

Other Own Risk and Solvency Assessment (ORSA) - NAIC Model Act comparisons

Stop Paying Consultants to Read Spreadsheets

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

$0/forever

Free

  • 706 framework browser
  • Cross-framework mappings (324K+)
  • 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 ISO/IEC 27003:2017 and Own Risk and Solvency Assessment (ORSA) - NAIC Model Act?

ISO/IEC 27003:2017 has 72 controls across its framework, while Own Risk and Solvency Assessment (ORSA) - NAIC Model Act covers 4 controls. Direct mapping analysis identifies 4 overlapping controls (6% coverage). The frameworks diverge most significantly in Support (Clause 7), where 9 ISO/IEC 27003:2017 controls have no direct Own Risk and Solvency Assessment (ORSA) - NAIC Model Act equivalent.

How many controls map between ISO/IEC 27003:2017 and Own Risk and Solvency Assessment (ORSA) - NAIC Model Act?

Of 72 total ISO/IEC 27003:2017 controls, 4 map directly to Own Risk and Solvency Assessment (ORSA) - NAIC Model Act controls — representing 6% coverage. The remaining 68 controls represent compliance gaps requiring additional documentation or compensating controls to satisfy both frameworks simultaneously.

What are the compliance gaps when mapping ISO/IEC 27003:2017 to Own Risk and Solvency Assessment (ORSA) - NAIC Model Act?

68 ISO/IEC 27003:2017 controls have no direct equivalent in Own Risk and Solvency Assessment (ORSA) - NAIC Model Act. The highest concentration of gaps is in Support (Clause 7) with 9 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 ISO/IEC 27003:2017 and Own Risk and Solvency Assessment (ORSA) - NAIC Model Act?

The domain with the highest gap count is Support (Clause 7) (9 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.