Most ISO 27001 projects either under-document and fail Stage 1, or over-document and drown in policies nobody reads. ISO/IEC 27001:2022 asks for a short, specific set of documented information in clauses 4 to 10, and Annex A adds more only where a control is applicable. This guide lists each required document and record clause by clause, separates what the standard demands from what auditors commonly expect, and shows how to keep the set small, current and defensible. It is written for ISMS owners, internal auditors and consultants preparing for certification or a surveillance visit. For the wider certification picture, see the ISO 27001 Certification Guide; this page stays on documentation.
Key takeaways
- The mandatory core is short. Clauses 4 to 10 require roughly a dozen documents and records: scope, policy, risk assessment and treatment processes and results, the Statement of Applicability, objectives, competence evidence, monitoring results, audit programme and results, management review results and corrective action records.
- Annex A documentation is conditional. Items such as the asset inventory, incident procedure or logs become required only when the related control is applicable in your Statement of Applicability.
- Clause 7.5.1 b is the open door. The standard also requires whatever documented information you decide is needed for the ISMS to be effective, so your own procedures become auditable once you declare them.
- Documents and records behave differently. Documents (policies, procedures) are maintained and versioned; records (results, evidence) are retained and protected from change.
- Auditors sample evidence, not page counts. A lean set that matches what people actually do passes more easily than a large library that contradicts practice.
Documents versus records in ISO 27001:2022
The 2022 edition, like other management system standards built on the harmonised structure, uses one term, documented information, for both. In practice the standard uses two verbs that matter for how you manage each item.
| Aspect | Maintained documented information (documents) | Retained documented information (records) |
|---|---|---|
| Examples | ISMS scope, information security policy, risk assessment methodology, Statement of Applicability | Risk assessment results, internal audit results, management review results, training records |
| Lifecycle | Drafted, approved, versioned, reviewed, superseded | Created once as evidence, then kept unchanged for a defined period |
| Key control under clause 7.5.3 | Version control, approval, distribution to those who need it | Retention period, integrity protection, controlled disposal |
| Typical audit question | Is this the current approved version and do staff know it? | Show me the evidence this happened, and when |
Clause 7.5 itself does not demand a written document control procedure. It requires that documented information is identified, in a suitable format, reviewed and approved, available where needed, protected, and kept under control for distribution, storage, change, retention and disposal. A short procedure is the usual way to show that, which is why it appears in the commonly expected list below.
Mandatory documented information in clauses 4 to 10
These items are required for every certified ISMS regardless of the Statement of Applicability. The clause references below are to ISO/IEC 27001:2022; the wording is our paraphrase.
| Clause | Item | Type | What the auditor usually checks |
|---|---|---|---|
| 4.3 | ISMS scope, including boundaries, interfaces and dependencies | Document | Scope matches the certificate wording, sites and services; exclusions are explained |
| 5.2 | Information security policy | Document | Approved by top management, includes objectives or a framework for them, commitments to requirements and continual improvement, communicated |
| 6.1.2 | Information security risk assessment process | Document | Risk acceptance criteria, criteria for performing assessments, consistent and comparable results, named risk owners |
| 6.1.3 | Information security risk treatment process | Document | How options are chosen, how controls are compared with Annex A, how owners approve residual risk |
| 6.1.3 d | Statement of Applicability | Document | All 93 Annex A controls listed with inclusion or exclusion, justification and implementation status |
| 6.1.3 e | Risk treatment plan | Document | Actions, owners, resources and timing, with risk owner approval of the plan and residual risk |
| 6.2 | Information security objectives | Document | Measurable where practicable, with what, who, when and how results will be evaluated |
| 7.2 | Evidence of competence | Record | Training, qualifications and experience for people whose work affects security |
| 7.5.1 b | Documented information the organisation decides is necessary | Either | Anything you declare (procedures, standards) is followed and controlled |
| 8.1 | Evidence that processes ran as planned | Record | Kept to the extent needed for confidence; change records and operational logs often serve here |
| 8.2 | Results of risk assessments | Record | Assessments at planned intervals and after significant change |
| 8.3 | Results of risk treatment | Record | Progress against the treatment plan |
| 9.1 | Monitoring and measurement results | Record | Metrics defined, collected and analysed, feeding management review |
| 9.2.2 | Internal audit programme and audit results | Record | Programme covers the whole ISMS over the cycle; auditors are objective; findings reported |
| 9.3.3 | Results of management reviews | Record | Required inputs covered, decisions on improvement and changes recorded |
| 10.2 | Nature of nonconformities, actions taken and results of corrective action | Record | Root cause, correction, corrective action and effectiveness check |
For how to run the internal audit and management review that generate the 9.2 and 9.3 records, see the ISMS Internal Audit and Management Review guide. For the SoA layout, start from the ISO 27001 Statement of Applicability Template.
Annex A documentation that becomes required when a control applies
Annex A controls are selected through risk treatment. When a control below is marked applicable in the SoA, its wording explicitly calls for something to be documented, identified or recorded, and auditors will expect to see it. If you exclude the control with justification, the item is not required.
| Annex A control | Documented item expected | Practical form |
|---|---|---|
| 5.1 Policies for information security | Topic-specific policies, approved and communicated | Access control, cryptography, supplier, backup and similar policies, often as short standards |
| 5.9 Inventory of information and other associated assets | Asset inventory with owners | CMDB or register covering information, systems, cloud services and identities |
| 5.10 Acceptable use of information and other associated assets | Rules and procedures for acceptable use | Acceptable use policy acknowledged by staff |
| 5.26 Response to information security incidents | Documented incident response procedures | Incident procedure and playbooks, with incident records as evidence |
| 5.31 Legal, statutory, regulatory and contractual requirements | Identified and documented requirements | Legal and contractual register, kept current |
| 5.37 Documented operating procedures | Operating procedures for information processing facilities | Runbooks for backups, provisioning, patching and recovery |
| 6.2 Terms and conditions of employment | Security responsibilities in employment contracts | Contract clauses and signed copies |
| 6.6 Confidentiality or non-disclosure agreements | Identified, documented and reviewed agreements | NDA templates and signed records |
| 8.9 Configuration management | Established and documented configurations, including security configurations | Hardening baselines and configuration records |
| 8.15 Logging | Logs of activities, exceptions, faults and other events | Centralised logs with protected retention |
| 8.27 Secure system architecture and engineering principles | Documented engineering principles | Secure design principles referenced in the SDLC |
Control-by-control implementation detail lives in the ISO 27001 Annex A.5 Organisational controls, ISO 27001 Annex A.6 People controls and ISO 27001 Annex A.8 Technological controls guides. ISO/IEC 27002:2022 is the guidance companion to Annex A; it cannot be certified against, but it explains each control's purpose.
Commonly expected but not mandatory
These documents are not demanded by the standard's wording, yet most certification bodies expect to see something equivalent because they are the simplest evidence that a clause or control operates. Declare the ones you adopt under 7.5.1 b and then follow them.
- Document and record control procedure (7.5, A.5.33): naming, approval, review cycle, retention periods and disposal.
- Internal audit procedure (9.2): planning, auditor independence, reporting and follow-up.
- Corrective action procedure (10.2): root cause method and effectiveness checks.
- Information classification policy (A.5.12, A.5.13): levels, labelling and handling rules.
- Access control and authentication policy (A.5.15 to A.5.18, A.8.5): joiner, mover and leaver steps, privileged access and credential rules.
- Supplier security policy (A.5.19 to A.5.23): due diligence, contract clauses and cloud service use.
- Business continuity and ICT readiness plans (A.5.29, A.5.30, A.8.14): recovery objectives and test records.
- Backup, encryption and change management policies (A.8.13, A.8.24, A.8.32): often combined into an IT operations standard.
Where identity fits
Identity evidence is where many ISMS libraries look complete on paper and thin in sampling. Three mandatory or conditional items depend on it directly.
- Asset inventory (A.5.9): auditors increasingly ask whether service accounts, API keys and workload identities are inventoried with owners. A register that lists servers but not the credentials that reach them leaves a gap. See the AI Register and AI Inventory Template for a comparable register structure.
- Access review records (A.5.18): a policy saying access is reviewed quarterly is a document; the signed-off review with removals is the record that proves it.
- Logs (A.8.15): logs must attribute actions to an identity, which fails when automation shares one account. Keep evidence that machine identities are individual and that log retention is protected.
How to build and maintain the documentation set
- Fix scope first (4.3). Every other item references it; write it in the exact words you want on the certificate.
- Write the policy and the two risk processes (5.2, 6.1.2, 6.1.3). Keep the methodology to a few pages with a scoring table and acceptance threshold.
- Run the first risk assessment and produce the SoA and treatment plan. The SoA becomes the index for which Annex A items you must document.
- Generate the conditional Annex A documents only for applicable controls. Reuse existing operational artefacts (runbooks, CMDB, contracts) rather than rewriting them as policies.
- Set retention periods for every record type. At least the full three-year certification cycle is a common baseline; legal or contractual obligations may require longer.
- Produce records by operating the ISMS. One cycle of metrics, an internal audit covering the scope and a management review are needed before Stage 2.
- Test with a mock sample. Pick ten controls at random and try to produce evidence within an hour; fix what you cannot find. Track requests in the Audit Evidence Request Tracker Template.
- Review annually and on significant change. Retire documents nobody uses; an outdated policy is a nonconformity, a missing optional one is not.
Decision guidance: how much to write
| Situation | Recommended approach | Trade-off |
|---|---|---|
| Small organisation, single site, under about 50 staff | One combined ISMS manual holding scope, policy and risk methodology, plus a short topic policy set | Fewer files to maintain; harder to delegate ownership |
| Mid-size with several teams | Separate documents per owner, central register of documented information with review dates | Clear ownership; needs a document controller role |
| Large or multi-certificate (27001 with 27701, 42001, 9001) | Shared management system documents for common clauses, standard-specific annexes | Less duplication; integration effort up front |
| Heavily automated cloud estate | Treat infrastructure as code, policy as code and ticket history as records | Strong evidence; auditors need a walkthrough of where to find it |
Measuring documentation health
- Review currency: percentage of controlled documents reviewed within their stated cycle (target 100 percent).
- SoA alignment: applicable controls with at least one evidence item mapped (target 100 percent before Stage 2).
- Evidence retrieval time: median minutes to produce a sampled record during mock audits.
- Audit findings linked to documentation: number of nonconformities citing clause 7.5 or a missing record per audit.
- Policy acknowledgement: percentage of in-scope staff who acknowledged current policies.
Framework mapping
| ISO 27001 item | NIST CSF 2.0 | NIST SP 800-53 Rev 5 |
|---|---|---|
| 5.2 Information security policy, A.5.1 | GV.PO-01 | PM-1 |
| Roles and responsibilities (5.3, A.5.2) | GV.RR-02 | PM-1 |
| A.5.31 Legal and contractual requirements | GV.OC-03 | PL-2 |
| A.5.9 Asset inventory | ID.AM-01 | CM-8 |
| A.8.15 Logging | PR.PS-04 | AU-2 |
Common failure patterns
- SoA justifications that only say "not applicable". Exclusions need a reason tied to scope or risk; bare labels draw findings.
- Policies copied from a template that contradict practice. A policy promising monthly access reviews when reviews are annual creates a nonconformity that a shorter, honest policy would avoid.
- No records from operating the ISMS. Documents exist but there is no metric data, audit report or management review minute before Stage 2.
- Uncontrolled copies. Old PDF versions on shared drives and wikis undermine 7.5.3; publish one controlled location.
- Records with no retention rule. Logs and tickets are purged before the next surveillance audit can sample them.
- Risk treatment plan without risk owner approval. Clause 6.1.3 expects owners to approve the plan and accept residual risk; missing sign-off is a frequent Stage 1 finding.
Practitioner checklist
- Write the scope in certificate wording, with interfaces and dependencies.
- Hold an approved policy, risk assessment process and risk treatment process.
- Complete the SoA for all 93 controls with justification and status.
- Keep a risk treatment plan with risk owner approval of residual risk.
- Define measurable objectives and collect at least one cycle of metric results.
- Keep competence records for everyone in security-relevant roles.
- Produce documented items for every applicable control that calls for them, starting with the asset inventory, incident procedure, legal register and operating procedures.
- Set retention periods and integrity protection for every record type.
- Complete an internal audit and management review before Stage 2 and keep the results.
- Maintain a register of documented information with owners and review dates.
Standards and references
- ISO: ISO/IEC 27001 Information security management systems
- ISO: ISO/IEC 27002:2022 Information security controls
- Advisera: List of mandatory documents required by ISO 27001
- NIST: Cybersecurity Framework 2.0
- NIST: SP 800-53 Rev 5 Security and Privacy Controls
- ISO: ISO/IEC 27006-1:2024 Requirements for ISMS certification bodies
Related NHI Mgmt Group resources: ISO 27001 Certification Guide · ISO 27001 Certification Readiness Checklist · ISO 27001 Statement of Applicability Template · ISO 27001 Surveillance Audit Checklist