# PS.3.1_ps31

> Securely archive the necessary files and supporting data (e.g., integrity verification information, provenance data) to be retained for each software

- Skill: `cyberstrikeus/ps-3-1-ps31` (Agent Skill)
- Install (CLI): `npx skillmds@latest add cyberstrikeus/ps-3-1-ps31`
- Raw SKILL.md: https://api.skillmd.com/api/skills/cyberstrikeus/ps-3-1-ps31/raw
- Safety review: PASS (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: cyberstrikeus (https://skillmd.com/u/cyberstrikeus)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/cyberstrikeus/ps-3-1-ps31

---


# PS.3.1 PS.3.1

> **Task of practice:** Archive and Protect Each Software Release (PS.3)

## High-Level Description

**Practice Group:** Protect Software (PS)
**Framework:** NIST SP 800-218 SSDF v1.1

Securely archive the necessary files and supporting data (e.g., integrity verification information, provenance data) to be retained for each software release.

## What to Check

- [ ] Verify PS.3.1 PS.3.1 is integrated into SDLC
- [ ] Review CI/CD pipeline for PS.3.1 implementation
- [ ] Confirm automated tooling supports this practice

## How to Test

### Step 1: Review SDLC Documentation

Examine development lifecycle documentation for evidence of PS.3.1 practice implementation.

### Step 2: Verify Tooling

```
# Check CI/CD pipeline configuration
# Verify security tools are integrated

# Example: Check for SAST/DAST in pipeline
grep -r "security\|scan\|sast\|dast" .github/workflows/ 2>/dev/null
grep -r "security\|scan" Jenkinsfile 2>/dev/null
```

### Step 3: Assess Developer Awareness

Verify development team understands and follows PS.3.1 PS.3.1 practice.

## Tools

| Tool                | Purpose                            | Usage                        |
| ------------------- | ---------------------------------- | ---------------------------- |
| github-security-mcp | Check repository security settings | `github_security_*` tools    |
| Manual Review       | SDLC process review                | Documentation and interviews |

## Remediation Guide

Implement PS.3.1 PS.3.1 in the software development lifecycle:

Securely archive the necessary files and supporting data (e.g., integrity verification information, provenance data) to be retained for each software release.

## Risk Assessment

| Finding                       | Severity | Impact                                |
| ----------------------------- | -------- | ------------------------------------- |
| PS.3.1 PS.3.1 not implemented | Medium   | Secure Development - Protect Software |

## CWE Categories

| CWE ID  | Title                   |
| ------- | ----------------------- |
| CWE-284 | Improper Access Control |

## References

- [NIST SP 800-218 SSDF v1.1](https://csrc.nist.gov/pubs/sp/800/218/final)
- [NIST SSDF Practices](https://csrc.nist.gov/projects/ssdf)
- [NIST OSCAL Content](https://github.com/usnistgov/oscal-content)

## Checklist

- [ ] Practice documented in SDLC policy
- [ ] Tooling configured and operational
- [ ] Development team trained
- [ ] Evidence of consistent application
- [ ] Periodic review scheduled