Skip to content
Technological controls
ISO 27001A.8.18

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.

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

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

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

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

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

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

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

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

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

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

Essential Eight

ASD Essential Eight: 5 mappings

ASD ISM

ASD Information Security Manual: 6 mappings

ASD Essentials

ASD Essentials for enterprise IT: 2 mappings

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.