ISO 27001:2022 Annex A 7.5 – Protecting Against Physical and Environmental Threats Explained

Not all security threats are digital.
Some arrive as fire, water, heat, power loss, or civil disruption.

Annex A 7.5 exists to ensure organisations identify and protect against physical and environmental threats that could damage information, systems, or supporting infrastructure.

This control is about anticipating what could physically go wrong, and designing for it.

ISO 27001

Quick Guide: Annex A 7.5 at a Glance

Annex A 7.5 of ISO 27001:2022 focuses on protecting information and assets from physical and environmental threats.

At a practical level, this means:

  • Identifying physical and environmental risks to information assets
  • Protecting facilities, systems, and media from damage or disruption
  • Reducing the likelihood and impact of natural and human-made events
  • Applying proportionate controls based on location and context
  • Monitoring and maintaining protections over time

The control does not require elimination of all risk. It expects reasonable, risk-based protection against foreseeable threats.

In-Depth Guide to Annex A 7.5

What Is Annex A 7.5 and Why Does It Matter?

Physical and environmental threats include:

  • Fire, smoke, and heat
  • Flooding or water ingress
  • Power failure or electrical surge
  • Extreme temperature or humidity
  • Structural failure
  • Civil disturbance, vandalism, or theft

These threats can lead to:

  • Loss or corruption of information
  • Extended system downtime
  • Damage to critical infrastructure
  • Safety risks to personnel
  • Regulatory, contractual, or operational impact

Annex A 7.5 ensures organisations do not assume buildings and environments are inherently safe, but assess and manage physical risk deliberately.

How to Implement Annex A 7.5 Effectively

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

1. Identify Physical and Environmental Threats

Organisations should identify threats relevant to their:

  • Geographic location
  • Building type and construction
  • Local environment and climate
  • Operational activities

Different sites face different risks. Controls should reflect reality, not templates.

2. Assess Risk to Information and Supporting Infrastructure

Risk assessment should consider:

  • Likelihood of physical or environmental events
  • Potential impact on information confidentiality, integrity, and availability
  • Dependency on utilities, access routes, or shared infrastructure

This assessment informs which protections are justified.

3. Apply Protective Controls Proportionate to Risk

Controls may include:

  • Fire detection and suppression systems
  • Flood detection or drainage
  • Temperature and humidity controls
  • Surge protection and power conditioning
  • Physical reinforcement or secure storage

Controls should protect both information and the infrastructure that supports it.

4. Consider Location When Selecting or Using Facilities

Annex A 7.5 supports considering physical risk when:

  • Selecting new premises
  • Locating data centres or communications rooms
  • Storing backups or critical media

Avoidable exposure should be addressed early rather than mitigated later.

5. Protect Against Human-Caused Physical Threats

Physical threats are not limited to natural events.

Organisations should also consider:

  • Theft or vandalism
  • Unauthorised interference
  • Civil unrest or targeted attack

Environmental design, layout, and physical security controls all contribute to risk reduction.

6. Monitor and Maintain Protective Measures

Protective controls must remain effective.

Organisations should:

  • Test alarms and detection systems
  • Maintain environmental controls
  • Inspect physical protections regularly
  • Address degradation or failure promptly

Unmaintained controls create false confidence.

7. Integrate With Business Continuity and Incident Response

Physical and environmental protection supports:

  • Business continuity planning
  • Incident response and recovery
  • ICT readiness and resilience

Annex A 7.5 works closely with continuity-focused controls, ensuring prevention and preparedness align.

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

  • Over-engineered facilities
  • Identical controls at every site
  • Elimination of all environmental exposure

It does require organisations to:

  • Understand physical and environmental risk
  • Apply reasonable and proportionate protection
  • Avoid ignoring non-cyber threats

Many major outages are environmental, not malicious.

Common Challenges and How to Overcome Them

  • Assuming buildings are safe by default
  • Assess physical and environmental risk explicitly
  • Focusing only on cyber threats
  • Treat physical risk as part of information security
  • Controls installed but not maintained
  • Monitor and test protections regularly
  • Ignoring location-specific threats
  • Tailor controls to geography and environment

Physical threats rarely announce themselves in advance.

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.5 is about protecting information from the physical world it depends on.

When physical and environmental threats are managed effectively:

  • Information availability is more resilient
  • Infrastructure damage is reduced
  • Disruption is less severe
  • Recovery is faster and more predictable

Cyber controls protect data from attackers.
Annex A 7.5 protects it from fire, water, power, and gravity.

Both are essential.

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