Cross-Framework Mapping

HKMA Cyber Resilience Assessment Framework (C-RAF)vsECSS Software Engineering Standards

See exactly how HKMA Cyber Resilience Assessment Framework (C-RAF) controls map to ECSS Software Engineering Standards. Pre-computed mappings, identified gaps, and coverage analysis.

8
Controls Mapped
16
Gaps Found
12%
Coverage

According to the TheArtOfService Compliance Knowledge Graph:

HKMA Cyber Resilience Assessment Framework (C-RAF) maps to ECSS Software Engineering Standards with 12% coverage across 3 directly mapped controls. Analysis of 24 HKMA Cyber Resilience Assessment Framework (C-RAF) controls identifies 21 compliance gaps — primarily concentrated in Domain 3: Protection.

Source: TheArtOfService Knowledge Graph | 24 controls analysed | 693 frameworks | 819K+ cross-framework mappings

Control Mappings

Showing 8 of 8 mapped controls across 2 domains. Sign up to explore all 819K+ mappings across 693 frameworks.

Domain 1: Governance(6 mappings)

CRAF-1.2Cyber Risk Strategy3 targets
ECSS-5.2.1System Requirements Analysis
ECSS-5.3.3Review Milestones
ECSS-5.4.1Software Requirements Specification
CRAF-1.4Cyber Risk Roles and Responsibilities3 targets
ECSS-5.2.1System Requirements Analysis
ECSS-5.3.3Review Milestones
ECSS-5.4.1Software Requirements Specification

Domain 3: Protection(2 mappings)

CRAF-3.3Infrastructure Security2 targets
ECSS-5.3.2Software Configuration Management
ECSS-E-40C-5.3.2Configuration Management

Related Comparisons

Other HKMA Cyber Resilience Assessment Framework (C-RAF) comparisons

Other ECSS Software Engineering Standards comparisons

Stop Paying Consultants to Read Spreadsheets

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

$0/forever

Free

  • 693 framework browser
  • Cross-framework mappings (819K+)
  • 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 HKMA Cyber Resilience Assessment Framework (C-RAF) and ECSS Software Engineering Standards?

HKMA Cyber Resilience Assessment Framework (C-RAF) has 24 controls across its framework, while ECSS Software Engineering Standards covers 33 controls. Direct mapping analysis identifies 3 overlapping controls (12% coverage). The frameworks diverge most significantly in Domain 3: Protection, where 5 HKMA Cyber Resilience Assessment Framework (C-RAF) controls have no direct ECSS Software Engineering Standards equivalent.

How many controls map between HKMA Cyber Resilience Assessment Framework (C-RAF) and ECSS Software Engineering Standards?

Of 24 total HKMA Cyber Resilience Assessment Framework (C-RAF) controls, 3 map directly to ECSS Software Engineering Standards controls — representing 12% coverage. The remaining 21 controls represent compliance gaps requiring additional documentation or compensating controls to satisfy both frameworks simultaneously.

What are the compliance gaps when mapping HKMA Cyber Resilience Assessment Framework (C-RAF) to ECSS Software Engineering Standards?

21 HKMA Cyber Resilience Assessment Framework (C-RAF) controls have no direct equivalent in ECSS Software Engineering Standards. The highest concentration of gaps is in Domain 3: Protection with 5 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 HKMA Cyber Resilience Assessment Framework (C-RAF) and ECSS Software Engineering Standards?

The domain with the highest gap count is Domain 3: Protection (5 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.