ISO/IEC 27001 is the world’s best-known standard for information security management systems. According to ISO, over 70,000 certificates were reported in 150 countries in 2022. For Ukrainian companies working with EU clients, a certificate can become a partner’s requirement rather than just an advantage.
Below: what ISO 27001 is, why it is needed, what changed in the 2022 edition and where to start preparing.
What ISO 27001 is
ISO/IEC 27001 sets the requirements for an information security management system (ISMS). In plain words: how a company identifies risks to its information, chooses protective measures, checks that they work and keeps improving them. As ISO puts it, conformity with the standard means a company has a system to manage risks related to the security of data it owns or handles.
- Who it is for: companies of any size and from any sector.
- Current edition: ISO/IEC 27001:2022 (October 2022) with Amendment 1:2024 on climate action changes.
- Controls are listed in Annex A, with detailed guidance on them in a separate standard, ISO/IEC 27002:2022.
- Certification is voluntary. Some companies implement the standard as best practice; others also get certified to reassure customers.
- The certificate is issued by a certification body. A certificate from an accredited body adds confidence: an accreditation body has independently confirmed its competence.
The 2013 edition no longer applies
According to the certification body SGS, after a three-year transition period that ended on 31 October 2025, all ISO/IEC 27001:2013 certifications were to expire or be withdrawn. A company with an expired certificate is treated as a new client and goes through a full initial audit.
In practice: if a partner shows you a certificate, check that it is to the 2022 edition.
Why a Ukrainian company needs it
- Client and partner requirements. During supplier due diligence, a customer may ask for the certificate or send a questionnaire with the same questions.
- Internal order. Risks, roles, documents and decisions become clear and manageable instead of resting on a few people.
- State systems. Since Law No. 4336-IX, systems without state secrets have an alternative to security authorisation — certification of conformity with an information security standard. More in “KSZI is no longer mandatory: what replaces it”.
ISO 27001 does not replace the GDPR or regulators’ requirements, but it gives a foundation that makes them easier to meet.
Where to start
- Goal and scope. Why you want certification and what it covers: the whole company or, say, one product or office. A narrow scope at the start is normal practice.
- Management support. The system will not work without it: management approves the policy, allocates resources and makes decisions on risks.
- Asset inventory: information, systems, people, suppliers and cloud services.
- Risk assessment and a risk treatment plan: what can happen, how likely and harmful it is, what to do about it.
- Statement of Applicability: which Annex A controls apply and why, and which do not.
- Policies and procedures: an information security policy, access management, backup, incident response, supplier management.
- Implementing the controls — organisational and technical.
- Staff training.
- Internal audit and management review — checking that the system works rather than just existing on paper.
- The certification audit at the chosen certification body. Then surveillance audits follow, because the system has to work between them too.
Common mistakes
- Template documents that nobody follows. The auditor checks how you work, not just what is written.
- Too wide a scope at the start.
- “It’s an IT matter.” Risks and decisions are the responsibility of management and process owners.
- Forgotten suppliers and cloud services your data passes through.
- “Certified and forgotten.” Without regular risk reviews and internal audits, the next audit will be painful.
What you may already have
Many companies cover part of the requirements before the project starts: backups, an incident response plan, password management, security monitoring, a penetration test. Preparing for ISO 27001 helps bring this into a system and close the gaps.
Checklist
- The goal of certification and the scope of the system are defined
- Management supports the project and has appointed those responsible
- There is an asset list, including suppliers and cloud services
- A risk assessment is done and a risk treatment plan approved
- A Statement of Applicability is prepared
- An information security policy and key procedures are approved
- Staff have been trained
- An internal audit and management review have taken place
- A certification body is chosen
How Bereg-IT can help
We prepare companies for ISO/IEC 27001 certification. At an audit we assess the current state, risks and conformity with the requirements and draw up a roadmap. We help with the risk assessment, policies and procedures, and implement technical controls — from network security and endpoint protection to SOC as a Service and penetration testing. The certificate itself is issued by a certification body you contract with.
The first consultation is free. Send a request and an information security specialist will get in touch.
Sources
- ISO, ISO/IEC 27001:2022 — Information security management systems — Requirements: https://www.iso.org/standard/27001
- ISO, ISO/IEC 27002:2022 — Information security controls: https://www.iso.org/standard/75652.html
- SGS, ISO/IEC 27001:2022 Transition Support — the transition period and 2013 certificates: https://www.sgs.com/en-at/showcases/iso-iec-27001-2022-transition-support
- National Cybersecurity Coordination Center at the NSDC of Ukraine, Review of the National Cybersecurity System of Ukraine 2025 (in Ukrainian) — section on the 2025 regulatory changes: https://www.rnbo.gov.ua/files/2026/NATIONAL_CYBER_SCC/kiber_2025.pdf