1.2.2 Changes to NSC reviewed and approved
All changes to network connections and configurations of NSCs are approved and managed via the formal change control process.
5
artefacts
3
held by a system
2
at each review
easy
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
- Sample of change tickets for NSC modifications · Ticketing / ITSM
- Approver signatures or workflow logs · SIEM / log platform
- Pre and post change configuration diffs · Ticketing / ITSM
periodic reviewEvidence produced at each review
- Rollback evidence for failed changes · Ticketing / ITSM
- Change advisory board minutes · Ticketing / ITSM
governing documentDocuments that govern the control
none for this control
First move
Automate the pull from your Ticketing / ITSM. The ticket itself, with approver, timestamps and linked change or incident, exported on a schedule.
Common gaps auditors find
- Emergency changes lack retrospective approval
- Tickets missing business justification
- No technical review evidence
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.1 NSC configuration standards defined · 1.2.3 Network diagrams maintained