Defense · SSDF · Protect Software (PS)

SSDF · Protect Software (PS) for defense AI workflows

SSDF · Protect Software (PS) in defense AI workflows: what compliance requires, who asks for evidence, and the records to keep.

Start free Open the Console

Legal forceVoluntary framework; no government-wide attestation since Jan 2026

Applies from3 Feb 2022

SectorDefense

Checked21 Oct 2026

01 / The rule

What SSDF · Protect Software (PS) requires

Software producers, including vendors selling software to US federal agencies, and their development teams.

01PS.1.1: store all source code, executable code and configuration-as-code with least-privilege access for people, tools and services.
02PS.2.1: make integrity verification information, such as cryptographic hashes or signatures, available to software acquirers.
03PS.3.1: securely archive each release with its supporting data, such as integrity and provenance information.
04PS.3.2: collect, safeguard, maintain and share provenance data for all components of each release, for example in an SBOM.

02 / In this sector

In a defense AI workflow

SP 800-218A adds PS.1.2 (protect training, testing, fine-tuning and aligning data) and PS.1.3 (protect model weights and configuration parameters), and applies PS.1.1, PS.2.1 and PS.3.2 to models, weights, pipelines and model provenance.

Usually asked by

Program office leads and ATO-package owners.

Named alongside

NIST AI RMF · DoW RAI · OMB M-25-21.

Sector pagePlanisphere for defense

03 / Records

Records to keep

01Repository access-control lists and access reviews
02Signed release artifacts and published hashes
03Release archive with integrity and provenance data
04SBOM or other provenance record for each release

Optional evidence · where Planisphere fits

Keep a record anyone can check

When your team meets a duty, Planisphere can seal the event it reports as a receipt.

01 · Your teamRecord the event

A disclosure shown, a review signed, a model change approved: the event your system reports.

02 · PlanisphereSeal it

The event becomes a sealed receipt, dated and attributed to whoever is signed in.

03 · AnyoneCheck it

Paste the receipt into Verify. No account or key.

A record supports your compliance evidence process. It is not a legal finding or a certification. Systems that call Planisphere's gate API can also hold or refuse an action before it runs.

SOURCES