hello@sterling-grc.com +1 201 263 4443 New York ISO & GRC consulting in 60+ countries
SterlingInternational Consulting Talk to a consultantTalk to us
Control A.7.9ISO/IEC 27001:2022 · Physical controls

ISO 27001 A.7.9: Protect assets away from your premises

An asset does not stop needing protection when it leaves the office. ISO 27001 Annex A.7.9 concerns equipment and information used or held away from the organisation's premises, including items that pass between people or remain at an external location. The objective is to reduce loss, damage and compromise while preserving the work the asset enables.

Part ofA.7 · Physical controls|Reading time 6 min

What A.7.9 requires in practice

Annex A control 7.9 asks the organisation to protect assets that are away from its premises. That includes laptops, phones, documents and other equipment carried by staff, items kept at a client site or a home, and assets in transit. The aim is to reduce loss, damage and compromise without stopping the work the asset enables. The parts to consider are the purpose and owner of each off-site use, the information the asset holds, how custody is maintained during transport, temporary storage and use, and what happens on loss or return. Privately owned devices used for business purposes are within its reach where such use is permitted. The outputs are authorisation arrangements that suit the role, practical handling guidance, and a clear route for reporting loss. The standard does not require every protective technology for every journey.

Decide what may leave and why

Identify the business purpose, responsible person and information involved. A laptop configured for general office work may contain more information than a short field assignment needs. Consider whether the task can use a restricted dataset, controlled remote access or a device prepared for the specific activity. Reducing unnecessary information can reduce the consequences of loss.

Authorisation should be understandable and proportionate. It may be built into a role or assignment rather than require a new signature for every routine journey. Exceptions need a clear route. Include privately owned devices used for organisational work where permitted; ownership alone does not decide whether business information needs protection.

ISO/IEC 27001 consulting & certification support

Get clause A.7.9 right the first time — with a global leader in ISO/IEC 27001 implementation

A Sterling consultant works the requirement through with your team, links it to the rest of the system and carries it to certification readiness. Expert and experienced consultants, 8,100+ client engagements in 60+ countries.

Follow custody through the whole journey

Consider transport, temporary storage, use and return. A journey can involve a vehicle, hotel, client location and another employee, each with different exposure. People need practical instructions for keeping control of the asset, protecting information from observation and reporting loss or suspected interference promptly.

When custody changes, establish who receives responsibility and what is transferred. Confirm whether information should be removed before another user receives the device, and preserve required business records appropriately. A courier collection receipt may show that a parcel changed hands without establishing which asset or sensitive content was inside.

Why protecting assets away from premises matters to the business

Assets leave the building every day in bags, vehicles and homes, and that is where theft, loss and casual exposure happen. A lost laptop or misplaced file can lead to notification duties, customer complaints and reputational damage far out of proportion to the equipment's value. Organisations that reduce what travels, and prepare people for the journey, cut both the likelihood and the consequences. Customers whose data is carried by your staff expect this to be thought through. For audit, off-site arrangements are tested by asking staff how they would protect and report a lost device, so practical, understood arrangements make findings less likely.

How to implement A.7.9

Match the protection to the journey and the information, not to a blanket rule. Keep the arrangements proportionate so that staff are not tempted to work around them. Involve the people who travel most often when drafting the guidance, since they know where the practical difficulties are.

  1. Identify who takes which assets off-site, for what purposes and how often.
  2. Consider limiting the information carried, for example by using a restricted dataset or controlled remote access for a specific task.
  3. Set authorisation arrangements built into roles or assignments, with an exception route for unusual cases.
  4. Describe custody through the whole journey, covering vehicles, hotels, client sites and handover to colleagues.
  5. Give people practical guidance on keeping control of devices and shielding information from observation.
  6. Define how loss or theft is reported, and how quickly the organisation can respond to it.
  7. Cover privately owned devices where use is allowed, agreeing the conditions with legal and HR input.

Illustrative construction example: a shared survey tablet

Illustrative example 1

A hypothetical contractor uses a tablet for site photographs and client drawings. Several supervisors borrow it, but the office asset register continues to name the original recipient. When the tablet is reported missing, the team cannot establish which site last held it or what information remained available.

Illustrative example 2

