ISO 27001:2022 Annex A 7.9 – Security of Assets Off-Premises Explained

The moment an asset leaves the building, your physical controls stop working.

Annex A 7.9 exists to ensure organisations protect information assets when they are taken or installed outside organisational premises, where loss, theft, damage, and unauthorised access are more likely.

This control is about extending physical security beyond the office — not assuming it still applies.

ISO 27001

Quick Guide: Annex A 7.9 at a Glance

Annex A 7.9 of ISO 27001:2022 focuses on securing information assets used or located off-premises.

At a practical level, this means:

  • Protecting equipment and media taken off-site
  • Reducing risk of loss, theft, damage, or unauthorised access
  • Controlling how assets are removed from organisational premises
  • Protecting information displayed or processed in public locations
  • Managing assets permanently installed outside organisational control

The control does not prohibit off-site use. It expects organisations to recognise the increased risk and apply appropriate safeguards.

In-Depth Guide to Annex A 7.9

What Is Annex A 7.9 and Why Does It Matter?

Once assets leave controlled premises:

  • Physical access controls no longer apply
  • Environmental conditions become unpredictable
  • Observation and theft risk increase significantly
  • Accountability can become unclear

Common examples include:

  • Laptops and mobile devices used for remote working
  • Removable media taken off-site
  • Equipment used during travel
  • Devices permanently installed in external locations

Annex A 7.9 ensures organisations do not rely on office-based controls for off-site assets, where those controls are ineffective.

This control replaces ISO 27001:2013 Annex A 11.2.6 and significantly expands expectations around modern working practices.

How to Implement Annex A 7.9 Effectively

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

1. Define Rules for Taking Assets Off-Premises

Organisations should define:

  • Which assets may be taken off-site
  • Who is authorised to remove them
  • Under what conditions removal is permitted

Where appropriate, authorisation and recording of asset removal helps maintain accountability and auditability.

2. Protect Assets From Loss, Theft and Damage

Assets taken off-premises should be protected against common risks.

This may include:

  • Never leaving assets unattended in public places
  • Securing assets during transport and storage
  • Protecting devices from water, heat, dust, or electromagnetic exposure

Manufacturer guidance should be considered when defining physical protection requirements.

3. Prevent Unauthorised Viewing of Information

Off-premises use increases the risk of shoulder-surfing and casual observation.

Organisations should take steps to:

  • Reduce visibility of screens in public or shared spaces
  • Avoid displaying sensitive information in transit
  • Apply privacy screens or positioning controls where appropriate

Visual exposure is one of the most common off-site weaknesses.

4. Control and Track Custody of Assets

Where risk justifies it, organisations may:

  • Maintain records of asset custody
  • Identify individuals responsible for off-site assets
  • Track responsibility during handover or shared use

Clear ownership reduces loss and dispute.

5. Enable Location Tracking and Remote Protection Where Appropriate

For some devices, particularly mobile computing equipment, organisations may consider:

  • Location tracking capabilities
  • Remote access management
  • Remote locking or data removal

These controls reduce impact when assets are lost or stolen.

6. Address Permanently Installed Off-Premises Equipment

Annex A 7.9 also applies to equipment installed outside organisational premises on a permanent basis.

Examples include:

  • Communications equipment
  • Monitoring devices
  • Infrastructure hosted at third-party or shared locations

For these assets, organisations should consider:

  • Physical access controls
  • Protection against interference
  • Monitoring and environmental protection
  • Alignment with physical monitoring and environmental threat controls

Permanent off-site installation typically carries higher and more sustained risk.

7. Align Off-Premises Asset Security With Other Controls

Annex A 7.9 should be aligned with:

Off-site security fails when controls operate in isolation.

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

  • Prohibition of remote or mobile working
  • Identical controls for all off-site assets
  • Constant tracking of every device

It does require organisations to:

  • Acknowledge that off-premises assets face higher risk
  • Apply proportionate, realistic safeguards
  • Avoid assuming office-based controls still apply

Off-site exposure is not hypothetical — it is routine.

Common Challenges and How to Overcome Them

  • Assuming mobile assets are low risk
  • Treat off-premises use as higher exposure by default
  • No accountability for removed assets
  • Define authorisation and responsibility clearly
  • Information visible in public spaces
  • Address screen visibility and observation risk
  • Ignoring permanently installed external equipment
  • Apply physical and monitoring controls off-site as well

Most off-site incidents are preventable with basic discipline.

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.9 is about protecting information when it leaves controlled space.

When off-premises assets are managed effectively:

  • Loss and theft impact is reduced
  • Unauthorised access is less likely
  • Accountability remains clear
  • Information security extends beyond the office

Assets move.
Annex A 7.9 ensures security moves with them.

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