A.8 Technological controls

A.8.19 Installation of software on operational systems

Not mandatory by default – decided in your SoA

What it means in plain language

Control software installation on operational systems.

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

Uncontrolled software installation often starts with a helpful shortcut: local admin access, ad hoc vendor tools, or a rushed fix outside normal change control. Teams can explain how requests are evaluated against an approved software list, licensing terms, compatibility, and security risk before deployment. It also supports traceable exceptions when business need is real but the installation route must stay constrained.

Common auditor findings to check for

Potential gaps to test in your own environment, not a claim about observed audit frequency.

  • Installations occur through informal support actions without recorded approval, creating unclear accountability and weak traceability for operational systems.
  • The approved software list is outdated or incomplete, so staff can install tools that bypass compatibility, licence, or malware checks.
  • Evidence does not show who reviewed elevated installation requests, what risk criteria were applied, or when removal happens for unapproved software.

How you can implement it

Tools and review intervals are examples; choose them according to risk, obligations and your operating environment.

  • Define a request path owned by IT operations or endpoint management: user need, business justification, package source, device scope, and installation method must be logged before deployment. Include checks for admin rights, endpoint hardening, licensing, and compatibility with managed build baselines so installs occur through controlled channels only.
  • Assign approval roles clearly: line manager confirms business need, information security reviews higher-risk or internet-sourced tools, and the service desk or MDM administrator performs the install. Use separate handling for emergency cases, with retrospective review and a short-lived record of why the exception was accepted.
  • Keep an approved software catalogue with version constraints, permitted sources, and forbidden categories such as unsigned installers or consumer remote-access tools. Review the catalogue after new vulnerabilities, major platform changes, or business platform rollouts, and record delisted software with removal dates and affected assets.
  • Capture practical evidence: request ticket, approval comments, package hash or source URL, deployment log from software centre or MDM, and post-install validation result. Where removal is required, record the decommission action, user notification, and confirmation that residual shortcuts, services, or scheduled tasks were cleared.

What an auditor will ask to see

  • Software Installation Procedure showing request criteria, approval thresholds, emergency exception handling, and removal steps.
  • Approved software list with owner, version limits, permitted deployment channel, and review date.
  • MDM or software centre deployment log linking device ID, package name, installer source, and completion timestamp.
  • Sample ticket with business justification, approval trail, and post-install validation note from endpoint support.

Baseline documents in the kit

These free kit documents help you document or evidence A.8.19. Each one is tailored to your organization when you build your kit.

Connect this work to your ISMS

Review the dependencies with A.8.9 — Configuration management and A.8.18 — Use of privileged utility programs. Keep the ownership and evidence consistent across these activities.

Required information and the kit’s 19-document core for the wider implementation context.

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.

Start free

Plain-language interpretation by an ISO/IEC 27001 lead implementer, not the official text of ISO/IEC 27001:2022.