Clause 5 – Leadership

Clause 5.2 Policy

Mandatory requirement Documented information required

What it means in plain language

Top management must issue an information security policy that fits your organization, sets or frames your security objectives, commits to meeting applicable requirements and to continual improvement. It must be documented, communicated internally and available to interested parties where appropriate.

Is it mandatory? Yes. Clauses 4–10 are the management-system requirements; all of them must be met to be certified, and none can be excluded.

Documented information

  • Information security policy.

Why this requirement matters

The information security policy connects the organisation’s purpose to the direction of its ISMS. A copied statement can sound comprehensive while offering no usable basis for objectives or decisions. A useful top-level policy explains management’s commitment to applicable requirements and continual improvement, gives people a recognisable direction, and stays consistent with the services and boundaries the organisation actually manages.

Common auditor findings to check for

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

  • The policy describes a different operating model from the current business, such as office-only work when sensitive processing also occurs remotely.
  • Security objectives cannot be linked to the policy’s direction, and the document omits a clear commitment to applicable requirements or continual improvement.
  • An approved policy exists in a restricted folder, but staff cannot find it and there is no defined approach to appropriate external availability.

How you can implement it

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

  • Have the ISMS lead draft a concise policy with leadership using the agreed scope, context and stakeholder requirements. Separate strategic commitments from detailed technical rules so routine platform changes do not require rewriting the top-level direction.
  • Obtain approval from top management through a controlled workflow and record the version approved. Confirm the wording provides a framework for objectives and fits the organisation’s purpose, rather than adding commitments that current operations cannot support.
  • Publish the approved version through a channel staff actually use and explain material changes during onboarding or relevant briefings. Determine which interested parties should receive it and provide a controlled public or shareable version where appropriate.
  • Review policy suitability when business context, obligations or scope change, alongside a planned review cycle chosen by the organisation. Record a review even when no wording changes, and retire obsolete copies to avoid conflicting instructions.

What an auditor will ask to see

  • The approved Information Security Policy, including accountable ownership, approval history and the commitments relevant to the current organisational purpose and scope.
  • Internal publication and communication records, supported by staff interviews demonstrating that the current policy is accessible and its direction is understood.
  • A trace from the policy to information security objectives, plus records explaining review decisions and how appropriate interested-party access is maintained.

Baseline documents in the kit

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

Connect this work to your ISMS

Review the dependencies with A.5.1 — Policies for information security and 6.2 — Information security objectives and planning to achieve them. 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.