The Complete Guide to ISO 27001 Certification
ISO/IEC 27001 is the international standard for an information security management system (ISMS). Certification means an accredited certification body has audited your ISMS against the standard’s requirements (Clauses 4–10) and the controls you selected from Annex A. The current version is ISO/IEC 27001:2022, with 93 Annex A controls in four themes. All certificates to the 2013 version expired or were withdrawn after October 31, 2025.
- ISO 27001 certifies a management system, not just a set of controls. Auditors test how you set scope, assess risk, choose controls, measure and improve.
- The 2022 edition has 93 Annex A controls in four themes — organizational, people, physical and technological — including 11 new controls such as threat intelligence, cloud services security and data leakage prevention.
- The 2013 transition deadline passed on October 31, 2025. Any organization still on a 2013 certificate is treated as a new client and needs a full initial audit.
- Certification runs in a three-year cycle: a Stage 1 and Stage 2 initial audit, two annual surveillance audits, then recertification.
- The Statement of Applicability and the risk treatment plan are the two documents auditors read first. Get them right and the rest follows.
What is ISO 27001 and why does it matter?
ISO/IEC 27001 is published jointly by the International Organization for Standardization and the International Electrotechnical Commission. It specifies how to establish, implement, maintain and continually improve an ISMS: the policies, processes, roles and controls an organization uses to manage information security risk.
Certification matters most when you sell internationally or to large enterprises. European, UK and Asia-Pacific buyers often ask for ISO 27001 the way North American buyers ask for SOC 2, and many global enterprises accept either. Public-sector tenders, financial services procurement and healthcare partners frequently list it as a requirement. Because it certifies a management system, it also gives leadership a durable way to run security rather than a once-a-year audit.
What are the ISO 27001 clauses?
Clauses 4 to 10 are mandatory. Every certified organization must meet all of them.
| Clause | Topic | What auditors look for |
|---|---|---|
| 4 | Context of the organization | Internal and external issues, interested parties, a defined ISMS scope |
| 5 | Leadership | Top management commitment, an information security policy, assigned roles |
| 6 | Planning | Risk assessment and risk treatment processes, security objectives, planning of changes |
| 7 | Support | Resources, competence, awareness, communication, documented information |
| 8 | Operation | Carrying out risk assessments and treatment plans, controlling outsourced processes |
| 9 | Performance evaluation | Monitoring and measurement, internal audit, management review |
| 10 | Improvement | Nonconformities, corrective action, continual improvement |
Clause 9 trips up many first-time programs: you need evidence of a completed internal audit and a management review before the Stage 2 audit. See Clause 9 explained.
What are the 93 Annex A controls?
Annex A of ISO 27001:2022 lists 93 controls drawn from ISO/IEC 27002:2022, grouped into four themes. You do not have to implement all of them; you select those your risk assessment calls for and justify any exclusions.
| Theme | Section | Controls | Examples |
|---|---|---|---|
| Organizational | A.5 | 37 | Policies, roles, asset inventory, supplier relationships, incident management, cloud services, threat intelligence |
| People | A.6 | 8 | Screening, terms of employment, awareness training, remote working, disciplinary process |
| Physical | A.7 | 14 | Perimeters, entry controls, equipment security, physical security monitoring, clear desk |
| Technological | A.8 | 34 | Endpoint devices, privileged access, malware protection, logging, configuration management, secure development, data leakage prevention |
The 11 controls new in 2022 are threat intelligence (5.7), information security for use of cloud services (5.23), ICT readiness for business continuity (5.30), physical security monitoring (7.4), configuration management (8.9), information deletion (8.10), data masking (8.11), data leakage prevention (8.12), monitoring activities (8.16), web filtering (8.23) and secure coding (8.28). See ISO 27001 vs 27002 controls.
What are the Statement of Applicability and risk treatment plan?
The Statement of Applicability (SoA) lists all 93 Annex A controls and records, for each one, whether it applies, why, and whether it is implemented. Exclusions must be justified by your risk assessment, not by convenience. The SoA is the bridge between your risks and your controls, and auditors use it to plan their testing.
The risk treatment plan records how each risk above your acceptance criteria will be treated: modified with controls, retained, avoided or shared. It needs owners, dates and risk-owner approval of residual risk. Together with the risk assessment methodology, these documents carry most of Clause 6.
Other mandatory documented information includes the ISMS scope, the information security policy, security objectives, evidence of competence, operational planning records, monitoring and measurement results, the internal audit program and results, management review results, and nonconformities with corrective actions. See ISO 27001 mandatory documents.
What is the ISO 27001 certification process?
| Step | What happens | Typical duration |
|---|---|---|
| 1. Scope and gap analysis | Define ISMS scope and compare current practice to Clauses 4–10 and Annex A | 2–4 weeks |
| 2. Risk assessment and treatment | Identify assets, threats and vulnerabilities; rate risks; select controls; write the SoA | 3–6 weeks |
| 3. Implement controls and documentation | Close gaps, write policies and procedures, train staff | 2–6 months |
| 4. Operate the ISMS | Run controls long enough to produce records; most bodies expect some operating history | Ongoing, often 2–3 months before Stage 2 |
| 5. Internal audit and management review | Required before certification | 2–4 weeks |
| 6. Stage 1 audit | Certification body reviews documentation and readiness | 1–3 days |
| 7. Stage 2 audit | Certification body tests implementation and effectiveness on site or remotely | Several days, depending on size |
| 8. Certification decision | Nonconformities closed; certificate issued | 2–6 weeks |
Most mid-market organizations take six to twelve months from kickoff to certificate. Choose an accredited certification body; certificates from unaccredited bodies carry little weight with buyers. See how to choose a certification body.
What happens after certification?
An ISO 27001 certificate is valid for three years, subject to surveillance:
- Year 1 and Year 2: surveillance audits test a sample of the ISMS and Annex A controls, and confirm that internal audits, management reviews and corrective actions continue.
- Year 3: a recertification audit covers the full ISMS before the certificate expires.
- Throughout: major nonconformities must be corrected within the timeframe the certification body sets, or the certificate can be suspended.
The ISMS should also absorb change. Amendment 1 (2024) added climate change considerations to Clause 4, so context and interested-party analysis should now note whether climate change is a relevant issue.
What did the 2013-to-2022 transition change?
The 2022 edition reorganized Annex A from 114 controls in 14 domains to 93 controls in four themes, merged many overlapping controls, and added 11 new ones. Clause changes were modest, including a new requirement to plan changes to the ISMS (6.3). According to SGS, initial and recertification audits to the 2013 version ended after April 30, 2024, and all 2013 certificates expired or were withdrawn after October 31, 2025. An organization whose 2013 certificate lapsed is treated as a new client. See transitioning to ISO 27001:2022.
How does ISO 27001 fit with SOC 2, ISO 42001 and other frameworks?
| Framework | Relationship to ISO 27001 |
|---|---|
| SOC 2 | Large control overlap; different output (attestation vs certificate). Many companies hold both. |
| ISO/IEC 27701 | Privacy extension to the ISMS; now a standalone management system standard in its 2025 edition. |
| ISO/IEC 42001 | AI management system with the same clause structure; integrates naturally with an existing ISMS. See our ISO 42001 guide. |
| ISO 22301 | Business continuity management system; shares structure and supports Annex A 5.29–5.30. See our ISO 22301 guide. |
| NIST CSF 2.0 | Outcome framework that maps closely to Annex A; useful for maturity reporting. |
| HIPAA, PCI DSS, NIS2, DORA | Regulatory requirements many Annex A controls already support. |
Because the management system standards share one structure, a single control library and risk register can serve several certifications. See our control mapping guide.
What are the most common ISO 27001 mistakes?
- Scoping too broadly for a first certificate, or so narrowly that buyers will not accept it.
- A risk assessment that does not drive the SoA, so controls look selected by habit rather than risk.
- Skipping the internal audit or management review before Stage 2.
- Policies without records showing the process actually runs.
- Treating surveillance audits as a fresh project instead of keeping the ISMS running.
- Managing ISO 27001 separately from SOC 2 or other frameworks and duplicating evidence.
Frequently asked questions
How long does ISO 27001 certification take?
How many controls are in ISO 27001:2022?
Is ISO 27001:2013 still valid?
How long is an ISO 27001 certificate valid?
What is the difference between ISO 27001 and ISO 27002?
Do I need both ISO 27001 and SOC 2?
What is a Statement of Applicability?
- ISO, ISO/IEC 27001:2022 Information security management systems
- SGS, ISO/IEC 27001 transition: what you should know
- ISACA Journal, Navigating the ISO/IEC 27001:2022 transition
- TÜV SÜD, ISO 27001:2013 to 2022 certification transition
- Compyl, Understanding ISO 27001 mandatory documents
- Compyl, How to choose an ISO 27001 certification body
- Compyl, ISO 27001 vs SOC 2
Run Your ISMS in One Place With Compyl
Compyl maintains your risk register, Statement of Applicability, policies and Annex A evidence in one platform, collects evidence from 125+ in-house integrations, and maps each control across ISO 27001, SOC 2, ISO 42001 and 70+ other frameworks so surveillance audits are routine.
About this guide. By Compyl Research. Last updated November 9, 2026. This is general information, not legal advice — consult counsel for your specific obligations. Compyl is an AI-powered, agentic GRC platform built by CISOs.