COS-04 Cross-network access
Control every network perimeter with security gateways, and grant cross-network system access only on the basis of a security assessment that reflects the requirements of the cloud customers concerned.
4
artefacts
0
held by a system
2
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
- Security assessment files supporting individual cross-network authorisations · Cloud console / configuration management
- Customer requirement statements captured as inputs to those assessments · Policy repository / GRC workspace
governing documentDocuments that govern the control
- Boundary diagram identifying each perimeter and the gateway enforcing it · Policy repository / GRC workspace
- Gateway policy set applied to cross-network access requests · 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
- Boundaries exist that no gateway inspects, typically newer direct interconnects
- Cross-network access permitted for operational convenience with no assessment on file
- Assessments make no reference to the requirements of customers whose data crosses the boundary
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 sheetCOS-03 Monitoring of connections in the Cloud Service Provider's network · COS-05 Networks for administration