ISO 27001 Annex A 8.18 Use of privileged utility programs
What it says
The use of utility programs that can be capable of overriding system and application controls shall be restricted and tightly controlled.
Quoted as published. Everything else on this page is written by Control Stack.
In plain English
Restrict and tightly control the use of utility programs that can override system and application controls, such as debuggers and backup or diagnostic tools.
Your organisation must restrict and tightly control the use of utility programs that can override system and application controls. Utility programs are tools for maintaining or diagnosing a system, such as debuggers and backup or network tools. Both duties apply:
- Restricted: only the people and systems that need such a program have it.
- Tightly controlled: your organisation decides when and how each use happens, and can see it afterwards.
Annex A 8.2 limits privileged access rights. Here the limit is on the programs themselves.
Free. Save your status, tasks and notes.
Why it matters
A debugger, diagnostic or backup tool can read or change data without passing the checks an application enforces, so anyone able to run one can sidestep those controls. Limiting who runs them and controlling each use narrows that route and makes misuse easier to see.
How to implement
Find the utility programs that can override controls.
Use software inventory reports and a scan of executable files across servers and administrator workstations. Look for debuggers and diagnostic, disk, backup, patching and network tools, including ones built into the operating system. On network devices, list diagnostic commands such as packet capture. Record where each sits and who can run it.
Remove or disable the ones you do not need.
Uninstall them, or block them with application control (rules on which programs may run) where a built-in tool cannot be removed. Keep what remains apart from application software, with its own folder and permissions, and keep these tools' network traffic apart from application traffic where practical.
Limit each remaining tool to named people and service accounts that need it.
Apply role-based permissions or application control, within your privileged access rules (Annex A 8.2). Use individual accounts, and a named owner for each service account, so each run traces to one person. Withhold tools from people whose application work requires segregation of duties (Annex A 5.3).
Require approval for use, and log every run.
Record which uses are pre-approved, and require approval for one-off use, tied to a change record where one applies (Annex A 8.32). Make the tool available only for that work. Send each run, with the account used, to your log platform (Annex A 8.15) and alert on unapproved use.
Check how providers control their own utility programs.
Where a provider manages the system, ask how it restricts and logs its tools, then check that answer against its independent assurance report or contract. Restrict any diagnostic functions or support access you can set in your own console, and record any gap you accept.
Keep it running
Re-run the scan after upgrades and new builds, because they can bring tools back. Look again when someone's role changes, when a change finishes and temporary access should end, or when a provider changes how it supports your service.
Evidence and audit
- Check 1 of 4What an auditor asks for
Ask for
The list of approved utility programs, compared with a scan of installed software and executable files on sampled servers and administrator workstations.
Look at
Tools the scan finds that are missing from the list, or that should have been removed.
Good evidence
Every tool found is on the list with a reason to keep it, and tools with no such reason are gone or disabled.
- Check 2 of 4What an auditor asks for
Ask for
A demonstration of starting a sampled tool from an ordinary account and from an account on the approved list.
Look at
Whether the ordinary account is refused, and whether copying the tool to another folder gets round the block.
Good evidence
Only accounts on the approved list can run the tool, each an individual account or a service account with a named owner, and the ordinary account is refused, including with the copied tool.
- Check 3 of 4What an auditor asks for
Ask for
Execution logs for the tools, including a run made for this check, matched to approvals and change records.
Look at
Whether each logged run names one person, or a service account with a named owner, and has an approval or a pre-approved use, and whether any run falls outside an approved change or time.
Good evidence
The run made for this check appears in the logs, and each sampled run traces to a named person, directly or through a service account's owner, and to an approval or a pre-approved use, with any run lacking these followed up.
- Check 4 of 4What an auditor asks for
Ask for
The provider's assurance report and your console's role settings for a provider-managed system.
Look at
Whether the report covers the service you use and how the provider's tools are restricted, and who holds diagnostic or support access on your side.
Good evidence
The report covers those tools for this service, or the gap is recorded and accepted, and access on your side is limited to named people.
Mappings
Closest match in ASD Essential Eight: E8-AH-ML3.3, PowerShell is configured to use Constrained Language Mode, which this control covers in full and more.
ASD Essential Eight: 5 mappings
This control is broader than E8-AH-ML3.3.
Annex A 8.18 requires restricting and tightly controlling utility programs that can override system and application controls to prevent unauthorised or unsafe changes. E8-AH-ML3.3 relates because configuring PowerShell to use Constrained Language Mode limits a powerful scripting utility that can be used to bypass controls or perform unauthorised system changes. However, Annex A 8.18 applies to utility programs generally (not just PowerShell) and is centred on restricting use, while E8-AH-ML3.3 is a specific hardening configuration for one tool.
This control partially overlaps E8-AC-ML1.3.
Annex A 8.18 requires restricting and tightly controlling utilities that can override system and application controls to prevent unauthorised changes on operational systems. E8-AC-ML1.3 implements application control so only approved applications and scripts (including installers) can run, which directly reduces the ability to execute unapproved installers or admin tools. E8-AC-ML1.3 is broader as a general execution control baseline, while Annex A 8.18 is focused on controlling powerful utility programs and their use.
This control partially overlaps E8-AC-ML2.1.
E8-AC-ML2.1 requires application control on internet-facing servers to prevent unapproved code execution. ISO/IEC 27001:2022 Annex A 8.18 restricts use of utility programs that can override system and application controls, which reduces the likelihood that application control is bypassed on those servers. E8-AC-ML2.1 is about allowlisting/enforcement, whereas A 8.18 targets administrative tools that could defeat that enforcement.
This control partially overlaps E8-AC-ML2.2.
Annex A 8.18 requires restrictions and tight control over utilities that can override system and application controls, which includes preventing unauthorised execution paths on operational systems. E8-AC-ML2.2 relates by applying application control broadly and explicitly excluding user profiles and temporary folders, reducing the ability to execute installers or utility programs from common user-writable locations. However, Annex A 8.18 is focused on controlling powerful utilities and administrative override capability, whereas E8-AC-ML2.2 is primarily about execution control coverage across filesystem locations rather than privileged utility governance.
This control partially overlaps E8-AC-ML3.2.
Annex A 8.18 requires restricting and tightly controlling utilities that can override system and application controls, which includes limiting low-level components that can change system behaviour. E8-AC-ML3.2 relates by restricting driver execution to an organisation-approved set, preventing unauthorised drivers that can bypass or undermine security controls. However, Annex A 8.18 covers a wider class of utilities and administrative tools beyond drivers, while E8-AC-ML3.2 is narrowly focused on driver execution allowlisting.
ASD Information Security Manual: 6 mappings
This control is broader than ISM-1491.
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.
This control partially overlaps ISM-0846.
Annex A 8.18 restricts and tightly controls utility programs able to override system and application controls. ISM-0846 requires that users cannot disable, bypass or be exempted from application control, except through local administrator or break glass accounts. Both bear on limiting privileged software execution, but Annex A 8.18 reaches utilities outside application control, and ISM-0846 sets a tamper resistance requirement Annex A 8.18 does not state.
This control partially overlaps ISM-1584.
ISM-1584 requires unprivileged users to be prevented from bypassing, disabling or modifying the security functionality of operating systems. Annex A 8.18 requires the use of utility programs capable of overriding system and application controls to be restricted and tightly controlled. The two meet where a utility could defeat operating system protections, but ISM-1584 covers any means of bypass and Annex A 8.18 covers utilities used by any user.
This control partially overlaps ISM-1592.
Annex A 8.18 requires that use of utility programs capable of overriding system and application controls is restricted and tightly controlled to prevent unauthorised changes on operational systems. ISM-1592 relates by ensuring unprivileged users cannot install unapproved applications, which is a practical restriction on software installation activities that could alter system state. However, Annex A 8.18 is broader in focusing on powerful utilities that can bypass controls (including administrative tools), while ISM-1592 focuses specifically on preventing user-driven installation of unapproved applications.
This control partially overlaps ISM-1657.
Annex A 8.18 requires restricting and tightly controlling use of utility programs that can override system and application controls, effectively limiting what can be installed or run with elevated capability on operational systems. ISM-1657 enforces application control so only an organisation-approved set of executables, libraries, scripts and installers can execute, which is a strong technical mechanism to prevent unauthorised software installation/execution. ISM-1657 is broader in execution control coverage, while Annex A 8.18 is specifically concerned with powerful utilities that bypass controls and the governance around their use.
This control partially overlaps ISM-1658.
Annex A 8.18 requires tight restriction of utilities capable of overriding system and application controls, which includes mechanisms that could introduce or load privileged components. ISM-1658 restricts driver execution to an approved set via application control, reducing the risk of installing/loading drivers that can subvert OS controls. ISM-1658 is specifically about drivers, whereas Annex A 8.18 covers a wider class of high-privilege utilities and administrative tools beyond drivers.
ASD Essentials for enterprise IT: 2 mappings
- IT.PRO-07.2Restrict administrative and management tools to approved sets and authorised locationsBroader than
This control is broader than IT.PRO-07.2.
IT.PRO-07.2 requires administrative and management tooling to be limited to approved software sets and run only from authorised, known locations. Such tooling largely corresponds to the utility programs capable of overriding system and application controls in Annex A 8.18, and IT.PRO-07.2 is a specific way of restricting them. Annex A 8.18 is broader, requiring tight control over how and by whom these utilities are used, not only which tools are approved and where they run from.
- IT.DET-04.1Continuously monitor software execution to detect malicious use of legitimate toolsPartially overlaps
This control partially overlaps IT.DET-04.1.
IT.DET-04.1 requires continuous monitoring and analysis of software execution behaviour to detect legitimate tools and utilities being used for malicious purposes, while Annex A 8.18 requires the use of utility programs capable of overriding system and application controls to be restricted and tightly controlled. The two meet over misuse of legitimate utilities, but IT.DET-04.1 covers detection across tools generally and Annex A 8.18 demands preventive restriction.
Mappings show how controls relate across frameworks. They do not imply full equivalence or certification.
Get help with this control
ISO 27001 training
Mindset Cyber, a PECB Authorised Titanium Partner, sells official PECB ISO/IEC 27001 courses that map directly to the controls in this library.




