ASD ISM 1491 Block unprivileged human users from running script execution engines
What it says
Unprivileged human users are prevented from running script execution engines, including:
- Windows Script Host (cscript.exe and wscript.exe)
- PowerShell (powershell.exe, powershell_ise.exe and pwsh.exe)
- Command Prompt (cmd.exe)
- Windows Management Instrumentation (wmic.exe)
- Microsoft Hypertext Markup Language (HTML) Application Host (mshta.exe).
Quoted as published. Everything else on this page is written by Control Stack.
What it means
In plain EnglishUnprivileged human users must be blocked from running script engines, including Windows Script Host, PowerShell, Command Prompt, wmic.exe and mshta.exe, and any others on the host.
Unprivileged human users must be prevented from running script execution engines, the programs that interpret and run scripts or commands. Privileged users and non-human users, such as service accounts, are outside this control. The statement says including, so other engines on a host count too, and these are the minimum:
- Windows Script Host (cscript.exe, wscript.exe)
- PowerShell (powershell.exe, powershell_ise.exe, pwsh.exe)
- Command Prompt (cmd.exe)
- Windows Management Instrumentation (wmic.exe)
- Microsoft HTML Application Host (mshta.exe)
Free. Save your status, tasks and notes.
Why it matters
A malicious file or link can use these engines to run commands with the access of whoever opened it, with nothing to install. Blocking them for unprivileged human users takes that route away from the everyday accounts that read email and browse the web.
How to implement
List every script engine on your hosts.
Start with the named files, including 32-bit copies, then search workstations and servers for others, such as Python, Perl or a Linux shell, because the statement's list is not complete.
Find what runs in users' own context today.
Use application control audit mode and command line logs (ISM-1889) to catch logon scripts, shortcuts and business applications that call these engines. Move that work to computer startup scripts or a non-human account, so it no longer runs as the user.
Block the engines for unprivileged human users.
Use application control deny rules scoped to those users' groups, in a tool that supports per-user rules, matching signed publisher details or hash rather than a path, so renamed copies stay blocked. Microsoft's blocklist (ISM-1544) omits cmd.exe and powershell.exe, and the 'Don't run specified Windows applications' policy only covers programs File Explorer starts.
Test each engine from an unprivileged test account.
Try each named file in 32-bit and 64-bit form, a renamed copy and a portable PowerShell download, on a workstation and on any server these users log on to. Fix whatever runs.
Handle anyone who asks to keep an engine.
The statement has no exception, so a developer or support role's need is a known shortfall until closed. Where the work is administration, use a dedicated privileged account (ISM-0445). A bought application that calls an engine as the user needs a vendor fix or a non-human account.
Evidence and audit
- Check 1 of 3What an auditor asks for
Ask for
A live test from a test account set up as an unprivileged human user, on sampled workstations and servers chosen from an independent asset list.
Look at
Attempts to run cscript.exe, wscript.exe, powershell.exe, powershell_ise.exe, pwsh.exe, cmd.exe, wmic.exe and mshta.exe, in 32-bit and 64-bit form and as a renamed copy.
Good evidence
Every attempt is blocked, including the 32-bit forms and renamed copies, and no engine runs for the test account. A recorded need for an engine does not change this result.
- Check 2 of 3What an auditor asks for
Ask for
A search of the same hosts for other script engines, such as Python or Perl, and the application control rules that apply to them.
Look at
Whether each engine found is blocked for unprivileged human users.
Good evidence
Every script engine found is blocked for unprivileged human users, not only the ones the statement names.
- Check 3 of 3What an auditor asks for
Look at
Any script engine run under an unprivileged human account, and whether the test attempts were recorded.
Good evidence
The test attempts appear as blocked events, so the logging works, and no script engine ran under an unprivileged human account in the period.
Mappings
Closest match in ASD Essential Eight: E8-AC-ML1.3, Ensure only approved applications and scripts can run, which this control partially meets.
ISO/IEC 27001: 1 mapping
This control partially overlaps A.8.18.
Annex A 8.18 requires restricting and tightly controlling utility programs that can override system and application controls, addressing misuse of powerful tools on operational systems. ISM-1491 relates by preventing unprivileged users from running script execution engines (e.g. PowerShell, cmd.exe, wmic.exe) that can function as utilities to bypass intended controls and install or execute unauthorised code. However, Annex A 8.18 focuses on tight control of override-capable utilities across all users and contexts, while ISM-1491 is specifically scoped to unprivileged users and a defined set of scripting/execution engines.
ASD Essential Eight: 4 mappings
This control partially meets E8-AC-ML1.3.
ISM-1491 requires organisations to block unprivileged users from running specific script execution engines such as PowerShell, cmd.exe, wmic.exe, mshta.exe and Windows Script Host. E8-AC-ML1.3 requires application control that restricts executables and scripts (including compiled HTML and HTML applications) to an approved set, which is a broader mechanism that can include blocking these engines. ISM-1491 is effectively a specific, named set of deny controls that can be implemented as part of the broader allowlisting requirement in E8-AC-ML1.3.
This control partially overlaps E8-AC-ML1.1.
ISM-1491 requires organisations to technically prevent unprivileged users from launching specific script execution engines (e.g. PowerShell, cmd.exe, wmic.exe, mshta.exe and Windows Script Host). E8-AC-ML1.1 requires application control on workstations, which can be implemented to block those same executables for standard users. E8-AC-ML1.1 is broader (covers general application allowlisting/denylisting) while ISM-1491 is a specific prohibition focused on script execution engines and unprivileged users.
This control partially overlaps E8-AH-ML3.3.
ISM-1491 requires organisations to prevent unprivileged users from running PowerShell (and other script execution engines) at all. E8-AH-ML3.3 requires PowerShell to use Constrained Language Mode, which limits what PowerShell can do rather than blocking it outright. The controls overlap in addressing PowerShell abuse, but ISM-1491 is stricter (deny execution) while E8-AH-ML3.3 is a hardening constraint that may still permit some PowerShell use.
This control supports E8-AC-ML1.2.
ISM-1491 requires organisations to prevent standard users from launching key script execution engines that are commonly abused for execution. E8-AC-ML1.2 applies application control to user profiles and temporary folders, reducing the likelihood that users can run scripts or dropped binaries from common writeable paths even if an engine is available. E8-AC-ML1.2 does not itself mandate blocking the listed engines, but it strengthens the effectiveness of ISM-1491 by constraining common execution locations.
Mappings show how controls relate across frameworks. They do not imply full equivalence or certification.




