← ISO 27001: Critical success factors ISO 27001

ISO 27001: Policies and Standards

The information security policy (clause 5.2 and Annex A 5.1)

Tom Whipp · 31 October 2026 · 3 min read

Part of ISO 27001: Critical success factors, a series on building a management system that reflects how your organisation really runs.

What it is

Policies set out what the organisation expects; standards say concretely how. In ISO 27001 there are two layers: a single top-level information security policy owned by leadership, and topic-specific policies and standards covering areas such as access, suppliers or acceptable use.

Policies need to be read to have an impact, so being as short as possible is an important feature.

What the standard asks

  • Clause 5.2 requires top management to establish an information security policy that fits the organisation's purpose, includes objectives or a framework for setting them, and commits to meeting applicable requirements and to continual improvement. It has to be documented, communicated within the organisation, and available to interested parties as appropriate.
  • Annex A control 5.1 covers topic-specific policies: defined, approved by management, published, communicated to and acknowledged by the people they apply to, and reviewed at planned intervals or when things change.

The standard doesn't prescribe a particular set of policies. What you need depends on your controls and your risks.

What good looks like

  • A short top-level policy, signed by leadership, that someone outside security could read in five minutes.
  • Topic-specific policies that match practice. They describe how people actually work, and they change when practice improves.
  • Standards carry the detail, such as configuration settings or retention periods, so the policies themselves stay readable.
  • Each document has an owner and a review date, and staff acknowledge the ones that apply to them.

When you find a gap between policy and practice, don't assume aligning to the policy is the right answer. Quite often live practice is more risk-aware, and policy can be updated.

Evidence an auditor will ask for

  • The approved information security policy and how it was communicated
  • Topic-specific policies and standards, with owners and review dates
  • Records of staff acknowledgement
  • Evidence of periodic review

Common failure modes

  • The template pack. A forty-page downloaded policy set promising things you don't do. Every promise is something the auditor can test, so you end up writing your own nonconformities.
  • Policies nobody reads. Long, legalistic documents signed at induction and never opened again.
  • Policy as control. A policy saying access is reviewed quarterly isn't evidence that it is.
  • Stale documents. Review dates long passed, owners who left two years ago.

How it connects

Feeds from

Feeds into

Where it sits in the plan

Stage: Commit (top-level policy) and Plan. The top-level policy is agreed with leadership before the loop starts. Topic-specific policies and standards are written in Plan, alongside the controls they describe.

The plan in the main article shows how this fits with everything else, and the bootstrapping guide covers each stage in detail.

Resources


Tom Whipp is the founder of RiskQuilt. He spent around thirty years in cyber and technology risk in UK financial services, including CISO and Director of Technology Risk roles.

Ready to leave the spreadsheets behind?

Start your free trial today. No credit card required. No sales call. Your data, your platform, in minutes.