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.
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.3 | ISMS scope | The boundaries of the ISMS: activities, locations, people, systems and interfaces |
| 5.2 | Information security policy | Management’s commitment, objectives framework, and commitment to continual improvement |
| 6.1.2 | Risk assessment process | How you identify, analyse and evaluate information security risks, and your risk acceptance criteria |
| 6.1.3 | Risk treatment process | How you choose treatment options and the controls that implement them |
| 6.1.3(d) | Statement of Applicability | Every Annex A control, whether it applies and why, and whether it is implemented |
| 6.1.3(e) | Risk treatment plan | The actions, owners and timescales for treating each risk, approved by the risk owners |
| 6.2 | Information security objectives | Measurable objectives, what will be done, by whom, by when, and how results are evaluated |
| 8.1 | Operational planning and control | Enough documentation to be confident processes are carried out as planned |
These prove the ISMS is operating. You cannot write them in advance; they accumulate as the system runs:
| Clause | Record | Typical example |
|---|---|---|
| 7.2 | Evidence of competence | Training records, qualifications and role descriptions for people working in the ISMS |
| 8.2 | Results of risk assessments | The current risk register, dated and reviewed |
| 8.3 | Results of risk treatment | Progress against the risk treatment plan |
| 9.1 | Monitoring and measurement results | Metrics against your objectives, such as patching times or completed access reviews |
| 9.2 | Internal audit programme and results | The audit plan, audit reports and findings |
| 9.3 | Management review results | Minutes recording the inputs reviewed, decisions and actions |
| 10.2 | Nonconformities and corrective actions | A 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.
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.
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.
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 QuoteClauses 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.
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.
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.
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.
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.
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.