PSS-10 Software Defined Networking
Where the service offers software defined networking, keep customer data confidential through suitable SDN procedures, validate the networking functions before releasing new ones or modifying existing ones, and assess an
4
artefacts
2
held by a system
1
at each review
easy
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
- Defect records showing risk oriented remediation decisions · Cloud console / configuration management
- Configuration evidence of isolation between customer virtual networks · Cloud console / configuration management
periodic reviewEvidence produced at each review
- Validation test results for a new or modified networking feature · Source control / CI pipeline
governing documentDocuments that govern the control
- Design documentation for tenant separation within the software defined network · Policy repository / GRC workspace
First move
Automate the pull from your Cloud console / configuration management. Configuration snapshots and change history from the cloud console or IaC repository, diffed against the baseline.
Common gaps auditors find
- Tenant isolation assumed from the underlying platform vendor and never tested
- Networking features shipped without validating the separation they affect
- Traffic separation defects triaged as functional bugs rather than security issues
- Overlay separation in place while management plane traffic remains shared
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 sheetPSS-09 Authorisation Mechanisms · PSS-11 Images for Virtual Machines and Containers