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.
Free. Save your status, tasks and notes.
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
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.
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.
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.
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.
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
- 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.
- 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.
- 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.
- 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.
- 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.
ASD Essential Eight: 7 mappings
This control is broader than E8-AH-ML1.4.
E8-AH-ML1.4 requires that web browser security settings are locked down so users cannot change them. Annex A 8.9 requires establishing, documenting, implementing, monitoring and reviewing security configurations across hardware, software, services and networks, which includes browser configuration as one component. E8-AH-ML1.4 is a specific endpoint/browser configuration constraint, whereas Annex A 8.9 is an organisation-wide configuration management requirement.
This control is broader than E8-AH-ML2.5.
E8-AH-ML2.5 requires Microsoft Office to be configured to prevent activation of OLE packages. Annex A 8.9 requires configurations (including security configurations) to be established, documented, implemented, monitored and reviewed, which is the management process needed to apply and sustain Office configuration settings. E8-AH-ML2.5 is a single hardening requirement, whereas Annex A 8.9 provides the broader configuration management framework that makes the control durable and auditable.
This control is broader than E8-AH-ML2.6.
E8-AH-ML2.6 requires implementing hardened configurations for office productivity suites based on ASD and vendor guidance. Annex A 8.9 requires configurations (including security configurations) for hardware, software, services and networks to be established, documented, implemented, monitored and reviewed, which encompasses office suite hardening as one application-specific instance. Annex A 8.9 has broader scope and stronger lifecycle expectations (monitoring/review) than the specific office-suite hardening requirement in E8-AH-ML2.6.
This control is broader than E8-AH-ML2.9.
E8-AH-ML2.9 requires hardening of PDF software using ASD and vendor guidance, with the most restrictive guidance applied in case of conflict. Annex A 8.9 requires organisations to establish, document, implement, monitor and review security configurations across hardware, software, services and networks. PDF hardening under E8-AH-ML2.9 is a specific configuration management outcome that would sit within the broader configuration management system required by Annex A 8.9.
This control is broader than E8-AH-ML3.1.
E8-AH-ML3.1 requires a specific secure configuration outcome: disabling or removing legacy .NET Framework versions to reduce the attack surface. Annex A 8.9 requires organisations to establish, document, implement, monitor, and review security configurations across hardware, software, services, and networks, which includes decisions like removing insecure/obsolete components. E8-AH-ML3.1 is a concrete, technology-specific instance of the broader configuration management discipline in Annex A 8.9.
This control is broader than E8-AH-ML3.2.
E8-AH-ML3.2 requires organisations to implement a specific secure configuration by disabling or removing Windows PowerShell 2.0. Annex A 8.9 requires configurations (including security configurations) of software to be established, documented, implemented, monitored and reviewed, which would encompass ensuring PowerShell 2.0 is not enabled. Annex A 8.9 is a general configuration management control across IT assets, while E8-AH-ML3.2 is a specific configuration hardening requirement.
This control is broader than E8-AH-ML3.3.
E8-AH-ML3.3 requires a specific security configuration: setting PowerShell to Constrained Language Mode to reduce exploitation of scripting features. Annex A 8.9 requires organisations to establish, document, implement, monitor and review security configurations across hardware, software, services and networks, which would include PowerShell configuration baselines. The ISO control is broader governance and lifecycle management, while E8-AH-ML3.3 is one concrete configuration requirement within that broader configuration management discipline.
ASD Information Security Manual: 76 mappings
This control is broader than ISM-0272.
ISM-0272 requires a secure configuration outcome: protective marking tools must not allow markings beyond the system's authorised classification handling. This maps to Annex A 8.9 (Configuration Management for Secure IT Systems) because that control governs establishing, implementing, monitoring, and reviewing security configurations for software and services, including application configuration settings that enforce security rules. Annex A 8.9 is broad configuration governance, while ISM-0272 is one specific configuration requirement focused on information marking enforcement.
This control is broader than ISM-0289.
ISM-0289 requires evaluated products to be installed, configured, administered and operated in an evaluated configuration and in accordance with vendor guidance. Annex A 8.9 requires configurations (including security configurations) for hardware, software, services and networks to be established, documented, implemented, monitored and reviewed, which overlaps with preventing configuration drift from an approved state. Annex A 8.9 is broader configuration governance across all ICT, while ISM-0289 is more specific about maintaining the product's evaluated configuration and following vendor operating guidance.
This control is broader than ISM-0290.
ISM-0290 requires high assurance IT equipment to be installed, configured, administered and operated in an evaluated configuration and in accordance with ASD guidance. Annex A 8.9 requires organisations to establish, document, implement, monitor and review security configurations across hardware, software, services and networks, which aligns with the configuration establishment and upkeep aspects of ISM-0290. ISM-0290 is narrower in asset scope (high assurance/evaluated equipment) but deeper in assurance expectations (evaluated configuration and ASD-specific operation), while Annex A 8.9 is broader across all IT systems.
This control is broader than ISM-0341.
ISM-0341 requires automatic execution features for removable media to be disabled to prevent code running when media is inserted. Annex A 8.9 requires security configurations to be established, implemented, monitored, and reviewed across systems, under which disabling AutoRun/AutoPlay for removable media is a specific configuration item. Annex A 8.9 is broader because it covers configuration management generally, while ISM-0341 is a single prescriptive hardening setting focused on removable media execution.
This control is broader than ISM-0380.
ISM-0380 requires unneeded operating system user accounts, components, services and functionality to be disabled or removed to reduce attack surface. Annex A 8.9 requires configurations (including security configurations) across hardware, software, services and networks to be established, documented, implemented, monitored and reviewed, which includes disabling/removing unnecessary OS accounts and services as a baseline hardening activity. The ISO control is broader because it covers the full configuration management lifecycle and many configuration domains beyond OS accounts/services, whereas ISM-0380 is a specific hardening outcome focused on removing unneeded OS functionality.
This control is broader than ISM-0383.
ISM-0383 requires default operating system user accounts and credentials (including pre-configured accounts) to be changed, disabled or removed during initial setup. This is a specific hardening action that fits within ISO/IEC 27001:2022 Annex A 8.9's broader requirement to establish, implement, monitor and review secure configurations for IT systems. Annex A 8.9 covers configuration management across many settings and lifecycle activities, while ISM-0383 targets a single high-risk configuration issue at build time.
This control is broader than ISM-0484.
ISM-0484 requires specific secure configuration settings for the SSH daemon, such as interface binding and authentication timeouts. Annex A 8.9 mandates that configurations for systems, services, and networks are established, documented, and reviewed, including hardening measures like SSH settings. ISM-0484 provides concrete, service-specific controls within the broader management context covered by Annex A 8.9.
This control is broader than ISM-0487.
ISM-0487 requires specific security configurations for SSH in passwordless scenarios, including disabling forwarding and limiting access from unnecessary IPs. This maps to Annex A 8.9 because these settings form a secure configuration baseline documented, implemented, monitored, and reviewed. Annex A 8.9 applies to configuration management across different platforms, not just SSH.
This control is broader than ISM-0498.
ISM-0498 requires organisations to configure IPsec security association (SA) lifetimes to less than four hours to limit cryptographic exposure and reduce the impact of key compromise. Annex A 8.9 requires security-relevant configurations for networks and services to be established, documented, implemented, monitored and reviewed, which would include IPsec parameters such as SA lifetimes where IPsec is used. The ISO control is broader because it covers configuration management across all IT components, whereas ISM-0498 is a specific configuration requirement for IPsec.
This control is broader than ISM-0518.
ISM-0518 requires organisations to keep network documentation current and available. Annex A 8.9 requires configurations of hardware, software, services and networks to be established, documented, implemented, monitored and reviewed, and network documentation from ISM-0518 provides the baseline context (topology, interfaces, dependencies) needed to document and review network configurations. Annex A 8.9 is broader because it mandates configuration controls and monitoring beyond documentation alone.
This control is broader than ISM-0567.
ISM-0567 requires email servers to be configured so they only relay emails destined for or originating from the organisation's own domains (including subdomains), preventing open relay misuse. ISO/IEC 27001:2022 Annex A 8.9 requires configuration management across IT systems, under which implementing and maintaining secure mail transfer agent (MTA) relay restrictions is a concrete configuration baseline item. Annex A 8.9 is broader (covering all system configurations and their governance), while ISM-0567 is a specific mail-server configuration requirement.
This control is broader than ISM-0570.
ISM-0570 requires that any backup or alternative email gateways are maintained to the same security and operational standard as the primary email gateway. Annex A 8.9 requires configurations (including security configurations) across hardware, software, services and networks to be established, documented, implemented, monitored and reviewed, which would explicitly include both primary and standby email gateway services. ISM-0570 is a specific parity requirement for one critical service path (email gateways), whereas Annex A 8.9 is an organisation-wide configuration management expectation that would drive that parity through baselines, change control and ongoing review.
This control is broader than ISM-0864.
ISM-0864 requires mobile devices to lock down security settings so users cannot disable or modify security functionality after provisioning. ISO/IEC 27001:2022 Annex A 8.9 requires configurations (including security configurations) to be established, implemented, monitored and reviewed across hardware, software, services and networks. ISM-0864 is one concrete configuration management outcome (preventing unauthorised local change on mobile devices), while Annex A 8.9 is broader and includes governance, documentation, monitoring and review across many technology domains.
This control is broader than ISM-1027.
ISM-1027 requires organisations to configure email distribution list applications used by external senders to ensure the sender's DKIM signature remains valid. This relates to Annex A 8.9, which encompasses configuration management across IT systems, as maintaining DKIM validity is part of secure email service configuration. ISM-1027 is more specific because it focuses solely on preserving mail-flow/DKIM outcomes for distribution lists, whereas A 8.9 covers broader configuration management needs.
This control is broader than ISM-1037.
ISM-1037 requires gateways to be tested after configuration changes and at least every six months to confirm they conform to expected security configurations. Annex A 8.9 requires organisations to establish, document, implement, monitor and review security configurations across hardware, software, services and networks, which would include gateways and the need to verify configuration state. ISM-1037 is a specific verification/testing cadence applied to gateways, whereas Annex A 8.9 is broader configuration management across the environment without prescribing a six-month test interval.
This control is broader than ISM-1055.
ISM-1055 requires a specific security configuration: disabling LAN Manager and NT LAN Manager authentication methods. Annex A 8.9 requires organisations to establish, document, implement, monitor and review security configurations across hardware, software, services and networks, under which disabling insecure authentication protocols is a typical baseline setting. Annex A 8.9 is broader because it covers configuration management as a discipline, while ISM-1055 is one concrete configuration item within that discipline.
This control is broader than ISM-1183.
ISM-1183 requires an organisation to publish and use hard fail SPF DNS records to specify which email servers are authorised to send for its domains (including subdomains). Annex A 8.9 requires configurations (including security configurations) for services and networks to be established, documented, implemented, monitored and reviewed, which can include DNS and email authentication settings such as SPF. ISM-1183 is one specific security configuration outcome within the broader configuration management lifecycle mandated by Annex A 8.9.
This control is broader than ISM-1196.
ISM-1196 mandates a specific security configuration state for mobile devices: Bluetooth must be undiscoverable except during pairing. Annex A 8.9 requires organisations to establish, document, implement, monitor and review security configurations across hardware, software, services and networks, which would include enforcing Bluetooth discoverability settings via configuration management/MDM baselines. ISM-1196 is a single prescriptive configuration requirement, while Annex A 8.9 is the overarching process control for managing such configurations.
This control is broader than ISM-1260.
ISM-1260 requires default server application accounts and credentials to be changed, disabled or removed as part of initial setup. This directly aligns with Annex A 8.9 because changing default accounts/credentials is a concrete configuration baseline requirement for applications and systems. Annex A 8.9 is broader, covering establishment, documentation, monitoring and review of configurations across hardware, software, services and networks, whereas ISM-1260 is one specific secure configuration requirement.
This control is broader than ISM-1272.
ISM-1272 requires a specific configuration state for database servers, where the DBMS is set to not accept remote connections unless needed, or to listen only on localhost. Annex A 8.9 mandates that configurations for systems, services, and networks (including security configurations) be established, implemented, and monitored. This encompasses the DBMS configuration as detailed in ISM-1272, serving as an instance of secure configuration.
This control is broader than ISM-1304.
ISM-1304 demands that default accounts or credentials on network devices be changed, disabled, or removed at initial setup. Annex A 8.9 calls for security configurations across hardware, software, services, and networks to be established, documented, implemented, monitored, and reviewed, often including baseline hardening like removing default device credentials. Annex A 8.9 offers a wider scope in configuration governance and monitoring, whereas ISM-1304 focuses specifically on a single device hardening step.
This control is broader than ISM-1311.
ISM-1311 mandates that organisations ensure SNMP version 1 and 2 are not used on networks. Annex A 8.9 deals with configurations (including security configurations) of networks and services to be established, implemented, monitored, and reviewed. This includes configuring network devices to use only secure SNMP versions (e.g., SNMPv3) or disabling SNMP. Annex A 8.9 is broader as it applies to all configuration items and security settings, not just SNMP.
This control is broader than ISM-1312.
ISM-1312 requires a specific secure configuration outcome for SNMP on network devices (non-default community strings and no write access). Annex A 8.9 requires security configurations for hardware, software, services and networks to be established, documented, implemented, monitored and reviewed, which encompasses enforcing secure SNMP configuration baselines. ISM-1312 is one prescriptive configuration requirement within the broader configuration management framework of Annex A 8.9.
This control is broader than ISM-1316.
ISM-1316 requires that default SSIDs are changed on wireless access points as part of secure configuration. Annex A 8.9 requires configurations of hardware, software, services and networks to be established, documented, implemented, monitored and reviewed. ISM-1316 is a specific configuration baseline requirement for wireless networks that sits within Annex A 8.9's broader configuration management lifecycle.
This control is broader than ISM-1319.
ISM-1319 requires organisations to avoid static IP addressing on wireless networks as a specific configuration choice to reduce risk. Annex A 8.9 requires configurations (including security configurations) of networks to be established, documented, implemented, monitored and reviewed, under which the organisation would define and enforce DHCP versus static addressing standards for wireless segments. ISM-1319 is a prescriptive configuration baseline item, while Annex A 8.9 is a broader configuration management control covering governance and lifecycle management.
This control is broader than ISM-1406.
ISM-1406 requires organisations to use SOEs for workstations and servers to ensure consistent, secure configurations. Annex A 8.9 requires configuration management across hardware, software, services and networks, including establishing, documenting, monitoring and reviewing configurations. An SOE is a specific configuration baseline and deployment approach within a broader configuration management regime, so ISM-1406 is a concrete subset of what Annex A 8.9 expects.
This control is broader than ISM-1408.
ISM-1408 requires organisations to use 64-bit versions of operating systems. This directly relates to ISO/IEC 27001:2022 Annex A 8.9 because selecting and enforcing a 64-bit OS standard is a defined security configuration decision that should be established as part of the organisation's secure configuration baseline and applied consistently. Annex A 8.9 is broader as it requires a managed lifecycle for configurations (document, implement, monitor, review) across many technology types, whereas ISM-1408 is one specific baseline requirement within that configuration set.
This control is broader than ISM-1409.
ISM-1409 requires organisations to implement hardened operating system configurations using ASD and vendor guidance, applying the most restrictive requirements where they conflict. Annex A 8.9 is broader because it requires configuration management across hardware, software, services and networks, including establishing, documenting, monitoring and reviewing configurations. ISM-1409 fits within Annex A 8.9 as a specific application of configuration management to OS hardening baselines and precedence rules.
This control is broader than ISM-1428.
ISM-1428 mandates a specific secure configuration setting: IPv6 tunnelling is disabled unless needed. This maps to ISO/IEC 27001:2022 Annex A 8.9 because the tunnelling setting is part of establishing, documenting, implementing, monitoring and reviewing security configurations for networks and network devices. Annex A 8.9 covers the full configuration management lifecycle for all technologies, whereas ISM-1428 is a single prescriptive configuration control.
This control is broader than ISM-1489.
ISM-1489 requires Microsoft Office macro security settings to be centrally enforced and locked against user changes. Annex A 8.9 requires organisations to establish, document, implement, monitor and review secure configurations across IT systems, which is the governance mechanism used to define and maintain those locked macro settings. Annex A 8.9 is broader configuration management, while ISM-1489 is a specific hardening requirement within that configuration baseline.
This control is broader than ISM-1552.
Annex A 8.9 requires the configurations of hardware, software, services and networks, security settings included, to be established, documented, implemented, monitored and reviewed. ISM-1552 fixes one of those settings, requiring all web application content to be offered exclusively using HTTPS so that nothing is served in the clear. Annex A 8.9 covers every configured asset and the documenting, monitoring and review that keep settings correct over time, where ISM-1552 states a single required outcome for web content.
This control is broader than ISM-1562.
ISM-1562 requires hardening of video conferencing and IP telephony infrastructure through secure configurations. Annex A 8.9 requires configurations of hardware, software, services and networks to be established, documented, implemented, monitored and reviewed, which is the overarching practice used to harden VoIP/video platforms and their components. ISM-1562 focuses that configuration management discipline specifically on conferencing/telephony systems.
This control is broader than ISM-1585.
ISM-1585 requires web browser security settings to be centrally enforced such that human users cannot change them. ISO/IEC 27001:2022 Annex A 8.9 requires secure configurations to be established, implemented, monitored and reviewed across hardware, software, services and networks, which includes browser configuration baselines and enforcement mechanisms. ISM-1585 is a specific configuration-hardening outcome for browsers, while Annex A 8.9 is broader and covers configuration management governance and lifecycle controls beyond browsers.
This control is broader than ISM-1588.
ISM-1588 requires organisations to review and update Standard Operating Environments (SOEs) at least annually. Annex A 8.9 requires configurations (including security configurations) across hardware, software, services and networks to be established, documented, implemented, monitored and reviewed, which includes reviewing endpoint/server baseline builds such as SOEs. ISM-1588 is a specific, time-bound subset focused on SOE baseline currency, whereas Annex A 8.9 is broader and applies to configuration management across many technology types and configurations beyond SOEs.
This control is broader than ISM-1598.
ISM-1598 requires IT equipment to be inspected after maintenance or repair to confirm it still matches the approved configuration and has no unauthorised modifications. Annex A 8.9 requires configurations for hardware, software, services and networks to be established, documented, implemented, monitored and reviewed, which provides the baseline and governance that post-maintenance inspection validates against. ISM-1598 is a specific checkpoint/control activity within a broader configuration management lifecycle described by Annex A 8.9.
This control is broader than ISM-1604.
ISM-1604 requires a hardened configuration for the software-based isolation mechanism, including removing unneeded functionality and restricting administrative interface access. Annex A 8.9 requires configurations (including security configurations) across hardware, software, services and networks to be established, documented, monitored and reviewed, which encompasses hypervisor configuration baselines and reviews. ISM-1604 is a specific configuration hardening requirement for virtualisation isolation, whereas Annex A 8.9 covers configuration management lifecycle controls broadly.
This control is broader than ISM-1605.
ISM-1605 requires the operating system underlying a software-based isolation mechanism that consumes shared physical computing resources to be hardened. Annex A 8.9 requires configurations, including security configurations, of hardware, software, services and networks to be established, documented, implemented, monitored and reviewed. Hardening that host operating system is one specific case within the wider configuration scope of Annex A 8.9.
This control is broader than ISM-1622.
ISM-1622 mandates a particular security configuration for a specific technology (PowerShell Constrained Language Mode). Annex A 8.9 requires security configurations for hardware, software, services and networks to be established, documented, implemented, monitored and reviewed. ISM-1622 fits within Annex A 8.9 as a single configuration requirement, while Annex A 8.9 also covers governance, documentation and monitoring across all system configurations.
This control is broader than ISM-1627.
Annex A 8.9 requires the configurations of hardware, software, services and networks, security settings among them, to be established, documented, implemented, monitored and reviewed. ISM-1627 names one of those network settings, blocking inbound connections that arrive from anonymity networks. Annex A 8.9 extends to every other device and service in the estate and to keeping each configuration documented, monitored and reviewed, while ISM-1627 asks for a single rule on inbound traffic.
This control is broader than ISM-1669.
ISM-1669 requires Microsoft Office to be blocked from injecting code into other processes. ISO/IEC 27001:2022 Annex A 8.9 is broader, requiring organisations to establish, document, implement, monitor and review security configurations across systems. ISM-1669 is a specific configuration requirement that would sit within an Annex A 8.9 configuration management program.
This control is broader than ISM-1673.
ISM-1673 requires implementing a specific security configuration: blocking Win32 API calls from Microsoft Office macros. ISO/IEC 27001:2022 Annex A 8.9 requires establishing, documenting, implementing, monitoring and reviewing system configurations in general, including security configurations. ISM-1673 is a single, prescriptive configuration item that would sit within the broader configuration management discipline required by Annex A 8.9.
This control is broader than ISM-1710.
ISM-1710 requires wireless access points to be hardened by changing insecure default settings and applying secure configuration. Annex A 8.9 requires organisations to establish, document, implement, monitor and review secure configurations across hardware, software, services and networks, which includes wireless access points as a specific asset class. ISM-1710 is a more specific, technology-scoped instantiation of the broader configuration management requirement in Annex A 8.9.
This control is broader than ISM-1806.
ISM-1806 requires default user accounts and credentials in user applications to be changed, disabled, or removed during initial setup. Annex A 8.9 requires organisations to establish, document, implement, monitor and review configuration (including security configuration) across systems and services, which would include removing or changing default credentials as a baseline configuration task. ISM-1806 is a specific configuration hardening requirement focused on initial credential state, whereas Annex A 8.9 is broader lifecycle configuration management.
This control is broader than ISM-1823.
ISM-1823 requires locking down office productivity suite security settings so users cannot change them. Annex A 8.9 requires configuration management across IT systems, including establishing, implementing, monitoring and reviewing security configurations for hardware, software, services and networks. ISM-1823 is a specific configuration control within the broader ISO configuration management discipline described by Annex A 8.9.
This control is broader than ISM-1824.
ISM-1824 requires preventing user changes to PDF application security settings, ensuring a fixed secure configuration for that application. Annex A 8.9 requires configuration management to establish, document, implement, monitor and review security configurations across hardware, software, services and networks. ISM-1824 is a specific configuration enforcement instance within the wider configuration management discipline of Annex A 8.9.
This control is broader than ISM-1825.
ISM-1825 requires that users cannot change the security settings of security products, preserving the intended secure state. Annex A 8.9 requires organisations to establish, document, implement, monitor and review configurations (including security configurations) across hardware, software, services and networks. ISM-1825 is a specific configuration control mechanism (immutability to users) within the broader configuration management program required by Annex A 8.9.
This control is broader than ISM-1828.
ISM-1828 requires the Print Spooler service to be disabled specifically on Microsoft AD DS domain controllers to reduce attack surface. This relates to Annex A 8.9 because disabling a high-risk service on a defined system role is a concrete security configuration that should be established, documented, implemented, monitored and reviewed under configuration management. Annex A 8.9 is broader and covers the governance and lifecycle of configurations across all systems, while ISM-1828 is a single prescriptive hardening setting for domain controllers.
This control is broader than ISM-1832.
ISM-1832 requires that only service accounts and computer accounts are configured with Service Principal Names (SPNs) in Active Directory. This relates to Annex A 8.9 because restricting which accounts can hold SPNs is a specific security configuration standard that should be established, documented, implemented, monitored, and reviewed. Annex A 8.9 is broader as it covers configuration management across all IT components, not just AD SPN assignment.
This control is broader than ISM-1834.
ISM-1834 requires organisations to maintain a correct Active Directory configuration state by preventing or remediating duplicate SPNs, which are a security-relevant directory configuration attribute. Annex A 8.9 requires configurations (including security configurations) for services and systems to be established, documented, monitored and reviewed, which would include managing and validating AD service-account/SPN configuration baselines. ISM-1834 is one concrete configuration check/control point inside the broader configuration management discipline mandated by Annex A 8.9.
This control is broader than ISM-1838.
ISM-1838 requires a specific security configuration outcome in AD: the UserPassword attribute for user accounts is not used. This is a direct, prescriptive instance of Annex A 8.9 because Annex A 8.9 requires organisations to establish, document, implement, monitor and review security configurations across systems, and ISM-1838 is one concrete security configuration that would be managed within that configuration management regime. Annex A 8.9 is broader and process-oriented across all hardware, software, services and networks, while ISM-1838 is a single AD attribute hardening requirement.
This control is broader than ISM-1860.
ISM-1860 requires hardening of PDF applications using ASD and vendor guidance, prioritising the most restrictive settings. Annex A 8.9 requires security configurations for hardware, software, services and networks to be established, documented, implemented, monitored and reviewed. ISM-1860 is a specific instance of configuration management focused on one application class (PDF applications) and does not on its own cover the full lifecycle governance elements (e.g. monitoring/review) across all assets.
This control is broader than ISM-1887.
ISM-1887 requires a particular security configuration on mobile devices: remote locate and wipe must be enabled and usable. ISO/IEC 27001:2022 Annex A 8.9 requires configurations (including security configurations) for hardware, software, services and networks to be established, documented, implemented, monitored and reviewed. ISM-1887 fits as a concrete configuration requirement within the wider configuration management regime described by Annex A 8.9.
This control is broader than ISM-1888.
Annex A 8.9 covers establishing, documenting, implementing, monitoring and reviewing configurations across hardware, software, services and networks. ISM-1888 sits inside that scope as one specific configuration requirement, namely that mobile devices carry secure password-based lock screens. Mobile lock screen settings such as timeout and PIN complexity are among the many configurations Annex A 8.9 governs.
This control is broader than ISM-1912.
Annex A 8.9 requires organisations to document and maintain configurations for systems and to keep them under review. ISM-1912 relates by requiring network documentation to include device settings for critical/high-value servers and key network/security devices, a form of configuration documentation. ISM-1912 focuses on specific asset classes, while Annex A 8.9 also requires establishing/implementing configurations and monitoring/reviewing them over time.
This control is broader than ISM-1913.
ISM-1913 requires approved configurations for IT equipment to be developed, implemented and maintained. Annex A 8.9 similarly requires configurations (including security configurations) for hardware, software, services and networks to be established, documented, implemented, monitored and reviewed. Both controls cover the configuration lifecycle and the expectation of ongoing maintenance and governance of secure baselines.
This control is broader than ISM-1914.
Annex A 8.9 requires secure configurations to be established and managed across IT systems. ISM-1914 aligns by requiring approved configurations for operating systems to be developed, implemented and maintained. ISM-1914 is limited to operating systems, while Annex A 8.9 spans OS, applications, hardware, services and networks and explicitly includes monitoring and review.
This control is broader than ISM-1915.
ISM-1915 requires approved configurations for user applications to be developed, implemented, and maintained. Annex A 8.9 addresses configurations for hardware, software, services, and networks to be established, documented, implemented, monitored, and reviewed, which includes user applications. It implies a broader ICT configuration management with monitoring and review, beyond the user application focus of ISM-1915.
This control is broader than ISM-1916.
Annex A 8.9 requires secure configurations to be established, documented, implemented, monitored and reviewed across IT assets. ISM-1916 maps to this by requiring approved configurations for server applications to be developed, implemented and maintained. ISM-1916 is a specific subset focused only on server applications, whereas Annex A 8.9 covers all hardware, software, services and networks plus ongoing monitoring/review.
This control is broader than ISM-1926.
ISM-1926 mandates a hardened configuration baseline for AD-related servers by restricting them to their designed roles. Annex A 8.9 requires configuration management to be established, documented, implemented, monitored, and reviewed across hardware, software, services, and networks, including server roles and installed components. Annex A 8.9 is broader and process-oriented, while ISM-1926 is a specific configuration requirement for high-value servers.
This control is broader than ISM-1931.
ISM-1931 requires SID Filtering to be enabled on domain and forest trusts to prevent abuse of SIDHistory/foreign SIDs across trust boundaries. Annex A 8.9 mandates organisations to establish secure configurations across systems and networks, which includes configuring Active Directory trusts securely. ISM-1931 specifies a technical configuration requirement within the broader configuration management expectations of Annex A 8.9.
This control is broader than ISM-1935.
ISM-1935 mandates that Active Directory computer accounts are not configured for unconstrained delegation, a specific security measure to prevent credential abuse. Annex A 8.9 covers the establishment and review of secure configurations for systems, which broadly includes the configuration of AD accounts. ISM-1935 fits as a specific requirement within the broader configuration management scope of Annex A 8.9.
This control is broader than ISM-1944.
ISM-1944 requires a specific secure configuration on Microsoft AD CS certification authorities by removing the EDITF_ATTRIBUTESUBJECTALTNAME2 flag to prevent requester-supplied SAN injection. Annex A 8.9 requires organisations to establish, document, implement, monitor and review secure configurations across IT systems, which would include AD CS CA configuration baselines and hardening. ISM-1944 is a single, product-specific hardening requirement, whereas Annex A 8.9 is a broad configuration management capability covering many platforms and settings.
This control is broader than ISM-1951.
ISM-1951 requires a specific security configuration: hard match takeover must be disabled on Microsoft Entra Connect servers. Annex A 8.9 (Configuration management) relates because it requires security configurations to be established, implemented, monitored and reviewed, which would include enforcing and validating the Entra Connect setting addressed by ISM-1951. ISM-1951 is a single-purpose configuration requirement, while Annex A 8.9 is a broad control covering configuration governance across hardware, software, services and networks.
This control is broader than ISM-2127.
ISM-2127 requires the operating system to enforce kernel-mode driver digital signature verification before any driver is loaded and to prevent that enforcement being bypassed. Annex A 8.9 requires organisations to establish, document, implement, monitor and review secure configurations across hardware, software, services and networks, which explicitly includes OS security configuration baselines and hardening settings. ISM-2127 is therefore a specific secure configuration setting within the broader configuration management lifecycle of Annex A 8.9, with Annex A 8.9 also covering governance and ongoing monitoring/review that ISM-2127 does not specify.
This control is broader than ISM-2130.
ISM-2130 requires organisations to disable AD CS web enrolment interfaces unless required, and if enabled, to harden them by enforcing HTTPS and Extended Protection for Authentication. Annex A 8.9 broadly requires secure configuration management across hardware, software, services and networks, including establishing, documenting, implementing, monitoring, and reviewing configurations. ISM-2130 is a specific secure-configuration requirement for a Microsoft PKI component, while Annex A 8.9 is a broader governance and lifecycle control that includes managing and assuring that hardening state.
This control is broader than ISM-2131.
ISM-2131 requires certificate templates to be reviewed at least quarterly to identify and remediate misconfigurations that could enable privilege escalation or unauthorised certificate enrolment. This directly fits within ISO/IEC 27001:2022 Annex A 8.9 because certificate template settings are a security-relevant configuration that should be established, monitored and reviewed. Annex A 8.9 is broader (covers configurations across hardware, software, services and networks), while ISM-2131 is a specific, time-bound review requirement focused on AD CS template misconfiguration risks.
This control is broader than ISM-2161.
ISM-2161 requires the integrity of network device firmware and running configurations to be verified against an approved known-good baseline following patching, on detection of anomalous behaviour and at least monthly. Annex A 8.9 covers establishing, documenting, implementing, monitoring and reviewing configurations of hardware, software, services and networks. The checks in ISM-2161 fall inside that wider configuration scope of Annex A 8.9.
This control is broader than ISM-2162.
ISM-2162 requires disabling or removing unneeded network device components and services as a secure configuration outcome. ISO/IEC 27001:2022 Annex A 8.9 requires configurations of hardware, software, services and networks to be established, documented, implemented, monitored and reviewed, which would include removing/disabling unnecessary network device services. Annex A 8.9 is broader because it covers the full configuration management lifecycle and all IT assets, whereas ISM-2162 focuses specifically on eliminating unnecessary network device functionality.
This control is broader than ISM-2167.
ISM-2167 requires organisations to disable MACsec's Pre-Shared Key (PSK) fallback authentication so links cannot silently downgrade to a weaker static secret. Annex A 8.9 requires security-relevant configurations for networks and devices to be established, documented, implemented, monitored and reviewed, which is the governance mechanism used to enforce settings like disabling PSK fallback on MACsec-capable equipment. Annex A 8.9 is broader and process-oriented, while ISM-2167 is a specific technical configuration requirement for MACsec authentication behaviour.
This control partially overlaps ISM-0042.
ISM-0042 requires organisations to develop, implement and maintain effective system administration practices and procedures for managing systems. Annex A 8.9 requires configuration management to be established, documented, implemented, monitored and reviewed, which is a core administrative discipline that operationalises consistent system builds and ongoing control. Annex A 8.9 is deeper and more prescriptive about configuration baselines and monitoring, while ISM-0042 is broader across multiple administration domains beyond configuration management alone.
This control partially overlaps ISM-0589.
Annex A 8.9 requires configurations of hardware, software, services and networks to be established, documented, implemented, monitored and reviewed. ISM-0589 stops multifunction devices from being used to scan or copy documents above the sensitivity or classification of the networks they connect to. Both bear on device settings, but Annex A 8.9 governs configuration generally, while ISM-0589 sets one classification limit on multifunction device use.
This control partially overlaps ISM-0912.
Annex A 8.9 requires configurations of hardware, software, services and networks to be established, documented, implemented, monitored and reviewed. ISM-0912 directly relates by mandating a formal change and configuration management plan including authorised baselines, change classification and governance. While ISM-0912 is more focused on change process mechanics, Annex A 8.9 covers the full configuration lifecycle.
- ISM-1211System administration performed under change and configuration management planPartially overlaps
This control partially overlaps ISM-1211.
ISM-1211 requires system administrators to carry out system administration activities in line with an established change and configuration management plan. ISO/IEC 27001:2022 Annex A 8.9 requires configurations for hardware, software, services and networks to be established, documented, implemented, monitored and reviewed, which is the configuration-management discipline that the ISM-1211 plan would define and administrators would follow. Annex A 8.9 asks for configuration baselines and ongoing review, which ISM-1211 does not, while ISM-1211 binds administrators to the plan as they work, which Annex A 8.9 does not.
This control partially overlaps ISM-1608.
ISM-1608 requires third-party SOEs to be checked for insecure or non-compliant configurations (as well as malicious code) before they are adopted. This overlaps with ISO/IEC 27001:2022 Annex A 8.9, which requires configurations for hardware, software, services, and networks to be established, documented, implemented, monitored, and reviewed across the environment. Both address configuration correctness, but ISM-1608 is specifically an acceptance/ingestion control for externally provided SOE builds, whereas Annex A 8.9 is a lifecycle governance control that extends to internal builds and ongoing monitoring/review rather than a one-off acceptance gate.
This control supports ISM-0516.
ISM-0516 requires network documentation to include high-level and logical network diagrams showing all connections and all critical components (e.g. critical servers and security appliances). Annex A 8.9 requires configurations of networks and related components to be established and documented, which is strengthened by having accurate network diagrams as part of the documented network configuration baseline. Annex A 8.9 is broader (covering the full configuration management lifecycle), while ISM-0516 is specifically about diagrammatic network documentation for critical components.
This control supports ISM-1798.
ISM-1798 requires publishing secure configuration guidance so consumers can securely configure the software. Annex A 8.9 requires configurations (including security configurations) to be established, documented, implemented, monitored and reviewed. ISM-1798 supports Annex A 8.9 by providing the vendor/developer guidance that helps an organisation document and implement secure baseline configurations, but Annex A 8.9 additionally covers ongoing monitoring and review which ISM-1798 does not.
ASD Essentials for enterprise IT: 7 mappings
- IT.PRO-04.1Define approved hardening baselines disabling unneeded services, insecure settings and weak protocolsBroader than
This control is broader than IT.PRO-04.1.
IT.PRO-04.1 requires approved configuration baselines, informed by vendor and industry hardening guidance, that disable or remove unnecessary services, insecure settings, and unsupported or weak communication protocols. This is a specific implementation of establishing and documenting secure configurations under Annex A 8.9. Annex A 8.9 is broader, also requiring configurations of hardware, software, services and networks to be implemented, monitored and reviewed.
- IT.PRO-04.2Deploy approved configuration baselines on systems, including infrastructure, operating systems and applicationsBroader than
This control is broader than IT.PRO-04.2.
IT.PRO-04.2 requires approved configuration baselines to be deployed on systems, including infrastructure, operating systems and applications. This is the implementation step of the configuration management required by Annex A 8.9. Annex A 8.9 is broader, also requiring configurations to be established, documented, monitored and reviewed.
- IT.PRO-04.3Detect and respond to configuration drift using scheduled assessments and monitoringBroader than
This control is broader than IT.PRO-04.3.
IT.PRO-04.3 requires configuration drift to be detected and responded to through scheduled technical assessments and, where supported, automated monitoring, scaled to system criticality and change rate. This directly implements the monitoring and review elements of Annex A 8.9 by checking that hardware, software, services and networks still match their established security configurations. Annex A 8.9 is broader, as it also requires configurations to be established, documented and implemented in the first place.
- IT.PRO-13.5Disable legacy authentication protocols and restrict, monitor and decommission exceptionsBroader than
This control is broader than IT.PRO-13.5.
IT.PRO-13.5 requires legacy authentication protocols to be disabled or, where that is not feasible, restricted, monitored, covered by compensating controls and placed on a time-bound decommissioning plan. Disabling these protocols is a specific security configuration that falls within the configuration management required by Annex A 8.9. Annex A 8.9 is broader, covering how all configurations are established, documented, implemented, monitored and reviewed, while IT.PRO-13.5 adds exception handling for protocols that cannot yet be removed.
- IT.PRO-01.1Design systems with telemetry, least privilege, data protection and minimal attack surfacePartially overlaps
This control partially overlaps IT.PRO-01.1.
IT.PRO-01.1 requires systems to be designed securely, including limiting exposed services and removing unnecessary functionality. These hardening outcomes are part of the security configurations that ISO/IEC 27001 Annex A 8.9 requires to be established, documented, implemented, monitored and reviewed. Annex A 8.9 covers the full configuration management process for hardware, software, services and networks, while IT.PRO-01.1 also covers design objectives such as visibility, access enforcement and data protection.
- IT.PRO-01.2Use secure build and deployment processes to enforce security controls consistentlyPartially overlaps
This control partially overlaps IT.PRO-01.2.
IT.PRO-01.2 requires secure build and deployment processes that enforce security controls consistently across systems. Consistent, secure builds are a primary means of implementing the security configurations required by ISO/IEC 27001 Annex A 8.9. Annex A 8.9 also requires configurations to be established, documented, monitored and reviewed over time, while IT.PRO-01.2 focuses on the build and deployment processes themselves.
- IT.PRO-06.1Continuously scan and assess assets for known software and configuration weaknessesPartially overlaps
This control partially overlaps IT.PRO-06.1.
IT.PRO-06.1 requires continuous and repeatable assessment activities, including vulnerability scanning, to identify known software and configuration weaknesses in assets. Its assessment of configuration weaknesses shares common ground with the monitoring and review of security configurations required by Annex A 8.9. Each has distinct scope: IT.PRO-06.1 also covers software vulnerabilities, while Annex A 8.9 also requires configurations to be established, documented and implemented.
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.




