What evidence do auditors commonly ask for on UAH-ISM-1669 Microsoft Office is blocked from injecting code into other processes?

Rule blocking Office from injecting code into other processes; Endpoint management compliance report showing the setting applied on each in-scope host.

What is the most common gap auditors find on UAH-ISM-1669?

Rule not applied to all Office versions in use

ACSC Essential Eight Maturity Model (November 2023) · User application hardening

`UAH-ISM-1669` Microsoft Office is blocked from injecting code into other processes

Microsoft Office is blocked from injecting code into other processes. Required at Maturity Levels Two and Three of the User application hardening mitigation strategy (Appendices B and C); ISM control ISM-1669 in ASD's Essential Eight to ISM mapping (December 2023).

Source: ACSC Essential Eight Maturity Model (November 2023), UAH-ISM-1669. The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open ACSC Essential Eight Maturity Model (November 2023) in the compliance library.

Each row is an ISM control the maturity model requires, with the maturity levels named in its text. Pick your target maturity level and use the rows for it.

artefacts

held by a system

at each review

easy

to go live

Endpoint management (MDM / EDR)

where the evidence lives

teal = a system already holds it · olive = produced at each review. To go live: easy when half or more of the artefacts are already held by a system, moderate from a quarter to a half, hard below a quarter.

These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.

system holds itEvidence a system already holds

Endpoint management compliance report showing the setting applied on each in-scope host · Endpoint management (MDM / EDR)

periodic reviewEvidence produced at each review

none for this control

governing documentDocuments that govern the control

Rule blocking Office from injecting code into other processes · Policy repository / GRC workspace

First move

Automate the pull from your Endpoint management (MDM / EDR). Device compliance report from the MDM (encryption, EDR agent, OS version) on a daily pull.

Common gaps auditors find

Rule not applied to all Office versions in use

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 sheet

UAH-ISM-1668 Microsoft Office is blocked from creating executable content · UAH-ISM-1670 PDF software is blocked from creating child processes