MACRO-ML3 Configure Microsoft Office Macro Settings (ML3)
All ML2 requirements plus: Only Microsoft Office macros running from within a sandboxed environment, a Trusted Location or that are digitally signed by a trusted publisher are allowed to execute. Microsoft Office macros
8
artefacts
1
held by a system
4
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
- GPO 'Disable Trust Bar Notification for unsigned application add-ins' and trusted publisher policy export · Policy repository / GRC workspace
periodic reviewEvidence produced at each review
- Macro code review checklist and sample reviewed macros with reviewer sign-off · Source control / CI pipeline
- Annual review record of trusted publisher list with additions, removals and approver · Document repository
- Documented sandboxed macro environment (Application Guard, Windows Sandbox, virtualised execution) for any non-signed legitimate use · Cloud console / configuration management
- User awareness evidence: how end users request a new macro signed · HR system / LMS
governing documentDocuments that govern the control
- Macro signing certificate inventory with issuance, expiry, owner and HSM storage evidence · Policy repository / GRC workspace
- Policy enforcing V3 (SHA-2) signatures only with downlevel signatures blocked · Policy repository / GRC workspace
- Trusted Locations list with NTFS ACLs showing only macro reviewers have write access · Document repository
First move
Mostly documents and reviews. Pull the 1 system-held artefact from your Policy repository / GRC workspace on a schedule; put the documents under version control with an owner and review date, and log each review as a dated record with a named reviewer.
Common gaps auditors find
- Macro reviewers and developers are the same people, no separation of duties
- Trusted Locations have inherited write permissions from Domain Users
- V3 signature enforcement bypassed because legacy add-ins still in use
- Trusted publisher list not reviewed annually, includes retired vendors
- Macro code review is informal, no signed evidence of review
- Sandbox option not implemented, leading to mass-signing of operational macros
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 sheetMACRO-ML2 Configure Microsoft Office Macro Settings (ML2) · MFA-ML1 Multi-Factor Authentication - Maturity Level 1