Cross-Framework Mapping

UNECE WP.29 R155vsSLSA

See exactly how UNECE WP.29 R155 controls map to SLSA. Pre-computed mappings, identified gaps, and coverage analysis.

38
Controls Mapped
10
Gaps Found
35%
Coverage

According to the TheArtOfService Compliance Knowledge Graph:

UNECE WP.29 R155 maps to SLSA with 35% coverage across 17 directly mapped controls. Analysis of 48 UNECE WP.29 R155 controls identifies 31 compliance gaps — primarily concentrated in Threat coverage.

Source: TheArtOfService Knowledge Graph | 48 controls analysed | 720 frameworks | 432K+ cross-framework mappings

Control Mappings

Showing 20 of 38 mapped controls across 6 domains. Sign up to explore all 432K+ mappings across 720 frameworks.

UNECE WP.29 R155: Information Security Policies(1 mappings)

WP29-R155-04Roles and responsibilities definition
SLSA-04Roles and responsibilities definition

UNECE WP.29 R155: Asset Management(10 mappings)

WP29-R155-06Asset inventory and ownership3 targets
SLSA-06Asset inventory and ownership
SLSA-07Acceptable use of assets
SLSA-10Media management and disposal
WP29-R155-07Acceptable use of assets3 targets
SLSA-06Asset inventory and ownership
SLSA-07Acceptable use of assets
SLSA-10Media management and disposal
WP29-R155-08Information classification and labeling
SLSA-08Information classification and labeling
WP29-R155-10Media management and disposal3 targets
SLSA-06Asset inventory and ownership
SLSA-07Acceptable use of assets
SLSA-10Media management and disposal

UNECE WP.29 R155: Access Control(9 mappings)

WP29-R155-11Access control policy and enforcement3 targets
SLSA-13Authentication and password management
SLSA-14Privileged access management
SLSA-15Access review and recertification
WP29-R155-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
WP29-R155-13Authentication and password management2 targets
SLSA-13Authentication and password management
SLSA-14Privileged access management

+18 more mappings

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

Create Free Account →

Free forever — no credit card required

Stop Paying Consultants to Read Spreadsheets

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

$0/forever

Free

  • 720 framework browser
  • Cross-framework mappings (432K+)
  • 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 UNECE WP.29 R155 and SLSA?

UNECE WP.29 R155 has 48 controls across its framework, while SLSA covers 51 controls. Direct mapping analysis identifies 17 overlapping controls (35% coverage). The frameworks diverge most significantly in Threat coverage, where 4 UNECE WP.29 R155 controls have no direct SLSA equivalent.

How many controls map between UNECE WP.29 R155 and SLSA?

Of 48 total UNECE WP.29 R155 controls, 17 map directly to SLSA controls — representing 35% coverage. The remaining 31 controls represent compliance gaps requiring additional documentation or compensating controls to satisfy both frameworks simultaneously.

What are the compliance gaps when mapping UNECE WP.29 R155 to SLSA?

31 UNECE WP.29 R155 controls have no direct equivalent in SLSA. The highest concentration of gaps is in Threat coverage 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 UNECE WP.29 R155 and SLSA?

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