Skip to content
The number one comparison site for certification in the Netherlands

Mandatory documents for ISO 27001

ISO 27001 requires a fixed set of documents. You need your scope, your information security policy, the method for risk assessment and risk treatment, the Statement of Applicability, the risk treatment plan and your objectives. In addition, you keep evidence. That is the results of your risk assessments, training, measurements, internal audits, the management review and nonconformities. For each control from Annex A the Statement of Applicability states whether it is needed. It also states whether you have implemented the control and why you exclude it. The auditor uses that Statement and your risk assessment as a map for the audit.

Compare certification bodies for ISO 27001
On this page
  1. Documented information in ISO 27001
  2. Documents you keep up to date for ISO 27001
  3. Mandatory records for ISO 27001
  4. Statement of Applicability for ISO 27001
  5. Risk treatment plan for ISO 27001
  6. Documents that follow from the controls of Annex A
  7. Documents in stage 1 of the ISO 27001 audit
  8. Documents in stage 2 of the ISO 27001 audit
  9. Comparing ISO 27001 certification bodies on the audit of your documents

Ready-made packages for ISO 27001 often supply dozens of policy documents and procedures. But which documents do you really need, and what does the auditor pay attention to? After reading this article you will know which documents and records are mandatory, what belongs in the Statement of Applicability and the risk treatment plan, which documents follow from Annex A and how the auditor uses your documents in stage 1 and stage 2.

Documented information in ISO 27001

ISO 27001 calls everything you record documented information. For each requirement the standard says whether you have to record something. Not every requirement asks for a document. In the fixed structure of its own standards, ISO explains what that means: for a requirement in which you only "determine" something, you do not need a document. You must be able to show it, though.

There are two kinds that you do have to record:

  • Documents. Information that you keep up to date and use, such as your policy and your Statement of Applicability.
  • Evidence. Results of what has happened, which you have recorded. Think of a risk assessment or an audit report. In plain language: your records.

You choose the form yourself: a document, a spreadsheet, a wiki or a record in a tool. How much else you record depends on the size and the kind of work of your company. It also depends on how complex your processes are and how competent your people are. The applicable edition is ISO/IEC 27001:2022. Which requirements lie behind this is explained in the requirements of ISO 27001.

Documents you keep up to date for ISO 27001

ISO 27001 requires these documents. The table adds the clause of the standard:

DocumentWhat it containsClause
Scope which departments, locations, systems and services fall under your ISMS 4.3
Information security policy what your company stands for and which objectives and commitments apply 5.2
Risk assessment method how you find and weigh risks, and when you accept a risk 6.1.2
Risk treatment method how you choose for each risk what you do 6.1.3
Statement of Applicability for each control from Annex A: needed or not, implemented or not, and why 6.1.3 d
Risk treatment plan which controls you take, who carries them out and when 6.1.3 e
Information security objectives what you want to achieve and how you measure it 6.2

You communicate the policy within the company. Where appropriate, you also communicate it to interested parties. You may put the two methods in one document. Then both must be in it.

Mandatory records for ISO 27001

In addition to the documents, you keep evidence. With it you show that you do what you have agreed. ISO 27001 requires this evidence:

SubjectWhat you keepClause
Competence evidence that your people can do their task in the ISMS, such as training and experience 7.2
Operation as much evidence as needed to know that your processes run as planned 8.1
Risk assessment the results of every assessment, including the repeats 8.2
Risk treatment the results of the treatment 8.3
Measurements the result of what you measure and analyse 9.1
Internal audit the audit programme and the results 9.2
Management review the result of the fixed moment at which management looks at whether the ISMS works 9.3
Nonconformities what went wrong, what you did and what your measure achieved 10.2

You control all these documents according to clause 7.5. They are approved before they apply. Whoever needs them must be able to find them. They have version control and a retention period. For ISO 27001 one rule from 7.5 counts extra heavily. Your documents must be protected against loss of confidentiality and integrity. So a risk assessment with your weak spots does not belong in a folder the whole company can access.

Statement of Applicability for ISO 27001

The Statement of Applicability (SoA) is an overview of all 93 controls from Annex A. For each control it contains your choice, with the reason. The Statement links your risk assessment to what you actually do. For each control it states:

  • whether it is needed, and why: because of a risk, a law or an agreement with a customer;
  • whether you have already implemented it;
  • why you exclude it, if you do.

