1.2.6 Security features for insecure services defined
Security features are defined and implemented for all services, protocols, and ports in use that are considered to be insecure.
5
artefacts
1
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
- Configuration showing compensating controls applied · Cloud console / configuration management
periodic reviewEvidence produced at each review
- Risk assessment document · Policy repository / GRC workspace
- Quarterly review records · Document repository
governing documentDocuments that govern the control
- Register of insecure protocols with control mapping · Policy repository / GRC workspace
- Approval by senior management · Document repository
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
- Controls documented but not implemented
- No senior approval
- Missing review cadence
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 sheet1.2.5 Services, protocols, ports inventoried and justified · 1.2.7 NSC rule sets reviewed every six months