ISMS meaning: the management system under ISO/IEC 27001

A cairn on an alpine ridge next to a red and white trail marker, with layered mountain ranges in the morning light behind it.

Anyone dealing with information security soon comes across the abbreviation ISMS. The meaning of ISMS can be summed up briefly: ISMS stands for information security management system. It is neither a software product nor a firewall. It is a structured framework with which an organisation systematically protects its information. The internationally recognised standard for this is ISO/IEC 27001, currently in its 2022 edition. This article shows the building blocks that make up an ISMS and how it differs from pure IT security. It also describes how SMEs in Switzerland, Germany and Austria approach setting one up.

What an ISMS is and what it protects

An ISMS is the totality of rules, responsibilities, processes and measures. With them, an organisation plans, steers, monitors and improves its information security. At its core are three protection objectives:

  • Confidentiality: information is accessible only to authorised persons.
  • Integrity: information is correct and complete and is not altered without notice.
  • Availability: information and systems are ready when they are needed.

What is protected is not just data on servers. Paper records, the knowledge of employees, contracts with service providers and confidential conversations are also included. An ISMS therefore first asks which information is important to the company. It then asks what happens if this information is lost, falsified or falls into the wrong hands.

How an ISMS differs from pure IT security

IT security deals with technical systems: networks, end devices, access rights, backups and updates. This is important, but covers only part of the subject. An ISMS operates one level higher. It defines who decides, by which criteria risks are assessed and how the effectiveness of measures is reviewed.

The difference shows in everyday practice. A good firewall is of little use if nobody knows who must be informed in the event of a security incident. Nor does it help if former employees keep their access rights or if a supplier works with sensitive data without clear requirements. An ISMS links technology with organisation, people, premises and the supply chain. Under ISO/IEC 27001, top management explicitly bears responsibility. Information security thus becomes a leadership task and is not solely a matter for IT.

The building blocks of an ISMS according to ISO/IEC 27001

ISO/IEC 27001 follows the common high-level structure of ISO management system standards. The actual requirements are set out in clauses 4 to 10. The following building blocks help with understanding:

  • Context and scope: The organisation determines internal and external issues as well as the requirements of interested parties, such as customers, authorities or partners. From this it derives the scope, that is, which sites, processes and systems the ISMS covers. This boundary determines the effort involved and, later, the content of the certificate.
  • Leadership and policy: Top management establishes an information security policy, assigns roles and authorities and provides the necessary resources.
  • Risk assessment and risk treatment: The organisation defines a traceable process for identifying, analysing and evaluating risks. For each relevant risk it decides how to deal with it, for example through controls, transfer or deliberate acceptance. The result is a risk treatment plan approved by the risk owners.
  • Controls from Annex A: Annex A of the 2022 edition contains 93 controls in four themes: organisational, people, physical and technological controls. The organisation compares its chosen controls with this catalogue. In the Statement of Applicability it documents which controls it implements, which it does not and why.
  • Evaluation and continual improvement: The organisation monitors and measures the effectiveness of its ISMS. It conducts internal audits, top management reviews the system regularly, and nonconformities are resolved through corrective actions.

The order matters. Annex A is not a checklist to tick off. The selection of controls follows from the risk assessment. Guidance on implementing the individual controls is provided by the companion standard ISO/IEC 27002.

Coiled climbing rope with a karabiner on a granite rock

What documentation an ISMS needs

The standard requires documented information but does not prescribe a particular form. For an SME, lean documentation is usually more sensible than an extensive manual. The key records include:

  • the defined scope and the information security policy
  • the process and results of risk assessment and risk treatment
  • the Statement of Applicability
  • the information security objectives
  • evidence of the competence of the people involved
  • results of monitoring and measurement, internal audits and management review
  • nonconformities and the corrective actions taken

Which further rules are needed, for example on access rights, data backup or incident management, depends on the risks and the scope.

How SMEs in Switzerland, Germany and Austria approach implementation

In practice, implementing an ISMS usually follows a similar sequence. The duration depends on the size, the scope and the existing level of maturity.

  • Clarify the objective: Why does the company need an ISMS? Common drivers are customer requirements, tenders, partner requirements or the wish for greater clarity about risks.
  • Define the scope: Better clear and appropriate than too broad. It must cover the services that are relevant to customers.
  • Take stock: A gap analysis shows what is already in place and where gaps exist.
  • Assess risks and implement controls: This is where most of the work lies.
  • Involve employees: Awareness and training are part of the requirements. The SICE Academy training courses support teams in this.
  • Check effectiveness: Before certification, at least one internal audit and one management review are required. If needed, SICE carries out internal audits as an independent body.

On the legal environment: in Switzerland the revised Data Protection Act applies, in Germany and Austria the GDPR. For certain companies in the EU, the national implementations of the NIS 2 Directive also apply. An ISMS according to ISO/IEC 27001 can help you address such requirements in a structured way. However, it does not replace a legal review. Which obligations apply to your company must be clarified case by case.

How certification with SICE works

Once the ISMS is in operation, certification follows. It can begin with an optional pre-audit that assesses the status in advance. In the stage 1 audit, SICE reviews the documentation. The on-site stage 2 audit verifies whether the ISMS is implemented as described and is effective. The certificate is valid for three years, with annual surveillance audits. You receive a quote within 24 hours. The audit usually starts within two weeks of order confirmation. You will find details on the page on ISO/IEC 27001 certification. You can clarify any open questions in the free initial consultation.

Frequently asked questions

Is an ISMS too demanding for small companies?

Not necessarily. ISO/IEC 27001 applies to organisations of any size. A clearly defined scope and lean documentation keep the effort reasonable. How much effort is actually involved depends on the starting point and the risks.

Do all 93 controls from Annex A have to be implemented?

No. The selection is based on the risk assessment. Controls may be excluded if this is justified in a traceable way. The justification is recorded in the Statement of Applicability.

Is an ISMS required by law?

Certification to ISO/IEC 27001 is generally voluntary. However, laws such as data protection legislation or national cybersecurity regulations may require organisational and technical measures. Whether, and which, obligations apply to your company should be examined case by case.

Mountain lake in the morning light, reflecting the peaks

Let's talk about your certification.

In a free initial consultation, we clarify the scope of certification and give you an initial cost estimate. You will receive your quotation within 24 hours.