A.5 Organizational controls

A.5.10 Acceptable use of information and other associated assets

Not mandatory by default – decided in your SoA

What it means in plain language

Set clear rules for how people may use information and company assets (devices, email, internet, AI tools).

Is it mandatory? Not automatically. You must consider this control in your Statement of Applicability (6.1.3 d). Include it if your risk assessment, laws, contracts or business needs require it; if you exclude it, write down a justification an auditor will accept.

Why this control matters

Acceptable use breaks down when staff are given broad prohibitions but no examples of permitted and prohibited behavior in real workflows. The strongest guidance connects device use, information handling, and external services so teams can see how misuse leads to exposure through copying, forwarding, personal accounts, or unsupported AI tools. It should also anchor expectations to ownership, awareness, and enforcement records rather than relying on policy text alone.

Common auditor findings to check for

Potential gaps to test in your own environment, not a claim about observed audit frequency.

  • Users can describe a policy but cannot explain which data classes may be stored, forwarded, or pasted into public AI services, suggesting the rules were not operationalized.
  • The organization lacks acknowledgment records or role-based exceptions, so high-risk activities such as admin access, remote access, or removable media use are not evidenced as controlled.
  • Incidents involving email misdirection, unapproved software, or personal account use are handled case by case without linked training updates, disciplinary references, or rule revisions.

How you can implement it

Tools and review intervals are examples; choose them according to risk, obligations and your operating environment.

  • Map acceptable use rules to actual work scenarios: managed laptops, personal devices, messaging apps, browsers, and public AI tools. Specify who approves exceptions, what data categories are never entered into external services, and which high-risk activities require additional approval or supervision.
  • Describe onboarding and annual acknowledgment steps, with the Acceptable Use Policy signed or electronically accepted by employees, contractors, and temporary staff. Include an owner for tracking missing acknowledgments, a reminder cadence, and a record of escalations for repeated refusal or non-response.
  • Add practical handling instructions aligned to classification and asset management: lock screens, no shared accounts, approved storage locations, secure disposal of printed notes, and prohibited forwarding to personal email. Make the guidance show how exceptions are documented and reviewed by line managers and information security.
  • Explain how breaches of acceptable use are detected and corrected through ticketing, HR escalation, or retraining. Name the roles that investigate, record facts, decide corrective action, and update awareness materials so the same misuse pattern is less likely to recur.

What an auditor will ask to see

  • Signed or electronically acknowledged Acceptable Use Policy records for staff, contractors, and privileged users, with onboarding date and annual re-acknowledgment status.
  • Exception register for approved personal-device or external-tool use, including business justification, data limits, approver, and review date.
  • Awareness or incident records showing misuse examples, corrective actions, and follow-up communication to affected teams.

Baseline documents in the kit

These free kit documents help you document or evidence A.5.10. Each one is tailored to your organization when you build your kit.

Connect this work to your ISMS

Review the dependencies with A.6.3 — Information security awareness, education and training and A.8.5 — Secure authentication. Keep the ownership and evidence consistent across these activities.

Required information and the kit’s 19-document core for the wider implementation context.

Use the SIG and CAIQ questionnaire accelerator to find supporting documents. A mapping is a starting point: verify your actual operating evidence before answering a buyer.

For help adapting this to your environment, explore ISO/IEC 27001 consulting, starting with a free one-hour consultation.

Get these documents tailored to your organization

109 ready-to-edit documents, including all 19 mandatory ones, tailored from a short scoping questionnaire and linked to your risk register and SoA.

Start free

Plain-language interpretation by an ISO/IEC 27001 lead implementer, not the official text of ISO/IEC 27001:2022.