ISO 27001:2022 Annex A 8.9 – Configuration Management Explained

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.

ISO 27001

Quick Guide: Annex A 8.9 at a Glance

Annex A 8.9 of ISO 27001:2022 focuses on configuration management.

At a practical level, this means:

  • Defining secure baseline configurations
  • Applying configurations consistently across systems
  • Preventing unauthorised or undocumented changes
  • Recording and monitoring configuration changes
  • Aligning configuration management with change control

The control does not mandate specific tools or templates. It expects organisations to manage configuration deliberately, consistently, and audibly.

In-Depth Guide to Annex A 8.9

What Is Annex A 8.9 and Why Does It Matter?

Configurations determine:

  • How systems behave
  • Which services are exposed
  • What security controls are active
  • How resilient systems are to failure or attack

Examples include:

  • Firewall rule sets
  • Operating system hardening settings
  • Application configuration files
  • Network device parameters
  • Cloud service configurations

If configurations are:

  • Inconsistent
  • Unauthorised
  • Poorly documented
  • Out of date

…the organisation is exposed to:

  • Unintended access paths
  • Security control bypass
  • Service instability
  • Audit and assurance failure

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.

How to Implement Annex A 8.9 Effectively

A pragmatic approach to Annex A 8.9 typically includes the following elements.

1. Define a Configuration Management Policy

Organisations should define a policy that covers:

  • Scope of configuration management
  • Roles and responsibilities
  • Approval and change requirements
  • Monitoring and review expectations

Clear ownership is essential — configuration without ownership degrades quickly.

2. Identify Configuration Items in Scope

Organisations should identify:

  • Systems and devices with configurable security impact
  • Applications and platforms
  • Network and cloud components

Configuration management depends on knowing what needs to be controlled.

3. Establish Secure Baseline Configurations

Baseline configurations should define:

  • Minimum security settings
  • Services that should be enabled or disabled
  • Logging, authentication, and access controls

Where possible, organisations should:

  • Use vendor guidance
  • Reference recognised hardening standards
  • Adapt baselines to business and operational need

Baselines provide consistency and repeatability.

4. Apply Standardised Configuration Templates Where Appropriate

Standard templates support:

  • Faster deployment
  • Reduced error
  • Easier assurance

Templates should:

  • Meet minimum security requirements
  • Align with organisational policies
  • Be practical to apply and maintain

Standardisation reduces variation — and variation is risk.

5. Restrict Configuration Changes to Authorised Personnel

Configuration changes should be:

  • Performed only by authorised individuals
  • Aligned with defined roles
  • Logged and attributable

Unrestricted administrative access is a frequent source of misconfiguration.

6. Remove Default and Unnecessary Settings

Default configurations often prioritise ease of use, not security.

Organisations should ensure:

  • Default credentials are removed
  • Unused services and accounts are disabled
  • Unnecessary functionality is not exposed

Defaults are a known attack path.

7. Record and Track Configuration Changes

Annex A 8.9 expects configurations and changes to be recorded.

Records should include:

  • Who made the change
  • When the change occurred
  • What was changed
  • The approved configuration version

This supports traceability, investigation, and audit.

8. Align Configuration Changes With Change Management

Configuration changes should follow defined change control processes.

This includes:

  • Authorisation before change
  • Testing where appropriate
  • Rollback planning

Annex A 8.9 aligns closely with Annex A 8.32 (Change Management).

9. Monitor Configurations for Unauthorised Change

Where risk justifies it, organisations should:

  • Detect configuration drift
  • Alert on unauthorised or unexpected changes
  • Restore approved configurations where necessary

Detection is essential when prevention fails.

10. Review Configurations Periodically

Configurations should not be static.

Organisations should review:

  • Baselines against emerging threats
  • Configurations following system updates
  • Templates when environments change

Configuration debt accumulates silently.

In-Depth Guide to Annex A 5.1

What is Annex A 5.1 and Why Does It Matter?

  • What the organisation values
  • How security decisions are approached
  • Where accountability sits
  • Aligns security with business objectives
  • Supports proportionate, risk-based decisions
  • Provides a reference point during incidents and disputes
  • Creates consistency without bureaucracy

How to Implement Annex A 5.1 Effectively

1. Define a Comprehensive Information Security Policy
  • Scope: What the policy applies to (systems, data, people).
  • Objectives: Why security is important for the business.
  • Roles & Responsibilities: Who is accountable for security.
  • Key Principles: Risk management, access control, and data protection.
