ISO/IEC 27001:2022 never says “write sixty documents”. It says documented information — and it says it in two ways. Some clauses require it outright (“shall be available as documented information”). Everything else is documented “to the extent necessary” for you to have confidence that processes run as planned. Auditors test the first list strictly and the second against your own risk assessment. A tidy ISMS is the mandatory set, plus the records your chosen controls produce, and nothing else.
1 · What Clauses 4–10 Require
| Clause | Documented information | What an auditor checks |
|---|---|---|
| 4.3 | ISMS scope | Boundaries, interfaces and exclusions are explicit |
| 5.2 | Information security policy | Approved by top management, communicated, includes objectives framework |
| 6.1.2 | Risk assessment process | Criteria for acceptance and for performing assessments; repeatable results |
| 6.1.3 | Risk treatment process | How controls are chosen and compared with Annex A |
| 6.1.3 d | Statement of Applicability (SoA) | Every Annex A control: included or excluded, why, and implementation status |
| 6.1.3 e | Risk treatment plan | Owners, actions and approval of residual risk by risk owners |
| 6.2 | Information security objectives | Measurable, with plans, owners and dates |
| 7.2 | Evidence of competence | Training, qualifications or experience records for ISMS roles |
| 8.1 | Operational planning and control | Enough evidence that processes ran as planned |
| 8.2 / 8.3 | Risk assessment and treatment results | Current risk register; dated reassessments after significant change |
| 9.1 | Monitoring and measurement results | What is measured, how, by whom, and the results |
| 9.2 | Internal audit programme and results | Plan covering the whole ISMS; independent auditors; findings |
| 9.3 | Management review results | All required inputs considered; decisions and actions recorded |
| 10.2 | Nonconformities and corrective actions | Root cause, action taken, effectiveness checked |
▸ The Statement of Applicability is the document everything else hangs from. It decides which Annex A controls apply — and therefore which of the documents in the next section you need at all.
2 · Documents Annex A Controls Call For
Once a control is in your SoA, these are the documents and records it is normally evidenced by. Several controls state that a procedure or list should be documented; for the rest, documentation is your choice, judged by whether it makes the control work.
| Control | Typical document | Form |
|---|---|---|
| 5.1 | Topic-specific security policies | Policy |
| 5.2–5.3 | Roles and responsibilities; segregation-of-duties matrix | Register |
| 5.9 | Inventory of information and other associated assets | Register |
| 5.10 | Acceptable use of information and assets | Policy |
| 5.12–5.13 | Classification scheme and labelling rules | Policy |
| 5.14 | Information transfer rules and agreements | Policy |
| 5.15–5.18 | Access control policy; access rights matrix; review records | Policy Log |
| 5.19–5.22 | Supplier security requirements; supplier register and assessments | Register |
| 5.24–5.28 | Incident management plan and procedure; incident log; evidence handling | Plan Log |
| 5.29–5.30 | Security during disruption; ICT continuity / disaster recovery plan and test records | Plan |
| 5.31–5.34 | Legal, regulatory and contractual requirements register; privacy / PII protection | Register |
| 5.37 | Documented operating procedures | Procedure |
| 6.1–6.6 | Screening, terms of employment, awareness records, disciplinary process, NDAs | Log |
| 8.8 | Vulnerability management procedure; patch tracker | Log |
| 8.9 | Configuration baselines (including cloud) | Standard |
| 8.10–8.12 | Retention and deletion schedule; data masking and DLP rules | Standard |
| 8.13 | Backup policy and restore-test records | Log |
| 8.15–8.16 | Logging standard; monitoring and log-source list | Standard |
| 8.24 | Cryptography and key management rules | Standard |
| 8.25–8.29 | Secure development lifecycle; secure coding standard; security test records | Standard Log |
| 8.32 | Change management procedure and change log | Procedure Log |
Control numbers follow ISO/IEC 27001:2022 Annex A. For what changed from the 2013 edition, see ISO 27001:2013 → 2022, Quantified.
3 · What the Template Packs Add
Commercial cybersecurity template packs group 60-odd spreadsheets and documents by domain. Measured against the two lists above, they fall into three bins:
| Bin | Examples from typical packs | Verdict |
|---|---|---|
| Evidence you need | Access rights & permissions matrix; data classification register; asset inventory; patch & update tracker; data breach notification log; encryption key management sheet; backup & recovery testing tracker; DR plan and comms plan; audit findings remediation tracker; compliance requirements tracker; third-party risk assessment | Keep — each is a record a mandatory clause or an applicable control will be tested against |
| Useful operational tools | Incident triage checklist; incident response playbooks; log-source onboarding checklist; secure coding checklist; application threat model; cloud security configuration baseline; control framework mapping; KRI tracker; root-cause analysis template | Adopt where the team will actually use them; they make controls work, but are not audit requirements |
| Noise or out of scope | Separate trackers for every log type; network traffic “dashboards” in a spreadsheet; workplace-violence and structural-damage reports; duplicate incident guide, policy and process | Skip — belongs to other functions (HR, facilities) or duplicates a tool you already run |
▸ The test for any document: which clause or SoA control does it evidence, and who updates it? If neither answer exists, it will be out of date by the next audit — and an outdated document is itself a finding.
4 · A 15-Document Starter Kit
For a small organisation starting an ISMS, these fifteen cover the mandatory clauses and the controls almost every SoA includes. Add the rest as your risk assessment demands.
- ISMS scope (4.3)
- Information security policy, with acceptable use and access control as sections (5.2, 5.10, 5.15)
- Risk methodology — assessment and treatment process in one document (6.1.2, 6.1.3)
- Risk register and treatment plan (6.1.3 e, 8.2, 8.3)
- Statement of Applicability (6.1.3 d)
- Security objectives and metrics (6.2, 9.1)
- Asset inventory and classification scheme (5.9, 5.12)
- Supplier register and assessments (5.19–5.22)
- Legal and contractual requirements register (5.31)
- Incident response plan and incident log (5.24–5.28)
- Business continuity / DR plan and test record (5.29, 5.30, 8.13)
- Operations standard — change, patching, backup, logging (5.37, 8.8, 8.13, 8.15, 8.32)
- Training and competence records (7.2, 6.3)
- Internal audit programme and reports (9.2)
- Management review minutes and corrective-action log (9.3, 10.2)
Bottom line
- The standard asks for about fifteen items outright; the rest follows from your SoA.
- The SoA decides the paperwork — an excluded control needs a justification, not a document.
- Records beat documents — auditors sample logs, reviews and test results more than policies.
- Every document needs a clause and an owner, or it will be stale by the next audit.
- Merge where you can — one policy with sections is easier to keep current than twelve.
Sources & method. Clause references from ISO/IEC 27001:2022 (including Amendment 1:2024, which added climate-change considerations to clause 4); Annex A control numbers from the 2022 edition. The template-pack review is the author’s analysis of commonly marketed cybersecurity template collections; no pack is endorsed. The starter kit is a recommendation, not a certification guarantee. Original analysis; no third-party graphics or text reproduced.
← Back to Cyber security