Skip to content
Technological controls
ISO 27001A.8.9

ISO 27001 Annex A 8.9 Configuration management

What it says

Configurations, including security configurations, of hardware, software, services and networks shall be established, documented, implemented, monitored and reviewed.

Quoted as published. Everything else on this page is written by Control Stack.

In plain English

Establish, document, implement, monitor and review configurations, including security configurations, of hardware, software, services and networks.

Your organisation must establish, document, implement, monitor and review configurations, including security configurations, of hardware, software, services and networks. Configurations are the settings that decide how something behaves. All five actions are required:

  • Establish: decide the required settings.
  • Document: write them down.
  • Implement: set systems that way.
  • Monitor: compare actual settings with the required ones.
  • Review: check that the settings are still right, and correct any that are not.

Why it matters

Default passwords, unneeded services and unapproved changes leave gaps that nobody sees until they are used. Defined, monitored configurations show when a system has drifted from what was approved, and help keep hardware, software, services and networks working with the settings they need.

How to implement

  1. Write a standard template for each type of system.

    Start from vendor or independent hardening guides (lists of secure settings), then adjust for your risks and policies. Cover administrator accounts, unused accounts and services, default passwords, clock settings and automatic log-off. Include cloud services and network devices as well as servers and laptops. Name an owner for each template.

  2. Build new systems from the templates and bring existing ones into line.

    Use standard images, build scripts, infrastructure as code (settings kept as version-controlled files) or device management tools. Record any setting that cannot follow the template, with the reason and who approved it.

  3. Record each configuration and log every change.

    Use a configuration database (a central record of settings) or version-controlled templates, showing the owner, date of last change and template version. Send changes through change management (Annex A 8.32). Restrict who can read and edit these records, because they show how systems are set up.

  4. Monitor live settings against the templates.

    Use a configuration scanner, management console or cloud security posture tool (which checks cloud settings) to find drift (unapproved differences), then enforce the template automatically or correct it by hand. For a bought service, monitor the admin settings it exposes. Where a provider manages the rest, get its configuration or assurance reports.

  5. Review templates and live settings on a period you set.

    Base the period on your risks. Also review when a new version arrives or a new threat or vulnerability needs a different setting. Check administrator numbers, password settings and exceptions that have outlived their reason, and record the outcome.

Keep it running

Revisit a template when a new version ships, a new threat or vulnerability calls for a different setting, or monitoring keeps flagging the same drift. Close exceptions once their reason has gone.

Evidence and audit

  1. Check 1 of 5What an auditor asks for

    Ask for

    The template list, compared with the asset inventory.

    Look at

    Whether each type of hardware, software, service and network device has a template, with cloud services and network devices the usual gaps.

    Good evidence

    Every type in the inventory has a dated template that includes security settings, or a recorded reason for not having one.

  2. Check 2 of 5What an auditor asks for

    Ask for

    Live settings exported from a sample of devices, cloud services and network equipment.

    Look at

    Each setting compared line by line with its template, including unused services, plus a log-on attempt or scanner result for default passwords.

    Good evidence

    Live settings match the template, no default password works, and each difference has a recorded, approved exception.

  3. Check 3 of 5What an auditor asks for

    Ask for

    Recent changes found by a drift report or system audit trail, traced to the change log.

    Look at

    Whether changes made on systems appear in the configuration log and have a change record, working from system to log rather than log to system.

    Good evidence

    Every sampled change on a system traces to a log entry and an approved change record.

  4. Check 4 of 5What an auditor asks for

    Ask for

    A harmless, unapproved setting change on a monitored test system.

    Look at

    Whether monitoring detects it, who is told and how quickly it is reversed.

    Good evidence

    Monitoring flags the test change to the owner, and it is reversed or formally approved.

  5. Check 5 of 5What an auditor asks for

    Ask for

    The last template review, compared with recent product versions and vulnerabilities.

    Look at

    Whether a new version or a relevant vulnerability prompted an update, and whether the period your organisation set was kept.

    Good evidence

    Reviews happened on the period your organisation set and after the latest major version, with the outcome recorded.

Mappings

Closest match in ASD Essential Eight: E8-AH-ML1.4, Prevent users from changing web browser security settings, which this control covers in full and more.

Essential Eight

ASD Essential Eight: 7 mappings

ASD ISM

ASD Information Security Manual: 76 mappings

ASD Essentials

ASD Essentials for enterprise IT: 7 mappings

Mappings show how controls relate across frameworks. They do not imply full equivalence or certification.

Get help with this control

ISO 27001 training

Mindset Cyber, a PECB Authorised Titanium Partner, sells official PECB ISO/IEC 27001 courses that map directly to the controls in this library.