2. Secure Senior Management Approval
  • Review and approve policies.
  • Ensure resources are allocated for implementation.
  • Lead by example in enforcing security policies.
3. Communicate and Train Employees
  • Include security policies in onboarding and ongoing training.
  • Ensure policies are easily accessible to all employees.
  • Encourage acknowledgment and acceptance of security responsibilities.
4. Regular Review & Continuous Improvement
  • Set a schedule for periodic policy reviews (at least annually).
  • Update policies based on business changes, new threats, or regulatory updates.
  • Conduct audits to ensure compliance and effectiveness.
5. Integrate Policies into the ISMS
  • Use it to develop more detailed security procedures.
  • Ensure policies align with other Annex A controls and broader risk management practices.
Key Differences: ISO 27001:2013 vs ISO 27001:2022
AspectISO 27001:2013ISO 27001:2022
Control StructureTwo separate controls: 5.1.1 & 5.1.2Merged into one control (5.1)
Implementation GuidanceLess prescriptiveMore detailed guidance for policy creation and alignment
Awareness & TrainingNot explicitly mentionedExplicitly requires policies to be part of training programmes
Attributes TableNot includedew attributes table for mapping policies to industry terms
Common Challenges & How to Overcome Them
  • Challenge: Employees don’t follow security policies.
  • Solution: Make policies practical and relevant to daily work. Use real-world examples in training.
  • Challenge: Policies are outdated or too generic.
  • Solution: Schedule annual reviews and update policies based on real threats and business changes.
  • Challenge: Policies are written in technical jargon.
  • Solution: Use plain language that all employees can understand.
  • Challenge: Lack of leadership buy-in.
  • Solution: Show how weak security affects business objectives—costs of breaches, loss of client trust, and legal penalties.
Final Recommendations
  • Make security policies living documents—review, refine, and update regularly.
  • Use policy training and awareness to create a security-conscious workforce.
  • Ensure policies are accessible, relevant, and easy to understand.
  • Keep policies aligned with business strategy and regulatory requirements.
  • Engage leadership in driving security culture from the top down.

Practical Considerations

Annex A 8.9 does not require:

  • Enterprise-grade tooling everywhere
  • Complex configuration databases by default
  • Elimination of all configuration variation

It does require organisations to:

  • Define what “secure configuration” means
  • Apply it consistently
  • Know when and why it changes

Most breaches involving misconfiguration were entirely preventable.

Common Challenges and How to Overcome Them

  • Configuration treated as an IT-only concern
  • Recognise configuration as an information security control
  • No defined baselines
  • Establish and maintain secure configuration standards
  • Untracked configuration changes
  • Record and review all changes
  • Default settings left in place
  • Harden systems deliberately

Misconfiguration thrives in unmanaged environments.

In-Depth Guide to Annex A 5.1

What is Annex A 5.1 and Why Does It Matter?

  • What the organisation values
  • How security decisions are approached
  • Where accountability sits
  • Aligns security with business objectives
  • Supports proportionate, risk-based decisions
  • Provides a reference point during incidents and disputes
  • Creates consistency without bureaucracy

How to Implement Annex A 5.1 Effectively

1. Define a Comprehensive Information Security Policy
  • Scope: What the policy applies to (systems, data, people).
  • Objectives: Why security is important for the business.
  • Roles & Responsibilities: Who is accountable for security.
  • Key Principles: Risk management, access control, and data protection.
2. Secure Senior Management Approval
  • Review and approve policies.
  • Ensure resources are allocated for implementation.
  • Lead by example in enforcing security policies.
3. Communicate and Train Employees
  • Include security policies in onboarding and ongoing training.
  • Ensure policies are easily accessible to all employees.
  • Encourage acknowledgment and acceptance of security responsibilities.
4. Regular Review & Continuous Improvement
  • Set a schedule for periodic policy reviews (at least annually).
  • Update policies based on business changes, new threats, or regulatory updates.
  • Conduct audits to ensure compliance and effectiveness.
5. Integrate Policies into the ISMS
  • Use it to develop more detailed security procedures.
  • Ensure policies align with other Annex A controls and broader risk management practices.
