Cross-Framework Mapping

API 1164vsIEEE 1686

See exactly how API 1164 controls map to IEEE 1686. Pre-computed mappings, identified gaps, and coverage analysis.

40
Controls Mapped
0
Gaps Found
67%
Coverage

According to the TheArtOfService Compliance Knowledge Graph:

API 1164 maps to IEEE 1686 with 67% coverage across 29 directly mapped controls. Analysis of 24 API 1164 controls identifies 16 compliance gaps — primarily concentrated in API 1164: Asset Identification & Governance.

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

Control Mappings

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

Risk(1 mappings)

API1164-02Risk Management Framework
IEEE1686-Scope-IED-Substation-Automation-2022-IEC-NERC-NIST-CoordIEEE 1686 - Scope + Intelligent Electronic Devices (IEDs) + Substation Automation + 2022 Edition + Coordination with IEC 62351 + IEC 62443 + NERC CIP + NIST SP 800-82

API 1164: Asset Identification & Governance(2 mappings)

API1164-02Risk Management Framework
IEEE1686-Scope-IED-Substation-Automation-2022-IEC-NERC-NIST-CoordIEEE 1686 - Scope + Intelligent Electronic Devices (IEDs) + Substation Automation + 2022 Edition + Coordination with IEC 62351 + IEC 62443 + NERC CIP + NIST SP 800-82
API1164-05Network Segmentation and Zones
IEEE1686-Scope-IED-Substation-Automation-2022-IEC-NERC-NIST-CoordIEEE 1686 - Scope + Intelligent Electronic Devices (IEDs) + Substation Automation + 2022 Edition + Coordination with IEC 62351 + IEC 62443 + NERC CIP + NIST SP 800-82

Architecture(1 mappings)

API1164-05Network Segmentation and Zones
IEEE1686-Scope-IED-Substation-Automation-2022-IEC-NERC-NIST-CoordIEEE 1686 - Scope + Intelligent Electronic Devices (IEDs) + Substation Automation + 2022 Edition + Coordination with IEC 62351 + IEC 62443 + NERC CIP + NIST SP 800-82

Access(3 mappings)

API1164-06Access Control
IEEE1686-Section5.1-AccessControl-Accounts-Roles-Password-Session-RemoteIEEE 1686 Section 5.1 - Electronic Access Account Management + Roles + Password + Failed Login + Session + Remote Access + Personnel
API1164-07Remote Access2 targets
IEEE1686-IR-Recovery-Reporting-Exercises-Drills-RECOVIEEE 1686 - Incident Response + Recovery from Failed Update + Reporting to Authorities + Coordination with Sector-Specific Agencies + Exercises and Drills
IEEE1686-Section5.1-AccessControl-Accounts-Roles-Password-Session-RemoteIEEE 1686 Section 5.1 - Electronic Access Account Management + Roles + Password + Failed Login + Session + Remote Access + Personnel

API 1164: Access Management(4 mappings)

API1164-06Access Control
IEEE1686-Section5.1-AccessControl-Accounts-Roles-Password-Session-RemoteIEEE 1686 Section 5.1 - Electronic Access Account Management + Roles + Password + Failed Login + Session + Remote Access + Personnel
API1164-07Remote Access2 targets
IEEE1686-IR-Recovery-Reporting-Exercises-Drills-RECOVIEEE 1686 - Incident Response + Recovery from Failed Update + Reporting to Authorities + Coordination with Sector-Specific Agencies + Exercises and Drills
IEEE1686-Section5.1-AccessControl-Accounts-Roles-Password-Session-RemoteIEEE 1686 Section 5.1 - Electronic Access Account Management + Roles + Password + Failed Login + Session + Remote Access + Personnel
API1164-09Patch and Vulnerability Management
IEEE1686-Section5.1-AccessControl-Accounts-Roles-Password-Session-RemoteIEEE 1686 Section 5.1 - Electronic Access Account Management + Roles + Password + Failed Login + Session + Remote Access + Personnel

Vulnerability(1 mappings)

