1.2.7 NSC rule sets reviewed every six months
Configurations of NSCs are reviewed at least once every six months to confirm they are relevant and effective.
5
artefacts
2
held by a system
2
at each review
moderate
to go live
Cloud console / configuration management
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
- Stale rule report from firewall tool · Cloud console / configuration management
- Remediation ticket trail · Ticketing / ITSM
periodic reviewEvidence produced at each review
- Last two semi-annual review reports · Document repository
- Reviewer sign-off with date · Document repository
governing documentDocuments that govern the control
- List of rules removed or modified · Document repository
First move
Start with the 2 of 5 artefacts that already live in a system (Cloud console / configuration management); keep the periodic reviews but log each one as a dated record with a named reviewer.
Common gaps auditors find
- Reviews skipped or backdated
- Stale rules left in place
- No reviewer independent of operations
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.6 Security features for insecure services defined · 1.2.8 Configuration files secured and synchronised