Implementation Guide 8 min read· 16 October 2026

How Long Does ISO/IEC 27001 Certification Take?

Plan ISO/IEC 27001 scope, controls, evidence and audit milestones without promising a fixed date. Start with the free documentation kit.

Aegora GRC Advisory Team

ISO/IEC 27001 implementation guidance

For most organisations, the question of ISO/IEC 27001 certification is not "if", but "how fast". Whether driven by a critical enterprise RFP, a board-level mandate to manage cyber risk, or the need to align with regulations like NIS2 or DORA, the timeline for certification is a primary project constraint.

In this article, we break down the 6 phases of an ISO/IEC 27001 project, provide realistic timelines based on company size, and identify the factors that either stall or accelerate your path to a documented ISMS.

Illustrative Planning Scenarios by Organisation Size

The ranges below are planning examples, not measured averages, minimum periods required by the standard, or a delivery promise. Agree your own schedule with process owners and the certification body after assessing scope, maturity, evidence and auditor availability.

A common mistake is to underestimate the time required for cultural and procedural change. While the documentation can be drafted quickly, the "M" in ISMS stands for Management System—and systems require time to operate before they can be audited.

Small Organisations (<50 staff) **Timeline: 3–6 months** Smaller teams can move rapidly. The context of the organisation is usually narrow, the asset inventory is manageable, and decision-making is centralised. An accountable lead can coordinate the work, but the evidence and control gaps determine the schedule; headcount alone does not establish readiness.

Mid-Sized Organisations (50–250 staff) **Timeline: 6–9 months** Complexity increases with the number of departments and physical locations. You will likely need to conduct more interviews for your risk assessment and spend more time training staff on new security behaviours. At this scale, information security often shifts from being an IT task to a cross-functional governance requirement.

Enterprise Organisations (250–1,000+ staff) **Timeline: 9–18 months** Large organisations face challenges with legacy systems, complex supply chains, and entrenched cultural silos. The "Stage 1" audit often reveals gaps in how policies are applied consistently across different business units. Enterprises often choose to certify specific business lines first (phased scope) rather than the entire organisation at once to manage this complexity.

The 6 Phases of ISO/IEC 27001 Implementation

Achieving certification is a structured journey. Skipping phases or rushing the sequence often leads to a "major nonconformity" during the external audit.

Phase 1: Scope Definition Before you write a single policy, you must define the boundaries of your Information Security Management System. This is where you decide exactly what is being certified: is it the whole company, a specific office, or a single SaaS product?

The output of this phase is the formal "Scope Statement". Under Clause 4.3 — Scope of the ISMS, you must consider your internal and external context, the requirements of interested parties (like customers and regulators), and the interfaces and dependencies between your organisation and third parties. A well-defined scope prevents "scope creep" and ensures your risk assessment remains focused.

Phase 2: Gap Analysis The gap analysis is a "pre-flight check". You compare your existing security controls and documentation against the requirements of the ISO/IEC 27001:2022 standard.

Practitioner tip: Do not be discouraged if your initial gap analysis looks bleak. Some existing processes may already address relevant risks, but they must be assessed rather than counted as effective without evidence. This phase identifies exactly which "auditor-ready documents" are missing and where technical controls need strengthening.

Phase 3: Risk Assessment Risk assessment is the heart of ISO/IEC 27001. The standard is risk-based, meaning you only implement the controls you actually need.

Following Clause 6.1.2 — Risk Assessment, you must identify the risks to the confidentiality, integrity, and availability of your information assets. You then decide how to treat those risks: avoid, transfer, accept, or mitigate. This leads to the creation of two critical documents: the Risk Treatment Plan (RTP) and the Statement of Applicability (SoA). The SoA tells the auditor which of the 93 Annex A controls apply to your business and why.

Phase 4: Implementation (Documentation & Controls) This is the most labour-intensive phase. You must draft and approve the policies, procedures, and registers that form your documented ISMS.

Central to this is A.5.1 — Information Security Policies. You need a top-level Information Security Policy signed by senior management, supported by topic-specific policies covering access control, encryption, and physical security.

