AM-5 Use only approved applications in virtual machine
Ensure only authorised software executes in virtual machines by maintaining an allow list and blocking unauthorised software from running.
4
artefacts
1
held by a system
0
at each review
moderate
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
- Enforcement mode configuration and its coverage · Cloud console / configuration management
periodic reviewEvidence produced at each review
none for this control
governing documentDocuments that govern the control
- Application allow list definition per workload role · Policy repository / GRC workspace
- Blocked execution events and their triage · Document repository
- Process for adding software to the allow list · Document repository
First move
Start with the 1 of 4 artefacts that already live in a system (Cloud console / configuration management); keep the periodic reviews but log each one as a dated record with a named reviewer.
Common gaps auditors find
- allow listing deployed in audit mode only
- list built once from a running system so existing unauthorised software is baked in
- no route to add legitimate software so the control gets disabled
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 sheetAM-4 Limit access to asset management · BR-1 Ensure regular automated backups