BSI IT-Grundschutz

On this page 8

BSI IT-Grundschutz is the information security methodology published by the German Federal Office for Information Security (BSI) that combines a management system framework with a large catalog of concrete security requirements for typical processes, systems and environments. Among security standards in cybersecurity, it stands out because it tells an organization not only that it must manage risk, but also which safeguards are expected for common components such as servers, networks, mobile devices and office rooms.

The approach rests on a simple premise: most organizations face the same typical threats, so a well-chosen set of standard safeguards achieves an adequate level of protection for normal needs without a full risk analysis of every asset. A dedicated risk analysis is reserved for assets with high or very high protection needs or for situations the catalog does not cover.

The building blocks of the IT-Grundschutz methodology

IT-Grundschutz consists of a family of BSI standards and the IT-Grundschutz Compendium, which together describe how to build, operate and verify an information security management system (ISMS). The standards define the process; the Compendium supplies the content that fills it.

The following table shows the main documents and the role each plays in the overall method.

DocumentScopeMain purpose
BSI Standard 200-1Management systemsRequirements for an ISMS, compatible with ISO 27001
BSI Standard 200-2MethodologyStep-by-step procedure for applying IT-Grundschutz
BSI Standard 200-3Risk analysisSimplified risk analysis for elevated protection needs
BSI Standard 200-4Business continuityBuilding a business continuity management system
IT-Grundschutz CompendiumModules and requirementsCatalog of modules with concrete security requirements
Core documents of IT-Grundschutz

The Compendium is organized into modules (in German, Bausteine). Each module covers one subject, such as a web server, an Active Directory domain or a remote workplace, and lists its specific threats and the security requirements that address them. The BSI revises the Compendium periodically, so organizations should always record which edition they used for their modeling.

How the IT-Grundschutz procedure runs

The procedure in BSI Standard 200-2 follows a fixed sequence that turns a description of the organization into a verified set of safeguards. Its core idea is modeling: every relevant target object in the scope is mapped to the modules that apply to it.

  1. Define the scope (information domain) and its business processes.
  2. Perform a structure analysis that records applications, IT systems, networks, rooms and their dependencies.
  3. Carry out a protection needs assessment for confidentiality, integrity and availability.
  4. Model the domain by assigning Compendium modules to each target object.
  5. Run the IT-Grundschutz check, a gap analysis of which requirements are fulfilled.
  6. Perform a risk analysis under BSI Standard 200-3 where protection needs exceed normal.
  7. Implement and consolidate the safeguards, then maintain them in a continuous improvement cycle.

The protection needs assessment uses three categories: normal, high and very high. The category is derived from realistic damage scenarios, such as legal violations, financial loss or harm to persons, and it propagates through dependencies according to the maximum principle: an IT system that supports a highly critical application inherits that high protection need.

Protection approaches and requirement levels

IT-Grundschutz offers three protection approaches so that organizations can start at a realistic level and grow. The choice depends on resources, maturity and the criticality of the assets.

ApproachCoverageTypical use
Basic protectionBasic requirements across the whole scopeQuick entry point for small or immature organizations
Core protectionFull protection for selected crown jewelsSecuring the most critical assets first
Standard protectionBasic and standard requirements across the scopeRecommended target; basis for ISO 27001 certification
Protection approaches in BSI Standard 200-2

Within each module, requirements are graded into three levels. Basic requirements must be fulfilled first because they remove the most serious gaps with modest effort. Standard requirements reflect the state of the art for normal protection needs. Requirements for elevated protection needs are candidates for selection when the risk analysis shows that standard safeguards are not sufficient.

Modules are grouped into process layers (for example ISMS, organization and personnel, concepts, operations, detection and reaction) and system layers (applications, IT systems, industrial IT, networks and communication, infrastructure). This layering lets assessors see whether management controls and technical controls are covered in a balanced way.

IT-Grundschutz compared with other security standards

IT-Grundschutz is more prescriptive than most international frameworks: where ISO 27001 requires a risk-based selection of controls, IT-Grundschutz delivers a pre-built selection for typical scenarios. The comparison below shows how it relates to frequently used neighbors.

FrameworkNatureLevel of detailCertification
BSI IT-GrundschutzMethodology plus requirements catalogVery detailed, per componentISO 27001 on the basis of IT-Grundschutz
ISO 27001ISMS requirements standardAbstract controls in Annex AAccredited certification bodies
NIST CSFOutcome-based frameworkFunctions and outcomesNo formal certification
CIS ControlsPrioritized technical safeguardsDetailed, technically focusedNo formal certification
Comparison with related frameworks

An organization can obtain an ISO 27001 certificate on the basis of IT-Grundschutz, issued by the BSI after an audit by a BSI-certified auditor. This certificate confirms both conformity with ISO 27001 and implementation of the relevant Compendium requirements, which makes it more demanding than a native ISO 27001 certificate. It is typically valid for three years, with annual surveillance audits.

Where IT-Grundschutz is used and what it costs

IT-Grundschutz is widely used in the German public sector, where federal agencies are expected to apply it, and it is common among operators of critical infrastructure, municipal utilities, hospitals and service providers to public administration. Private companies outside Germany use it less often, but its modules are valued worldwide as a free, practical checklist for hardening specific technologies.

The method also supports IT-Grundschutz profiles, which are reusable templates prepared by an industry group or authority for a typical setting, such as a municipal administration or a small hospital. A profile shortens modeling considerably because the scope, protection needs and module selection are already worked out.

Limitations and common mistakes

The greatest strength of IT-Grundschutz, its detail, is also its main weakness. Full standard protection in a large organization means evaluating thousands of requirements, which demands tool support and dedicated staff. Typical problems and their remedies are summarized below.

ProblemCauseRemedy
Documentation overloadChecking every requirement without prioritiesStart with basic protection, then expand
Outdated modelingStructure analysis not maintained after changesTie updates to change management
Missed risksSkipping risk analysis for high protection needsApply BSI Standard 200-3 consistently
Paper complianceRequirements marked as met without evidenceVerify implementation through internal audits
Typical problems in IT-Grundschutz projects

A frequent misconception is that IT-Grundschutz replaces risk management. It does not: the catalog assumes typical threats and normal protection needs, and anything beyond that requires an explicit risk analysis. Another mistake is treating the Compendium as static, even though new modules and revised requirements appear with each edition and the BSI has been working on a modernized, more automatable format.

Put simply

BSI IT-Grundschutz is a detailed security handbook from the German government. Instead of asking every organization to invent its own protections from scratch, it says: most offices, servers and networks face the same dangers, so here is a proven list of protections for each of them.

You first describe what you have and how important it is. Then you pick the matching chapters of the handbook and check, item by item, what is already done and what is missing. Only the especially sensitive parts need extra thinking. The result is a documented, checkable level of security that an auditor can confirm.

In practice

A mid-sized German municipal utility that supplies water and electricity must show regulators that its IT is properly protected. Its security officer defines a scope covering the billing system, the customer portal, the office network and two server rooms, and records about 120 target objects in the structure analysis.

The protection needs assessment rates the customer database as high for confidentiality and the control-room network as very high for availability. The team models the domain with Compendium modules for Windows servers, web applications, firewalls and server rooms, and the IT-Grundschutz check reveals about 300 open requirements, mostly in patch management and logging.

For the control-room network, a risk analysis under BSI Standard 200-3 adds network segmentation and redundant links. After roughly eighteen months, the utility passes the audit and receives an ISO 27001 certificate on the basis of IT-Grundschutz, which also simplifies later regulatory reviews.