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

UAH-ISM-1819 Following the identification of a cyber security incident, the cyber security incident response plan is…

Following the identification of a cyber security incident, the cyber security incident response plan is enacted. Required at Maturity Levels Two and Three of the User application hardening mitigation strategy (Appendices B and C); ISM control ISM-1819 in ASD's Essential Eight to ISM mapping (December 2023). ASD lists this event logging and incident requirement under User application hardening, so it is assessed for the events this strategy generates.

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

none for this control

periodic reviewEvidence produced at each review

  • Post-incident review report recording the plan steps taken · Cloud console / configuration management

governing documentDocuments that govern the control

  • Incident response plan activation after a script or process detection · Policy repository / GRC workspace

First move

No system holds this evidence for you: it is people and documents. Reminders and routing to the owner still save time. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date.

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-1815 Event logs are protected from unauthorised modification and deletion · UAH-ISM-1823 Office productivity suite security settings cannot be changed by users