Archive and Protect Each Software Release (PS.3)_archive-and-protect-each-software-release
DevOps & SecurityArchive and Protect Each Software Release (PS.3)_archive-and-protect-each-software-release is an Agent Skill for devops & security published in the CyberStrikeus/CyberStrike repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Preserve software releases in order to help identify, analyze, and eliminate vulnerabilities discovered in the software after release.
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Inspect the Agent Skill at https://github.com/CyberStrikeus/CyberStrike/blob/HEAD/.cyberstrike/skill/NIST/SP800-218_SSDF/PS_protect-software/Archive and Protect Each Software Release (PS.3)_archive-and-protect-each-software-release/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/archive-and-protect-each-software-release-ps-3-archive-and-protect-each-software-release, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
Archive and Protect Each Software Release (PS.3) Archive and Protect Each Software Release
High-Level Description
Practice Group: Protect Software (PS) Framework: NIST SP 800-218 SSDF v1.1
Preserve software releases in order to help identify, analyze, and eliminate vulnerabilities discovered in the software after release.
What to Check
- Verify Archive and Protect Each Software Release (PS.3) Archive and Protect Each Software Release is integrated into SDLC
- Review CI/CD pipeline for Archive and Protect Each Software Release (PS.3) implementation
- Confirm automated tooling supports this practice
How to Test
Step 1: Review SDLC Documentation
Examine development lifecycle documentation for evidence of Archive and Protect Each Software Release (PS.3) 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 Archive and Protect Each Software Release (PS.3) Archive and Protect Each Software Release 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 Archive and Protect Each Software Release (PS.3) Archive and Protect Each Software Release in the software development lifecycle:
Preserve software releases in order to help identify, analyze, and eliminate vulnerabilities discovered in the software after release.
Risk Assessment
| Finding | Severity | Impact |
|---|---|---|
| Archive and Protect Each Software Release (PS.3) Archive and Protect Each Software Release not implemented | Medium | Secure Development - Protect Software |
CWE Categories
| CWE ID | Title |
|---|---|
| CWE-284 | Improper Access Control |
References
Checklist
- Practice documented in SDLC policy
- Tooling configured and operational
- Development team trained
- Evidence of consistent application
- Periodic review scheduled