2.2.5 Insecure services or protocols documented
If any insecure services, protocols, or daemons are present, business justification is documented and additional security features are documented and implemented.
5
artefacts
1
held by a system
3
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
- Compensating control configuration · Cloud console / configuration management
periodic reviewEvidence produced at each review
- Senior approval records · Policy repository / GRC workspace
- Risk assessment · Policy repository / GRC workspace
- Periodic review records · Policy repository / GRC workspace
governing documentDocuments that govern the control
- Register of insecure services with justification · Policy repository / GRC workspace
First move
Mostly documents and reviews. Pull the 1 system-held artefact from your Cloud console / configuration management on a schedule; put the documents under version control with an owner and review date, and log each review as a dated record with a named reviewer.
Common gaps auditors find
- Insecure services without controls
- No senior approval
- No periodic re-review
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.4 Only necessary services enabled · 2.2.6 System security parameters configured