IVS-08 Network Architecture Documentation
Identify high-risk environments and document them in the network architecture record.
4
artefacts
0
held by a system
0
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
none for this control
governing documentDocuments that govern the control
- Network architecture documentation with high-risk environments identified · Policy repository / GRC workspace
- The criteria that define a high-risk environment · Policy repository / GRC workspace
- Evidence the documentation is current against the deployed architecture · Policy repository / GRC workspace
- Controls applied specifically to the identified environments · 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
- Architecture documentation that predates the current environment
- High risk asserted with no criteria behind it
- Environments identified as high risk with no differentiated control
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 sheetIVS-07 Migration to Cloud Environments · IVS-09 Network Defense