COS-02 Security requirements for connections in the Cloud Service Provider's network
Design, publish and issue binding connection requirements stating when security zones separate and customers are segregated, which protocols and communication relationships are permitted, how administration and monitorin
4
artefacts
1
held by a system
0
at each review
moderate
to go live
SIEM / log platform
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
- Design showing administration and monitoring traffic carried on distinct paths · SIEM / log platform
periodic reviewEvidence produced at each review
none for this control
governing documentDocuments that govern the control
- Published connection requirement document listing permitted protocols for each zone · Policy repository / GRC workspace
- Communication matrix defining allowed source and destination pairings · Policy repository / GRC workspace
- Provisions governing site-to-site and cross-network communication · Policy repository / GRC workspace
First move
Start with the 1 of 4 artefacts that already live in a system (SIEM / log platform); keep the periodic reviews but log each one as a dated record with a named reviewer.
Common gaps auditors find
- Requirements describe zones in general terms without naming the protocols allowed in them
- Administrative traffic carried on the same segment as production payload flows
- Interconnections built by engineering teams with no reference back to the stated requirements
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-01 Technical safeguards · COS-03 Monitoring of connections in the Cloud Service Provider's network