Ensure Windows PowerShell 2.0 is disabled or removed
Disable or remove Windows PowerShell 2.0 to enhance security.
🏛️ Framework
ASD Essential Eight
🧭 Control effect
Proactive
🛠️ E8 mitigation strategy
Application hardening
🔐 Classifications
N/A
🗓️ Official last update
N/A
✏️ Control Stack last updated
22 Feb 2026
🎯 E8 maturity levels
ML3
Windows PowerShell 2.0 is disabled or removed.
Source: ASD Essential Eight
Plain language
Disabling or removing Windows PowerShell 2.0 helps protect your systems from attackers who might exploit weaknesses in this outdated software version. It reduces the risk of malicious software and hackers using old PowerShell features to cause harm.
Why it matters
If PowerShell 2.0 remains enabled, attackers can use the legacy engine to evade modern script logging and security controls, increasing compromise risk.
Operational notes
Audit Windows Features/optional components and GPO to confirm PowerShell 2.0 is removed/disabled and only newer PowerShell versions are in use.
Implementation tips
- System Administrator: Identify all systems running PowerShell 2.0 across your organisation by using asset management tools that list installed software.
- IT Team: Remove PowerShell 2.0 from identified systems by using the 'Turn Windows features on or off' settings in the Control Panel, ensuring newer versions of PowerShell remain available.
- System Administrator: Ensure that scripts and tools compatible with newer PowerShell versions are used by updating any business processes reliant on PowerShell 2.0.
- Security Officer: Communicate the removal or disabling of PowerShell 2.0 to all staff, explaining the security benefits and providing guidance on using newer PowerShell versions.
- IT Team: Set up automated updates for PowerShell to make sure the platform remains up-to-date, leveraging configuration management tools like Group Policy.
Audit / evidence tips
-
Ask: Can you confirm that Windows PowerShell 2.0 is no longer in use on your systems?
-
Good: There is no listing for PowerShell 2.0 in the installed features; only newer versions are active
-
Ask: How has the organisation confirmed the removal of PowerShell 2.0?
-
Good: Reports demonstrate that procedures were implemented and completed to remove PowerShell 2.0 from all systems
Cross-framework mappings
How E8-AH-ML3.2 relates to controls across ISO/IEC 27001, Essential Eight, and ASD ISM.
These mappings show relationships between controls across frameworks. They do not imply full equivalence or certification.
ASD ISM
| Control | Notes | Details |
|---|---|---|
| Partially meets (2) | ||
| ISM-1247 | E8-AH-ML3.2 requires organisations to disable or remove Windows PowerShell 2.0 | |
| ISM-1470 | E8-AH-ML3.2 requires organisations to disable or remove Windows PowerShell 2.0 specifically | |
| Partially overlaps (2) | ||
| ISM-1246 | ISM-1246 requires server applications to be hardened with ASD and vendor guidance, applying the most restrictive guidance where conflicts... | |
| ISM-1655 | E8-AH-ML3.2 requires organisations to disable or remove Windows PowerShell 2.0 to reduce attack surface and weaken common living-off-the-... | |
| Supports (2) | ||
| ISM-1584 | E8-AH-ML3.2 requires organisations to disable or remove Windows PowerShell 2.0 | |
| ISM-1622 | ISM-1622 requires PowerShell to use Constrained Language Mode to reduce capability available to scripts and interactive sessions | |
| Related (5) | ||
| ISM-0380 | ISM-0380 requires unneeded operating system accounts, components, services and functionality to be disabled or removed | |
| ISM-1409 | ISM-1409 requires operating systems to be hardened in accordance with ASD and vendor hardening guidance, applying the most restrictive gu... | |
| ISM-1621 | E8-AH-ML3.2 requires organisations to ensure Windows PowerShell 2.0 is disabled or removed to reduce exposure to legacy scripting abuse | |
| ISM-1798 | ISM-1798 requires producing and providing secure configuration guidance (hardening/loosening) for consumers | |
| ISM-1858 | ISM-1858 requires IT equipment to be hardened in accordance with ASD and vendor guidance, prioritising the most restrictive requirements | |