OpenParable
Skip to content
← Back to skills

PO.2.3_po23

Productivity

PO.2.3_po23 is an Agent Skill for productivity published in the CyberStrikeus/CyberStrike repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Obtain upper management or authorizing official commitment to secure development, and convey that commitment to all with development-related roles and

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/CyberStrikeus/CyberStrike/blob/HEAD/.cyberstrike/skill/NIST/SP800-218_SSDF/PO_prepare-the-organization/PO.2.3_po23/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/po-2-3-po23, 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.

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

ToolPurposeUsage
github-security-mcpCheck repository security settingsgithub_security_* tools
Manual ReviewSDLC process reviewDocumentation 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

FindingSeverityImpact
PO.2.3 PO.2.3 not implementedMediumSecure Development - Prepare the Organization

CWE Categories

CWE IDTitle
N/ANo direct CWE mapping

References

Checklist

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