SDG data protection blog

IT security

Implementing an ISMS: 8 Steps to ISO 27001

03 November 2026 by Sebastian Baier · Reading time approx. 12 minutes

You implement an ISMS in eight steps: management mandate, context and scope, stocktaking, risk assessment, risk treatment with the Statement of Applicability, implementation of policies and controls, monitoring with internal audit and management review, and finally improvement and certification. The basis is ISO/IEC 27001:2022 including Amendment 1:2024. In our project experience, the journey to an ISMS ready for certification takes 6 to 18 months.

This guide shows what needs to be done in each step, which documents the standard requires and where projects typically stall. You can find our consulting services on the page ISO 27001 Consulting.

What is an ISMS?

An information security management system (ISMS) is a systematic approach to protecting a company's information. It covers people, processes and IT systems and aims at the confidentiality, integrity and availability of information, both digital and non-digital.

An ISMS is not a software product but a management system following the cycle of Plan, Do, Check, Act (PDCA).

The standard consists of two parts: clauses 4 to 10 with the requirements for the management system, and Annex A with 93 controls in four themes: organisational, people, physical and technological. Clauses 4 to 10 are mandatory; what they require is explained in the article ISO 27001 requirements.

The eight steps at a glance

Step Content Reference in the standard
1. Management mandate management support, project organisation, roles clause 5
2. Context and scope internal and external issues, interested parties, scope clause 4
3. Stocktaking gap analysis, asset register preparation for clause 6
4. Risk assessment identify, analyse and evaluate risks 6.1.2, 8.2
5. Risk treatment select controls, Statement of Applicability, treatment plan 6.1.3, 8.3, Annex A
6. Implementation policies, processes, technical controls, training clauses 7 and 8
7. Monitoring metrics, internal audit, management review clause 9
8. Improvement and certification corrective actions, certification audit clause 10

Step by step

Step 1: Management mandate and project organisation

Without management, every ISMS fails. Clause 5 of the standard expressly requires top management to demonstrate leadership and establish an information security policy. The policy includes information security objectives or the framework for setting them, as well as a commitment to satisfy applicable requirements and to continually improve the ISMS; it is communicated within the organisation (5.2). Management also assigns roles and authorities, in particular for ensuring that the ISMS conforms to the standard and for reporting on its performance to top management (5.3). In practice, this means:

  • A decision on the project with objectives, budget and time frame
  • Appointment of an information security officer and an internal project lead
  • Clarifying who in the company contributes: IT, HR, purchasing, business units, data protection
Important: an ISMS is not a task for the IT department

Because it is about information security, many management teams assume that the ISMS falls to the IT department. That is not correct. Responsibility lies with management, and the ISMS concerns the whole company. IT takes on a supporting part, above all for technical controls. Two examples: every department has to contribute to the asset register, because only they know their business processes and information. And all departments are involved in business continuity management, from the business impact analysis to the emergency plans.

Step 2: Determining the context and scope

Under clause 4, you determine which internal and external issues are relevant to your information security and which requirements interested parties have, such as customers, authorities or insurers. Since Amd 1:2024, you must expressly determine whether climate change is a relevant issue.

From this you derive the scope: which sites, processes, systems and organisational units belong to the ISMS? Under 4.3, you also take into account interfaces and dependencies with activities performed for you by other organisations, such as IT service providers or cloud providers. The scope must be available as documented information. Take your time over this step: an unclear or badly drawn scope leads to problems later, at the latest in the certification audit. If your company has several sites or companies, this is also where you decide on the later type of certification: single certification, matrix or multi-site certification, or group certification. More on this in the article ISO 27001 certification.

Step 3: Stocktaking with gap analysis and asset register

A gap analysis shows what already exists and what is missing, measured against clauses 4 to 10 and Annex A. Existing material such as backup concepts or data protection documentation can often be reused.

