Back to skills
SKILL.md
PO.2.3 Po23
ASecurityObtain upper management or authorizing official commitment to secure development, and convey that commitment to all with development-related roles and
- 3,518 stars
- 0 votes
- 0 copies
- 4 views
- Added September 3, 2026
Works with
Security analysis
100/100npx -y skills add CyberStrikeus/CyberStrike --skill PO.2.3_po23 --agent claude-codeAre you the author of PO.2.3 Po23?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/cyberstrikeus-po-2-3-po23)---
name: "PO.2.3_po23"
description: "Obtain upper management or authorizing official commitment to secure development, and convey that commitment to all with development-related roles and"
category: "configuration"
version: "1.1"
author: "cyberstrike-official"
tags:
- nist
- sp800-218
- ssdf
- po-2-3
- po
- secure-development
- task
tech_stack:
- any
cwe_ids: []
chains_with: []
prerequisites:
- Implement Roles and Responsibilities (PO.2)
severity_boost: {}
---
# PO.2.3 PO.2.3
> **Task of practice:** Implement Roles and Responsibilities (PO.2)
## High-Level Description
**Practice Group:** Prepare the Organization (PO)
**Framework:** NIST SP 800-218 SSDF v1.1
Obtain upper management or authorizing official commitment to secure development, and convey that commitment to all with development-related roles and responsibilities.
## What to Check
- [ ] Verify PO.2.3 PO.2.3 is integrated into SDLC
- [ ] Review CI/CD pipeline for PO.2.3 implementation
- [ ] Confirm automated tooling supports this practice
## How to Test
### Step 1: Review SDLC Documentation
Examine development lifecycle documentation for evidence of PO.2.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 PO.2.3 PO.2.3 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.2.3 PO.2.3 in the software development lifecycle:
Obtain upper management or authorizing official commitment to secure development, and convey that commitment to all with development-related roles and responsibilities.
## Risk Assessment
| Finding | Severity | Impact |
| ----------------------------- | -------- | --------------------------------------------- |
| PO.2.3 PO.2.3 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
Related skills
View all in security →Comments
Loading comments…
Newsletter
Get the weekly list of safe new skills, and the ones we pulled.