1.2.3 Network diagrams maintained
An accurate network diagram is maintained showing all connections between the CDE and other networks.
5
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
- Annual review sign-off · Cloud console / configuration management
governing documentDocuments that govern the control
- Current network diagram with version date · Policy repository / GRC workspace
- Mapping of all ingress and egress points · Policy repository / GRC workspace
- Wireless network locations marked · Policy repository / GRC workspace
- Third-party connections labelled · Vendor register / contract repository
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
- Diagrams not updated after changes
- Missing wireless or cloud segments
- No CDE boundary indicated
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.2 Changes to NSC reviewed and approved · 1.2.4 Data flow diagram of account data