News · 23 October 2025
ISO/IEC 27001:2013 certificates end on 31 October: what the 2022 revision changed
The transition period for the 2022 revision of ISO/IEC 27001 ends on 31 October 2025. After that date, certificates issued against the 2013 version are no longer valid. Organisations that have not completed the transition will need to move to the 2022 edition to keep a valid certificate.
What changed
The management-system requirements in clauses 4 to 10 changed only modestly. The main change is in Annex A, the controls catalogue, which aligns with ISO/IEC 27002:2022. The 114 controls in 14 groups became 93 controls in four themes: organisational, people, physical and technological. Eleven controls are new, including:
- 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.
Why the new controls matter
They reflect how organisations actually work today: cloud-hosted, data-heavy and software-driven. "Secure coding" and "configuration management" make explicit what well-run engineering teams already do. "Monitoring activities" asks organisations to detect anomalous behaviour, not merely write policies about it.
A pragmatic view of certification
A certificate is evidence that a management system exists and has been audited. It is not a guarantee that the organisation is secure. Customers increasingly know this, and they supplement certificates with questions about specific practices.
That means certification and testing complement one another. An ISMS sets expectations and records decisions. Independent technical testing checks whether the controls work in reality. A strong programme uses both and feeds the findings back into risk assessment.
For teams still deciding
- Compare your Statement of Applicability against the new control set and note gaps.
- Prioritise technological controls where evidence is easy to generate: logs, configurations, test reports.
- Keep the scope honest. A narrow scope covering what you really operate is more credible than a broad one you cannot evidence.
- Use the audit as an opportunity to simplify, not just to add.
Standards are most useful when they change what people do on a Tuesday.
Written in October 2025; details reflect the situation at that time.