PSS-01 Guidelines and Recommendations for Cloud Customers
Publish and keep current secure use guidance for customers on the productive service version, pitched at their security, compliance and audit specialists, covering secure configuration, vulnerability and update informati
4
artefacts
1
held by a system
0
at each review
moderate
to go live
Source control / CI pipeline
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
- Published secure configuration guidance matching the current production release · Source control / CI pipeline
periodic reviewEvidence produced at each review
none for this control
governing documentDocuments that govern the control
- Defined list of the topics the guidance must cover and their content owners · Document repository
- Version comparison showing guidance updated alongside a service release · Policy repository / GRC workspace
- Guidance section describing rights combinations that create elevated risk · Document repository
First move
Start with the 1 of 4 artefacts that already live in a system (Source control / CI pipeline); keep the periodic reviews but log each one as a dated record with a named reviewer.
Common gaps auditors find
- Guidance describes a superseded release and references settings that no longer exist
- Privileged administration functions left out of the guidance entirely
- Material written for end users rather than for security and audit specialists
- No pointer given to sources of vulnerability and update information
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 sheetPS-07 Surveillance of operational and environmental parameters · PSS-02 Identification of Vulnerabilities of the Cloud Service