# ISO/IEC 27001:2022 A.8.9 — Configuration management - Source: https://support.icompaas.com/compliance/iso-27001-2022/a-8-9-configuration-management - Section: [Compliance](https://support.icompaas.com/compliance) › [ISO/IEC 27001:2022 Annex A Controls](https://support.icompaas.com/compliance/iso-27001-2022) › Technological controls - Last updated: 2026-06-05 - Publisher: iCompaas, Inc. (https://www.icompaas.com) **ISO/IEC 27001:2022**·Annex A `A.8.9`·medium·Component: **Technological controls** ## What this control requires > Configurations, including security configurations, of hardware, software, services and networks shall be established, documented, implemented, monitored and reviewed. > > — ISO/IEC 27001:2022, Annex A A.8.9 ### In plain English Configurations, including security configurations, of hardware, software, services and networks shall be established, documented, implemented, monitored and reviewed. In practice, this means you can prove you policy management-level controls on a defined cadence. ## Why it matters ISO 27001 certification depends on showing each Annex A control is either implemented or explicitly justified for exclusion in the Statement of Applicability (SoA). Certification bodies sample controls during surveillance audits, and a missing SoA entry — or implementation that doesn't match the SoA wording — is a finding. ## What an auditor looks for An ISO 27001 lead auditor looks for: (1) an SoA entry covering the control with justification, (2) a documented procedure or policy implementing it, (3) records that prove the procedure runs (logs, tickets, training records) and (4) management-review evidence that effectiveness is monitored. Within **Technological controls**, the assessor will trace your implementation back to the catalogue reference (Annex A A.8.9) and look for objective evidence on the latest two assessment cycles. ## How to implement #### Configuration Management **Policy-as-code.** Codify the control as Service Control Policies (AWS), Azure Policy initiatives, or Organisation Policy (GCP) so the platform enforces what the document promises. **IaC.** Gate Terraform / Pulumi / CloudFormation changes with Checkov / tfsec / OPA so misconfigurations never reach production. **Drift.** Run a CSPM (Wiz / Prisma / Defender for Cloud / Security Command Center) over every account and route findings to a single risk register. #### Policy Management **Docs.** Keep each policy in version-controlled Markdown alongside the code that implements it; ship a signed PDF snapshot at each annual review and link the SHA into the SoA. ### Operational checklist - **Policy.** Document the trigger, the owner and the cadence. - **Management.** Document the trigger, the owner and the cadence. - **Security.** Document the trigger, the owner and the cadence. - **Networks.** Document the trigger, the owner and the cadence. - **Scope:** management, security, security configurations, hardware, software, services, networks. ## Evidence to collect - **Code Repo Scan.** Source-control evidence — branch protection, required reviewers, CI status, SCA / SAST reports. - **Infra Scan.** Continuous infrastructure-posture telemetry — AWS Config, Azure Policy compliance, GCP Organisation Policy, Wiz / Prisma findings. Infrastructure compliance scanners (AWS Config, Azure Policy) and IaC checks enforce approved configurations. ## Common pitfalls - Manual cloud-console changes that never make it back to Terraform — drift accumulates until the next outage forces a reconciliation. - Policies that no engineer has read; the version in Confluence drifts from the version that's actually being enforced. ## How it maps to other frameworks Computed from shared tags, control component and key-operation subjects — handy when you are reconciling controls across an audit. - [**NIST SP 800-53 Rev. 5 SA-3(3)** — Technology Refresh](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/sa-3-3-technology-refresh) - [**NIST SP 800-171 Rev. 3 3.13.2** — Recategorized as NCO](https://support.icompaas.com/compliance/nist-sp-800-171-rev-3/3-13-2-recategorized-as-nco) - [**HIPAA (45 CFR Part 164) 164.308(a)(5)(i)** — Security Awareness and Training](https://support.icompaas.com/compliance/hipaa/164-308-a-5-i-security-awareness-and-training) - [**SOC 2 (2017 TSC) PI1.3** — Processing Controls](https://support.icompaas.com/compliance/soc-2-trust-services-criteria/pi1-3-processing-controls) - [**BSI C5:2020 SP-01** — Documentation, communication and provision of policies and instructions](https://support.icompaas.com/compliance/bsi-c5-2020/sp-01-documentation-communication-and-provision-of-policies-and-instructions) ## Related controls in ISO/IEC 27001:2022 - [**Annex A A.8.19** — Installation of software on operational systems](https://support.icompaas.com/compliance/iso-27001-2022/a-8-19-installation-of-software-on-operational-systems) - [**Annex A A.8.13** — Information backup](https://support.icompaas.com/compliance/iso-27001-2022/a-8-13-information-backup) - [**Annex A A.8.26** — Application security requirements](https://support.icompaas.com/compliance/iso-27001-2022/a-8-26-application-security-requirements) - [**Annex A A.8.22** — Segregation of networks](https://support.icompaas.com/compliance/iso-27001-2022/a-8-22-segregation-of-networks) - [**Annex A A.8.11** — Data masking](https://support.icompaas.com/compliance/iso-27001-2022/a-8-11-data-masking) - [**Annex A A.5.21** — Managing information security in the ICT supply chain](https://support.icompaas.com/compliance/iso-27001-2022/a-5-21-managing-information-security-in-the-ict-supply-chain) ## References - [ISO/IEC JTC 1/SC 27 — ISO/IEC 27001:2022](https://www.iso.org/standard/27001) - Catalogue identifier: `Annex A A.8.9` Topics: governance riskconfiguration managementpolicy management ## Related compliance guidance - [ISO/IEC 27001:2022 compliance: a practical implementation guide](https://support.icompaas.com/compliance/iso-27001-2022): Start with the full ISO 27001 implementation guide — scope, roadmap, evidence and how the assessment runs. - [SOC 2 compliance: a practical implementation guide for cloud-native SaaS teams](https://support.icompaas.com/compliance/soc-2-trust-services-criteria): Most companies that hold ISO 27001 also need a SOC 2 report for North American customers, and the two share most of their technical controls.