Define and Use Criteria for Software Security Checks (PO.4)_define-and-use-criteria-for-software-security-checks

Define and Use Criteria for Software Security Checks (PO.4) Define and Use Criteria for Software Security Checks

High-Level Description

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

Help ensure that the software resulting from the SDLC meets the organization’s expectations by defining and using criteria for checking the software’s security during development.

What to Check

• Verify Define and Use Criteria for Software Security Checks (PO.4) Define and Use Criteria for Software Security Checks is integrated into SDLC
• Review CI/CD pipeline for Define and Use Criteria for Software Security Checks (PO.4) implementation
• Confirm automated tooling supports this practice

How to Test

Step 1: Review SDLC Documentation

Examine development lifecycle documentation for evidence of Define and Use Criteria for Software Security Checks (PO.4) 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 Define and Use Criteria for Software Security Checks (PO.4) Define and Use Criteria for Software Security Checks practice.

Tools

Remediation Guide

Implement Define and Use Criteria for Software Security Checks (PO.4) Define and Use Criteria for Software Security Checks in the software development lifecycle:

Help ensure that the software resulting from the SDLC meets the organization’s expectations by defining and using criteria for checking the software’s security during development.

Risk Assessment

CWE Categories

References

• NIST SP 800-218 SSDF v1.1
• NIST SSDF Practices
• NIST OSCAL Content

Checklist

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