Cross-Framework Mapping

SLSAvsOWASP SAMM

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

37
Controls Mapped
14
Gaps Found
35%
Coverage

According to the TheArtOfService Compliance Knowledge Graph:

SLSA maps to OWASP SAMM with 35% coverage across 18 directly mapped controls. Analysis of 51 SLSA controls identifies 33 compliance gaps — primarily concentrated in SLSA: Information Security Policies.

Source: TheArtOfService Knowledge Graph | 51 controls analysed | 722 frameworks | 437K+ cross-framework mappings

Control Mappings

Showing 20 of 37 mapped controls across 6 domains. Sign up to explore all 437K+ mappings across 722 frameworks.

SLSA: Information Security Policies(1 mappings)

SLSA-04Roles and responsibilities definition
SAMM-04Roles and responsibilities definition

SLSA: Asset Management(10 mappings)

SLSA-06Asset inventory and ownership3 targets
SAMM-08Information classification and labeling
SAMM-09Asset handling procedures
SAMM-10Media management and disposal
SLSA-07Acceptable use of assets3 targets
SAMM-08Information classification and labeling
SAMM-09Asset handling procedures
SAMM-10Media management and disposal
SLSA-08Information classification and labeling
SAMM-08Information classification and labeling
SLSA-10Media management and disposal3 targets
SAMM-08Information classification and labeling
SAMM-09Asset handling procedures
SAMM-10Media management and disposal

SLSA: Access Control(9 mappings)

SLSA-12User access management and provisioning
SAMM-12User access management and provisioning
SLSA-13Authentication and password management3 targets
SAMM-11Access control policy and enforcement
SAMM-13Authentication and password management
SAMM-14Privileged access management
SLSA-14Privileged access management3 targets
SAMM-11Access control policy and enforcement
SAMM-13Authentication and password management
SAMM-14Privileged access management
SLSA-15Access review and recertification2 targets
SAMM-11Access control policy and enforcement
SAMM-13Authentication and password management

+17 more mappings

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

Create Free Account →

Free forever — no credit card required

Stop Paying Consultants to Read Spreadsheets

AI-powered compliance intelligence across 722 frameworks — at a fraction of consulting costs.

$0/forever

Free

  • 722 framework browser
  • Cross-framework mappings (437K+)
  • 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 SLSA and OWASP SAMM?

SLSA has 51 controls across its framework, while OWASP SAMM covers 51 controls. Direct mapping analysis identifies 18 overlapping controls (35% coverage). The frameworks diverge most significantly in SLSA: Information Security Policies, where 4 SLSA controls have no direct OWASP SAMM equivalent.

How many controls map between SLSA and OWASP SAMM?

Of 51 total SLSA controls, 18 map directly to OWASP SAMM controls — representing 35% coverage. The remaining 33 controls represent compliance gaps requiring additional documentation or compensating controls to satisfy both frameworks simultaneously.

What are the compliance gaps when mapping SLSA to OWASP SAMM?

33 SLSA controls have no direct equivalent in OWASP SAMM. The highest concentration of gaps is in SLSA: Information Security Policies 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 SLSA and OWASP SAMM?

The domain with the highest gap count is SLSA: Information Security Policies (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.