Ir al contenido
Implementación
13 min de lectura

ISO 27001 Implementation Phases: A Practical Roadmap

support@ismscalculator.com|

Sponsor and project owner define ISMS scope

ISO 27001 implementation runs in six practical phases: scope and gap assessment, risk assessment, risk treatment and documentation, control implementation and operation, internal audit and management review, and the two-stage certification audit. Surveillance audits follow after certification. Every phase has an owner, a set of outputs and a cost in staff time, so the plan is only as good as the estimate behind it. We built our calculator so that you can put numbers on each phase before you commit budget.

This guide walks through each phase: what the work is, what you should have in hand when it ends, and where teams lose time. It is written for compliance officers, IT managers and startup founders who need a plan they can defend to an executive or an auditor.

Ismscalculator
ismscalculator.com
Plan ISO 27001 With Clearer Estimates
Use company size, industry, and security maturity to estimate implementation effort and compare your plans with the model reference.
Visit

TL;DR

  • ISO 27001 follows the Plan-Do-Check-Act (PDCA) cycle. Clauses 4 to 10 of the standard map onto it, and the practical work splits into six phases.
  • The gap assessment and the risk assessment come first. Starting control work before the risk assessment is the classic way to waste months.
  • Preparation commonly takes anywhere from three months to a year, depending on size, scope and how mature your controls already are.
  • Certification is a two-stage audit, then surveillance audits every year and a full recertification every third year.
  • You can size each phase by company size, industry and maturity with our free 2-minute readiness check and cost calculator.

Table of Contents

How the phases map to the standard

The standard itself does not number “phases”. It gives you clauses 4 to 10: context, leadership, planning, support, operation, performance evaluation and improvement. ISACA explains that these clauses align with the PDCA cycle. Planning and establishment is Plan, implementation and operation is Do, monitoring and review is Check, and maintenance and improvement is Act.

PDCA is a loop, not a one-way road. NQA’s implementation guide describes it as a closed system in which what you learn while doing and checking feeds the next round of planning. That is why certification is not the finish line: the same cycle keeps running afterward.

Here is how the clauses translate into a working project plan.

Phase PDCA What you produce Main clauses
1. Scope and gap assessment Plan ISMS scope, sponsor, gap list, project plan 4, 5
2. Risk assessment Plan Risk criteria, risk register with owners 6
3. Risk treatment and documentation Plan Risk treatment plan, Statement of Applicability, policies 6, 7
4. Control implementation and operation Do Working controls, training records, evidence 7, 8
5. Internal audit and management review Check, Act Audit report, review minutes, corrective actions 9, 10
6. Certification audit Check Stage 1 and Stage 2 results, certificate 9, 10

The split of Plan into three phases is deliberate. In most projects, Plan is the longest stretch, and lumping it into one block hides the work.

Phase 1: Scope and gap assessment

The first phase answers three questions: who sponsors this, what is inside the ISMS (information security management system), and how far are you from the standard today.

Sponsorship and scope. The standard expects top management to commit, and auditors will look for that commitment. In practice you need a named executive sponsor, a project owner and a written scope: which business units, locations, systems and data are in. A narrow, honest scope finishes faster than a broad one, but it must match what you tell customers the certificate covers.

Gap assessment. ISACA describes two steps. First, assess current practices by learning the requirements and involving the people who run your systems. Second, identify the gaps, categorize them by effort, impact and cost, prioritize by severity and risk, and map the dependencies between them. The gaps that come up most often are in policy, access control, risk assessment, documentation, incident response and training.

The output you want is a ranked list, not a long report. Each gap should have an owner and a rough effort figure, because that list becomes your project plan. For a full walkthrough, see our step-by-step gap analysis guide.

Where it goes wrong: treating the gap assessment as a one-person desk exercise. If the people who run access control, HR onboarding and vendor management are not in the room, the gap list will be too optimistic and the surprises arrive during the audit.

Phase 1: Scope and gap assessment

Phase 2: Risk assessment

Risk assessment is the engine of ISO 27001. Every control you later implement, and every control you decide to leave out, must trace back to a risk.

