ISO/IEC 27001:2022
Information Security Requirements and Implementation
ISO/IEC 27001 is the international standard for information security management systems (ISMS). In practice, it helps organisations identify information security risks and select appropriate safeguards. As a result, these measures protect the confidentiality, integrity and availability of information. Importantly, its requirements apply to an ISMS rather than to a single piece of software.
The current international edition is ISO/IEC 27001:2022, with a climate action amendment published in 2024. Organisations of any size and in any sector can use the standard. Its risk-based approach helps each organisation choose controls that fit its context instead of applying the same technical solution everywhere.
Organisations can implement ISO/IEC 27001 internally or pursue independent certification. In either case, define the ISMS scope and assess relevant risks. Then check that security measures work in practice. The guidance below explains the requirements, Annex A controls and an achievable implementation path.
What is ISO/IEC 27001 and why does it matter?
ISO/IEC 27001 sets requirements for establishing, implementing, maintaining and continually improving an information security management system. In particular, information security covers people, processes, technology and information in every format. For example, organisations need to protect data in applications, documents, cloud services and information shared with suppliers.
An ISMS starts with an understanding of business context and the information that needs protection. From there, it connects security objectives to an agreed method for assessing and treating risks. It also helps teams check whether controls are effective.ISO/IEC 27005:2022 provides further guidance for managing information security risks.
Information security starts with risk management, not just technology.
ISO/IEC 27001 requires organisations to assess information security risks, assign responsibilities and select controls based on their needs. Effective management involves people and processes as well as technical safeguards.
ISO/IEC 27001 does not prescribe identical technical measures for every organisation. Instead, it requires a documented and repeatable approach that reflects the organisation’s activities, exposure and risk appetite. For example, smaller organisations can apply the same requirements with a proportionate level of complexity.
In general, the standard is voluntary, and certification is optional. However, customers, contracts and procurement processes may call for independent certification. Importantly, ISO does not issue certificates; independent certification bodies assess organisations against the standard.
For organisations subject to Slovenian cybersecurity legislation, ISO/IEC 27001 can support a structured approach to risk management. Article 28 of ZInfV-1 encourages the use of European and international standards, but certification alone does not establish legal compliance.
Is ISO/IEC 27001 suitable for your organisation?
Organisations of any size, sector or legal status can use ISO/IEC 27001. In particular, it is useful for organisations that handle confidential information or rely on critical systems. It also helps where customers have demanding security requirements or responsibilities need clearer oversight.
Before implementation, decide which locations, business activities, systems and information belong within the ISMS. In practice, the defined scope should reflect the organisation’s operations and dependencies. However, a certificate covers only the approved scope. Therefore, it does not automatically include every process or subsidiary within a wider group.
If your customers request evidence of information security controls, the standard can provide a common management framework. Beyond certification, a well-maintained ISMS helps teams assign risk owners, address gaps and adapt to new threats.
Assess your information security needs
Identify the information, systems and services that are important to customers, employees and business operations. Then consider what could happen if this information was lost, changed or disclosed.
Review current security responsibilities
Next, check whether risk owners, process owners and management responsibilities are clear. For this purpose, an ISMS can create a consistent way to record decisions and oversee improvements.
Consider contractual and supplier expectations
Customers, tenders and supply chains may require evidence of security management. For example, ISO/IEC 27001 provides a recognised framework and an option for independent certification.
Conduct a quick ISMS self-assessment
Ask whether teams have identified key information assets and assess risks regularly. Then check whether controls have owners and teams review incidents. If these activities depend on informal arrangements, a structured ISMS may help.
Choose the right scope and edition
Finally, define an ISMS scope that matches your organisation and verify the current requirements. Use ISO/IEC 27001:2022, Amendment 1:2024 and, in Slovenia, the corresponding SIST adoption as the reference.
Key requirements of ISO/IEC 27001
How ISO/IEC 27001 requirements are structured
Clauses 4 to 10 cover organisational context, leadership, planning, support, operation, performance evaluation and improvement. Together, these requirements form the foundation of an effective ISMS. In addition, Annex A provides a reference set of 93 information security controls, grouped into organisational, people, physical and technological controls.
Context of the organisation and ISMS scope
Identify the internal and external factors that can affect information security. Also consider the needs of relevant interested parties, including customers, regulators, employees and service providers. Use this information to define and maintain the boundaries of the ISMS.
In particular, the scope should be clear about activities, locations, technology and interfaces with other organisations. In addition, the scope should reflect information assets and dependencies that affect the organisation’s services.
Leadership, policy and responsibilities
Top management must demonstrate leadership and commitment to the ISMS. In particular, management needs to establish an information security policy, assign responsibilities and ensure that the necessary resources are available. Therefore, security management should be part of business decision-making, not a separate IT exercise.
Risk owners and control owners need to understand their responsibilities. As a result, clear accountability helps teams make informed decisions, approve treatments and review results.
Information security risk assessment and treatment
The organisation needs a consistent method to identify, analyse and evaluate information security risks. In particular, it must define risk criteria, assess relevant threats and consequences, and decide which risks need treatment. As a result, teams can review risks consistently and compare results over time.
A risk treatment plan sets out proposed measures and their owners. In addition, the organisation must document its decisions and obtain the necessary approval for treatment and residual risks.
Statement of Applicability and Annex A controls
When selecting controls, the organisation must compare its chosen measures with Annex A. The Statement of Applicability (SoA) then explains which controls the organisation needs. It also explains any Annex A exclusions and records whether teams have implemented the selected controls.
Annex A contains 93 controls across four groups: organisational, people, physical and technological. However, the objective is not to implement every control identically. Instead, the controls should reflect risk assessment results, legal duties and the organisation’s needs. ISO/IEC 27002:2022 provides practical control guidance.
Competence, awareness and documented information
An effective ISMS depends on employees who understand relevant security risks and their own responsibilities. Therefore, the organisation should identify competence needs, provide suitable training and communicate important security expectations.
Alongside training, maintain documented information that supports the ISMS and provides evidence of key decisions. For example, this can include policies, risk assessments, treatment plans, the SoA, audit results and records of completed actions. The organisation should control these documents and keep them up to date.
Operations, monitoring and internal review
Plan and control the activities needed to operate the ISMS, including risk assessment and risk treatment. After that, monitor selected measures and assess whether the security objectives and controls remain effective as systems, services and threats change.
In addition, the ISMS requires internal audits and management reviews. Together, they help verify conformity, assess performance, identify gaps and make informed improvement decisions.
Continual improvement
ISO/IEC 27001 requires organisations to improve the suitability, adequacy and effectiveness of their ISMS. Consequently, findings from monitoring, audits, incidents and management reviews should lead to timely action.
When a nonconformity occurs, the organisation should address its consequences, consider its causes and take appropriate corrective action. Finally, review the results to prevent similar weaknesses from recurring.
How to implement ISO/IEC 27001
A practical ISO/IEC 27001 implementation programme can follow nine connected steps. However, adapt the level of detail to your organisation’s size, scope and security risks.
Define the purpose and scope of the ISMS
Agree why your organisation needs the ISMS. Then identify the business units, locations, services, information and systems it will cover.
Establish leadership support and ownership
Next, confirm management commitment, assign responsibilities and secure the resources needed to operate the ISMS.
Identify critical information and dependencies
Build an overview of important information, business processes, technologies and external service providers. Also identify who is responsible for them.
Assess information security risks
After mapping the dependencies, choose risk assessment criteria and a repeatable method. Then identify threats, assess potential consequences and prioritise the risks that need action.
Prepare the risk treatment plan and SoA
Based on the assessment, select appropriate controls, appoint owners and establish priorities. Next, compare the controls with Annex A and document decisions in the Statement of Applicability.
Implement measures and document evidence
Apply the selected organisational and technical measures. At the same time, align procedures with actual practice and keep relevant records of implementation.
Monitor the effectiveness of the ISMS
For ongoing assurance, decide what you will measure and review. Then assess whether controls remain effective and whether the ISMS is achieving its objectives.
Carry out an internal audit and management review
Before seeking certification, check the ISMS, record findings and provide management with evidence for decisions and improvements.
Address nonconformities and improve
Finally, assign corrective actions, investigate root causes and review whether actions have resolved identified weaknesses.
If you need independent certification, contact an external certification body after implementing, reviewing and improving the ISMS. ISO develops the standard but does not certify organisations.
How Blue Octopus supports ISO/IEC 27001
Blue Octopus can support the management work around an ISMS by connecting information assets, risks, controls, responsible people and documentation. However, it does not replace technical safeguards, internal audits or an independent certification body.
Structure, assess and prioritise information security risks
Assign risks and treatment activities to responsible owners
Track measures, priorities and accountable individuals
Link relevant documents and evidence to risks and analyses
Review findings, priorities, responsibilities and open actions
Monitor findings and corrective or improvement activities
For practical examples of the asset, risk analysis and compliance functions, see the Blue Octopus modules. In practice, the platform can help teams see what needs attention and who is responsible.
Nevertheless, using management software alone does not establish ISO/IEC 27001 conformity or certification. Ultimately, organisations must implement their controls and retain evidence that the ISMS is effective.
Frequently asked questions
Answers to common questions about ISO/IEC 27001:2022, information security controls and certification.
In general, ISO/IEC 27001 is a voluntary international standard. However, an organisation may face contractual or procurement requirements to use the standard or obtain certification.
No. An organisation can implement the standard as an internal information security management system without certification. However, an independent certification body can assess the ISMS if external assurance is needed.
The standards serve different purposes: ISO/IEC 27001 defines requirements for an information security management system and supports certification. In contrast, ISO/IEC 27002 provides additional guidance on information security controls and is not itself a certification standard.
Not automatically. The organisation determines the controls it needs through risk assessment and treatment, then compares them with Annex A. After that, the Statement of Applicability records the decisions and reasons for inclusion or exclusion.
No. Although ISO/IEC 27001 supports risk management, legislation can impose separate duties. As a result, organisations must assess the specific legal requirements of the applicable jurisdiction, including Slovenia’s ZInfV-1 where relevant.
The current international edition is ISO/IEC 27001:2022, with Amendment 1:2024 covering climate action changes. However, the previous 2013 edition is withdrawn. Slovenia adopted the standard as SIST EN ISO/IEC 27001:2023.
Official sources
Next step
ISO/IEC 27001 works best when organisations treat information security as an ongoing responsibility, not a one-off certification project. Therefore, start by defining the ISMS scope, assigning owners and identifying the information and risks that matter most.
Blue Octopus can help structure risk assessments, treatment actions, responsibilities and supporting documents in one place. Explore the platform modules to see how its management tools can support your implementation.