PSS-11 Images for Virtual Machines and Containers
Where customers run virtual machines or containers, let the customer restrict which images its users may launch, inform the customer of what changed between versions of any images the provider supplies, and harden those
4
artefacts
0
held by a system
1
at each review
hard
to go live
Document repository
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
- Hardening baseline and build evidence for one provider supplied image · Cloud console / configuration management
governing documentDocuments that govern the control
- Customer facing setting restricting which images users are permitted to launch · Document repository
- Release notes describing what changed between successive provider supplied images · Policy repository / GRC workspace
- Catalogue showing the approved image set made available to a tenant · Document repository
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
- Image restriction applies in the console while other launch paths ignore it
- New image versions published with no statement of what changed
- Provider images shipped with default accounts and unnecessary services enabled
- Hardening applied at first build and not maintained across later rebuilds
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-10 Software Defined Networking · PSS-12 Locations of Data Processing and Storage