CM-6 Configuration Settings
Sets and verifies secure settings on delivered components rather than accepting the supplier default.
Source: NIST SP 800-161 Rev 1 (supply chain), CM-6. 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-161 Rev 1 (supply chain) 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
none for this control
periodic reviewEvidence produced at each review
- Compliance evidence after deployment · Source control / CI pipeline
- Records of default credentials and services changed or disabled · Identity provider / directory
governing documentDocuments that govern the control
- Setting standards applied to delivered component types · Policy repository / GRC workspace
First move
Common gaps auditors find
- appliances run on shipped defaults
- supplier forbids configuration change and the risk is unaccepted
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 sheetCM-5 Access Restrictions for Change · CM-7 Least Functionality