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

UAH-ISM-1860 PDF software is hardened using ASD and vendor hardening guidance, with the most restrictive guidance taking…

PDF software is hardened using ASD and vendor hardening guidance, with the most restrictive guidance taking precedence when conflicts occur. Required at Maturity Levels Two and Three of the User application hardening mitigation strategy (Appendices B and C); ISM control ISM-1860 in ASD's Essential Eight to ISM mapping (December 2023).

Source: ACSC Essential Eight Maturity Model (November 2023), UAH-ISM-1860. 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.

2
artefacts
1
held by a system
0
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

  • PDF software hardening baseline from ASD and vendor guidance · Vendor register / contract repository

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

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-1859 Office productivity suites are hardened using ASD and vendor hardening guidance, with the most restrictive… · UAH-ISM-1889 Command line process creation events are centrally logged