Cross-Framework Mapping

API 1164vsISO 22313:2020 — Guidance on Business Continuity Management Systems

See exactly how API 1164 controls map to ISO 22313:2020 — Guidance on Business Continuity Management Systems. Pre-computed mappings, identified gaps, and coverage analysis.

8
Controls Mapped
16
Gaps Found
21%
Coverage

According to the TheArtOfService Compliance Knowledge Graph:

API 1164 maps to ISO 22313:2020 — Guidance on Business Continuity Management Systems with 21% coverage across 5 directly mapped controls. Analysis of 24 API 1164 controls identifies 19 compliance gaps — primarily concentrated in API 1164: Incident Response & Recovery.

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.

API 1164: Access Management(1 mappings)

API1164-07Personnel risk assessment
ISO-22313-8.2Business impact analysis and risk assessment

API 1164: Supply Chain & Configuration(7 mappings)

API1164-21Supply chain risk management for critical components2 targets
ISO-41001-8.4Control of outsourced processes and services
ISO-50001-8.3Procurement
API1164-22Configuration management for OT systems2 targets
ISO-41001-8.4Control of outsourced processes and services
ISO-50001-8.3Procurement
API1164-23Change management procedures2 targets
ISO-41001-8.4Control of outsourced processes and services
ISO-50001-8.3Procurement
API1164-24Vulnerability assessment for critical systems
ISO-22313-8.2Business impact analysis and risk assessment

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 API 1164 and ISO 22313:2020 — Guidance on Business Continuity Management Systems?

API 1164 has 24 controls across its framework, while ISO 22313:2020 — Guidance on Business Continuity Management Systems covers 145 controls. Direct mapping analysis identifies 5 overlapping controls (21% coverage). The frameworks diverge most significantly in API 1164: Incident Response & Recovery, where 5 API 1164 controls have no direct ISO 22313:2020 — Guidance on Business Continuity Management Systems equivalent.

How many controls map between API 1164 and ISO 22313:2020 — Guidance on Business Continuity Management Systems?

Of 24 total API 1164 controls, 5 map directly to ISO 22313:2020 — Guidance on Business Continuity Management Systems controls — representing 21% coverage. The remaining 19 controls represent compliance gaps requiring additional documentation or compensating controls to satisfy both frameworks simultaneously.

What are the compliance gaps when mapping API 1164 to ISO 22313:2020 — Guidance on Business Continuity Management Systems?

19 API 1164 controls have no direct equivalent in ISO 22313:2020 — Guidance on Business Continuity Management Systems. The highest concentration of gaps is in API 1164: Incident Response & Recovery 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 API 1164 and ISO 22313:2020 — Guidance on Business Continuity Management Systems?

The domain with the highest gap count is API 1164: Incident Response & Recovery (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.