API1164-09Patch and Vulnerability Management
IEEE1686-Section5.1-AccessControl-Accounts-Roles-Password-Session-RemoteIEEE 1686 Section 5.1 - Electronic Access Account Management + Roles + Password + Failed Login + Session + Remote Access + Personnel

Detection(1 mappings)

API1164-11Logging and Monitoring
IEEE1686-Section5.5-5.6-5.7-5.8-Firmware-ConfigSW-TimeSync-DataAtRestIEEE 1686 Section 5.5-5.8 - Firmware Quality + Configuration Software Security + Time Synchronisation + Data Protection at Rest + Patch + Malware + Hardening + Vulnerability

API 1164: Systems Security(4 mappings)

API1164-11Logging and Monitoring
IEEE1686-Section5.5-5.6-5.7-5.8-Firmware-ConfigSW-TimeSync-DataAtRestIEEE 1686 Section 5.5-5.8 - Firmware Quality + Configuration Software Security + Time Synchronisation + Data Protection at Rest + Patch + Malware + Hardening + Vulnerability
API1164-12Incident Response
IEEE1686-Section5.5-5.6-5.7-5.8-Firmware-ConfigSW-TimeSync-DataAtRestIEEE 1686 Section 5.5-5.8 - Firmware Quality + Configuration Software Security + Time Synchronisation + Data Protection at Rest + Patch + Malware + Hardening + Vulnerability
API1164-13Business Continuity and Recovery
IEEE1686-Section5.2-5.3-AuditLog-Retention-Export-MonitoringIEEE 1686 Section 5.2 + 5.3 - Audit Trail Records + Retention + Export + Supervisory Monitoring and Control + Network Security Monitoring
API1164-14Physical Security
IEEE1686-Section5.5-5.6-5.7-5.8-Firmware-ConfigSW-TimeSync-DataAtRestIEEE 1686 Section 5.5-5.8 - Firmware Quality + Configuration Software Security + Time Synchronisation + Data Protection at Rest + Patch + Malware + Hardening + Vulnerability

Incident(1 mappings)

API1164-12Incident Response
IEEE1686-Section5.5-5.6-5.7-5.8-Firmware-ConfigSW-TimeSync-DataAtRestIEEE 1686 Section 5.5-5.8 - Firmware Quality + Configuration Software Security + Time Synchronisation + Data Protection at Rest + Patch + Malware + Hardening + Vulnerability

Resilience(1 mappings)

API1164-13Business Continuity and Recovery
IEEE1686-Section5.2-5.3-AuditLog-Retention-Export-MonitoringIEEE 1686 Section 5.2 + 5.3 - Audit Trail Records + Retention + Export + Supervisory Monitoring and Control + Network Security Monitoring

Physical(1 mappings)

API1164-14Physical Security
IEEE1686-Section5.5-5.6-5.7-5.8-Firmware-ConfigSW-TimeSync-DataAtRestIEEE 1686 Section 5.5-5.8 - Firmware Quality + Configuration Software Security + Time Synchronisation + Data Protection at Rest + Patch + Malware + Hardening + Vulnerability

+20 more mappings

Plus AI-powered gap analysis, compliance advisory, PDF exports, and cross-mapping for all 718 frameworks.

Create Free Account →

Free forever — no credit card required

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 IEEE 1686?

API 1164 has 24 controls across its framework, while IEEE 1686 covers 7 controls. Direct mapping analysis identifies 29 overlapping controls (67% coverage). The frameworks diverge most significantly in API 1164: Asset Identification & Governance, where 3 API 1164 controls have no direct IEEE 1686 equivalent.

How many controls map between API 1164 and IEEE 1686?

Of 24 total API 1164 controls, 29 map directly to IEEE 1686 controls — representing 67% coverage. The remaining 16 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 IEEE 1686?

16 API 1164 controls have no direct equivalent in IEEE 1686. The highest concentration of gaps is in API 1164: Asset Identification & Governance with 3 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 IEEE 1686?

The domain with the highest gap count is API 1164: Asset Identification & Governance (3 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.