Also include your own controls that are not in Annex A. In practice the Statement is a table with 93 rows plus your own controls. One column refers to the evidence, such as the policy or the tool in which you arrange the control. Many ISO 27001 certificates state the version of the Statement on which the certificate is based. That way a customer sees which controls are included. If your Statement changes significantly, you consult your certification body. Then you hear whether the certificate needs to be updated.

When you may exclude a control is explained in the requirements of ISO 27001.

Risk treatment plan for ISO 27001

The risk treatment plan says how you tackle the risks you found in your risk assessment. The Statement of Applicability says which controls you have. The plan says who does what and when it is finished. It also includes the risk owners approving the plan. They also accept the risks that remain.

So a good plan is a work list. An example: "multi-factor authentication for all admin accounts, owner IT management, done in March". A plan without names or dates does not show the auditor that you are carrying it out. After you have carried it out, you keep what it produced (8.3). After a change, such as a new cloud service, you assess the risks again. Then you update the plan.

Documents that follow from the controls of Annex A

If you choose a control in your Statement of Applicability, that control sometimes itself requires documentation. These are not requirements from clauses 4 to 10. They only apply if the control applies to you. A few examples from Annex A:

ControlWhat you then record
5.1 Policies for information security topic-specific policies, such as access or remote working
5.9 Inventory of information and other associated assets an overview of your information, systems and devices, with an owner
5.31 Legal, statutory, regulatory and contractual requirements which laws and agreements apply to your information
5.37 Documented operating procedures work instructions for your IT management

For the other controls the standard does not prescribe a document. So a procedure per control is not needed. Often a setting in your system or a tick in your tool is the evidence. Guidance per control is in ISO/IEC 27002. You are not audited against that guidance.

Documents in stage 1 of the ISO 27001 audit

In stage 1 the auditor checks whether your documents are complete enough to really assess your ISMS. The rules for this are in ISO/IEC 17021-1. Additions for information security are in ISO/IEC 27006-1:2024. The auditor looks at:

  • your documented ISMS: scope, policy, objectives, risk assessment, Statement of Applicability and risk treatment plan;
  • your locations, your systems and the laws and agreements that apply to your information;
  • whether you understand the requirements of the standard and how far along you are;
  • whether your internal audit and management review are planned and under way.

The auditor gives you the conclusions in writing. They contain the points that may become a nonconformity in stage 2. For ISO 27001 this is often a scope that does not match the risk assessment. It can also be an exclusion in the Statement without a reason. Resolve those points before stage 2 starts.

Documents in stage 2 of the ISO 27001 audit

In stage 2 the auditor checks whether your ISMS works in practice. Your risk assessment and your Statement of Applicability serve as a map. The auditor picks controls from the Statement and follows a trail. That trail runs from a risk to the chosen control. From there it runs to the evidence that the control works. That evidence is, for example, an overview of access rights, a test of your backup or the report of an incident. A control that you call "implemented" must be visible to the auditor. The auditor must be able to trace an exclusion back to your risk assessment.

Is a mandatory document missing, such as the Statement of Applicability or the evidence of your internal audit? Then that is often a major nonconformity. You have to resolve it before you get the certificate. What happens after stage 2 is explained in the certification audit. The whole process is in the steps for ISO 27001.

Comparing ISO 27001 certification bodies on the audit of your documents

The requirements for your documents are the same at every certification body. What differs is how a certification body approaches stage 1 and how many days it charges. Ask three things in the quote. Can stage 1 be done remotely? How much time is there between stage 1 and stage 2? What does it cost if stage 2 has to be redone? The days themselves are in the costs of ISO 27001. With your scope and your Statement of Applicability at hand, you request quotes in one go through CertificeerWijzer. These are certification bodies that may cover ISO 27001. Then you put their answers side by side. If you work with health data, also look at NEN 7510. That standard requires the same documents, plus its own controls for healthcare.

Sources

  1. ISO, ISO/IEC 27001:2022, Information security management systems, Requirements (edition 3) iso.org
  2. NEN, NEN-EN-ISO/IEC 27001:2023 nl, preview copy (contents, introduction, clauses 1 to 3) nen.nl
  3. NEN, Frequently asked questions about ISO/IEC 27001 nen.nl
  4. ISO/TMBG, ISO/IEC Harmonized structure for MSS with guidance for use, 2026-07-01 iso.org
  5. ISO, ISO/IEC 27002:2022, Information security controls iso.org
  6. IAS, summary of ISO/IEC 17021-1:2015 section 9 iasonline.org
  7. UKAS F627, Transition Requirements and Gap Analysis ISO/IEC 27006-1:2024 (structure of sections) ukas.com