ISO/IEC 27001:2022 Implementation: A Practical Roadmap
What it actually takes to stand up an ISO/IEC 27001:2022 ISMS — from scoping and risk assessment to the Statement of Applicability and the certification audit.
ISO/IEC 27001:2022 is an international standard for an Information Security Management System (ISMS) — a documented, risk-based way of governing how an organisation protects information. Implementing it means defining a scope, assessing risk, selecting controls from Annex A, operating the system, and then passing a two-stage external audit by an accredited certification body. In practice a first implementation typically runs three to nine months depending on size and starting maturity.
1. Define scope and context
The first decision is the boundary: which parts of the business, which systems, and which locations the ISMS covers. A scope that is too broad slows everything down; one that is too narrow undermines the certificate's value. Document the internal and external issues that matter (Clause 4), identify interested parties and their requirements, and record the decision clearly — the scope statement is one of the first things an auditor reads.
2. Secure leadership and assign roles
Clause 5 requires demonstrable top-management commitment: an approved information security policy, assigned responsibilities, and resources. This is not a formality — certification auditors look for evidence that leadership actively directs the ISMS, not that a security team runs it in isolation.
3. Run a risk assessment and treatment plan
The core of ISO 27001 is risk. Establish a repeatable method for identifying risks to the confidentiality, integrity and availability of information, then assess each by likelihood and impact. For every risk you decide to treat, select controls and record the decision. The output is a risk treatment plan plus a Statement of Applicability (SoA) — the document that lists every Annex A control and justifies its inclusion or exclusion.
The 2022 revision reorganised Annex A into 93 controls across four themes — Organizational, People, Physical and Technological — and introduced controls such as threat intelligence, information security for cloud services, and secure coding.
4. Operate, measure and improve
Controls only count if they run. Operate the ISMS, collect evidence, and measure effectiveness against objectives. Clauses 9 and 10 require internal audits, a management review, and a process for handling nonconformities and continual improvement. Most failed certification attempts trace back to a system that was documented but never actually operated long enough to produce evidence.
5. Certification audit
- 01Stage 1: the certification body reviews your documentation and readiness.
- 02Stage 2: an on-site/remote audit tests whether the ISMS operates as described.
- 03Surveillance: annual checks maintain the certificate over a typical three-year cycle.
Certification is issued by an accredited body, not by a consultant. Advisory support helps you build an aligned ISMS and prepare evidence, but the certificate itself always comes from an independent auditor.
Common pitfalls
- Treating the SoA as paperwork rather than a live record of real decisions.
- Scoping around the certificate instead of around genuine risk.
- Buying tools before defining the risks they are meant to treat.
- Leaving no evidence window — auditors need records of the system running over time.