Cross-Framework Mapping

MITRE ATT&CKvsSLSA

See exactly how MITRE ATT&CK controls map to SLSA. Pre-computed mappings, identified gaps, and coverage analysis.

39
Controls Mapped
13
Gaps Found
35%
Coverage

According to the TheArtOfService Compliance Knowledge Graph:

MITRE ATT&CK maps to SLSA with 35% coverage across 18 directly mapped controls. Analysis of 52 MITRE ATT&CK controls identifies 34 compliance gaps — primarily concentrated in Tactic.

Source: TheArtOfService Knowledge Graph | 52 controls analysed | 725 frameworks | 447K+ cross-framework mappings

Control Mappings

Showing 20 of 39 mapped controls across 6 domains. Sign up to explore all 447K+ mappings across 725 frameworks.

MITRE ATT&CK: Information Security Policies(1 mappings)

MITRE-04Roles and responsibilities definition
SLSA-04Roles and responsibilities definition

MITRE ATT&CK: Asset Management(10 mappings)

MITRE-06Asset inventory and ownership3 targets
SLSA-06Asset inventory and ownership
SLSA-07Acceptable use of assets
SLSA-10Media management and disposal
MITRE-07Acceptable use of assets3 targets
SLSA-06Asset inventory and ownership
SLSA-07Acceptable use of assets
SLSA-10Media management and disposal
MITRE-08Information classification and labeling
SLSA-08Information classification and labeling
MITRE-09Asset handling procedures3 targets
SLSA-06Asset inventory and ownership
SLSA-07Acceptable use of assets
SLSA-10Media management and disposal

MITRE ATT&CK: Access Control(9 mappings)

MITRE-11Access control policy and enforcement3 targets
SLSA-13Authentication and password management
SLSA-14Privileged access management
SLSA-15Access review and recertification
MITRE-12User access management and provisioning4 targets
SLSA-12User access management and provisioning
SLSA-13Authentication and password management
SLSA-14Privileged access management
SLSA-15Access review and recertification
MITRE-13Authentication and password management
SLSA-13Authentication and password management
MITRE-14Privileged access management
SLSA-13Authentication and password management

+19 more mappings

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

Create Free Account →

Free forever — no credit card required

Stop Paying Consultants to Read Spreadsheets

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

$0/forever

Free

  • 725 framework browser
  • Cross-framework mappings (447K+)
  • 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 MITRE ATT&CK and SLSA?

MITRE ATT&CK has 52 controls across its framework, while SLSA covers 51 controls. Direct mapping analysis identifies 18 overlapping controls (35% coverage). The frameworks diverge most significantly in Tactic, where 12 MITRE ATT&CK controls have no direct SLSA equivalent.

How many controls map between MITRE ATT&CK and SLSA?

Of 52 total MITRE ATT&CK controls, 18 map directly to SLSA controls — representing 35% coverage. The remaining 34 controls represent compliance gaps requiring additional documentation or compensating controls to satisfy both frameworks simultaneously.

What are the compliance gaps when mapping MITRE ATT&CK to SLSA?

34 MITRE ATT&CK controls have no direct equivalent in SLSA. The highest concentration of gaps is in Tactic with 12 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 MITRE ATT&CK and SLSA?

The domain with the highest gap count is Tactic (12 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.