GS-4 Define and implement network security strategy
Define and implement a network security strategy with documented guidance, policy and standards covering network design, segmentation, perimeter controls and monitoring.
4
artefacts
0
held by a system
1
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
none for this control
periodic reviewEvidence produced at each review
- Periodic review record · Cloud console / configuration management
governing documentDocuments that govern the control
- Network security strategy document and its approval · Policy repository / GRC workspace
- Reference network designs derived from it · Policy repository / GRC workspace
- Policy and standards covering segmentation and perimeter controls · Policy repository / GRC workspace
First move
This control is evidenced by people and documents, not systems. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date. Do not try to automate it.
Common gaps auditors find
- network patterns decided per workload with no reference design
- strategy exists but no standard makes it enforceable
- no review after major architecture change
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 sheetGS-3 Define and implement data protection strategy · GS-5 Define and implement security posture management strategy