COS-06 Segregation of data traffic in jointly used network environments
Segregate the traffic of different cloud customers in shared network environments at network level following a documented segregation concept, so transmitted data retains its confidentiality and integrity between tenants
4
artefacts
1
held by a system
1
at each review
moderate
to go live
Cloud console / configuration management
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
- Network configuration listing the per-tenant identifiers currently in use · Cloud console / configuration management
periodic reviewEvidence produced at each review
- Test results demonstrating traffic cannot pass between two tenant segments · Source control / CI pipeline
governing documentDocuments that govern the control
- Documented tenant segregation concept for shared network environments · Policy repository / GRC workspace
- Controls preventing a retired tenant identifier from being handed to another customer · Policy repository / GRC workspace
First move
Start with the 1 of 4 artefacts that already live in a system (Cloud console / configuration management); keep the periodic reviews but log each one as a dated record with a named reviewer.
Common gaps auditors find
- Separation depends on application logic rather than measures taken at network level
- Identifiers recycled after decommissioning, allowing traffic to surface in the wrong tenant
- A shared services segment lets tenants observe one another's traffic
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-05 Networks for administration · COS-07 Documentation of the network topology