At the same time, the asset register is created: an inventory of information assets with their owners, i.e. information, applications, IT systems, service providers and rooms. The asset register is the basis for the risk assessment. Every department contributes to it: the business units describe their business processes and the information they work with, and IT adds the systems and applications.

Step 4: Risk assessment

The core of the ISMS. Under 6.1.2, the risk assessment consists of four parts:

  1. Establish criteria Criteria for performing the assessment and risk acceptance criteria, i.e. the point at which a risk is tolerable.
  2. Identify risks Risks associated with the loss of confidentiality, integrity and availability of information within the scope, each with a risk owner.
  3. Analyse risks Assess the potential consequences and the realistic likelihood of occurrence and determine the level of risk from these.
  4. Evaluate risks Compare the results with the acceptance criteria and prioritise the risks for treatment.

The standard requires repeated assessments to produce consistent, valid and comparable results. You must document the process. A simple matrix with three to five levels is sufficient for most medium-sized companies.

Step 5: Risk treatment and Statement of Applicability

For each risk you choose a treatment option based on the assessment, in practice usually to reduce, avoid, transfer or consciously accept it. Under 6.1.3, you then determine all the controls you need for this. You can design these yourself or take them from any source. You then compare them with Annex A to make sure that no necessary control has been overlooked. Annex A is not exhaustive; additional controls are possible.

The result is two central documents:

  • Statement of Applicability (SoA): it contains the necessary controls with the justification for their inclusion, their implementation status and the justification for excluding individual Annex A controls.
  • Risk treatment plan: which controls will be implemented, by whom and by when? The risk owners approve the plan and accept the remaining residual risks.

The controls are explained in detail in the article ISO 27001 Annex A.

Step 6: Implementing policies, processes and controls

Now the actual work begins, and it usually takes the longest. Typical building blocks:

  • Policies and procedures: information security policy, rules on access, passwords, remote working, backup, classification
  • Processes: incident management, change management, granting access rights, joiners and leavers
  • Supplier requirements: the ISMS sets security requirements for assessments and contracts; supplier management itself is carried out by purchasing and the business units, see NIS2 and the supply chain
  • Business continuity management: emergency plans and recovery for critical processes, with all departments involved, see Setting up BCM
  • Technical controls: for example multi-factor authentication, hardening, logging
  • Competence and awareness: training so that all employees know their role (clause 7)

Under clause 8, you implement the risk treatment plan and repeat the risk assessment at planned intervals or when significant changes are proposed or occur.

Step 7: Monitoring, auditing, reviewing

Under 9.1, you determine what is monitored and measured, using which method, when and by whom, for example training rates, patch levels or incidents. The internal audit (9.2) checks at planned intervals whether the ISMS conforms to the standard and to your own requirements and is effectively implemented. It is based on an audit programme. Auditors must ensure objectivity and impartiality; in practice, this means nobody audits their own work.

In the management review (9.3), management reviews the ISMS at planned intervals, based among other things on nonconformities, measurement and audit results, the achievement of objectives, risks and the status of the treatment plan. It decides on improvements and necessary changes.

Step 8: Improving and certifying

For nonconformities, 10.2 requires you to react, take action to control and correct them and deal with the consequences; determine the causes and whether similar nonconformities exist or could occur; implement any corrective action needed, review its effectiveness and make changes to the ISMS if necessary. Nonconformities, actions and results must be documented.

Once the ISMS has been lived for a while and evidence is available, the certification audit by an accredited certification body follows in two stages: stage 1 mainly reviews the documentation and readiness, stage 2 the implementation in day-to-day operations. The certificate is then valid for three years, with annual surveillance audits. An ISMS can also be operated without certification if no customer or law requires evidence.

Mandatory documents under ISO 27001

The standard requires certain documented information. The most important:

