CM.L2-3.4.8 Application Execution Policy
Operate a software execution policy, either deny by exception blocking of unauthorized software or permit by exception allowing only authorized software.
3
artefacts
0
held by a system
1
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
- Maintained allow or deny list and its review records · Cloud console / configuration management
governing documentDocuments that govern the control
- Documented decision on which policy approach is used · Policy repository / GRC workspace
- Application control configuration implementing that policy · 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
- Policy chosen but deployed in audit mode only
- Lists never maintained after initial deployment
- Coverage limited to a subset of endpoints
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 sheetCM.L2-3.4.7 Nonessential Functionality · CM.L2-3.4.9 User-Installed Software