Key Differences: ISO 27001:2013 vs ISO 27001:2022
AspectISO 27001:2013ISO 27001:2022
Control StructureTwo separate controls: 5.1.1 & 5.1.2Merged into one control (5.1)
Implementation GuidanceLess prescriptiveMore detailed guidance for policy creation and alignment
Awareness & TrainingNot explicitly mentionedExplicitly requires policies to be part of training programmes
Attributes TableNot includedew attributes table for mapping policies to industry terms
Common Challenges & How to Overcome Them
  • Challenge: Employees don’t follow security policies.
  • Solution: Make policies practical and relevant to daily work. Use real-world examples in training.
  • Challenge: Policies are outdated or too generic.
  • Solution: Schedule annual reviews and update policies based on real threats and business changes.
  • Challenge: Policies are written in technical jargon.
  • Solution: Use plain language that all employees can understand.
  • Challenge: Lack of leadership buy-in.
  • Solution: Show how weak security affects business objectives—costs of breaches, loss of client trust, and legal penalties.
Final Recommendations
  • Make security policies living documents—review, refine, and update regularly.
  • Use policy training and awareness to create a security-conscious workforce.
  • Ensure policies are accessible, relevant, and easy to understand.
  • Keep policies aligned with business strategy and regulatory requirements.
  • Engage leadership in driving security culture from the top down.

Final Recommendations

Annex A 8.9 is about making secure behaviour the default state of systems.

When configuration management is implemented effectively:

  • Attack surface is reduced
  • Stability improves
  • Incidents are easier to investigate
  • Assurance becomes defensible

Systems don’t become insecure overnight.
They drift there — one configuration change at a time.

Annex A 8.9 ensures organisations control the drift.

In-Depth Guide to Annex A 5.1

What is Annex A 5.1 and Why Does It Matter?

  • What the organisation values
  • How security decisions are approached
  • Where accountability sits
  • Aligns security with business objectives
  • Supports proportionate, risk-based decisions
  • Provides a reference point during incidents and disputes
  • Creates consistency without bureaucracy

How to Implement Annex A 5.1 Effectively

1. Define a Comprehensive Information Security Policy
  • Scope: What the policy applies to (systems, data, people).
  • Objectives: Why security is important for the business.
  • Roles & Responsibilities: Who is accountable for security.
  • Key Principles: Risk management, access control, and data protection.
2. Secure Senior Management Approval
  • Review and approve policies.
  • Ensure resources are allocated for implementation.
  • Lead by example in enforcing security policies.
3. Communicate and Train Employees
  • Include security policies in onboarding and ongoing training.
  • Ensure policies are easily accessible to all employees.
  • Encourage acknowledgment and acceptance of security responsibilities.
4. Regular Review & Continuous Improvement
  • Set a schedule for periodic policy reviews (at least annually).
  • Update policies based on business changes, new threats, or regulatory updates.
  • Conduct audits to ensure compliance and effectiveness.
5. Integrate Policies into the ISMS
  • Use it to develop more detailed security procedures.
  • Ensure policies align with other Annex A controls and broader risk management practices.
Key Differences: ISO 27001:2013 vs ISO 27001:2022
AspectISO 27001:2013ISO 27001:2022
Control StructureTwo separate controls: 5.1.1 & 5.1.2Merged into one control (5.1)
Implementation GuidanceLess prescriptiveMore detailed guidance for policy creation and alignment
Awareness & TrainingNot explicitly mentionedExplicitly requires policies to be part of training programmes
Attributes TableNot includedew attributes table for mapping policies to industry terms
Common Challenges & How to Overcome Them
  • Challenge: Employees don’t follow security policies.
  • Solution: Make policies practical and relevant to daily work. Use real-world examples in training.
  • Challenge: Policies are outdated or too generic.
  • Solution: Schedule annual reviews and update policies based on real threats and business changes.
  • Challenge: Policies are written in technical jargon.
  • Solution: Use plain language that all employees can understand.
  • Challenge: Lack of leadership buy-in.
  • Solution: Show how weak security affects business objectives—costs of breaches, loss of client trust, and legal penalties.
Final Recommendations
  • Make security policies living documents—review, refine, and update regularly.
  • Use policy training and awareness to create a security-conscious workforce.
  • Ensure policies are accessible, relevant, and easy to understand.
  • Keep policies aligned with business strategy and regulatory requirements.
  • Engage leadership in driving security culture from the top down.

The Annex Control Table

ISO 27001:2022 Organisational Controls
ISO 27001:2022 Technological Controls