Home › Resources › Templates › Statement of Applicability template

Resources · Template

Statement of Applicability (SoA) template for ISO 27001

In shortA Statement of Applicability template gives each ISO 27001 control one row with the same columns: whether it applies, why it is included or excluded, whether it is implemented, how, who owns it and where the evidence is. This template has ten columns and three example rows. Add one row for each of the 93 Annex A controls.

What is a Statement of Applicability?

The Statement of Applicability, or SoA, records which controls your organisation has decided are necessary, and why. ISO 27001 requires it, and requires a justification for every Annex A control you leave out.

It is not a risk assessment. The risk assessment decides which controls you need; the SoA records the result and checks it against Annex A so that nothing necessary is missed.

RequiredInclusion and reason

Each necessary control and why it is included: a risk, a law, a contract or a business need.

RequiredStatus

Whether the control is implemented.

RequiredExclusions

A justification for every Annex A control that is excluded.

Statement of Applicability template

Ten columns. Three example rows are shown; the control names come from Annex A.

Statement of Applicability template10 rows · example values shown
ColumnExample: includedExample: excluded
Control referenceA.5.15A.7.4
Control nameAccess controlPhysical security monitoring
ApplicableYesNo
Reason for inclusionRisks R-04 and R-11; customer contractsNot applicable
Justification for exclusionNot applicableNo premises of our own; staff work remotely and hosting is with a cloud provider
ImplementedYesNot applicable
How it is implementedAccess control policy v3; role-based access in each systemNot applicable
Control ownerHead of ITNot applicable
EvidencePolicy; quarterly access review recordsSupplier's certificate for hosting
Last reviewed1 Oct 20261 Oct 2026
Ask for an editable file

The example values are illustrative. Copying pastes the table as rows and columns into a spreadsheet or document.

How do you fill it in?

  1. Finish the risk treatment first

    The SoA records decisions; it does not make them.

  2. List all 93 Annex A controls

    Add any other controls you use.

  3. Decide each one

    Included with a reason, or excluded with a justification.

  4. Record status and how

    Point to the policy, procedure or system setting.

  5. Get it approved

    By management, with risk owners.

  6. Review on change

    And at least before each audit.

What goes wrong most often?

01

'Not applicable' with no reason

The auditor cannot assess the exclusion.

Instead: write a specific justification.

02

All 93 marked applicable by default

Controls are claimed that cannot operate in your context.

Instead: decide each on your risks.

03

No link to risks

Inclusions are justified only by 'best practice'.

Instead: refer to the risk, law or contract.

Do you need a template at all?

Pre-mapped Control Library

Controls arrive already mapped across frameworks, each with an owner and a status.

See the module

Statement of Applicability template: common questions

What must an SoA contain?

The necessary controls, the justification for including them, whether they are implemented, and the justification for excluding any Annex A controls.

Does the SoA need a version number?

It is documented information, so it should be controlled: versioned, dated and approved.

Can the SoA be a spreadsheet?

Yes. The standard does not prescribe a format.

Is this template free?

Yes. It is on this page, with no form to fill in. The Annex A control text itself is copyright of ISO and is not reproduced here.

Applicability, status and evidence for every control

The record lives with the audit, linked to its controls, findings and report.

Schedule
Book a Demo