At a glance
- Owner
- ISO and IEC (joint technical committee ISO/IEC JTC 1/SC 27)
- Version
- ISO/IEC 27001:2022 with Amendment 1:2024
- Published
- 25 Oct 2022
- Applies to
- Any organisation, of any size, in any sector
- Mandatory
- Voluntary; often contractual in supply chains and public sector procurement
- Assessed by
- Accredited certification bodies (UKAS accredited in the UK)
- Cost model
- Paid standard; certification fees set by the certification body
Key points
- Certifies a management system, not a set of controls. Clauses 4 to 10 are mandatory; Annex A is a reference list of 93 controls, applied through risk assessment.
- Annex A is grouped into four themes: organisational (37), people (8), physical (14) and technological (34). Eleven controls were new in 2022.
- The transition period from the 2013 edition ended on 31 October 2025. Certificates to ISO/IEC 27001:2013 are no longer valid.
- Amendment 1:2024 requires the organisation to determine whether climate change is a relevant issue.
- Certification runs on a three year cycle: a two stage initial audit, surveillance audits, then recertification.
What it is
ISO/IEC 27001 specifies requirements for establishing, implementing, maintaining and continually improving an information security management system (ISMS). The ISMS is the set of policies, processes, roles and controls through which an organisation identifies its information security risks and decides how to treat them.
The standard does not tell an organisation which controls to implement. It requires a risk assessment and a risk treatment process, and requires the organisation to compare its chosen controls against Annex A so that nothing necessary is overlooked. Guidance on implementing each Annex A control is in a companion standard, ISO/IEC 27002:2022.
ISO standards are copyrighted and sold by ISO and national standards bodies (BSI in the UK). This page summarises their structure; it does not reproduce requirement text.
Structure
- Clauses 0 to 3
Introduction, scope, normative references, terms and definitions. No requirements.
Clause 4Context of the organisationInternal and external issues, interested parties and their requirements, ISMS scope, and the ISMS and its processes.
Clause 5LeadershipTop management commitment, the information security policy, roles and authorities.
Clause 6PlanningRisk assessment, risk treatment and the Statement of Applicability, information security objectives, and planning of changes.
Clause 7SupportResources, competence, awareness, communication and documented information.
Clause 8OperationOperational planning and control, and performing risk assessment and treatment at planned intervals.
Clause 9Performance evaluationMonitoring and measurement, internal audit and management review.
Clause 10ImprovementContinual improvement, nonconformity and corrective action.
- Annex A
93 reference controls in four themes: 5 Organisational controls (5.1 to 5.37), 6 People controls (6.1 to 6.8), 7 Physical controls (7.1 to 7.14), 8 Technological controls (8.1 to 8.34).
Key artefacts
Statement of Applicability (SoA). Required by clause 6.1.3. Lists every Annex A control, states whether it is applied, justifies inclusion and exclusion, and records implementation status. Auditors treat it as the index to the whole ISMS.
Risk treatment plan. Records how each risk will be treated, by whom and by when, with risk owner approval of the plan and of residual risk.
Mandatory documented information. Includes the ISMS scope, the information security policy, the risk assessment and treatment processes and their results, the SoA, information security objectives, evidence of competence, monitoring and measurement results, the internal audit programme and results, management review results, and records of nonconformities and corrective actions.
What changed in the 2022 edition
Changes from ISO/IEC 27001:2013 to ISO/IEC 27001:2022 and Amd 1:2024
- Annex A restructured from 114 controls in 14 domains to 93 controls in four themes, aligned with ISO/IEC 27002:2022. Many 2013 controls were merged rather than removed.
- Eleven new controls: 5.7 Threat intelligence; 5.23 Information security for use of cloud services; 5.30 ICT readiness for business continuity; 7.4 Physical security monitoring; 8.9 Configuration management; 8.10 Information deletion; 8.11 Data masking; 8.12 Data leakage prevention; 8.16 Monitoring activities; 8.23 Web filtering; 8.28 Secure coding.
- Clause changes: 4.4 now requires the ISMS processes and their interactions to be established; 6.2 requires objectives to be monitored; a new 6.3 requires changes to the ISMS to be planned; 9.3 adds changes in interested parties' needs as a management review input.
- Amendment 1:2024 (February 2024): clause 4.1 now requires the organisation to determine whether climate change is a relevant issue, and a note to 4.2 states that interested parties can have climate related requirements.
- Transition: under IAF MD 26, certificates to the 2013 edition expired at the end of the three year transition period on 31 October 2025.
Note
ISO/IEC 27002:2022 tags each control with five attributes: control type (preventive, detective, corrective), information security properties (confidentiality, integrity, availability), cybersecurity concepts (identify, protect, detect, respond, recover), operational capabilities and security domains. The attributes are useful for filtering the SoA into views for different audiences.
How certification works
- Stage 1 audit. The certification body reviews ISMS documentation, scope and readiness, and confirms Stage 2 can proceed.
- Stage 2 audit. The certification body tests whether the ISMS is implemented and effective, sampling processes, controls and records across the scope.
- Certification decision. Major nonconformities must be closed before a certificate is issued. Minor nonconformities need an accepted corrective action plan.
- Surveillance audits. Normally annually in years two and three, covering a sample of clauses and controls plus the effectiveness of corrective actions.
- Recertification audit. Before the certificate's three year expiry.
Only certificates from certification bodies accredited by a member of the Global ACI Multilateral Recognition Arrangement (UKAS in the UK) carry accredited status. Global ACI replaced the IAF and its recognition arrangement from 1 January 2026. Certificates from unaccredited bodies are common and worth checking in supplier assurance.
Evidence expected
At Stage 2 and surveillance, auditors typically sample: the risk register and the SoA against each other; risk owner sign off of residual risk; internal audit reports and the follow up of their findings; management review minutes covering every input clause 9.3 requires; objectives with measured results; and, for a sample of Annex A controls, operating records such as access reviews, supplier assessments, change records and incident logs.
Common nonconformities
Common nonconformity
- An SoA that does not match the risk treatment plan, or excludes Annex A controls without a justification linked to risk.
- Risk assessment carried out once for certification and not repeated at planned intervals or on significant change (clause 8.2).
- Internal audit that does not cover the whole ISMS within the audit programme, or is performed by someone auditing their own work.
- Management review that omits required inputs or produces no decisions.
- Information security objectives that are not measurable or not monitored.
- Scope statements that exclude interfaces and dependencies with no explanation.
Practitioner note
The most common failure in mature programmes is not missing controls but a disconnected ISMS: risk register, SoA, policies and operational records maintained by different people and drifting apart. Auditors find this quickly by tracing one risk from the register, through the SoA and treatment plan, to the operating evidence. Run that trace yourself on three risks before every audit.
Relationship to other frameworks
ISO/IEC 27001 certifies how information security is managed. The NCSC Cyber Assessment Framework assesses outcomes for specific essential functions, and the NIST Cybersecurity Framework is a voluntary outcome taxonomy without certification. Many organisations run ISO/IEC 27001 as the management system and use CAF or NIST CSF to frame and report capability. For control level mappings, use OpenCRE.