Configure Software to Have Secure Settings by Default (PW.9)_configure-software-to-have-secure-settings-by-default

Configure Software to Have Secure Settings by Default (PW.9) Configure Software to Have Secure Settings by Default

High-Level Description

Practice Group: Produce Well-Secured Software (PW) Framework: NIST SP 800-218 SSDF v1.1

Help improve the security of the software at the time of installation to reduce the likelihood of the software being deployed with weak security settings, putting it at greater risk of compromise.

What to Check

• Verify Configure Software to Have Secure Settings by Default (PW.9) Configure Software to Have Secure Settings by Default is integrated into SDLC
• Review CI/CD pipeline for Configure Software to Have Secure Settings by Default (PW.9) implementation
• Confirm automated tooling supports this practice

How to Test

Step 1: Review SDLC Documentation

Examine development lifecycle documentation for evidence of Configure Software to Have Secure Settings by Default (PW.9) 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 Configure Software to Have Secure Settings by Default (PW.9) Configure Software to Have Secure Settings by Default practice.

Tools

Remediation Guide

Implement Configure Software to Have Secure Settings by Default (PW.9) Configure Software to Have Secure Settings by Default in the software development lifecycle:

Help improve the security of the software at the time of installation to reduce the likelihood of the software being deployed with weak security settings, putting it at greater risk of compromise.

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