cyberstrikeus PO.3.1 PO.3.1
Task of practice: Implement Supporting Toolchains (PO.3)
High-Level Description
Practice Group: Prepare the Organization (PO) Framework: NIST SP 800-218 SSDF v1.1
Specify which tools or tool types must or should be included in each toolchain to mitigate identified risks, as well as how the toolchain components are to be integrated with each other.
What to Check
- Verify PO.3.1 PO.3.1 is integrated into SDLC
- Review CI/CD pipeline for PO.3.1 implementation
- Confirm automated tooling supports this practice
How to Test
Step 1: Review SDLC Documentation
Examine development lifecycle documentation for evidence of PO.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 PO.3.1 PO.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 PO.3.1 PO.3.1 in the software development lifecycle:
Specify which tools or tool types must or should be included in each toolchain to mitigate identified risks, as well as how the toolchain components are to be integrated with each other.
Risk Assessment
| Finding | Severity | Impact |
|---|---|---|
| PO.3.1 PO.3.1 not implemented | Medium | Secure Development - Prepare the Organization |
CWE Categories
| CWE ID | Title |
|---|---|
| N/A | No direct CWE mapping |
References
Checklist
- Practice documented in SDLC policy
- Tooling configured and operational
- Development team trained
- Evidence of consistent application
- Periodic review scheduled