The contractor introduces a practical handover record tied to the device and assignment. It limits locally held information to the current need, applies suitable technical protection and clarifies the loss-reporting route. An authorised check follows a sample transfer between supervisors and confirms that responsibility, condition and relevant content are understood. The purpose is traceable custody, not collecting signatures that nobody reconciles.

Automate™ on Effivity · included in every Sterling engagement

Keep clause A.7.9 alive in Effivity

Record what you decided under clause A.7.9, link it to the records and controls it affects, and let the review date trigger the next look. Effivity is the ISO & GRC software used in 50+ countries — and part of every Sterling ISO/IEC 27001 programme.

Illustrative software example: a client demonstration abroad

A fictional software company sends a developer to demonstrate a product at a client's office. The developer initially intends to use a daily work laptop containing unrelated customer material and development credentials. The demonstration itself needs only a prepared environment and sample information.

The company authorises a suitable demonstration setup, removes unnecessary access and agrees how the device will be handled during the visit and return. The employee knows whom to contact if the device is lost or unexpectedly inspected or retained. Before departure, a check confirms the prepared content and access. After return, the organisation reviews any reported concerns and restores the normal arrangement through its approved process.

Combine physical and technical protection

Technical measures can reduce exposure, but their limits matter. Encryption does not prevent loss of the equipment or every disclosure from an unlocked session. Remote deletion depends on conditions such as connectivity and device state and should not be treated as certain recovery of control. Select measures using the asset, information and actual working situation.

Equipment permanently installed at an external location also needs attention. Agree who controls access, inspects its condition and reports damage or changes. A device installed at a customer site can be physically remote while still supporting the organisation's service. The arrangement should explain the retained responsibilities rather than assuming the customer's premises transfer them automatically.

Evidence and useful checks

What counts as evidence

Evidence can include authorised use, current custody, relevant configurations, handover records and incident reports. The organisation needs appropriate documented information for its chosen treatment and operation, but no universal off-site asset form is prescribed. Avoid collecting unnecessary personal travel detail when the security decision requires only asset responsibility and relevant conditions.

A useful review selects a real off-site assignment and follows preparation, use, transfers and return. Ask whether the employee could report a problem outside office hours. Check whether a returned device is assessed before reassignment. Common failures include stale ownership records, uncontrolled loan devices and a loss process that depends on the missing device itself.

Related arrangements include remote working, endpoint security and information transfer. Connect them through operational control so the person travelling receives one usable set of expectations.

Common nonconformities with A.7.9

Typical findings show assets travelling without thought. They typically reflect arrangements written for the office and never adapted for staff who spend most of their time elsewhere.

  • Laptops carrying far more information than the field task requires.
  • No record of which equipment is held away from the premises or by whom.
  • Staff unsure how to report a lost or stolen device.
  • Equipment left unattended in vehicles or hotel rooms with no guidance.
  • Personal devices used for client work with no agreed conditions.

Frequently asked questions

Does this apply only to laptops?

No. Consider relevant devices, media, records and other information assets away from the premises, including equipment at external sites. Protection should reflect the asset and its use.

Is remote wipe a substitute for reporting a loss?

No. Prompt reporting enables assessment and authorised action. Remote deletion may be one measure, but its success and the remaining exposure need evaluation.

Must every off-site transfer use a paper form?

No particular format is required. Choose a reliable way to establish authorisation and custody, and test whether the information remains current when people or locations change.

Support mobile work with clear responsibilities

Discuss off-site asset arrangements with Sterling, including practical documentation, employee learning and agreed Effivity ISO & GRC automation software. Wider implementation support can include scoped authorised vulnerability scanning and findings review. Continued support serves the agreed programme; certification remains the independent body's decision. Enrol employees in ISO/IEC 27001 Awareness to strengthen information-handling and reporting understanding. Return to the physical controls overview for supporting safeguards.

Source basis and reading note. This is original practical guidance for ISO/IEC 27001:2022. Use an authorised copy for definitive requirements. Illustrative examples describe hypothetical situations, not client results. Implementation methods are distinguished from requirements; independent bodies decide certification outcomes. Issuer standard record Issuer standard record: iso.org.
Disclaimer. This guide is provided for general information only. It is not the text of the standard, not legal or professional advice, and not a representation of how any certification body will assess your organisation. Sterling International Consulting accepts no liability for any loss arising from reliance on it. Requirements are applied to each organisation's own context through an engagement; contact us to implement ISO/IEC 27001 in your organisation.