The work, as the IMA’s account of the certification journey lays it out for the Plan stage, includes adopting a framework, getting top-management commitment, defining risk assessment and acceptance criteria, performing the assessment and mapping controls to the risks you find. The criteria matter more than most teams expect. You decide in advance how you score likelihood and impact, and what level of risk the business will accept. Change those rules halfway and your earlier results no longer compare.

Outputs to hold at the end of this phase:

  • A documented risk methodology with scoring scales and an acceptance threshold
  • An asset and process inventory in scope
  • A risk register, with a named owner for each risk

Our risk assessment methodology guide covers scoring approaches in detail.

Where it goes wrong: jumping to tooling. Buying endpoint detection or a SIEM before the risk assessment tells you what you need is how budgets are spent on controls the auditor never asks about, while the real risks stay untreated.

Phase 3: Risk treatment and documentation

Here you decide what to do about each risk: reduce it with controls, accept it, avoid it or transfer it. Two documents come out of this phase, and auditors read both closely.

The risk treatment plan lists, for each risk, the chosen treatment, the controls, the owner and the date. Our risk treatment plan guide shows the structure.

The Statement of Applicability (SoA) lists every Annex A control, says whether it applies, explains why, and states whether it is implemented. The 2022 edition of Annex A has 93 controls grouped into organizational, people, physical and technological themes, down from 114 in the 2013 version, according to ISACA. Our Statement of Applicability guide explains how to justify inclusions and exclusions.

This is also when the core policies get written: information security policy, access control, acceptable use, incident response, supplier security and so on. Documentation under clause 7 usually runs in parallel with the controls work that follows, so start early and keep each document short enough that staff actually read it.

Where it goes wrong: a copy-pasted SoA. Excluding a control with a one-word reason, or marking everything “implemented” without evidence, is easy for an auditor to spot.

Phase 4: Control implementation and operation

This is the Do phase and the longest one in most projects. You put the planned controls into service and run them long enough to produce evidence.

Typical work covers technical controls (multi-factor authentication, logging, backups, vulnerability management), organizational controls (supplier reviews, change management, incident procedures), people controls (security awareness training, onboarding and offboarding steps) and physical controls (office access, equipment handling).

Two points to plan for:

  1. Evidence is the product. A control that works but leaves no record does not exist for an auditor. Decide up front what record each control produces: a ticket, a log export, a signed review, a training completion list.
  2. Operation needs time. The standard expects the ISMS to run, not just exist on paper. Auditors want to see the controls working over a period, which is why this phase and the internal audit cannot be compressed to nothing.

Teams that already hold another framework often move faster. For startups, our guide for SaaS and tech companies covers how the controls map to cloud-first environments.

Phase 5: Internal audit and management review

Before an outside auditor arrives, you audit yourself. This is the Check phase.

The internal audit examines whether the ISMS meets the standard and your own rules. The auditor should be independent of the work being audited, so a small company often assigns someone from another team rather than the person who built the controls. Findings go into a corrective action log. Our internal audit playbook shows how to run it.

Then comes the management review: top management examines audit results, risk status, incidents, objectives and resourcing, and records decisions. Certification bodies require both. For example, one registrar’s published rules state that an internal audit and a management review must be completed before Stage 2.

Correct what the audit finds, and record the fix. This is the Act step, and it is the one most often skipped when a deadline looms.

Phase 6: Certification audit

Certification is carried out by an accredited certification body, not by you or your consultant. It happens in two stages.

  • Stage 1 reviews your documentation and your readiness for the main audit.
  • Stage 2 assesses whether the ISMS is actually implemented and effective.

According to the same registrar’s regulations, certification follows successful Stage 1 and Stage 2 audits, with major nonconformities corrected and minor ones addressed. Surveillance audits take place every six or twelve months, the first no later than 12 months after the certification decision, and recertification comes every three years.

Audit length scales with headcount and scope. Schellman explains that ISO/IEC 27006 ties initial audit days to in-scope staff, that surveillance reviews take about a third of the initial audit time and recertification about two thirds. A 12-day initial audit therefore implies roughly 4 surveillance days and 8 recertification days. Many teams run a pre-audit with their certification body first; TÜV SÜD notes that nonconformities are addressed before the certification audit. For a sample of what auditors ask for at each stage, see our audit stages guide.

