PW.9.1 Configure Software to Have Secure Settings by Default
Ship software with secure default configuration so that customers receive a secure posture out of the box. Document the security implications of any settings that customers can change.
Source: NIST SP 800-218 (SSDF), PW.9.1. The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open NIST SP 800-218 (SSDF) in the compliance library.
These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.
system holds itEvidence a system already holds
- Telemetry on customer adoption of insecure settings · Cloud console / configuration management
periodic reviewEvidence produced at each review
- Default configuration review · Cloud console / configuration management
governing documentDocuments that govern the control
- Documentation of security implications of settings · Document repository
- Deprecation plan for unsafe defaults · Policy repository / GRC workspace
First move
Common gaps auditors find
- secure defaults rolled back after customer complaint
- documentation does not call out security implications
- no measurement of how customers configure the product
Do this for your whole sheet
Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.
Build my evidence sheetPW.8.2 Execute Security Testing · PW.9.2 Implement and Document Secure Defaults