ISO 27001:2022 Annex A 7.13 – Equipment Maintenance Explained

Equipment does not usually fail suddenly.
It fails because maintenance was inconsistent, unauthorised, or overlooked.

Annex A 7.13 exists to ensure organisations maintain equipment securely and correctly, so information assets are not compromised through degradation, failure, or insecure maintenance activity.

This control treats maintenance as a preventative security activity, not just an operational task.

ISO 27001

Quick Guide: Annex A 7.13 at a Glance

Annex A 7.13 of ISO 27001:2022 focuses on secure equipment maintenance.

At a practical level, this means:

  • Maintaining equipment in line with manufacturer guidance
  • Preventing unauthorised or unsupervised maintenance activity
  • Protecting information during maintenance and repair
  • Recording maintenance actions and faults
  • Verifying equipment integrity after maintenance

The control does not dictate maintenance schedules or tools. It expects organisations to apply planned, authorised, and secure maintenance practices.

In-Depth Guide to Annex A 7.13

What Is Annex A 7.13 and Why Does It Matter?

Information security depends on reliable equipment, including:

  • Servers and storage
  • End-user devices
  • Network and communications equipment
  • Environmental and supporting infrastructure

Poorly maintained equipment increases risk of:

  • Data loss or corruption
  • Unexpected outages
  • Security control failure
  • Undetected tampering or compromise

Annex A 7.13 ensures organisations do not treat maintenance as neutral activity, recognising that maintenance introduces both operational and security risk.

How to Implement Annex A 7.13 Effectively

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

1. Establish a Maintenance Programme

Organisations should define a structured approach to maintenance, covering:

  • What equipment is subject to maintenance
  • How often maintenance is performed
  • Which activities are preventative versus reactive

A defined programme supports consistency and predictability.

2. Follow Manufacturer and Supplier Guidance

Equipment should be maintained:

  • In line with manufacturer specifications
  • Within recommended service intervals
  • According to environmental and operational limits

Ignoring manufacturer guidance is a common cause of avoidable failure.

3. Restrict Maintenance to Authorised Personnel

Maintenance should only be performed by:

  • Authorised employees
  • Approved and trusted third parties

Authorisation ensures accountability and reduces insider and third-party risk.

4. Supervise Maintenance Activities Where Risk Justifies It

Annex A 7.13 explicitly recognises supervision as a control.

Organisations may:

  • Supervise on-site maintenance activities
  • Restrict access to specific components
  • Ensure maintenance staff do not have unnecessary access to information

Supervision reduces risk of accidental or deliberate compromise.

5. Secure Remote Maintenance Activities

Where maintenance is performed remotely:

  • Access should be explicitly authorised
  • Authentication and access controls should be enforced
  • Activities should be logged and monitored

Remote maintenance bypasses physical controls and therefore requires additional attention.

6. Record Maintenance Activities and Faults

Organisations should record:

  • Equipment faults and failures
  • Maintenance actions performed
  • Dates, outcomes, and responsible parties

Records support accountability, trend analysis, and audit evidence.

7. Protect Information During Maintenance

Maintenance activities may expose information.

Organisations should consider:

  • Restricting access to data during maintenance
  • Protecting backups and storage media
  • Applying confidentiality obligations to maintenance personnel

Maintenance should not become a data exposure event.

8. Inspect Equipment After Maintenance

After maintenance, organisations should verify that:

  • Equipment functions as intended
  • No unauthorised changes were made
  • Security controls remain intact

Post-maintenance checks close the loop on risk.

9. Apply Off-Premises Controls When Equipment Is Removed

If equipment is removed from premises for maintenance:

  • Security measures aligned with Annex A 7.9 should apply
  • Custody and transport risk should be managed
  • Responsibility should remain clear

Removal from site significantly increases exposure.

10. Align Maintenance With Disposal and Reuse Controls

Maintenance activities may trigger:

  • Component replacement
  • End-of-life decisions

Organisations should align with:

  • Secure reuse controls
  • Secure disposal requirements

Maintenance and disposal are often linked operationally.

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 7.13 does not require:

  • Vendor-only maintenance
  • Overly complex maintenance tooling
  • Zero tolerance for failure

It does require organisations to:

  • Plan maintenance deliberately
  • Control who performs it
  • Treat maintenance as a security-relevant activity

Unmanaged maintenance is a common root cause of incidents.

Common Challenges and How to Overcome Them

  • Maintenance treated as purely operational
  • Recognise maintenance as a security control
  • Unsupervised third-party maintenance
  • Apply authorisation, supervision, and confidentiality controls
  • Remote maintenance with weak access controls
  • Enforce strong authentication and logging
  • No post-maintenance verification
  • Inspect equipment after work is completed

Equipment failure rarely starts with attack — it starts with neglect.

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 7.13 is about keeping security intact while equipment is touched, repaired, or changed.

When equipment maintenance is managed effectively:

  • Availability improves
  • Failure risk decreases
  • Tampering is more likely to be detected
  • Information security controls remain reliable

Systems age.
Annex A 7.13 ensures they do so securely, not unpredictably.

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