Understanding ISO 27001 Document Requirements
One of the most common questions from organizations starting their ISO 27001 journey is: "What documents do we actually need?" The answer is more nuanced than many expect. ISO 27001:2022 explicitly requires certain documents (referred to as "documented information"), while other documents are strongly recommended but technically optional.
Getting your ISO 27001 mandatory documents right is critical. Missing a required document is an automatic nonconformity in a certification audit. Having poorly written documents that do not meet the standard's requirements is equally problematic.
This guide provides the complete ISO 27001 mandatory documents list for 2026, covering every document explicitly required by clauses 4 through 10 and the applicable Annex A controls.
What Does "Mandatory" Mean in ISO 27001?
ISO 27001 uses the term "documented information" to refer to any document, record, policy, procedure, or evidence that the standard requires. There are two categories:
-
Documents that must be maintained - These are policies, procedures, and plans that define how your ISMS operates. They must exist, be current, and be accessible to relevant personnel.
-
Records that must be retained - These are evidence of activities performed, such as risk assessment results, audit reports, management review minutes, and training records. They must be retained for a defined period as proof that your ISMS is operational.
Mandatory Documents Required by ISO 27001 Clauses
Clause 4: Context of the Organization
4.3 - Scope of the ISMS (Mandatory) You must have a documented scope statement that defines the boundaries and applicability of your ISMS. The scope must consider:
- External and internal issues (from 4.1)
- Requirements of interested parties (from 4.2)
- Interfaces and dependencies with activities performed by other organizations
Common mistakes:
- Scope is too vague ("all company activities")
- Scope does not address interfaces with external parties
- Scope does not mention physical locations or services covered
Clause 5: Leadership
5.2 - Information Security Policy (Mandatory) Top management must establish an information security policy that:
- Is appropriate to the purpose of the organization
- Includes information security objectives or provides a framework for setting them
- Includes a commitment to satisfy applicable requirements
- Includes a commitment to continual improvement
The policy must be documented, communicated within the organization, and available to interested parties as appropriate.
Common mistakes:
- Policy is generic and not tailored to the organization
- Policy does not include measurable objectives or a framework for setting them
- Policy is not signed or approved by top management
- Policy has no review date
5.3 - Organizational Roles, Responsibilities, and Authorities (Mandatory) Documented assignment of information security responsibilities. This can be in a RACI matrix, organizational chart, or role descriptions.
Clause 6: Planning
6.1.2 - Information Security Risk Assessment Process (Mandatory) A documented risk assessment methodology that defines:
- Risk acceptance criteria
- Criteria for performing risk assessments
- How risks are identified, analyzed, and evaluated
- How the process ensures consistent, valid, and comparable results
6.1.3 - Risk Treatment Plan (Mandatory) A documented plan showing how each identified risk will be treated (mitigate, accept, transfer, or avoid) along with the controls selected and justification for their selection.
6.1.3d - Statement of Applicability (Mandatory) The Statement of Applicability (SoA) is one of the most important ISO 27001 documents. It must list:
- All controls from Annex A
- Whether each control is applicable or not
- Justification for inclusion or exclusion
- Implementation status
6.2 - Information Security Objectives (Mandatory) Documented objectives that are measurable, consistent with the security policy, and communicated to relevant personnel.
Clause 7: Support
7.2 - Evidence of Competence (Mandatory Record) Records demonstrating that personnel performing work affecting information security have the necessary competence. This includes training records, certifications, qualifications, and experience documentation.
7.5 - Documented Information Control (Mandatory) You need a documented approach to creating, updating, and controlling documented information. This is essentially your document management procedure.
Clause 8: Operation
8.1 - Operational Planning and Control (Mandatory) Documentation of operational processes and their planned outcomes. This includes any processes that have been outsourced.
8.2 - Results of Information Security Risk Assessment (Mandatory Record) Retained records of each risk assessment performed, including the methodology used, risks identified, risk analysis results, and risk evaluation outcomes.
8.3 - Results of Information Security Risk Treatment (Mandatory Record) Retained records showing how risk treatment decisions were made and implemented.
Clause 9: Performance Evaluation
9.1 - Monitoring, Measurement, Analysis, and Evaluation Results (Mandatory Record) Records of what was monitored and measured, when, by whom, and the results.
9.2 - Internal Audit Program and Results (Mandatory Record)
- A documented internal audit program (schedule, scope, frequency)
- Audit reports with findings and conclusions
- Evidence that audit results were reported to relevant management
9.3 - Management Review Results (Mandatory Record) Minutes or records of management review meetings showing that all required inputs were considered and decisions/actions were documented.
Clause 10: Improvement
10.1 - Nonconformity and Corrective Action Records (Mandatory Record) Records of:
- The nature of nonconformities
- Actions taken in response
- Results of corrective actions
Mandatory Documents Required by Annex A Controls
While Annex A controls are selected based on your risk assessment and SoA, several controls explicitly require documented policies or procedures when they are applicable:
A.5.1 - Policies for Information Security A set of information security policies, approved by management, published, and communicated.
A.5.10 - Acceptable Use of Information and Associated Assets Rules for the acceptable use of information and assets must be identified, documented, and implemented.
A.5.13 - Labelling of Information Procedures for information labelling in accordance with the classification scheme.
A.5.23 - Information Security for Use of Cloud Services Processes for acquisition, use, management, and exit from cloud services.
A.5.29 - Information Security During Disruption Plans for maintaining information security during adverse situations.
A.5.37 - Documented Operating Procedures Operating procedures for information processing facilities must be documented and made available.
A.6.1 - Screening Background verification procedures for all candidates.
A.6.2 - Terms and Conditions of Employment Employment contracts stating information security responsibilities.
A.6.3 - Information Security Awareness, Education, and Training A documented awareness and training program.
A.8.1 - User Endpoint Devices A topic-specific policy for managing endpoint devices.
A.8.9 - Configuration Management Documented configurations for hardware, software, services, and networks.
A.8.13 - Information Backup A topic-specific backup policy (see our backup policy template guide).
A.8.15 - Logging A topic-specific policy on logging.
A.8.25 - Secure Development Lifecycle Rules for the secure development of software and systems.
The Complete ISO 27001 Mandatory Documents List
Here is a consolidated checklist of all ISO 27001 required documents:
| # | Document | Clause/Control | Type |
|---|---|---|---|
| 1 | ISMS Scope | 4.3 | Document |
| 2 | Information Security Policy | 5.2 | Document |
| 3 | Roles and Responsibilities | 5.3 | Document |
| 4 | Risk Assessment Methodology | 6.1.2 | Document |
| 5 | Risk Treatment Plan | 6.1.3 | Document |
| 6 | Statement of Applicability | 6.1.3d | Document |
| 7 | Information Security Objectives | 6.2 | Document |
| 8 | Competence Evidence | 7.2 | Record |
| 9 | Document Control Procedure | 7.5 | Document |
| 10 | Risk Assessment Results | 8.2 | Record |
| 11 | Risk Treatment Results | 8.3 | Record |
| 12 | Monitoring and Measurement Results | 9.1 | Record |
| 13 | Internal Audit Program | 9.2 | Document |
| 14 | Internal Audit Reports | 9.2 | Record |
| 15 | Management Review Minutes | 9.3 | Record |
| 16 | Nonconformity and Corrective Action Records | 10.1 | Record |
| 17 | Acceptable Use Policy | A.5.10 | Document |
| 18 | Access Control Policy | A.5.15 | Document |
| 19 | Operating Procedures | A.5.37 | Document |
| 20 | Backup Policy | A.8.13 | Document |
| 21 | Logging Policy | A.8.15 | Document |
| 22 | Secure Development Policy | A.8.25 | Document |
This list covers the minimum. Most organizations also maintain additional policies for topics like incident management, supplier security, change management, and business continuity.
Common Mistakes That Cause Audit Findings
-
Missing the Statement of Applicability - The SoA is the single most important document. Without it, you cannot pass a Stage 1 audit. Use our free SoA generator to create one quickly.
-
No version control - Every document must have a version number, approval date, review date, and document owner. Auditors check this immediately.
-
Policies without evidence of implementation - A well-written policy that nobody follows is worse than no policy at all. Auditors verify implementation through interviews and record reviews.
-
Incomplete risk assessment records - Your risk assessment must cover all assets in scope and use the methodology defined in your documented process. Partial assessments are flagged.
-
No management review minutes - Management review is mandatory at planned intervals. Missing minutes means missing evidence of leadership engagement.
-
Training records without competence proof - Attending a training session is not the same as demonstrating competence. Records should show how competence was evaluated.
-
Outdated documents - If your policy says "reviewed annually" but the last review was two years ago, that is a nonconformity.
-
Inconsistent documents - If your risk assessment methodology document describes a 5x5 matrix but your risk register uses a 3x3 matrix, auditors will flag the inconsistency.
How Many Documents Do You Actually Need?
The mandatory minimum is approximately 20-25 documents and records. However, a well-structured ISMS for a medium-sized organization typically includes 35-50 documents when you add recommended policies and procedures for all applicable Annex A controls.
Our ISO 27001 Document Pack includes 40+ consultant-reviewed documents covering the mandatory and recommended documents listed above. All templates are in editable Word format, written for ISO 27001:2022, and need to be adapted to your organization before auditor review.
Get All Your ISO 27001 Documents in One Pack
Instead of writing each document from scratch, start with consultant-reviewed templates that you can customize to your organization. Our Document Pack covers every ISO 27001 mandatory document plus recommended policies for all applicable Annex A controls.
Browse all documents | Get the complete Document Pack - $99
Found this article helpful?
Share it with your colleagues.
