1.2.1 NSC configuration standards defined
Configuration standards for network security controls are defined, implemented, and maintained.
5
artefacts
2
held by a system
0
at each review
moderate
to go live
Ticketing / ITSM
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
- Change tickets approving deviations · Ticketing / ITSM
- Version-controlled config repository · Source control / CI pipeline
periodic reviewEvidence produced at each review
none for this control
governing documentDocuments that govern the control
- Firewall configuration standard document · Policy repository / GRC workspace
- Sample running configurations matching standard · Policy repository / GRC workspace
- Baseline comparison reports · Policy repository / GRC workspace
First move
Start with the 2 of 5 artefacts that already live in a system (Ticketing / ITSM); keep the periodic reviews but log each one as a dated record with a named reviewer.
Common gaps auditors find
- Standard exists but devices drift
- No evidence of approval workflow
- Standards do not cover all device types
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.1.2 Roles and responsibilities for Requirement 1 · 1.2.2 Changes to NSC reviewed and approved