Skip to main content
Talk to a human
AI Assistant

ISO 27001 Mandatory Documents: The Complete 2022 List

ISO/IEC 27001:2022 requires a specific set of documented information in clauses 4 to 10. It falls into two kinds: documents, which describe how your information security management system (ISMS) should work, and records, which prove that it does. The documents can be written in a few weeks. The records only exist once the ISMS has been running, and they are what the Stage 2 certification audit is really looking for.

At a glance

  • Mandatory documents: scope, information security policy, risk assessment and risk treatment processes, Statement of Applicability, risk treatment plan, objectives, operational planning
  • Mandatory records: risk assessment and treatment results, competence, monitoring and measurement, internal audit, management review, nonconformities and corrective actions
  • Plus: documents required by the Annex A controls you apply, such as an asset inventory and topic-specific policies
  • Not required by name: procedures, a manual, or one policy per control
  • Any format: a wiki, shared drive or ticketing system is fine, as long as it is controlled

Mandatory documents

These describe how your ISMS is set up. Each is required by a specific clause of ISO/IEC 27001:2022:

Clause Document What it must show
4.3ISMS scopeThe boundaries of the ISMS: activities, locations, people, systems and interfaces
5.2Information security policyManagement’s commitment, objectives framework, and commitment to continual improvement
6.1.2Risk assessment processHow you identify, analyse and evaluate information security risks, and your risk acceptance criteria
6.1.3Risk treatment processHow you choose treatment options and the controls that implement them
6.1.3(d)Statement of ApplicabilityEvery Annex A control, whether it applies and why, and whether it is implemented
6.1.3(e)Risk treatment planThe actions, owners and timescales for treating each risk, approved by the risk owners
6.2Information security objectivesMeasurable objectives, what will be done, by whom, by when, and how results are evaluated
8.1Operational planning and controlEnough documentation to be confident processes are carried out as planned

Mandatory records

These prove the ISMS is operating. You cannot write them in advance; they accumulate as the system runs:

Clause Record Typical example
7.2Evidence of competenceTraining records, qualifications and role descriptions for people working in the ISMS
8.2Results of risk assessmentsThe current risk register, dated and reviewed
8.3Results of risk treatmentProgress against the risk treatment plan
9.1Monitoring and measurement resultsMetrics against your objectives, such as patching times or completed access reviews
9.2Internal audit programme and resultsThe audit plan, audit reports and findings
9.3Management review resultsMinutes recording the inputs reviewed, decisions and actions
10.2Nonconformities and corrective actionsA log of what went wrong, the action taken, and whether it worked

Clause 7.5.1 adds one more category: any other documented information you decide is necessary for the ISMS to be effective. That is your call, and it is where most of an organisation’s procedures sit.

Documents the Annex A controls usually add

Annex A controls only apply if your Statement of Applicability includes them, but for most organisations these do, and each implies something written down:

Two documents are not strictly required but are almost always expected: an analysis of internal and external issues (clause 4.1) and a register of interested parties and their requirements (clause 4.2). They feed the scope, and an auditor will ask how you arrived at it.

What the standard does not require

Why a document list is not enough

A template pack can give you every document in the first table. It cannot give you a single record from the second, because records come from running the ISMS: holding the internal audit, minuting the management review, logging the access reviews and the nonconformities. The certification body expects to see those before the Stage 2 audit.

That is also where template documents cause trouble. If the policy commits you to quarterly access reviews and nobody performs them, there is no record to show, and the document itself becomes the finding.

The order that works: write the documents around what your business already does, so the records start accumulating from day one, then close the gaps. That way, by the time of the Stage 2 audit, every document has the evidence behind it.

Want the documents written around how you already work?

We map how your business operates, assess it against ISO/IEC 27001:2022, and write the mandatory documents and the Annex A policies you need, set up so the records start building straight away. Part of our ISO 27001 readiness work, from S$13,500.

Get an ISO 27001 Quote

Frequently asked questions

What documents are mandatory for ISO 27001:2022?

Clauses 4 to 10 of ISO/IEC 27001:2022 require the ISMS scope, the information security policy, the risk assessment process, the risk treatment process, the Statement of Applicability, the risk treatment plan, information security objectives and operational planning documentation. They also require records: results of risk assessment and risk treatment, evidence of competence, monitoring and measurement results, the internal audit programme and results, management review results, and nonconformities with their corrective actions.

Are procedures mandatory in ISO 27001?

ISO/IEC 27001:2022 does not require procedures by name. It requires documented information, and leaves the organisation to decide what else it needs for the ISMS to work. Some Annex A controls, such as 5.37 documented operating procedures, do call for documented procedures where the control applies.

What is the difference between ISO 27001 documents and records?

Documents describe how the ISMS should work, such as the policy, scope and Statement of Applicability. Records prove that it does, such as internal audit results, management review minutes and evidence of competence. Documents can be written in weeks; records only exist once the ISMS has been running, which is why certification bodies expect a period of operation before the Stage 2 audit.

Do we need a separate policy for every Annex A control?

No. Annex A control 5.1 calls for an information security policy and topic-specific policies where relevant, but there is no requirement for one policy per control. Many SMEs cover the applicable controls with a small set of topic-specific policies, such as access control, acceptable use, supplier security, incident management and backup, referenced from the Statement of Applicability.

Do ISO 27001 documents have to be in a particular format?

No. Clause 7.5 allows documented information in any format or medium, including a wiki, a shared drive or a ticketing system. What it does require is control: documents must be identified, reviewed and approved, kept current, available where needed and protected.

Useful resources

Disclaimer: This article is for general information only and summarises the documented information requirements of ISO/IEC 27001:2022. Refer to the standard for the authoritative text, and to your certification body for how it will assess your documentation.