Cross-Framework Mapping

API 1164vsISO 22320:2018

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

20
Controls Mapped
4
Gaps Found
17%
Coverage

According to the TheArtOfService Compliance Knowledge Graph:

API 1164 maps to ISO 22320:2018 with 17% coverage across 8 directly mapped controls. Analysis of 24 API 1164 controls identifies 37 compliance gaps — primarily concentrated in API 1164: Access Management.

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

Control Mappings

Showing 20 of 20 mapped controls across 6 domains. Sign up to explore all 332K+ mappings across 718 frameworks.

Communications(3 mappings)

API1164-17Wireless and Field Communications3 targets
ISO-22320-5.2Incident management process
ISO-22320-BAnnex B: Incident management plan structure
ISO-22320-CAnnex C: Incident management task examples

API 1164: Incident Response & Recovery(9 mappings)

API1164-17Wireless and Field Communications3 targets
ISO-22320-5.2Incident management process
ISO-22320-BAnnex B: Incident management plan structure
ISO-22320-CAnnex C: Incident management task examples
API1164-18Field Device Security3 targets
ISO-22320-5.2Incident management process
ISO-22320-BAnnex B: Incident management plan structure
ISO-22320-CAnnex C: Incident management task examples
API1164-19Safety Instrumented Systems Interface3 targets
ISO-22320-5.2Incident management process
ISO-22320-BAnnex B: Incident management plan structure
ISO-22320-CAnnex C: Incident management task examples

Endpoint(3 mappings)

API1164-18Field Device Security3 targets
ISO-22320-5.2Incident management process
ISO-22320-BAnnex B: Incident management plan structure
ISO-22320-CAnnex C: Incident management task examples

Safety(3 mappings)

API1164-19Safety Instrumented Systems Interface3 targets
ISO-22320-5.2Incident management process
ISO-22320-BAnnex B: Incident management plan structure
ISO-22320-CAnnex C: Incident management task examples

Regulatory(1 mappings)

API1164-21TSA Pipeline Security Directive Alignment
ISO-22320-4.3Risk-based approach

API 1164: Supply Chain & Configuration(1 mappings)

API1164-21TSA Pipeline Security Directive Alignment
ISO-22320-4.3Risk-based approach

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 (332K+)
  • 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 22320:2018?

API 1164 has 24 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 API 1164: Access Management, where 5 API 1164 controls have no direct ISO 22320:2018 equivalent.

How many controls map between API 1164 and ISO 22320:2018?

Of 24 total API 1164 controls, 8 map directly to ISO 22320:2018 controls — representing 17% coverage. The remaining 37 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 22320:2018?

37 API 1164 controls have no direct equivalent in ISO 22320:2018. The highest concentration of gaps is in API 1164: Access Management 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 22320:2018?

The domain with the highest gap count is API 1164: Access Management (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.