Cross-Framework Mapping

API 1164vsSLSA

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

24
Controls Mapped
0
Gaps Found
38%
Coverage

According to the TheArtOfService Compliance Knowledge Graph:

API 1164 maps to SLSA 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 20 of 24 mapped controls across 12 domains. Sign up to explore all 332K+ mappings across 718 frameworks.

Risk(1 mappings)

API1164-02Risk Management Framework
SUPCHAIN-1Build Integrity - Source, Build, Provenance

API 1164: Asset Identification & Governance(1 mappings)

API1164-02Risk Management Framework
SUPCHAIN-1Build Integrity - Source, Build, Provenance

Access(4 mappings)

API1164-06Access Control2 targets
SUPCHAIN-1Build Integrity - Source, Build, Provenance
SUPCHAIN-2Source Integrity - Branch Protection, Code Review, Two-Person Rule
API1164-07Remote Access2 targets
SUPCHAIN-1Build Integrity - Source, Build, Provenance
SUPCHAIN-2Source Integrity - Branch Protection, Code Review, Two-Person Rule

API 1164: Access Management(6 mappings)

API1164-06Access Control2 targets
SUPCHAIN-1Build Integrity - Source, Build, Provenance
SUPCHAIN-2Source Integrity - Branch Protection, Code Review, Two-Person Rule
API1164-07Remote Access2 targets
SUPCHAIN-1Build Integrity - Source, Build, Provenance
SUPCHAIN-2Source Integrity - Branch Protection, Code Review, Two-Person Rule
API1164-09Patch and Vulnerability Management2 targets
SUPCHAIN-1Build Integrity - Source, Build, Provenance
SUPCHAIN-2Source Integrity - Branch Protection, Code Review, Two-Person Rule

Vulnerability(2 mappings)

API1164-09Patch and Vulnerability Management2 targets
SUPCHAIN-1Build Integrity - Source, Build, Provenance
SUPCHAIN-2Source Integrity - Branch Protection, Code Review, Two-Person Rule

Incident(1 mappings)

API1164-12Incident Response
SUPCHAIN-2Source Integrity - Branch Protection, Code Review, Two-Person Rule

API 1164: Systems Security(2 mappings)

API1164-12Incident Response
SUPCHAIN-2Source Integrity - Branch Protection, Code Review, Two-Person Rule
API1164-13Business Continuity and Recovery
SUPCHAIN-3Dependency Verification and SBOM

Resilience(1 mappings)

API1164-13Business Continuity and Recovery
SUPCHAIN-3Dependency Verification and SBOM

Communications(1 mappings)

API1164-17Wireless and Field Communications
SUPCHAIN-2Source Integrity - Branch Protection, Code Review, Two-Person Rule

API 1164: Incident Response & Recovery(1 mappings)

API1164-17Wireless and Field Communications
SUPCHAIN-2Source Integrity - Branch Protection, Code Review, Two-Person Rule

+4 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 SLSA?

API 1164 has 24 controls across its framework, while SLSA covers 4 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 SLSA equivalent.

How many controls map between API 1164 and SLSA?

Of 24 total API 1164 controls, 18 map directly to SLSA 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 SLSA?

27 API 1164 controls have no direct equivalent in SLSA. 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 SLSA?

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.