🌐 Global · Framework guide

ISO/IEC 27001:2022: what certification requires, clause by clause

ISO/IEC 27001 is the international standard for an information security management system and the certificate most often requested by enterprise and government customers worldwide. The 2022 edition reorganised the controls and added eleven new ones, and the transition from the 2013 edition closed on 31 October 2025. This guide explains the clauses, the controls, the statement of applicability and the audit cycle.

PublisherISO and IEC, through joint technical committee ISO/IEC JTC 1/SC 27
Current editionISO/IEC 27001:2022, published October 2022 (with Amendment 1:2024 on climate change considerations)
StructureClauses 4–10 define the management system; Annex A lists 93 controls in 4 themes
Annex A themesOrganisational (37), People (8), Physical (14), Technological (34)
CertificationAccredited certification body; Stage 1 (documentation) and Stage 2 (implementation) audits; three-year certificate with annual surveillance audits
TransitionCertificates to the 2013 edition expired 31 October 2025

ISO 27001 certifies a system, not a set of controls. The auditor checks that you have defined the scope and context of your ISMS, that leadership owns it, that you assessed risk and chose controls through a documented process, that the controls are operating and measured, that internal audit and management review happen, and that nonconformities are corrected. Annex A is the menu of controls you select from; the statement of applicability is where you record which you chose and why.

The 2022 edition merged the 114 controls of 2013 into 93 and added eleven that reflect how organisations now operate: threat intelligence, information security for use of cloud services, ICT readiness for business continuity, physical security monitoring, configuration management, information deletion, data masking, data leakage prevention, monitoring activities, web filtering and secure coding.

The management-system clauses

Clause 4 Context of the organisation

Internal and external issues, interested parties and their requirements, and the scope of the ISMS. Scope is the first thing a certification body checks and the most common source of a weak certificate.

Clause 5 Leadership

Top management commitment, an information security policy, and roles, responsibilities and authorities assigned.

Clause 6 Planning

Risk assessment and risk treatment methodology, the statement of applicability, security objectives and plans to achieve them, and planning of changes.

Clause 7 Support

Resources, competence, awareness, communication and documented information under control.

Clause 8 Operation

Operational planning, performing risk assessments at planned intervals and implementing the risk treatment plan.

Clause 9 Performance evaluation

Monitoring and measurement, internal audit at planned intervals, and management review with defined inputs and outputs.

Clause 10 Improvement

Continual improvement, nonconformity and corrective action, with records.

The certification path

  1. Scoping and gap assessment (4–8 weeks). Define the ISMS scope, assess against the clauses and Annex A, write the risk methodology.
  2. Implementation (3–9 months). Risk assessment, risk treatment plan, statement of applicability, policies, controls operating, records accumulating.
  3. Internal audit and management review. Required before certification; the auditor will ask for both.
  4. Stage 1 and Stage 2 audits. Stage 1 reviews documentation and readiness; Stage 2, typically a few weeks later, tests implementation. Certificate issued on closure of any major nonconformities.
  5. Surveillance and recertification. Annual surveillance audits in years one and two, full recertification audit in year three.

Who it applies to

Any organisation, in any sector, that needs to demonstrate information security to customers, regulators or partners. It is the certificate most often required in European, Asia-Pacific, Middle East and government procurement, and the one international customers accept where SOC 2 is unfamiliar. Many regulatory frameworks, including APRA CPS 234, the NCA ECC and sector rules in the EU, treat ISO 27001 as the expected baseline.

How GRCorb covers ISO/IEC 27001:2022

From scope to evidence, in one system

The ISMS as records, not documents

Scope, interested parties, risk methodology, objectives, roles, internal audits, management reviews and corrective actions live in the ISMS Scope and Records and Management Review modules, with the history an auditor samples.

Risk-driven control selection and the SoA

The Risk & Quantification module assesses risks against assets and produces the treatment plan; the statement of applicability is generated from the control decisions with justifications, and updated when risks change.

All 93 Annex A controls with evidence

Each control carries an owner, implementation status, measurement and evidence, with technological controls evidenced automatically from Microsoft 365, Entra ID, Intune, Defender, AWS, Azure, GitHub and your SIEM.

Policies and awareness that auditors can trace

The AI Policy Builder generates the policy set, the Policy Register tracks versions and employee acknowledgement, and the Awareness module records training, which closes clause 7.

One certificate, many frameworks

ISO 27001 is the hub of the GRCorb crosswalk. Evidence collected for it counts toward SOC 2, the Essential Eight, NIST CSF, 800-53, CPS 234 and the national frameworks in your scope, and the programme matrix shows what each piece of work advances.

Frequently asked questions

Do we have to implement all 93 controls?

No. You select controls based on your risk assessment and record exclusions with justification in the statement of applicability. In practice most organisations find very few Annex A controls genuinely not applicable, and auditors challenge weak justifications.

How long does certification take?

Six to twelve months for an organisation starting from little, less for one with existing controls and a clear scope. The audit itself is a few days spread across Stage 1 and Stage 2; the time goes into implementation and accumulating records.

ISO 27001 or SOC 2?

ISO 27001 for international, government and regulated customers; SOC 2 for North American enterprise customers. The control overlap is large, GRCorb maps between them, and companies selling globally commonly hold both.

What about ISO 27701, 27017 and 27018?

They are extensions: 27701 adds a privacy information management system, 27017 and 27018 add cloud security and cloud privacy controls. They are certified alongside 27001, not instead of it, and GRCorb carries them in the same ISMS.

Related frameworks

Reviewed November 2026. This guide is general information about the published framework and is not legal advice; always check the current official text from the publisher before relying on it.