Guide
Implementing an ISMS: 8 steps to ISO 27001
The eight steps to an ISMS, the mandatory documents and the most common pitfalls.
With an information security management system (ISMS) based on ISO/IEC 27001, you organise information security systematically and can demonstrate it to customers and partners. More and more clients require this evidence, and anyone covered by NIS2 needs working risk management anyway. In our project experience, the journey from the start to an ISMS ready for certification takes 6 to 18 months.
Süddeutsche Datenschutzgesellschaft mbH (SDG) supports you along the way: from the free initial consultation and the build-up of the ISMS to the certification audit, and afterwards as your external information security officer who looks after your ISMS on an ongoing basis.
We agree how we will work together in the initial consultation.
We take care of everything, from the gap analysis to supporting you in the certification audit. You make the decisions, provide information and contribute where your own processes matter, for example when modelling processes or agreeing policies with your IT department.
Your team builds the ISMS itself. We provide the methodology, review interim results and prepare you for certification.
In both models we recommend filling the role of information security officer externally: this avoids conflicts of interest with IT management, limits liability risks for employees and keeps expertise up to date without you having to organise your own training. More on the page External Information Security Officer.
One of the most common misconceptions: information security is equated with IT security and delegated to the IT department. But an ISMS protects all company assets, including processes, know-how and non-digital information, and it needs decisions from management on resources, priorities and risk acceptance. IT supports it, data protection overlaps with it. We also use this graphic in our talks and initial consultations:
Three areas, clear responsibilities: what is protected and who is accountable.
Protection of the company's assets
Responsible: Management, coordinated by the information security officer
Protected assets
Protection of the IT systems
Responsible: IT department
Protection of personal data
Responsible: Data protection officer (DPO), advises and monitors
involving all areas of the company and the information security officer
Steps to build an ISMS
Ongoing in the PDCA cycle
Implementation of, for example
Why SDG
Our Head of Information Security is a certified IT security officer and BCM officer. Since 2014 we have been advising from Regensburg, throughout Germany and internationally, clients including healthcare institutions, manufacturers of digital health applications, medium-sized companies and operators of critical infrastructure.
In addition, we check technical measures with penetration tests of your web applications, APIs and cloud environments, train management and employees in our training courses and link the ISMS with your data protection, for example in the data protection impact assessment. If you are covered by NIS2, we build your ISMS so that it also meets the legal obligations: NIS2 consulting.
In-depth articles
Requirements of the standard, controls and the certification process are explained in detail in our blog.
Guide
The eight steps to an ISMS, the mandatory documents and the most common pitfalls.
Certification
How the audit works, how long it takes and what comes after the certificate.
Standard
What the mandatory clauses of the standard require of your ISMS.
Standard
Structure and topics of Annex A and how to select the right controls.
Comparison
Differences, the current status of Grundschutz++ and help with deciding.
NIS2
What an ISMS does for NIS2 and where you need to extend it.
That depends mainly on the scope, your starting point and the model of cooperation you choose, so we do not quote flat rates. After a free initial consultation and, as a rule, a gap analysis, you receive a realistic estimate of the effort involved.
The all-inclusive package suits you if there is little internal capacity or a certification date is fixed. Classic consulting suits you if your own employees with time and basic knowledge are to build the ISMS. In the dual model, an internal coordinator handles coordination in-house, while we are responsible for content, methodology and the role of information security officer.
It cannot be done entirely without you, because an ISMS only works if it fits your actual operations. You make the decisions, provide information and take part when we map your operations into processes or agree policies with your IT and the specialist departments. We do most of the work.
Yes. As external information security officer, SDG is appointed by your management, meets with it at least quarterly, monthly if required, develops the ISMS further and supports you in the surveillance audits. The annual internal audit is carried out by an SDG ISMS consultant who is not your information security officer, so that the review remains objective.
Yes. We provide both the external data protection officer and the external information security officer. At SDG the two roles are held by different people who work closely together, for example on risk analyses and technical and organisational measures.
Sources: ISO/IEC 27001:2022 (iso.org), Deutsche Akkreditierungsstelle (DAkkS, the German national accreditation body)
Note: Time frames are based on SDG's experience and are not a commitment for individual cases.