← ISO 27001: Critical success factors ISO 27001

ISO 27001: Control Selection and the SoA

The Statement of Applicability (clause 6.1.3)

Tom Whipp · 31 October 2026 · 4 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

Control selection is deciding which controls you need to treat your risks. The Statement of Applicability (SoA) records the result and maps it against Annex A of the standard.

This is where most of the design effort belongs. Your big efficiencies come from better control statements, not from automating evidence collection later.

What the standard asks

Clause 6.1.3 sets out the sequence:

  • Determine the controls you need to implement your chosen risk treatment. A note to the clause makes clear they can come from any source: designed yourself, taken from another framework, or already running across the business.
  • Compare them against Annex A to check nothing necessary has been missed. Another note confirms Annex A isn't exhaustive, so adding controls of your own is expected.
  • Produce a Statement of Applicability listing the necessary controls, why each is included, whether it's implemented, and why any Annex A control has been excluded.

There's no requirement to select your controls from Annex A. If you genuinely don't need one of its controls, the obligation is to say why.

What good looks like

  • Controls describe what you actually do. Say what you actually do, not what you wish you did. That's the biggest mistake in any audit preparation.
  • Each control is well formed. Write it as what happens, when, where, who does it and why. A control focused on who makes a decision is much easier to evidence.
  • The evidence is designed in. Each control says what evidence it produces and where that evidence will be kept.
  • Exclusions are justified by your scope and risks, in a sentence or two.
  • The SoA is versioned and approved, and updated when controls change.

Evidence an auditor will ask for

  • The Statement of Applicability, with inclusions, implementation status and justified exclusions
  • Control descriptions, including owners and expected evidence
  • The link from controls back to the risks they treat
  • Approval of the SoA, and its change history

Common failure modes

  • Annex A titles as controls. Copying "Access control policy" into your control list describes a topic, not something anyone does.
  • Implementing all 93 to be safe. Every control you claim is a control you have to evidence. Controls without a risk behind them are pure cost.
  • Aspirational controls. Quarterly reviews that actually happen annually turn into nonconformities you wrote yourself.
  • The SoA as a one-off. Built for the first audit and never touched again, it drifts away from reality within a year.

How it connects

Feeds from

Feeds into

Where it sits in the plan

Stage: Plan. Control selection is the core of the first Plan. Start from what you already do, describe it properly, then map it to Annex A. Front-load the work in design and the audits become far less stressful. On later cycles the SoA changes as risks, events and audit findings change the controls.

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.