CM-6 Configuration Settings
Sets and verifies secure settings on delivered components rather than accepting the supplier default.
3
artefacts
0
held by a system
2
at each review
hard
to go live
Policy repository / GRC workspace
where the evidence lives
teal = a system already holds it · olive = produced at each review
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
This control is evidenced by people and documents, not systems. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date. Do not try to automate it.
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