Document Clause
Scope of the ISMS 4.3
Information security policy 5.2
Information security risk assessment and risk treatment process 6.1.2, 6.1.3
Statement of Applicability 6.1.3 d)
Information security objectives 6.2
Evidence of competence 7.2
Results of information security risk assessments and risk treatment 8.2, 8.3
Evidence of the monitoring and measurement results 9.1
Audit programme and audit results 9.2
Results of management reviews 9.3
Nonconformities and corrective actions 10.2

In addition, there is the documentation that you yourself consider necessary for the effectiveness of the ISMS (7.5.1), for example policies on individual Annex A controls.

Typical stumbling blocks

Stumbling block Consequence Remedy
ISMS as a pure IT project business units and management are missing, processes remain unregulated management mandate, involvement of all areas from the start
Scope too large or too small too much effort, or a certificate that does not help customers align the scope with objectives and customer expectations
Template documents without adaptation paper and practice do not match, nonconformities in the audit tailor documents to the actual workflows
Too little internal time the project drags on, knowledge is lost plan fixed time allocations for internal contacts

Do it yourself or with support?

You can build an ISMS yourself, but time and experience with the standard are often lacking. We agree how we will work together in the initial consultation:

  • All-inclusive package: we largely take over the build-up, on request in a dual model with an internal coordinator on your side.
  • Classic consulting: your team does the work itself, and we support you with methodology, templates and reviews up to certification.

In both cases, we recommend an external information security officer, because of conflicts of interest, liability risks and the effort required for continuing training. More on this on the page external information security officer.

Under NIS2, an ISMS based on ISO 27001 largely covers Section 30 BSIG (the German BSI Act), see NIS2 and ISO 27001 and NIS2 checklist. If a client expressly requires BSI IT-Grundschutz, that is the alternative.

How SDG supports you

  • Gap analysis against ISO 27001 as the basis for a realistic estimate of the effort involved
  • Building the ISMS as an all-inclusive package or classic consulting, from scope and risk assessment to the Statement of Applicability
  • Policies and processes tailored to your actual workflows
  • Internal audit and preparation for the certification audit
  • External information security officer for the build-up and ongoing operation
  • Training for employees and management: Training

It is best to talk to us directly about costs, for example in a free initial consultation.

Frequently asked questions about implementing an ISMS

What is an ISMS, in simple terms?

An information security management system is a systematic approach to protecting information in a company. It sets out objectives, responsibilities, risk assessment, controls and their regular review, and covers people, processes and IT systems.

How long does it take to implement an ISMS?

In our project experience, 6 to 18 months until the ISMS is ready for certification. What matters is the starting point, the size of the scope and the time internal contacts can contribute.

Where do I start when implementing an ISMS?

With the mandate from management and a gap analysis. It shows what already exists and is the basis for the project plan and the estimate of the effort involved.

Which documents does ISO 27001 require?

Among others: the scope, the information security policy, the risk assessment and risk treatment process and its results, the Statement of Applicability, information security objectives, evidence of competence, the audit programme and audit results, the results of management reviews, and nonconformities and corrective actions.

Can I implement an ISMS without certification?

Yes. An ISMS is worthwhile even without a certificate, for example to manage risks or meet NIS2 requirements. A certificate makes sense if customers, tenders or partners require independent evidence.

Do I need an information security officer for an ISMS?

The standard does not prescribe the role under this name, but it does require clear responsibilities. This kind of management is not possible without an information security officer, so for us the role is a must. We recommend filling it externally to avoid conflicts of interest and liability risks; the head of IT and the data protection officer should not take on the role.

Is implementing an ISMS a task for the IT department?

No. Responsibility lies with management, and the ISMS concerns all areas. IT takes on a supporting part, above all for technical controls. Every department contributes to the asset register, and all departments are involved in business continuity management.


Sources: ISO/IEC 27001:2022 (incl. Amd 1:2024), DAkkS

Note: this article is for general information only. Version of the standard: ISO/IEC 27001:2022 incl. Amd 1:2024.