ISO 27001:2022 Annex A 7.8 – Equipment Siting and Protection Explained

Where equipment is placed often matters as much as how it is secured.

Annex A 7.8 exists to ensure organisations site and protect equipment in a way that reduces physical, environmental, and unauthorised access risks, protecting the confidentiality, integrity, and availability of information throughout its lifecycle.

This control is about preventing avoidable loss and disruption through poor placement and protection.

ISO 27001

Quick Guide: Annex A 7.8 at a Glance

Annex A 7.8 of ISO 27001:2022 focuses on equipment siting and protection.

At a practical level, this means:

  • Placing equipment in locations that reduce risk
  • Protecting equipment from physical and environmental threats
  • Preventing unauthorised access, use, or interference
  • Reducing opportunities for observation or tampering
  • Aligning equipment protection with information risk

The control does not require specialist facilities everywhere. It expects deliberate, risk-based decisions about where equipment is located and how it is protected.

In-Depth Guide to Annex A 7.8

What Is Annex A 7.8 and Why Does It Matter?

Information processing equipment is vulnerable to more than cyber attack.

Common risks include:

  • Theft or unauthorised use
  • Accidental damage
  • Environmental exposure (heat, moisture, dust)
  • Power fluctuation or electrical interference
  • Observation of screens or output

Poorly sited equipment increases the likelihood of:

  • Information loss or compromise
  • Service disruption
  • Safety incidents
  • Costly recovery or replacement

Annex A 7.8 ensures organisations reduce exposure to these risks before technical controls are tested.

This control replaces ISO 27001:2013 Annex A 11.2.1 and adds emphasis on segregation and environmental considerations.

How to Implement Annex A 7.8 Effectively

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

1. Identify Equipment That Requires Protection

Organisations should identify equipment that:

  • Processes or stores sensitive information
  • Supports critical services
  • Is costly or difficult to replace

This includes servers, network devices, end-user devices, printers, and removable media.

2. Site Equipment to Reduce Physical Risk

Equipment should be located to minimise exposure to:

  • Theft or unauthorised access
  • Accidental damage
  • Environmental hazards

Examples include:

  • Avoiding public or high-traffic areas
  • Using secure rooms or cabinets for critical equipment
  • Positioning equipment away from water sources or heat

Location choices often prevent incidents before controls are needed.

3. Protect Equipment From Environmental Threats

Environmental factors can disrupt or damage equipment.

Organisations should consider protection against:

  • Temperature and humidity extremes
  • Dust or contaminants
  • Power instability or surges
  • Fire or water ingress

Controls should reflect the operating environment, not generic assumptions.

4. Prevent Unauthorised Access or Interference

Equipment should be protected against casual or deliberate interference.

This may include:

  • Physical locks or enclosures
  • Restricted access areas
  • Supervision or monitoring where justified

Unauthorised physical access often leads to logical compromise.

5. Reduce Risk of Unauthorised Observation

Annex A 7.8 supports positioning equipment to reduce visual exposure.

This may involve:

  • Positioning screens away from public view
  • Using privacy screens where appropriate
  • Locating printers and output devices in controlled areas

Observation risk is frequently overlooked but easy to reduce.

6. Separate Organisational and Non-Organisational Equipment

The 2022 revision emphasises segregation.

Organisations should clearly separate:

  • Equipment owned and controlled by the organisation
  • Equipment not owned or controlled by the organisation

This reduces confusion, interference, and accountability gaps.

7. Address Special Environments Deliberately

Where equipment operates in unusual environments, additional controls may be needed.

Examples include:

  • Industrial or manufacturing environments
  • Temporary or mobile locations
  • Shared or co-located facilities

Controls should match environmental reality, not policy language.

8. Monitor and Maintain Equipment Protection

Protection degrades over time.

Organisations should:

  • Inspect siting and protection periodically
  • Adjust controls when layouts or usage change
  • Maintain protective measures and environmental controls

Equipment protection should evolve with the environment.

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

  • Data centre–grade controls for all equipment
  • Identical protection everywhere
  • Zero exposure to physical risk

It does require organisations to:

  • Avoid poor or convenient placement
  • Consider environmental and physical threats explicitly
  • Apply proportionate protection

Most equipment incidents are preventable with basic planning.

Common Challenges and How to Overcome Them

  • Equipment placed for convenience rather than security
  • Consider physical and environmental risk during siting
  • Ignoring environmental conditions
  • Match protection to temperature, humidity, and location
  • Shared or mixed ownership equipment
  • Clearly segregate organisational and non-organisational assets
  • Screens and printers visible to unauthorised individuals
  • Reduce visual exposure through layout and controls

Poor siting creates risk that no software can fix.

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.8 is about preventing avoidable physical exposure.

When equipment siting and protection are handled effectively:

  • Information loss and disruption are reduced
  • Physical and environmental incidents are less likely
  • Recovery is simpler and faster
  • Security controls work as intended

Before attackers, accidents, or environment cause harm,
Annex A 7.8 ensures organisations remove easy opportunities for failure.

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