Skip to content
Back to skills

PO.4.1 Po41

ASecurity

Define criteria for software security checks and track throughout the SDLC.

  • 3,518 stars
  • 0 votes
  • 0 copies
  • 4 views
  • Added September 3, 2026
securitygogitci/cdsecuritydocumentation

Works with

  • mcp

Security analysis

A100/100

Scanned September 3, 2026

npx -y skills add CyberStrikeus/CyberStrike --skill PO.4.1_po41 --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of PO.4.1 Po41?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for PO.4.1 Po41
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/cyberstrikeus-po-4-1-po41/badge)](https://www.skillsdirectory.com/skills/cyberstrikeus-po-4-1-po41)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: "PO.4.1_po41"
description: "Define criteria for software security checks and track throughout the SDLC."
category: "configuration"
version: "1.1"
author: "cyberstrike-official"
tags:
  - nist
  - sp800-218
  - ssdf
  - po-4-1
  - po
  - secure-development
  - task
tech_stack:
  - any
cwe_ids: []
chains_with: []
prerequisites:
  - Define and Use Criteria for Software Security Checks (PO.4)
severity_boost: {}
---

# PO.4.1 PO.4.1

> **Task of practice:** Define and Use Criteria for Software Security Checks (PO.4)

## High-Level Description

**Practice Group:** Prepare the Organization (PO)
**Framework:** NIST SP 800-218 SSDF v1.1

Define criteria for software security checks and track throughout the SDLC.

## What to Check

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

## How to Test

### Step 1: Review SDLC Documentation

Examine development lifecycle documentation for evidence of PO.4.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 PO.4.1 PO.4.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 PO.4.1 PO.4.1 in the software development lifecycle:

Define criteria for software security checks and track throughout the SDLC.

## Risk Assessment

| Finding                       | Severity | Impact                                        |
| ----------------------------- | -------- | --------------------------------------------- |
| PO.4.1 PO.4.1 not implemented | Medium   | Secure Development - Prepare the Organization |

## CWE Categories

| CWE ID | Title                 |
| ------ | --------------------- |
| N/A    | No direct CWE mapping |

## 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

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

View all in security →

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.