What evidence do auditors commonly ask for on A.8.18 Use of privileged utility programs?

Statement of Applicability entry for control A.8.18, showing inclusion or justified exclusion, implementation status and the risks it treats; An inventory of utility programs capable of overriding controls on each platform, with those not needed removed or disabled; A list of authorized users and documented authorization levels for each utility; Approvals for ad hoc use and time-limited availability, for example tied to change tickets; Logs of all utility program use with unique user identification.

What is the most common gap auditors find on A.8.18?

Debuggers and database tools remain installed on production servers

ISO/IEC 27001:2022 · Technological controls

`A.8.18` Use of privileged utility programs

Utility programs able to override system and application controls are to have their use limited and tightly controlled. Purpose (stated in ISO/IEC 27002:2022): ensures utility programs do not harm system and application security controls. As an Annex A reference control, it is compared with the controls determined in risk treatment (6.1.3 c) and recorded in the Statement of Applicability as included or excluded, with the justification and implementation status (6.1.3 d); implementation guidance is ISO/IEC 27002:2022 8.18.

Source: ISO/IEC 27001:2022, A.8.18. The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open ISO/IEC 27001:2022 in the compliance library.

Clauses 4 to 10 are the management-system requirements: none of them can be excluded when an organisation claims conformity. The 93 Annex A controls are a reference set: one may be excluded with a justification in the Statement of Applicability. Certification bodies assess conformity; the evidence lists here are what auditors commonly ask for, not a list the standard prescribes.

artefacts

held by a system

at each review

moderate

to go live

Document repository

where the evidence lives

teal = a system already holds it · olive = produced at each review. To go live: easy when half or more of the artefacts are already held by a system, moderate from a quarter to a half, hard below a quarter.

These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.

system holds itEvidence a system already holds

A list of authorized users and documented authorization levels for each utility · Document repository
Logs of all utility program use with unique user identification · SIEM / log platform

periodic reviewEvidence produced at each review

Approvals for ad hoc use and time-limited availability, for example tied to change tickets · Ticketing / ITSM

governing documentDocuments that govern the control

Statement of Applicability entry for control A.8.18, showing inclusion or justified exclusion, implementation status and the risks it treats · Policy repository / GRC workspace
An inventory of utility programs capable of overriding controls on each platform, with those not needed removed or disabled · Policy repository / GRC workspace

First move

Start with the 2 of 5 artefacts that already live in a system (Document repository); keep the periodic reviews but log each one as a dated record with a named reviewer.

Common gaps auditors find

Debuggers and database tools remain installed on production servers
Utility use is not logged or not attributable to individuals
Business users with segregation of duties constraints can run administrative tools
Utilities are permanently available instead of enabled only for approved changes

Do this for your whole sheet

Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.

Build my evidence sheet

A.8.17 Clock synchronization · A.8.19 Installation of software on operational systems