UAH-ISM-1623 PowerShell module logging, script block logging and transcription events are centrally logged
PowerShell module logging, script block logging and transcription events are centrally logged. Required at Maturity Levels Two and Three of the User application hardening mitigation strategy (Appendices B and C); ISM control ISM-1623 in ASD's Essential Eight to ISM mapping (December 2023).
Source: ACSC Essential Eight Maturity Model (November 2023), UAH-ISM-1623. 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.
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
- Sample events in the log platform · SIEM / log platform
periodic reviewEvidence produced at each review
none for this control
governing documentDocuments that govern the control
- Central logging of PowerShell module logging, script block logging and transcription · Policy repository / GRC workspace
First move
Common gaps auditors find
- Script block logging enabled but not forwarded
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 sheetUAH-ISM-1622 PowerShell is configured to use Constrained Language Mode · UAH-ISM-1654 Internet Explorer 11 is disabled or removed