Cross-Framework Mapping

NIST SP 800-190vsSLSA

See exactly how NIST SP 800-190 controls map to SLSA. Pre-computed mappings, identified gaps, and coverage analysis.

10
Controls Mapped
35
Gaps Found
22%
Coverage

According to the TheArtOfService Compliance Knowledge Graph:

NIST SP 800-190 maps to SLSA with 22% coverage across 10 directly mapped controls. Analysis of 45 NIST SP 800-190 controls identifies 35 compliance gaps — primarily concentrated in Orchestrator.

Source: TheArtOfService Knowledge Graph | 45 controls analysed | 718 frameworks | 332K+ cross-framework mappings

Control Mappings

Showing 10 of 10 mapped controls across 5 domains. Sign up to explore all 332K+ mappings across 718 frameworks.

NIST SP 800-190: Cloud Governance(1 mappings)

NIST190-01Shared responsibility model definition
SUPCHAIN-1Build Integrity - Source, Build, Provenance

NIST SP 800-190: Identity & Access in Cloud(3 mappings)

NIST190-06Cloud identity management
SUPCHAIN-1Build Integrity - Source, Build, Provenance
NIST190-07Multi-factor authentication for cloud
SUPCHAIN-1Build Integrity - Source, Build, Provenance
NIST190-08Privileged access in cloud environments
SUPCHAIN-2Source Integrity - Branch Protection, Code Review, Two-Person Rule

NIST SP 800-190: Data Protection in Cloud(3 mappings)

NIST190-11Data classification for cloud
SUPCHAIN-1Build Integrity - Source, Build, Provenance
NIST190-12Encryption of cloud-stored data
SUPCHAIN-2Source Integrity - Branch Protection, Code Review, Two-Person Rule
NIST190-14Data backup and recovery in cloud
SUPCHAIN-2Source Integrity - Branch Protection, Code Review, Two-Person Rule

NIST SP 800-190: Cloud Infrastructure Security(1 mappings)

NIST190-16Virtual network segmentation
SUPCHAIN-3Dependency Verification and SBOM

NIST SP 800-190: Cloud Operations & Monitoring(2 mappings)

NIST190-21Cloud security monitoring and logging
SUPCHAIN-2Source Integrity - Branch Protection, Code Review, Two-Person Rule
NIST190-23Cloud vulnerability management
SUPCHAIN-2Source Integrity - Branch Protection, Code Review, Two-Person Rule

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 NIST SP 800-190 and SLSA?

NIST SP 800-190 has 45 controls across its framework, while SLSA covers 4 controls. Direct mapping analysis identifies 10 overlapping controls (22% coverage). The frameworks diverge most significantly in Orchestrator, where 5 NIST SP 800-190 controls have no direct SLSA equivalent.

How many controls map between NIST SP 800-190 and SLSA?

Of 45 total NIST SP 800-190 controls, 10 map directly to SLSA controls — representing 22% coverage. The remaining 35 controls represent compliance gaps requiring additional documentation or compensating controls to satisfy both frameworks simultaneously.

What are the compliance gaps when mapping NIST SP 800-190 to SLSA?

35 NIST SP 800-190 controls have no direct equivalent in SLSA. The highest concentration of gaps is in Orchestrator with 5 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 NIST SP 800-190 and SLSA?

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