Cookies on this site. Help us understand what works and improve your experience. Essential cookies keep the site working. With your permission, our visit insights and Google Analytics measure usage, and Google Ads measures advertising. Optional cookies are not required to use the free kit. Change your choice anytime in Cookie settings. Privacy policyCookie policy
Restrict and control use of utility programs that can override system or application controls.
Is it mandatory? Not automatically. You must consider this control in your Statement of Applicability (6.1.3 d). Include it if your risk assessment, laws, contracts or business needs require it; if you exclude it, write down a justification an auditor will accept.
Why this control matters
Privileged utility programs can bypass normal control paths, so misuse often appears as legitimate administration unless access, installation, and logging are tightly managed. Utilities should be approved, restricted to named roles, monitored in use, and removed or reclassified when they are no longer needed in production.
Common auditor findings to check for
Potential gaps to test in your own environment, not a claim about observed audit frequency.
Powerful diagnostic or recovery tools are installed on servers without approval, creating a path to bypass access controls or alter files invisibly.
Administrators share utility accounts or local admin rights, so the organization cannot attribute who used a tool or why it was launched.
Tool use is not logged centrally, leaving no evidence to review when a utility changes configuration, exports data, or disables safeguards.
How you can implement it
Tools and review intervals are examples; choose them according to risk, obligations and your operating environment.
Create a controlled inventory of privileged utilities by platform and purpose: backup recovery tools, database editors, packet capture tools, password reset utilities, and script runners. The asset owner or system custodian should approve each tool, justify need, and define whether use is permanent, temporary, or break-glass only.
Limit installation and execution through allow-listing, application control, or packaging rules. Administration rights should be granted only to the roles that need them, with step-up authentication for sensitive tools. Keep a procedure for emergency use that requires post-event review, so urgent access still leaves a traceable trail.
Log tool execution with enough detail to reconstruct actions: username, device, command or module, start and end time, target system, and reason code. Reconcile logs with change tickets and maintenance windows, because a utility used during approved work should still be explainable if later questioned.
Review privileged utilities during software installation and access recertification. Confirm that obsolete tools are removed, vendor support tools are disabled outside maintenance, and locally stored executables are approved or blocked. Feed repeated misuse, missing approvals, or unexplained launches into corrective action and stronger privileged access governance.
What an auditor will ask to see
Approved privileged utility inventory with owner, purpose, and permitted platforms.
Application control or allow-list rules blocking unapproved admin tools.
Execution logs or endpoint telemetry showing who ran each privileged utility and when.
Change ticket or emergency access record linking tool use to an authorized task.
Baseline documents in the kit
These free kit documents help you document or evidence A.8.18. Each one is tailored to your organization when you build your kit.
Use the SIG and CAIQ questionnaire accelerator to find supporting documents. A mapping is a starting point: verify your actual operating evidence before answering a buyer.
For help adapting this to your environment, explore ISO/IEC 27001 consulting, starting with a free one-hour consultation.
Get these documents tailored to your organization
109 ready-to-edit documents, including all 19 mandatory ones, tailored from a short scoping questionnaire and linked to your risk register and SoA.