Skip to content
System hardening
ASD ISMISM-1491

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 English

Unprivileged 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)

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

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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.

Keep it running

Repeat the test after new software, operating system or PowerShell upgrades and any application control change, since each can add or move an engine. Blocking does not replace ISM-1622 (Constrained Language Mode) or ISM-1623 (PowerShell logging), which still apply to other use.

Evidence and audit

  1. 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.

  2. 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.

  3. Check 3 of 3What an auditor asks for

    Ask for

    Central command line and application control logs for a recent period (ISM-1889, ISM-1660), including the test attempts above.

    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 27001

ISO/IEC 27001: 1 mapping

  • A.8.18Use of privileged utility programsPartially overlaps
Essential Eight

ASD Essential Eight: 4 mappings

Mappings show how controls relate across frameworks. They do not imply full equivalence or certification.