# ISO/IEC 27001:2022 A.8.18 — Use of privileged utility programs - Source: https://support.icompaas.com/compliance/iso-27001-2022/a-8-18-use-of-privileged-utility-programs - Section: [Compliance](https://support.icompaas.com/compliance) › [ISO/IEC 27001:2022 Annex A Controls](https://support.icompaas.com/compliance/iso-27001-2022) › Technological controls - Last updated: 2026-06-05 - Publisher: iCompaas, Inc. (https://www.icompaas.com) **ISO/IEC 27001:2022**·Annex A `A.8.18`·high·Component: **Technological controls** ## What this control requires > The use of utility programs that can be capable of overriding system and application controls shall be restricted and tightly controlled. > > — ISO/IEC 27001:2022, Annex A A.8.18 ### In plain English The use of utility programs that can be capable of overriding system and application controls shall be restricted and tightly controlled. In practice, this means you can prove you policy management-level controls on a defined cadence. ## Why it matters ISO 27001 certification depends on showing each Annex A control is either implemented or explicitly justified for exclusion in the Statement of Applicability (SoA). Certification bodies sample controls during surveillance audits, and a missing SoA entry — or implementation that doesn't match the SoA wording — is a finding. This control is rated **high**. Auditors expect a named owner, a remediation SLA, and a tooling artefact that evidences continuous operation. ## What an auditor looks for An ISO 27001 lead auditor looks for: (1) an SoA entry covering the control with justification, (2) a documented procedure or policy implementing it, (3) records that prove the procedure runs (logs, tickets, training records) and (4) management-review evidence that effectiveness is monitored. Within **Technological controls**, the assessor will trace your implementation back to the catalogue reference (Annex A A.8.18) and look for objective evidence on the latest two assessment cycles. ## How to implement #### Policy Management **Docs.** Keep each policy in version-controlled Markdown alongside the code that implements it; ship a signed PDF snapshot at each annual review and link the SHA into the SoA. ### Operational checklist - **Policy.** Document the trigger, the owner and the cadence. - **Management.** Document the trigger, the owner and the cadence. - **Access.** Document the trigger, the owner and the cadence. - **Application.** Document the trigger, the owner and the cadence. - **Change.** Document the trigger, the owner and the cadence. - **Scope:** management, utility. ## Evidence to collect - **Infra Scan.** Continuous infrastructure-posture telemetry — AWS Config, Azure Policy compliance, GCP Organisation Policy, Wiz / Prisma findings. - **Ticketing Workflow.** `ticketing_workflow` evidence Infrastructure compliance tooling (AWS Config, Azure Policy) and change-management workflows (ServiceNow, Jira) demonstrate restrictions on privileged utility programs. ## Common pitfalls - Policies that no engineer has read; the version in Confluence drifts from the version that's actually being enforced. ## How it maps to other frameworks Computed from shared tags, control component and key-operation subjects — handy when you are reconciling controls across an audit. - [**SOC 2 (2017 TSC) CC3.4** — Change Identification](https://support.icompaas.com/compliance/soc-2-trust-services-criteria/cc3-4-change-identification) - [**NIST SP 800-171 Rev. 3 3.5.1** — User Identification and Authentication](https://support.icompaas.com/compliance/nist-sp-800-171-rev-3/3-5-1-user-identification-and-authentication) - [**HIPAA (45 CFR Part 164) 164.308(a)(5)(i)** — Security Awareness and Training](https://support.icompaas.com/compliance/hipaa/164-308-a-5-i-security-awareness-and-training) - [**CIS Controls v8 6.1** — Establish an Access Granting Process](https://support.icompaas.com/compliance/cis-controls-v8/6-1-establish-an-access-granting-process) - [**NIST SP 800-53 Rev. 5 AC-17(4)** — Privileged Commands And Access](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/ac-17-4-privileged-commands-and-access) ## Related controls in ISO/IEC 27001:2022 - [**Annex A A.8.32** — Change management](https://support.icompaas.com/compliance/iso-27001-2022/a-8-32-change-management) - [**Annex A A.8.11** — Data masking](https://support.icompaas.com/compliance/iso-27001-2022/a-8-11-data-masking) - [**Annex A A.8.6** — Capacity management](https://support.icompaas.com/compliance/iso-27001-2022/a-8-6-capacity-management) - [**Annex A A.8.14** — Redundancy of information processing facilities](https://support.icompaas.com/compliance/iso-27001-2022/a-8-14-redundancy-of-information-processing-facilities) - [**Annex A A.8.19** — Installation of software on operational systems](https://support.icompaas.com/compliance/iso-27001-2022/a-8-19-installation-of-software-on-operational-systems) - [**Annex A A.5.11** — Return of assets](https://support.icompaas.com/compliance/iso-27001-2022/a-5-11-return-of-assets) ## References - [ISO/IEC JTC 1/SC 27 — ISO/IEC 27001:2022](https://www.iso.org/standard/27001) - Catalogue identifier: `Annex A A.8.18` Topics: privileged accessgovernance riskchange managementpolicy management ## Related compliance guidance - [ISO/IEC 27001:2022 compliance: a practical implementation guide](https://support.icompaas.com/compliance/iso-27001-2022): Start with the full ISO 27001 implementation guide — scope, roadmap, evidence and how the assessment runs. - [SOC 2 compliance: a practical implementation guide for cloud-native SaaS teams](https://support.icompaas.com/compliance/soc-2-trust-services-criteria): Most companies that hold ISO 27001 also need a SOC 2 report for North American customers, and the two share most of their technical controls.