P‑SSCRM Proactive Secure Software Supply Chain Risk Management

P‑SSCRM

Proactive Secure Software Supply Chain Risk Management

One framework for managing software supply chain risk: your code dependencies, build systems, AI models and data, and the people who maintain them.

Securing a software supply chain means working with many standards — SSDF, SSDF-AI, SLSA, NIST 800-161, OWASP SCVS, and five more — that overlap and use different terms. P-SSCRM brings them together in one model of Groups, Practices, and Controls. Each control points back to the standards it came from, so you can work from a single checklist and still show you meet the standards that apply to you.

Who P-SSCRM is for

P-SSCRM Framework

5 Groups, 16 Practices, 78 Controls. Select any cell to explore it.

Each column is a Group and each tile a Practice — open a tile for its Controls, or go to the full framework.

How it relates to what you already use

Every P-SSCRM control maps to one or more established government and industry standards, including EO, 800-161, SSDF, SLSA, BSIMM, CNCF-SSC, and more.

See all the standards and which controls draw on each one →

Each control is also linked to the MITRE ATT&CK attack techniques it helps defend against. See how the ATT&CK mapping works →

Background & citation

P-SSCRM combines the common ground of the field's government and industry standards. It is described in a paper on arXiv and run with the S3C2 research center.

P-SSCRM v1.0 · Baseline study · S3C2 · Full background

Current framework data: v2.0 (JSON). MITRE ATT&CK mapping: v1.1. Data comes from p-sscrm/p-sscrm and p-sscrm/ats-to-ts.

Put P-SSCRM to work

Read the framework, work through the assessment questions for your Groups and Practices, or help shape P-SSCRM by taking part in an interview-based assessment.

Measure and Improve View the Framework