Phase 6: Certification audit

After certification: the cycle keeps turning

The certificate is valid for three years, but only if the ISMS stays alive. Internal audits, management reviews and risk reassessments continue, and corrective actions update your risks and controls. That is PDCA in its everyday form.

If you are still on the 2013 edition, note that the transition to the 2022 version ended on October 31, 2025, so valid certificates now have to align with the 2022 standard. The same source notes that Amendment 1:2024 adds climate-related context checks under clauses 4.1 and 4.2.

For US organizations, there is a legal angle worth knowing. California’s CCPA cybersecurity audit regulations became effective on January 1, 2026, and one law firm’s analysis finds that mature ISO 27001 programs align strongly with them, though they should be supplemented in areas such as personal-information inventories and phishing-resistant MFA. Check with your counsel whether the thresholds apply to you.

How long each phase takes

Timelines vary more than any single blog suggests. Preparation commonly takes three months to a year, and the main drivers are:

  • Headcount and scope. More people and systems in scope mean more controls to evidence and more audit days.
  • Existing maturity. If you already run a recognized framework, much of the policy and control work exists.
  • Sequence discipline. Doing risk assessment before control implementation avoids rework.
  • Remediation speed. Nonconformities found late can stretch the timeline from weeks to months.
  • Industry. A finance firm usually has more regulatory obligations to fold into the context and risk work than a ten-person startup.

A small, early-stage team and a regulated mid-size firm should not use the same plan. A 20-person startup might compress phases 1 to 3 into a couple of months. A bank subsidiary with several sites will spend longer in scope and risk work alone. Our implementation timeline article goes deeper on realistic ranges, and our 80-step certification checklist lets you track every task.

Perspective

Most teams we talk to ask the same question first: how long and how much? Then they discover that nobody can answer it without knowing company size, industry and current maturity. A generic range from a blog is a starting point, not a budget.

That is why we built our calculator around those three inputs and made the assumptions editable. When you can see why a phase costs what it does, you can challenge the number, defend it to your CFO and adjust it when the scope changes. Our methodology is versioned and traceable, and the first calculation needs no signup.

The phases in this article are the same ones you will see in the plan. What we add is the estimate for each one, a maturity assessment across the four Annex A control themes, and Gantt-style planning so phase 1 to 6 become dates and owners instead of a diagram. Save several scenarios, compare them, export a PDF, and share the link with your sponsor.

The strongest projects we see start with an honest baseline. Get that first, and every later phase gets easier to plan.

Martin

Plan your phases with real numbers

If you are early, start with our free 2-minute readiness check to see where you stand. Then open the ISO 27001 cost calculator, which gives real-time estimates tailored to company size, industry and security maturity, with model reference comparisons to validate your plan. You can save and compare multiple estimates, plan implementation phases on customizable Gantt charts, and request introductions to independent ISO 27001 consultants. For a deeper baseline, the ISO 27001 readiness assessment covers the four Annex A control themes.

Ismscalculator

FAQ

How many phases are there in ISO 27001 implementation?

The standard does not fix a number, but clauses 4 to 10 follow Plan-Do-Check-Act. Most project plans split the work into five to nine phases. The six used here are scope and gap assessment, risk assessment, risk treatment and documentation, control implementation, internal audit and management review, and certification audit.

Which phase takes the longest?

Usually control implementation and operation, because it involves technical changes, training and the time needed to generate evidence. Risk assessment and documentation can also run long when scope is broad or the methodology is not agreed early.

Do I need a gap assessment before starting?

It is not a formal requirement of the standard, but it is the sensible first step. It shows what already meets the requirements, ranks what does not by effort and risk, and gives you a plan with owners. Our free 2-minute check gives you a first read in minutes.

What happens after Stage 2?

If there are no unresolved major nonconformities, the certification body makes the certification decision. After that, surveillance audits occur every six or twelve months and recertification every three years, so internal audits and management reviews continue.

Sources

¿Listo para estimar los costos de su ISO 27001?

Use nuestro calculador gratuito para obtener una estimación personalizada de costos, esfuerzo y plazos basada en su perfil empresarial.

Calcule su estimación — gratis
Volver a todos los artículos