UAH-ISM-1621 Windows PowerShell 2.0 is disabled or removed
Windows PowerShell 2.0 is disabled or removed. Required at Maturity Level Three of the User application hardening mitigation strategy (Appendix C); ISM control ISM-1621 in ASD's Essential Eight to ISM mapping (December 2023).
Source: ACSC Essential Eight Maturity Model (November 2023), UAH-ISM-1621. 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
- Endpoint management compliance report showing the setting applied on each in-scope host · Endpoint management (MDM / EDR)
periodic reviewEvidence produced at each review
- Evidence Windows PowerShell 2.0 is disabled or removed · Cloud console / configuration management
governing documentDocuments that govern the control
none for this control
First move
Common gaps auditors find
- PowerShell 2.0 engine still installed allowing downgrade
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-1585 Web browser security settings cannot be changed by users · UAH-ISM-1622 PowerShell is configured to use Constrained Language Mode