A.5 Organizational controls

A.5.1 Policies for information security

Not mandatory by default – decided in your SoA

What it means in plain language

Have a top-level security policy plus topic-specific policies (access, backup, crypto…), approved by management, communicated to staff and reviewed regularly.

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

This control is strongest when the policy set is treated as a managed hierarchy rather than a single static document. The top-level policy should express management direction, while topic policies translate that direction into practical rules for access, backup, crypto, remote work, and incident reporting. Teams should document approval, communication, review cycles, and version control so auditors can see policy intent, distribution, and currency.

Common auditor findings to check for

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

  • The top-level policy existed, but topic policies were missing, outdated, or inconsistent, so staff had no authoritative source for specific security decisions.
  • Policy approval was informal or undocumented, leaving no evidence that management endorsed the current version before communication to personnel.
  • Acknowledgement records were incomplete after onboarding or major updates, so awareness of policy obligations could not be demonstrated for all relevant staff.

How you can implement it

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

  • Maintain one top-level Information Security Policy that sets intent, scope, and governance, then create topic policies for access, backup, cryptography, acceptable use, remote working, and supplier handling where risk justifies them. Align wording so topic rules do not contradict the overarching policy.
  • Route each policy through a formal review path with content owner, approver, effective date, version, and change summary. Use document control fields to record why a review occurred, for example risk change, incident learning, legal update, or management review action.
  • Communicate policies through onboarding, annual refreshers, or significant-change briefings. The IS Policy Acknowledgement Form can capture named recipients, date, version viewed, and exceptions raised, with follow-up for anyone who has not acknowledged within the expected window.
  • Test policy usability by sampling operational decisions against the written rules: access exceptions, backup retention, encryption use, or remote-working conditions. Where staff interpret a rule differently, update the policy language and related procedures so the policy remains practical and enforceable.

What an auditor will ask to see

  • Approved Information Security Policy with version history, owner, approver, and review date.
  • Set of topic policies or standards linked to the top-level policy, showing controlled versions and issue dates.
  • IS Policy Acknowledgement Form records for new starters and staff after substantive policy changes.
  • Review minutes or change log explaining why policy updates were made and who signed off them.

Baseline documents in the kit

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

Connect this work to your ISMS

Review the dependencies with 5.2 — Policy and A.5.2 — Information security roles and responsibilities. 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.