Beyond documentation, you must implement technical and organisational controls. For example, A.5.24 — Information Security Incident Management Planning requires you to move beyond "fixing things when they break" to having a formal, tested plan for responding to security events. During this phase, you are not just writing documents; you are changing how the organisation operates.

Phase 5: Internal Audit ISO/IEC 27001 requires internal audits at planned intervals. Select auditors and conduct audits to ensure objectivity and impartiality; avoid assigning someone to review their own work without adequate independence.

The internal audit tests whether your ISMS is effective and whether staff are actually following the policies you have implemented. If the auditor finds that your "Access Control Policy" says passwords must be 16 characters, but your systems only require 8, that is a nonconformity you must fix before the Stage 2 audit.

Phase 6: Stage 1 & Stage 2 Certification Audit Finally, an accredited Certification Body (CB) conducts the formal assessment.

Stage 1 (Documentation Audit): The auditor reviews your ISMS documentation (Scope, SoA, Risk Assessment, Policies) to ensure they meet the standard's requirements. They are looking for a "documented ISMS".

Stage 2 (Effectiveness Audit): At a date agreed with the certification body after Stage 1 issues have been addressed, the auditor returns to see the system in action. They will interview staff, inspect systems, and look for evidence (logs, meeting minutes, training records) that your controls are working.

What Delays ISO/IEC 27001 Projects?

1. Lack of Management Buy-in: If senior leadership treats the ISMS as "something IT does", the project will fail. Implementation requires resources, budget, and occasionally, changes to how people work that only management can authorise.

2. Resource Bottlenecks: Expecting a CISO or IT Manager to implement an ISMS in their spare time can leave critical work without an accountable schedule. You need dedicated time or external support to maintain momentum.

3. Complex Asset Inventories: Many organisations do not know where their data is. Discovering hidden shadow IT and undocumented data flows during the risk assessment phase is a major cause of delay.

4. Scope Creep: Trying to boil the ocean by including every possible office and subsidiary in the first year often leads to project paralysis.

What Accelerates the Project?

1. Auditor-Ready Documentation Kits: Starting with a blank page can consume time better spent adapting and operating the controls. Using a high-quality kit provides the structure you need immediately.

2. Pre-existing Frameworks: If you have already achieved SOC 2 or Cyber Essentials Plus, you have already implemented many of the technical controls. The project then becomes one of "mapping" and "governance" rather than building from scratch.

3. Dedicated Project Management: ISO/IEC 27001 is a project, not just a standard. Treating it with the same rigour as a product launch—with milestones, owners, and deadlines—is a practical way to coordinate the work.

4. Expert Guidance: An experienced consultant knows what an auditor wants to see and what they don't. This prevents over-engineering controls that add cost without adding security or compliance value.

Plan around evidence, not just documents

Use the internal audit guide to identify what must be sampled, and the management review guide to prepare the decisions leadership needs to make. Work backwards from these activities: each depends on results from processes that have actually operated. A template cannot substitute for a completed access review, restored backup or evaluated training outcome. Keep a milestone register with dependencies, owners and exit criteria, then revise it when a test reveals a real gap.

If scheduling or scope is uncertain, book a free one-hour consultation through our consulting team. The purpose is to identify the constraints in your environment, not to promise a certificate on a predetermined date.

Conclusion

ISO/IEC 27001 certification is a marathon, not a sprint, but it doesn't have to be an endurance test. By following a structured 6-phase approach and using the right accelerators, teams can set an evidence-based schedule and adjust it as control gaps and assurance requirements become clearer.

The result is more than just a certificate; it is a resilient, documented ISMS that protects your organisation’s capital, reputation, and commercial potential.

Start your documented ISMS with the free kit The Blueprint kit includes 109 documents, 19 core documents flagged for implementation, and 93 Annex A control mappings. It is free for every signed-in account—no paywalls, no trial limits, and no credit card required.

Get Started for Free

Start with the free documentation kit

Get 109 editable documents with a free account. Adapt them, implement selected controls and retain real evidence of operation.

More articles