Skip to content
Phalanx
roRequest a quote
Menu+

Resources ·

ISO 27001: where to start, without writing 93 policies

The 93 Annex A controls do not require 93 documents. What the standard asks for, in what order, and what the auditor checks.

ISO 27001 is usually the first framework a company takes on, generally because a customer asked for it in a tender. The good news is that it also gives you the most coverage for everything else: NIS2, the CRA and SOC 2 all sit on top of it. The less good news is that most projects start in the wrong place, which is writing policies.

The standard has two halves

The first half is clauses 4 to 10, the management system. Context, interested parties, roles, objectives, risk assessment, internal audit, management review, nonconformities. None of it can be bought and none of it can be generated. These are things the organisation does and records.

The second half is Annex A, the 93 controls grouped into four themes: organisational, people, physical and technological. The annex is not a task list. It is a reference catalogue you select from, based on assessed risk.

The confusion that costs the most time is treating Annex A as a form to fill in. A control does not necessarily require a policy of its own. It requires that the risk it addresses is treated, and that the treatment can be shown.

The Statement of Applicability

The document the auditor asks for first. For each of the 93 controls you say whether it applies, why, and how it is implemented. A control declared not applicable, with a written reason, is a correct answer. A control declared applicable and implemented, with no evidence that it works, is a nonconformity.

That is where a folder and a system part ways. The policy says access is reviewed quarterly. The evidence is the last review, with its date and who did it. The auditor looks at the second one.

What changed recently

Two things worth knowing.

The transition from the 2013 version is over. Accredited certifications against ISO 27001:2013 had to expire or be withdrawn by 31 October 2025. Any valid certificate today references the 2022 version.

Amendment 1:2024 added, in clauses 4.1 and 4.2, the requirement to determine whether climate change is a relevant issue for the management system, and to consider the climate related requirements of interested parties. It is a small addition, settled with a written and dated analysis, but it is checked at audit. A company with nothing recorded on the subject collects a finding for something that two paragraphs would have closed.

Where to start

In this order, not another.

Scope. What exactly you certify: the whole company, one service, one site. A scope drawn too wide turns the project into a permanent building site.

Inventory. Which assets and services fall inside the scope. Without it, risk assessment is fiction.

Risk assessment. It is what determines which controls apply. Not the other way round.

Then the documents, and only for what came out of the steps before.

Phalanx works in the same order: it reads the documentation you already have, separates the control with no policy from the one that has a policy but no evidence it is applied, and generates only what is missing. A person approves before a policy goes live, because text that walks into an audit without anyone in the company having read it is a risk, not progress.

Want to see how this looks in the platform?

Tell us which regulations apply to you and we will show you the part that matters for you. A person answers, not a qualification form.

Request a quote