Cross-Framework Mapping

HKMA SPMvsISO 22320:2018

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

16
Controls Mapped
30
Gaps Found
17%
Coverage

According to the TheArtOfService Compliance Knowledge Graph:

HKMA SPM maps to ISO 22320:2018 with 17% coverage across 8 directly mapped controls. Analysis of 46 HKMA SPM controls identifies 38 compliance gaps — primarily concentrated in HKMA SPM: Cybersecurity Controls.

Source: TheArtOfService Knowledge Graph | 46 controls analysed | 726 frameworks | 455K+ cross-framework mappings

Control Mappings

Showing 16 of 16 mapped controls across 4 domains. Sign up to explore all 455K+ mappings across 726 frameworks.

HKMA SPM: Information Security Governance(3 mappings)

HKMA-05Roles and responsibilities definition3 targets
ISO-22320-5.1General process requirements
ISO-22320-5.3Incident management structure (command)
ISO-22320-5.4Roles and responsibilities

HKMA SPM: Operational Resilience(1 mappings)

HKMA-12Disaster recovery procedures
ISO-22320-5.2Incident management process

HKMA SPM: Third-Party Risk Management(3 mappings)

HKMA-16Due diligence and onboarding
ISO-22320-4.3Risk-based approach
HKMA-17Contractual security requirements
ISO-22320-4.3Risk-based approach
HKMA-18Ongoing monitoring and assessment
ISO-22320-4.3Risk-based approach

HKMA SPM: Incident Management & Reporting(9 mappings)

HKMA-21Incident detection and classification3 targets
ISO-22320-5.2Incident management process
ISO-22320-BAnnex B: Incident management plan structure
ISO-22320-CAnnex C: Incident management task examples
HKMA-23Regulatory reporting requirements3 targets
ISO-22320-5.2Incident management process
ISO-22320-BAnnex B: Incident management plan structure
ISO-22320-CAnnex C: Incident management task examples
HKMA-25Post-incident review and improvement3 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 726 frameworks — at a fraction of consulting costs.

$0/forever

Free

  • 726 framework browser
  • Cross-framework mappings (455K+)
  • 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 SPM and ISO 22320:2018?

HKMA SPM has 46 controls across its framework, while ISO 22320:2018 covers 37 controls. Direct mapping analysis identifies 8 overlapping controls (17% coverage). The frameworks diverge most significantly in HKMA SPM: Cybersecurity Controls, where 5 HKMA SPM controls have no direct ISO 22320:2018 equivalent.

How many controls map between HKMA SPM and ISO 22320:2018?

Of 46 total HKMA SPM controls, 8 map directly to ISO 22320:2018 controls — representing 17% coverage. The remaining 38 controls represent compliance gaps requiring additional documentation or compensating controls to satisfy both frameworks simultaneously.

What are the compliance gaps when mapping HKMA SPM to ISO 22320:2018?

38 HKMA SPM controls have no direct equivalent in ISO 22320:2018. The highest concentration of gaps is in HKMA SPM: Cybersecurity Controls 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 SPM and ISO 22320:2018?

The domain with the highest gap count is HKMA SPM: Cybersecurity Controls (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.