An ISMS based on BSI Grundschutz++ rarely fails because of technical issues, but rather because of its basic setup: a lack of support, unclear roles, or an overly broad scope. Those who start small, clearly define the scope, and implement it consistently can go from zero to a fully operational ISMS in five steps.
From the BSI Grundschutz++ series · approx. 8 minutes
You are currently viewing a placeholder content from Default. To access the actual content, click the button below. Please note that doing so will share data with third-party providers.
More InformationThe project kickoff for BSI Grundschutz++ follows five steps: clarifying support and roles, defining the scope of the information network, identifying and modeling assets, conducting a target-actual comparison, and finally implementing measures and continuously improving them. The order is crucial—only once the setup, scope, and asset model are in place is it worthwhile to compare them against the requirements.
With Grundschutz++, a risk-based approach takes center stage: How critical an asset is to the business determines how much is invested in its protection. The goal is not a folder full of documents, but an ISMS that works in day-to-day operations and is regularly updated—with or without certification.
➔ Would you like to establish an ISMS in accordance with BSI Grundschutz++ and set it up properly from the very beginning? We’ll guide you every step of the way, from the project kickoff to a fully operational ISMS—schedule a no-obligation initial consultation.
The first step is to secure management support and define clear roles, particularly that of an information security officer who has sufficient time. Next, the information environment is delineated, the assets are inventoried and modeled, and gaps are identified through a target-actual comparison. Only then do the prioritized implementation of measures and continuous improvement follow.
The scope of the ISMS is defined by the information network. It specifies which business processes, locations, and areas are included, as well as which interfaces exist with service providers and suppliers. A clear definition of scope ensures that all stakeholders are aware of the boundaries and scope of the ISMS.
No. Some companies seek certification, while others simply align their ISMS with the standard. The five-step project launch process is the same in both cases.
Common issues include an overly broad scope, choosing a tool before clarifying one’s own processes, and an information security officer who performs the role only as a side job. The most common mistake is having a lot of paper documentation that isn’t actually put into practice. An ISMS is something that actually works in everyday life.
More videos from the BSI-Grundschutz++ series:
Welcome to the presentation “Launching a Project in 5 Steps with BSI Grundschutz++”—from real-world experience, for real-world application. It’s always important to us to explain and work in a way that’s as practical as possible. There’s a lot of talk about how documentation is always a key issue. Ultimately, though, it’s about putting theory into practice—that’s what delivers IT security.
Not just any documentation that goes unused and unupdated, but a living ISMS that is continuously improved and adapted to current situations and changes within the company. If you want to start from scratch: We’ve summarized in 5 steps how to go from zero to BSI Grundschutz++. Often, it’s not the technology, but the basic setup.
It’s important to clearly define how the project should work, who is responsible for what, and what pitfalls to watch out for. We’ll address these points and guide you through the 5 steps. Support and roles are key: The project needs support throughout the entire organization, and it must be clear to everyone what priority it has and what impact it will have on the entire company. Next, you need to define the scope of the information network. Next, the assets are inventoried and modeled, and only then do we move on to the target-actual comparison: Where do we stand, and where do we need to go in order to certify the ISMS according to BSI Grundschutz++?
Some organizations do not seek certification at all, but simply want to align their ISMS with the standard—that is also a valid approach. The next step is to implement the measures and engage in a continuous improvement process, ensuring that the ISMS is always up to date.
Step 1: Support and Roles. It’s important that senior management is on board: We want to carry out this project; it’s important for the company; and we’ll receive the resources, budget, objectives, and timeline—whether predefined or at least agreed upon company-wide. You’ll also need an information security officer who has the necessary time to dedicate to the role. This person can be an internal or external employee. The result: clear guidelines for information security and a clear project mandate.
Step 2: Define the scope of the information system. It is important to determine which business processes, locations, and areas are included, which processes will be considered initially, and what interfaces exist with service providers and suppliers. This ensures that, in the end, you have a clearly defined scope that everyone understands—everyone knows where the boundaries of the ISMS lie and how far it extends.
Step 3: Identify and model assets. With the transition to BSI Grundschutz++, asset management has become a key focus. Processes, applications, IT systems, and facilities are identified and then assessed based on how critical they are to the business. Grundschutz++ places much greater emphasis on sensible risk management: How important is an asset, and how much does it really need to be protected? And how much are we willing to invest in its protection? There are also so-called target object categories that are mapped to the assets. The result is an asset model from which the requirements can be derived.
Step 4: Target-Actual Comparison. It is only now, in Step 4, that the target-actual comparison takes place. The setup leading up to this is extremely important to ensure there are no ambiguities in the project. BSI Grundschutz++ essentially sets out clearly what needs to be done. This is compared with the requirement packages from the asset model. Machine readability is crucial here, as BSI Grundschutz++ fundamentally requires that the ISMS be machine-readable. The process culminates in a target-actual comparison: you know exactly where the gap lies between what currently exists and what still needs to be done. This results in a list of gaps with a status assigned to each requirement.
Step 5: Implement and improve measures. When implementing these measures, it is important to proceed based on priority. Attacks can happen at any time, even while you are establishing an ISMS. So it’s always a matter of taking the next best step from the current situation to protect yourself even while the project is underway. The measures are prioritized, with clear responsibilities and deadlines. The result is an ISMS that works in everyday practice and isn’t just sitting in a folder. It’s very important to involve the line departments so that the documents don’t just gather dust somewhere, and to plan for at least one annual review to ensure the ISMS remains up to date.
Four Common Mistakes Made at the Start of a Project. First: taking on too much—you set your sights too high and don’t make any progress. Second: tools before processes. Tools are meant to support you; you shouldn’t have to adapt to the tool. First, clarify processes, roles, and workflows, and then consider whether—and which—software to use. Third: an information security officer who treats the role as a side job and doesn’t have the necessary time. And probably the biggest mistake: a lot of paper documentation is created that doesn’t work in practice. An ISMS is what is actually put into practice, not what is written in documents. That’s why the focus is on ensuring it is implemented and works in practice.
So here are my tips: start small, set clear boundaries, and then implement them consistently. If you have any questions, feel free to schedule an appointment with me. We’ll spend half an hour discussing how to implement this effectively and what works well—and what doesn’t. You’ll find the link below in the description. I look forward to our conversation—until then, all the best.