ISO/IEC 27001 requires documented information and evidence of an operating information security management system. It does not prescribe exactly 19 separate files. Organisations can combine information, use different formats and add documentation according to their processes, risks and obligations. The useful question is whether the required information exists, is controlled and reflects what actually happens.
Blueprint flags 19 core documents in its 109-document kit to help organise implementation. That is a product grouping, not a claim that the standard mandates every file title below. Some entries hold explicitly required information; others provide a supporting procedure or plan for implementing a requirement. Blank templates are not operational records, and downloading the kit does not establish conformity or certification.
How to use the list
Start with scope and boundaries, then develop the risk assessment method and risk treatment decisions. Use the list below to assign owners and decide where the approved information will live. Keep references between files consistent if your organisation combines them or stores the evidence in an existing business tool.
The 19 core documents in the kit ### 1. Information Security Policy
Clause 5.2 requires a documented policy. State management’s direction, applicable commitments and the framework for objectives. Obtain top-management approval and communicate the current version. An auditor can compare the policy with actual responsibilities and decisions; a signature alone does not show that the organisation follows it.
2. ISMS Scope Document
Clause 4.3 requires the scope to be available as documented information. Describe the services, locations, systems and interfaces covered, considering context and interested parties. Check outsourced dependencies as well as owned infrastructure. Avoid exclusions that make the written boundary inconsistent with the activities your organisation actually performs.
3. Information Security Objectives
Clause 6.2 requires documented objectives. Define meaningful targets, responsibilities and how progress is evaluated. Link each objective to the policy and relevant risks rather than using an arbitrary checklist. Keep results and decisions when an objective changes; a statement such as “improve security” is not sufficient to explain performance.
4. Management Review Procedure
The kit provides a procedure to organise the review required by Clause 9.3. A separate procedure file is a supporting implementation choice; retained review results are the explicit evidence requirement. Establish the inputs, participants and decision process, then use actual performance information rather than a meeting assembled only for an audit.
5. Information Security Roles & Responsibilities
Clause 5.3 requires responsibilities and authorities to be assigned and communicated. This file is the kit’s way of making that assignment explicit, not a prescribed standalone ISO form. Identify owners and deputies for risk, controls, reporting and improvement. Check that people have the authority and capacity needed to discharge their responsibilities.
6. Context of the Organization
Clauses 4.1 and 4.2 require understanding relevant issues and interested-party requirements. A standalone context document is a practical supporting choice. Record the security implications of business changes, customers, suppliers and obligations. Explain which requirements the ISMS addresses and keep the analysis current enough to inform scope and risk decisions.
7. ISMS Communication Plan
Clause 7.4 requires the organisation to determine relevant internal and external communications. This plan is a useful way to record topics, audiences, timing, responsibilities and channels, rather than a universally prescribed separate document. Include urgent communications and deputies, and test whether the plan remains usable when the normal channel is unavailable.
8. Control of Documented Information Procedure
Clause 7.5 sets requirements for creating, updating and controlling documented information. A separate procedure helps teams apply those rules consistently but is not a fixed-format requirement. Define approval, availability, protection, change history, retention and disposal. Sample the repository and operational records to show the rules are actually applied.
9. Risk Assessment Methodology
Clause 6.1.2 requires documented information about the risk assessment process. Define criteria, risk ownership and a method that produces consistent, comparable results. Describe how likelihood and consequences are assessed and how acceptance decisions are made. Test the methodology on real scenarios before relying on scores produced by a register.
10. Risk Register & Treatment Plan
This is one combined kit document, not separate files for assessment results and treatment planning. It supports Clauses 6.1.2, 6.1.3, 8.2 and 8.3. Record risks, chosen responses, control links, action owners, dates and residual-risk acceptance. Retain evidence of reassessment and treatment results as the organisation operates and changes.
11. Statement of Applicability (SoA)
Clause 6.1.3 requires a Statement of Applicability. Identify necessary controls, justify their inclusion, state implementation status and justify exclusions from Annex A. Consider all 93 Annex A controls without assuming every one applies automatically. Keep the SoA consistent with risk treatment and applicable legal, contractual and business needs.
12. Internal Audit Procedure
Clause 9.2 requires internal audits and retained evidence of programme implementation and results. The procedure supports consistent planning, impartial review and reporting; the separate procedure file is an implementation choice. Define criteria, scope, methods and handling of findings, then ensure the completed audits examine operation rather than merely document existence.
13. Competence Evaluation Procedure
Clause 7.2 requires the necessary competence to be determined and appropriate evidence retained. This supporting procedure explains how to assess capability, address gaps and evaluate actions. Attendance alone may not demonstrate competence. Match the assessment method to the work performed, including specialist tasks entrusted to contractors or external providers.
14. Non-Conformity & Corrective Action Register
Clause 10.2 requires retained information about nonconformities, subsequent actions and the results of corrective action. Record the condition, correction, cause analysis, owner and effectiveness check. Do not close a finding simply because a document was updated. Keep corrective action distinct from the broader continual-improvement requirement in Clause 10.1.
15. Training & Awareness Register
This register supports competence evidence under Clause 7.2, awareness under Clause 7.3 and selected awareness controls. Record the relevant people, activity, date and outcome, including missed participation and follow-up. Make clear whether a session develops a practical skill or simply communicates information; the evidence needed for each may differ.
16. Audit Programme Register
Clause 9.2 requires retained evidence of audit programme implementation and results. Use this register to plan scope, timing and responsible reviewers and to link completed reports. Consider process importance, organisational changes and previous results. A planned date without an executed audit and recorded conclusions does not demonstrate that the programme operated.
17. Management Review Minutes
Clause 9.3 requires retained evidence of management review results. Capture required inputs, actual decisions, owners and follow-up rather than attendance alone. Link actions to resources, risks and improvement opportunities. Keep enough detail to explain what leadership concluded and revisit earlier actions so decisions do not disappear between review meetings.
18. Competence Records Template
Clause 7.2 requires appropriate documented information as evidence of competence. This template records role requirements, evaluation method, assessor, outcome and improvement needs. Use evidence suited to the role, such as demonstrated work, qualifications or supervised assessment. Restrict access to personal records and apply a justified retention arrangement.
19. Continual Improvement Procedure
Clause 10.1 addresses continual improvement; Clause 10.2 addresses nonconformity and corrective action. This procedure is a supporting way to manage improvement, not a universally prescribed separate file. Draw opportunities from audits, incidents, measures and staff suggestions, prioritise them and check whether implemented changes improve suitability, adequacy or effectiveness.
What this list does not replace
The core grouping is not an exhaustive list of every record your organisation may need. For example, monitoring and measurement requires retained evidence of results. Operational records, treatment evidence and control-specific documentation must also reflect the processes and safeguards you choose. Annex A controls are selected through risk treatment and relevant obligations; a policy for every control is not automatically mandatory.
Before a review, trace one risk through its assessment, treatment decision, SoA entry, responsible owner and evidence of operation. Trace an internal finding through correction, cause analysis and effectiveness review. These connected examples show more than a folder containing a prescribed number of documents. Use the controls library to examine the particular requirements and the questionnaire accelerator to locate supporting documents for buyer questions.
Start with the free documentation kit
The full 109-document kit is free for signed-in accounts, without a trial limit or watermark. Adapt its content, approve the relevant documents, implement selected controls and retain real operating evidence. Get the free kit, or book a free one-hour consultation through our consulting team if you need help organising the work.