COS-03 Monitoring of connections in the Cloud Service Provider's network
Separate trusted from untrusted networks into risk-based security zones, configure physical and virtual networks to restrict and monitor those connections, reassess that design at least annually, and periodically re-just
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
- Firewall and virtual network rule bases with evidence of their latest review · Cloud console / configuration management
- Annual assessment report on the connection monitoring conception and configuration · SIEM / log platform
governing documentDocuments that govern the control
- Zone model distinguishing trusted, untrusted and any demilitarised areas · Policy repository / GRC workspace
- Register of services, ports and protocols carrying current business justifications · 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
- Rule bases still carrying permissive any-to-any entries left over from migration work
- Annual assessment limited to physical networking and omitting virtualised overlays
- Insecure protocols retained with compensating measures asserted verbally but never written down
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-02 Security requirements for connections in the Cloud Service Provider's network · COS-04 Cross-network access