Most security weaknesses aren’t exotic exploits.
They’re misconfigurations that quietly accumulate over time.
Annex A 8.9 exists to ensure organisations define, apply, monitor, and control system configurations, so hardware, software, and network components operate securely and consistently throughout their lifecycle.
This control is about preventing accidental insecurity, not chasing incidents after the fact.

Annex A 8.9 of ISO 27001:2022 focuses on configuration management.
At a practical level, this means:
The control does not mandate specific tools or templates. It expects organisations to manage configuration deliberately, consistently, and audibly.
Configurations determine:
Examples include:
If configurations are:
…the organisation is exposed to:
Annex A 8.9 ensures organisations treat configuration as a security control, not just a technical detail.
This is a new control in ISO 27001:2022, reflecting the increasing impact of misconfiguration in modern environments.
A pragmatic approach to Annex A 8.9 typically includes the following elements.
Organisations should define a policy that covers:
Clear ownership is essential — configuration without ownership degrades quickly.
Organisations should identify:
Configuration management depends on knowing what needs to be controlled.
Baseline configurations should define:
Where possible, organisations should:
Baselines provide consistency and repeatability.
Standard templates support:
Templates should:
Standardisation reduces variation — and variation is risk.
Configuration changes should be:
Unrestricted administrative access is a frequent source of misconfiguration.
Default configurations often prioritise ease of use, not security.
Organisations should ensure:
Defaults are a known attack path.
Annex A 8.9 expects configurations and changes to be recorded.
Records should include:
This supports traceability, investigation, and audit.
Configuration changes should follow defined change control processes.
This includes:
Annex A 8.9 aligns closely with Annex A 8.32 (Change Management).
Where risk justifies it, organisations should:
Detection is essential when prevention fails.
Configurations should not be static.
Organisations should review:
Configuration debt accumulates silently.
Annex A 8.9 does not require:
It does require organisations to:
Most breaches involving misconfiguration were entirely preventable.
Misconfiguration thrives in unmanaged environments.
Annex A 8.9 is about making secure behaviour the default state of systems.
When configuration management is implemented effectively:
Systems don’t become insecure overnight.
They drift there — one configuration change at a time.
Annex A 8.9 ensures organisations control the drift.
We can help you understand your actual security needs and even if we cant help we can point you in the right direction
Talk to a security expert today