A.8 Technological controls

A.8.9 Configuration management

Not mandatory by default – decided in your SoA

What it means in plain language

New in 2022: define, apply and monitor secure configurations (hardening baselines) for hardware, software, services and networks.

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

The Configuration Management Procedure should define how secure baselines are selected, approved, deployed, and monitored across systems, services, and network devices. Focus on the practical failure points: inconsistent hardening, undocumented overrides, and configuration drift after urgent changes. Reviewers often need to see who owns each baseline, how exceptions are approved, and how the organization detects when actual settings no longer match the intended standard.

Common auditor findings to check for

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

  • Secure baselines exist in theory, but servers and cloud services run different settings because no one owns review and revalidation after platform changes.
  • Administrators apply local fixes directly on systems, creating drift from approved templates; change records do not show what was altered or why.
  • Monitoring tools report configuration deviations, but alerts are not triaged consistently, so exceptions can persist beyond their intended expiry or business justification.

How you can implement it

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

  • Define baseline ownership for each platform family, such as workstation, server, network, database, and cloud service. The owner should approve minimum settings, review exception requests, and confirm periodic revalidation after operating system updates, new service releases, or business-driven changes. Store the baseline as documented information with version history.
  • Use controlled deployment methods such as infrastructure as code, golden images, or hardened templates. Require peer review for changes to templates and maintain a clear approval trail linking the change to the risk decision. This reduces ad hoc drift and makes it easier to demonstrate that deployed configurations match approved intent.
  • Operate drift detection and exception handling together. Configure tools to compare live settings against the baseline, route deviations to a named owner, and record whether the issue was fixed, accepted temporarily, or formally exempted. Each exception should include scope, rationale, expiry, compensating measures, and approval authority.
  • Keep implementation evidence practical and specific: baseline documents, template repositories, change tickets, drift reports, and validation checks after patching or provisioning. Useful records include a hardened build checklist, a sample server comparison report, and sign-off showing that a privileged change was tested before deployment to production.

What an auditor will ask to see

  • Configuration Management Procedure with platform owners, exception handling, and review frequency.
  • Approved hardening baseline or template for a server, cloud service, or network device.
  • Drift detection report showing deviations, owner assignment, and closure status.
  • Change record or pull request demonstrating peer review and controlled baseline update.

Baseline documents in the kit

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

Connect this work to your ISMS

Review the dependencies with A.8.1 — User endpoint devices and A.8.32 — Change management. 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.