ISO 27001:2022 Annex A 5.10 – Acceptable Use of Information and Other Associated Assets Explained

Most information security incidents involve misuse, not technical failure.

Annex A 5.10 exists to ensure people understand how information and associated assets are expected to be used, and where the boundaries are. Without that clarity, organisations rely on assumption, which is rarely consistent or safe.

This control focuses on setting clear, practical rules for acceptable use, aligned to risk and business context.

ISO 27001

Quick Guide: Annex A 5.10 at a Glance

Annex A 5.10 of ISO 27001:2022 addresses the acceptable use of information and other associated assets.

At a practical level, this means:

  • Defining how information and assets may be used
  • Making expectations clear to those who access them
  • Reducing the risk of accidental or deliberate misuse
  • Supporting confidentiality, integrity, and availability
  • Ensuring expectations are understood, not just documented

The control does not require exhaustive rules for every scenario. It expects reasonable, proportionate guidance that reflects how information and assets are actually used within the organisation.

The aim is clarity, not restriction for its own sake.

In-Depth Guide to Annex A 5.10

What Is Annex A 5.10 and Why Does It Matter?

People interact with information and assets constantly.

This includes:

  • Using devices and systems
  • Accessing and processing data
  • Creating, copying, sharing, or storing information
  • Disposing of information and equipment

Without clear guidance, individuals make their own judgements about what is acceptable. Those judgements vary, and risk is introduced quietly.

Annex A 5.10 ensures that:

  • Acceptable behaviour is defined
  • Unacceptable behaviour is clearly signposted
  • Misuse is easier to prevent and address
  • Accountability is supported

This control underpins many others, including asset management, access control, and awareness.

How to Implement Annex A 5.10 Effectively

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

1. Define Acceptable Use Expectations

Start by defining what acceptable use looks like in practice.

This often includes guidance on:

  • Business use versus personal use
  • Handling of sensitive or classified information
  • Use of organisational devices and services
  • Use of cloud, email, and collaboration tools

Expectations should reflect reality, not idealised behaviour.

2. Clarify Prohibited or High-Risk Activities

Clear boundaries reduce ambiguity.

Organisations often highlight activities that are not permitted, such as:

  • Bypassing security controls
  • Unauthorised data sharing
  • Installing unapproved software
  • Using assets in ways that create legal or security risk

The goal is prevention through clarity, not enforcement alone.

3. Align Use with Asset Value and Classification

Not all information and assets carry the same risk.

Acceptable use guidance should take into account:

  • The sensitivity of information
  • Legal or regulatory obligations
  • Business criticality

This ensures controls remain proportionate and credible.

4. Make Expectations Known and Understandable

Guidance is only effective if people are aware of it.

Common approaches include:

  • Policy acknowledgement during onboarding
  • Awareness and training activities
  • Reinforcement through management behaviour

Documentation without communication rarely changes behaviour.

5. Address the Full Asset Lifecycle

Acceptable use does not end when information is created.

Guidance often covers:

  • Secure handling and storage
  • Copying and transmission
  • Temporary or permanent disposal
  • Return of assets when roles change

This reduces risk throughout the lifecycle of information and assets.

Common Challenges and How to Overcome Them

  • Overly restrictive or unrealistic rules
  • Align acceptable use with how the organisation actually operates
  • Vague guidance that leaves room for interpretation
  • Be clear about expectations and boundaries
  • Policies that are ignored after induction
  • Reinforce expectations through awareness and leadership behaviour
  • Focusing only on misuse after it occurs
  • Use guidance to prevent misuse in the first place

Acceptable use works best when it supports, rather than fights, normal operations.

Final Recommendations

Annex A 5.10 is about setting clear expectations.

When acceptable use is defined and understood:

  • Accidental misuse is reduced
  • Risky behaviour is easier to challenge
  • Accountability is clearer
  • Other security controls are more effective

People cannot meet expectations they do not understand.

Clear, proportionate acceptable use guidance helps ensure information and associated assets are protected without unnecessary friction.

The Annex Control Table

ISO 27001:2022 Organisational Controls
ISO 27001:2022 Technological Controls