Cross-Framework Mapping

API 1164vsPTES

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

18
Controls Mapped
6
Gaps Found
38%
Coverage

According to the TheArtOfService Compliance Knowledge Graph:

API 1164 maps to PTES with 38% coverage across 18 directly mapped controls. Analysis of 24 API 1164 controls identifies 27 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 18 of 18 mapped controls across 12 domains. Sign up to explore all 332K+ mappings across 718 frameworks.

Risk(1 mappings)

API1164-02Risk Management Framework
PTESPHASE-1Pre-Engagement Interactions and Scoping

API 1164: Asset Identification & Governance(1 mappings)

API1164-02Risk Management Framework
PTESPHASE-1Pre-Engagement Interactions and Scoping

Access(2 mappings)

API1164-06Access Control
PTESPHASE-2Intelligence Gathering (OSINT)
API1164-07Remote Access
PTESPHASE-2Intelligence Gathering (OSINT)

API 1164: Access Management(3 mappings)

API1164-06Access Control
PTESPHASE-2Intelligence Gathering (OSINT)
API1164-07Remote Access
PTESPHASE-2Intelligence Gathering (OSINT)
API1164-09Patch and Vulnerability Management
PTESPHASE-2Intelligence Gathering (OSINT)

Vulnerability(1 mappings)

API1164-09Patch and Vulnerability Management
PTESPHASE-2Intelligence Gathering (OSINT)

Incident(1 mappings)

API1164-12Incident Response
PTESPHASE-3Threat Modeling

API 1164: Systems Security(2 mappings)

API1164-12Incident Response
PTESPHASE-3Threat Modeling
API1164-13Business Continuity and Recovery
PTESPHASE-4Vulnerability Analysis

Resilience(1 mappings)

API1164-13Business Continuity and Recovery
PTESPHASE-4Vulnerability Analysis

Communications(1 mappings)

API1164-17Wireless and Field Communications
PTESPHASE-3Threat Modeling

API 1164: Incident Response & Recovery(3 mappings)

API1164-17Wireless and Field Communications
PTESPHASE-3Threat Modeling
API1164-18Field Device Security
PTESPHASE-3Threat Modeling
API1164-19Safety Instrumented Systems Interface
PTESPHASE-3Threat Modeling

Endpoint(1 mappings)

API1164-18Field Device Security
PTESPHASE-3Threat Modeling

Safety(1 mappings)

API1164-19Safety Instrumented Systems Interface
PTESPHASE-3Threat Modeling

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 PTES?

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

How many controls map between API 1164 and PTES?

Of 24 total API 1164 controls, 18 map directly to PTES controls — representing 38% coverage. The remaining 27 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 PTES?

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

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