Guide
ISO 27001 Checklist: What Is Missing Before Your Audit?
Use this ISO 27001 checklist to identify gaps before your audit and plan the next steps towards certification. Includes a free PDF download.


Certification is planned. But is your ISMS ready for the audit? Policies are written, tasks assigned and evidence stored. You still need to know whether it all fits together, and where work remains.
Use this ISO 27001 checklist to assess your position against evidence. You should come away knowing what you can demonstrate, which gaps put preparation at risk and what to tackle first. This guide walks you through the review; the free PDF helps you record the results with your team.
How to use the ISO 27001 checklist
- Record scope and review date. Assess the specific ISMS rather than making assumptions about the whole company. Record which area your assessment covers.
- Open the evidence. Check its content, approval, currency and actual implementation. A file with the right name is not enough.
- Assign a status. Open, partial or evidenced. “Evidenced” means you checked suitable evidence; it is not a certification decision.
- Turn the gap into an action. Record an owner, deadline and expected result. This tells your team which result is needed next.
- Verify the result. Close the item only after checking evidence. Repeat the assessment after relevant changes and before the audit.
Example: A backup policy has been approved, but no restoration test has been performed. The item remains partial. The next action is: “Test restoration of a selected system, record and evaluate the result.” This needs an owner and a deadline. The policy alone does not demonstrate that restoration works.
Which gaps should you close first?
Not every open item has the same urgency. Start with gaps that block other work:
- The scope is unclear: Agree which systems, locations and services belong to the ISMS before assessing risks and collecting evidence against an undefined boundary.
- Control selection lacks a rationale: Compare your risks, requirements and SoA. Our Statement of Applicability guide and template helps you record selection, exclusions and implementation status.
- An action exists only on paper: Check implementation. For backups, look for an evaluated restoration test rather than just an approved policy.
- Internal reviews or decisions are missing: Schedule your internal audit and management review with time to address findings. Agree prerequisites for the external audit with your certification body.
The checklist supports an initial assessment of clauses 4–10 of ISO/IEC 27001:2022 and certification preparation, including Amd 1:2024. It replaces neither the standard nor a complete internal audit.
Which evidence should you check first?
| Work area | Typical evidence | Common gap |
|---|---|---|
| Context and scope | Approved scope with dependencies | An outsourced service is missing |
| Leadership | Policy, roles and resource decisions | Ownership was agreed only verbally |
| Risks and SoA | Assessment method, register, treatment plan and SoA | Residual risk has not been accepted |
| Support | Competence, communication and document control | An outdated policy remains in circulation |
| Operation | Actions with current operational evidence | Documented but not implemented |
| Performance evaluation | Measurements, internal audit and management review | Results lead to no decision |
| Improvement | Root cause analysis and verified corrective action | Ticket closed, effectiveness not checked |
| Certification | Agreed scope, audit plan and available evidence | Internal reviews remain incomplete |
These are evidence examples. ISO 27001 does not prescribe a specific file format or document name for every task. What matters is meeting the requirement and being able to demonstrate it.
Define context and scope (Clause 4)
The first question is what your ISMS should actually cover. The scope defines which locations, departments, systems and processes are included, and where you deliberately draw a line. A scope that's too wide drags the project out unnecessarily; one that's too narrow looks unconvincing during the audit if central systems are missing.
Context also means identifying internal and external issues that affect your information security, such as regulatory requirements, your IT landscape, or market demands. Just as important: capturing interested parties, like customers, regulators or employees, and their concrete requirements for the ISMS. Also assess whether climate change is relevant to the ISMS. Amd 1:2024 adds this question to clause 4.1 and notes potential climate-related requirements of interested parties in 4.2. Record your assessment; this does not automatically require an additional climate-protection measure.
Use the stakeholder analysis template to record which parties raise which requirements, who addresses them and when you review them.
Anchor leadership and policy (Clause 5)
ISO 27001 requires visible commitment from top management, not just a signed policy sitting in a drawer. Leadership needs to provide resources, back the objectives, and visibly stand behind the ISMS in day-to-day operations. The information security policy itself describes objectives and framework, and should be short, understandable, and accessible to every employee.
At the same time, roles and responsibilities get assigned: who is the information security officer, who owns which risks, who is accountable for individual controls. Without clear ownership, tasks in the certification process tend to fall through the cracks because nobody feels responsible.
Risk management and the Statement of Applicability (Clause 6)
Risk management is the core of every ISMS. First you define a methodology for identifying and rating risks consistently, for example based on likelihood and impact. Next comes the actual risk analysis: which threats and vulnerabilities affect the confidentiality, integrity and availability of your information?
Every identified risk needs a decision in the risk treatment plan, such as avoidance, mitigation, transfer or deliberate acceptance. The Statement of Applicability (SoA) records necessary controls, reasons for their inclusion and implementation status. Compare them with the 93 Annex A reference controls and justify exclusions. Additional controls may be necessary. Not all 93 automatically require implementation; the requirements of clauses 4–10 cannot be excluded. Selection must reflect risks and other requirements. Risk owners approve the treatment plan and accept residual risks. Our SoA guide and template helps structure this.
Ensure resources and awareness (Clause 7)
An ISMS lives through the people who run it. Clause 7 requires sufficient staff, time and budget, and requires responsible people to have the necessary competence or to build it deliberately. It also calls for an awareness program that teaches every employee what role they play in information security day to day, from password hygiene to spotting phishing attempts.
Define what is communicated, when, to whom and by whom. Documented information also needs to be controlled: policies and records need versioning, approval workflows and protection against unauthorized changes. That sounds bureaucratic, but during the audit it's often exactly where poorly maintained documentation gets noticed.
Implement operation and Annex A controls (Clause 8)
This is where it gets practical: the controls marked as applicable in the SoA need to actually be implemented and effective, not just described. That includes supplier and vendor security, for example through contractual requirements or self-assessments, and change management that keeps security-relevant changes to systems and processes under control.
Reassess risks at planned intervals and after significant changes. Collect evidence continuously, not just before the audit. Screenshots, logs, approvals and tickets that arise naturally during day-to-day operations are often far more convincing in the certification audit than documents assembled after the fact. Our guide to keeping ISMS evidence current and verifiable shows a practical review process. For the external audit, see our guide to ISO 27001 audit preparation.
Performance evaluation and improvement (Clauses 9 and 10)
Before the external certification body reviews your ISMS, it needs to review itself. Clause 9 requires monitoring with defined metrics, an internal audit covering all relevant areas, and a management review where leadership discusses results, risks and objective achievement. Clause 10 closes the loop: nonconformities are documented, root causes analyzed and corrective actions tracked, while continual improvement should be demonstrable through concrete examples, not just a statement of intent in the policy document.
Our ISMS management review guide helps you turn results into decisions about resources, ownership and next steps.
Stage 1 vs. Stage 2 audit: what's the difference?
The external certification audit runs in two stages that check different things:
| Aspect | Stage 1 audit | Stage 2 audit |
|---|---|---|
| Focus | Preparation and readiness for Stage 2 | ISMS implementation and effectiveness |
| What is checked | Documentation, scope, context and progress of internal reviews | Meeting requirements in day-to-day operation |
| Method | Document review and discussions; additional assessment according to the audit plan | Interviews, sampling and operational evidence |
| Outcome | Findings and Stage 2 planning | Audit findings and a recommendation for the certification decision |
Stage 1 is more than a paper review. The certification body assesses readiness for Stage 2. Agree the required evidence, participants and format with it. Stage 2 requires demonstrable implementation through samples. A completed worksheet cannot replace this.
A successful conversation with the audit team does not itself issue a certificate. The certification body makes the certification decision based on the results and any required corrections. Plan subsequent surveillance and recertification within the agreed cycle.
For the full path from decision to finished certificate, including costs and typical pitfalls, see our article ISO 27001 certification explained. For an overview of the standard as a whole, including every control, visit our ISO 27001 hub. To get a first cost estimate for your certification audit, you can also use the audit cost calculator.
Turn your assessment into audit preparation
The checklist should answer three questions: What is evidenced? What is missing? Who will close the gap by when? Assess your position using current evidence. A percentage derived from ticks says little about ISMS effectiveness.
When maintaining separate files becomes difficult, you can manage this workflow in Kopexa ISMS software: evidence is attached to actions, and actions are mapped to controls. This makes the basis for your assessment traceable from requirement to implementation.
Sources and scope
-
ISO/IEC 27001:2022 – ISO overview: the basis for an ISMS and certification.
-
ISO/IEC 27001:2022/Amd 1:2024: climate additions to context and interested-party requirements.
-
ISO/IEC JTC 1/SC 27 Journal, Vol. 3, Issue 4: explanation of requirements and risk-based control selection.
-
TÜV NORD: ISO 27001 certification: the two audit stages and limits of a pre-audit (German source).
The questions and evidence examples are original working aids by Kopexa, not a reproduction of the full standard.
Quick answers
Frequently Asked Questions
Still have a question? Find the answers here.
What belongs in an ISO 27001 checklist?
A preparation checklist should cover clauses 4–10 and certification preparation: scope, policy and roles, risk management with the Statement of Applicability, resources and awareness, implementation of Annex A controls, performance evaluation, improvement, and preparation for the external certification audit. Use the free PDF to assess your position and agree next steps with your team. It does not replace the standard or a complete audit.
How does ISO 27001 certification work step by step?
You start by defining scope and policy, run a risk assessment and create the Statement of Applicability. Then you implement the applicable controls, collect evidence and carry out an internal audit and a management review. Finally, a certification body assesses your ISMS in a Stage 1 and Stage 2 audit.
How long does it take to implement an ISMS under ISO 27001?
Duration depends heavily on company size, scope and where you're starting from. It includes preparation, risk analysis, control implementation, and internal and external audits. Smaller organizations with a clear scope are often faster than companies with multiple locations and a complex IT landscape.
What is the difference between a Stage 1 and a Stage 2 audit?
Stage 1 assesses documentation and readiness for Stage 2, including scope and progress of internal reviews. Stage 2 evaluates implementation and effectiveness through interviews, sampling and operational evidence. Agree the format with your certification body.
Do I need a consultant for ISO 27001?
That depends on your team and experience. Some organizations implement an ISMS in-house, others bring in a consultant or partner for specific parts, such as the risk assessment or audit preparation. Both paths are possible. What matters is the capacity and know-how you have internally.
How long is an ISO 27001 certificate valid?
An issued certificate is typically valid for three years. During that time, annual surveillance audits check a sample of your ISMS. After the three years expire, a full recertification is required.