2.2.6 System security parameters configured
System security parameters are configured to prevent misuse.
5
artefacts
2
held by a system
1
at each review
moderate
to go live
Vulnerability scanner / patch tooling
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
- Configuration scan reports · Vulnerability scanner / patch tooling
- Drift remediation tickets · Ticketing / ITSM
periodic reviewEvidence produced at each review
- Sample system inspections · Cloud console / configuration management
governing documentDocuments that govern the control
- Hardening checklists per platform · Policy repository / GRC workspace
- Parameter standards document · Policy repository / GRC workspace
First move
Start with the 2 of 5 artefacts that already live in a system (Vulnerability scanner / patch tooling); keep the periodic reviews but log each one as a dated record with a named reviewer.
Common gaps auditors find
- Default parameters unchanged
- No periodic verification
- Inconsistent application across estate
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 sheet2.2.5 Insecure services or protocols documented · 2.2.7 Non-console administrative access encrypted