A B3S describes how the state of the art can be implemented in your industry. It does not do the work for you, but it shortens it: instead of justifying a benchmark of your own, you implement a standard whose suitability the BSI has already confirmed. You provide the evidence every three years.
As of: 23 September 2026
| Deficiency | Topic area | Rating | Plan |
|---|---|---|---|
| Network separation between office and control systems incomplete | Technology | in place | |
| Recovery times not tested | Emergency | in place | |
| Log data without defined analysis | Operations | in progress | |
| Service provider contracts without security requirements | Organization | open |
According to the German Federal Office for Information Security (BSI), an industry-specific security standard, B3S for short, specifies how the state of the art requirements can be met. Operators of critical facilities or their industry associations develop it and can submit it to the BSI for a determination of suitability. There is no legal obligation to develop a B3S, and implementing an existing B3S is also not mandatory for operators.
The advantage lies elsewhere: anyone who applies a B3S with determined suitability has legal certainty regarding the state of the art in audits. In addition, they do not have to justify the benchmark themselves.
There is no nationwide deadline. The cycle depends on your last evidence submission. That is why it pays not to rebuild the path to it from scratch every time.
The operator is responsible for full coverage of the scope. The auditing body verifies completeness once more.
A B3S can serve as the audit basis. If it is kept abstract, it may be necessary to specify it in more detail using concrete measures.
The requirements are applied to your facilities, processes and systems, and every measure is assigned an owner and a deadline.
The audit is performed by a certification body accredited by Germany's national accreditation body (Deutsche Akkreditierungsstelle) or by a European body with equivalent accreditation.
The evidence documents are submitted with their annexes, including the list of security deficiencies together with the implementation plan for remediation.
According to the BSI, a regularly recurring deadline of three years applies to the next evidence submission. The determination of suitability of a B3S is separate from this: according to a BSI notice, from 2024 onward it is regularly granted for three years. The BSI maintains its own overview of which B3S currently have determined suitability and how long it is valid.
For operators of critical facilities who have to provide the evidence and do not want to justify a benchmark of their own.
The BSI maintains an overview of the B3S with determined suitability. It covers the sectors energy, water, food, information technology and telecommunications, health, finance, transport and traffic, and municipal waste disposal.
Every determination of suitability is time-limited, and the periods end at different times. A list on this page would therefore quickly be out of date. The BSI overview is authoritative.
According to the BSI, a B3S that is valid at the start of the audit can continue to be used to create the audit basis. For ongoing operations, what remains decisive is that the requirements correspond to the state of the art.
Eight points along the evidence procedure. The B3S sets the benchmark, you are responsible for implementation and evidence.
| Requirement | Stage | What matters | How you map it in CRISAM® |
|---|---|---|---|
| Define the scope | Scope | The scope must be fully described and shown graphically. Responsibility for this lies with the operator | Company structures are modeled flexibly. Facilities, processes and systems are captured as objects in the same model as risks and measures. |
| Define the audit basis | Audit basis | The audit must be based on the audit basis. A B3S can take on this role if it is specific enough | Industry-specific security standards can be mapped in a structured way and linked to existing ISMS elements. |
| Specify the requirements | Audit basis | Where the standard remains abstract, it may be necessary to specify it in more detail using concrete measures | Every requirement can be linked to the measures that fulfill it. What it means specifically for your company is documented directly on the object and not in a separate file. |
| Treat risks systematically | Implementation | Without a procedure that identifies, assesses, treats and tracks risks, you can only show the result at the audit, not how you got there | Security risks are systematically identified, assessed and treated, as part of the information security management system and not alongside it. |
| Manage measures | Implementation | Every measure needs an owner and a deadline, otherwise it remains a mere declaration of intent at the audit | Measures to increase cyber and operational resilience are planned, implemented and monitored with workflow support, including responsibilities and deadlines. |
| Document incidents | Operations | Security-relevant incidents, the resulting measures and the responsibilities must be verifiable | CRISAM® supports the structured documentation of security-relevant incidents, measures and responsibilities to fulfill reporting and evidence obligations toward authorities and auditors. |
| Track deficiencies with a plan | Evidence | The evidence includes the list of security deficiencies, including the implementation plan for remediation | Open items are tracked as measures on the same object as the affected requirement, with status, deadline and owner. |
| Hand documents over to auditors | Evidence | What counts is which documents the auditing body receives, not what is stored in the system | Audit and compliance reports for internal and external audits as well as export functions for authorities, auditors and stakeholders are available. |
From the scope to the documents the auditing body receives.
It starts with the question of what belongs to the scope. Facilities, processes and systems are modeled as objects so that every requirement can later be assigned to a specific object.
| Facility | Type | Location | Systems | Capture |
|---|---|---|---|---|
| North facility | Generation | Plant 1 | 41 | |
| East facility | Distribution | Plant 2 | 33 | |
| Control center | Control | Headquarters | 28 | |
| South facility | Generation | Plant 3 | 24 |
The industry standard is adopted as a requirements catalog and linked to existing ISMS elements. You do not have to describe again what is already fulfilled.
Requirements of the industry standard can be linked to existing ISMS elements. Duplicate documentation arises where this connection is missing.
Abstract is not always enoughWhere the standard remains general, the concrete measure belongs next to it. Otherwise the audit basis will not hold up at the audit.
One source, several obligationsThe same measure can fulfill a requirement of the industry standard and one from the law. It is maintained once.
The gap analysis shows not only what is missing, but where it is missing. The result is a concrete work list instead of a mere percentage.
| Requirement | Topic area | Status | Evidence | Reviewed |
|---|---|---|---|---|
| Network separation between zones | Technology | missing | 4 Sep 2026 | |
| Recovery tested | Emergency | missing | 4 Sep 2026 | |
| Logging and analysis | Operations | partial | 21 Aug 2026 | |
| Requirements for service providers | Organization | in progress | 21 Aug 2026 | |
| Review access rights periodically | Organization | in place | 12 Jun 2026 | |
| Patch and change procedures | Operations | in place | 12 Jun 2026 |
Every gap results in a measure with an owner and a deadline. This produces the implementation plan that the auditing body will want to see later.
Incidents are part of the evidence too. What was reported, which measures followed and who was responsible must be documented just like the list of measures.
| Incident | Affected | Rating | Report | Outcome |
|---|---|---|---|---|
| Failure of a control component | North facility | submitted | Measure open | |
| Unauthorized access attempt | Control center | submitted | Measure in progress | |
| Malware on a client | Plant 2 | submitted | completed | |
| Failure of a network link | Plant 3 | not required | completed | |
| Misconfigured firewall rule | Headquarters | not required | Analysis open |
| Item | Impact | Owner |
|---|---|---|
| Two incidents without completed analysis | Learning loop missing from the evidence | Information security |
| Service provider remote access not fully recorded | Scope incomplete | IT operations |
At the end, you hand the auditing body the compliance level per topic area, the list of deficiencies with implementation plan and the associated documents.
| Document | Content | As of | Owner | Status |
|---|---|---|---|---|
| Description of the scope | 4 facilities, 38 processes, 126 systems | 4 Sep 2026 | Information security | |
| Audit basis | Industry standard, specified | 4 Sep 2026 | Information security | |
| List of security deficiencies | 29 open items | 4 Sep 2026 | Information security | |
| Implementation plan | Measures with deadline and owner | ongoing | Business units | |
| Incident documentation | 11 incidents with rating and outcome | ongoing | Information security | |
| Evidence documents | Forms and annexes for submission | in preparation | Information security |
Decision on scope, resources and how to handle open deficiencies.
Audit basis, gap analysis, list of deficiencies, evidence documents.
Implementation of technical measures, incidents, system documentation.
Audit based on the audit basis, check of the scope.
The industry standard, the law and your own certification largely ask for the same content. In CRISAM® you capture it only once.
KRITIS-relevant requirements and industry-specific security standards can be mapped in a structured way and linked to existing ISMS elements.
The requirements from NIS2 are not treated in isolation, but integrated directly into existing ISMS, risk and control structures.
Anyone operating a management system in line with ISO 27001 already has a large part of the structure in place. The industry standard supplements this structure, it does not replace it.
Recovery and emergency operations are topic areas of the evidence and at the same time the subject of business continuity management. The same plans cover both.
All three describe how information security is organized, but they answer different questions. The B3S describes what counts as the state of the art in your industry. ISO 27001 defines how a management system is structured. IT-Grundschutz provides the building blocks in between. What counts for the evidence is which audit basis you choose and whether it is specific enough.
| Criterion | B3S | ISO/IEC 27001 | BSI IT-Grundschutz |
|---|---|---|---|
| Who develops it | Operators of critical facilities or their industry associations | International Organization for Standardization | German Federal Office for Information Security (BSI) |
| Reach | One industry | Any organization | Any organization, with a focus on German public authorities |
| What it answers | How the state of the art can be met in this industry | How an information security management system is set up and operated | Which building blocks and requirements apply to typical target objects |
| Binding nature | Voluntary. There is no obligation to develop or apply a B3S | Voluntary, but often required in contracts and tenders | Voluntary, made binding in parts of the public administration |
| Role in the evidence | Can be the audit basis if it is specific enough | Provides the structure, but does not replace the audit basis | Provides requirements that can feed into the audit basis |
| What you end up with | Evidence provided to the BSI, every three years | A certificate from an accredited body | An attestation or certificate following the BSI approach |
| Mapping in CRISAM® | As a requirements catalog, linked to existing ISMS elements | As a management system with risks, controls and measures | As building blocks with requirements, applied to the same objects |
What matters is not which standard is better, but whether the chosen audit basis is specific enough. According to the BSI, it may be necessary to specify an abstract audit basis in more detail using concrete measures. This effort pays off because you can build on it for the next evidence submission. You can find an overview of all frameworks under Standards and frameworks.
The first step depends on where you stand today.
Then you start with the mapping. The requirements are managed as a catalog and linked to existing ISMS elements instead of being maintained in a separate spreadsheet.
Then linking is the next step. Some of the requirements are already fulfilled through existing controls and measures. This only becomes visible through the assignment.
Then the focus is on the implementation plan. Every deficiency is tracked as a measure on the affected requirement, with owner, deadline and status.
For this you need the CRISAM® GRC Platform and the CRISAM® ISMS Module. In the demo, we discuss your starting point and show what you already have in place.
According to the German Federal Office for Information Security (BSI), an industry-specific security standard, B3S for short, specifies how the state of the art requirements can be met. Operators of critical facilities or their industry associations develop it and can submit it to the BSI for a determination of suitability. There is no legal obligation to develop a B3S, and implementing an existing B3S is also not mandatory for operators.
Because it already sets the benchmark. According to the BSI, operators who apply a B3S with determined suitability have legal certainty regarding the state of the art in audits. Anyone who chooses their own route instead has to justify at the audit why this route corresponds to the state of the art.
All three describe how information security is organized, but they answer different questions. The B3S describes what counts as the state of the art in your industry. ISO 27001 defines how a management system is structured. IT-Grundschutz provides the building blocks in between. What counts for the evidence is which audit basis you choose and whether it is specific enough.
According to the BSI, after the evidence has been provided for the first time, a regularly recurring deadline of three years applies until the next evidence submission in each case. The legal basis is § 39 (1) BSIG, formerly § 8a (3) BSIG. There is no nationwide deadline, the cycle depends on your own last evidence submission.
According to the BSI, suitable bodies are certification bodies accredited by Germany's national accreditation body (Deutsche Akkreditierungsstelle) as well as European bodies with equivalent accreditation. The evidence must meet the framework conditions required by the BSI, which are set out in the document Grundsätzliche Anforderungen im Nachweisverfahren (General Requirements in the Evidence Procedure).
According to the BSI guidance document, it includes the evidence document for the critical infrastructure and the evidence document for the audit, plus annexes: the description and graphical representation of the scope, the description of the audit basis and the list of security deficiencies including the implementation plan for remedying the deficiencies.
Yes. According to the BSI, the audit basis is central: the audits must be based on it, and a B3S can take on this role. If the level of detail is abstract, it may be necessary to specify the audit basis in more detail using concrete measures in order to provide the evidence.
What matters is whether requirement, measure, incident and evidence are linked in one shared model. In CRISAM®, KRITIS-relevant requirements and industry-specific security standards can be mapped in a structured way and linked to existing ISMS elements. Measures are planned, implemented and monitored with workflow support, including responsibilities and deadlines. For the handover, audit and compliance reports as well as export functions for authorities, auditors and stakeholders are available.
The information on B3S and the evidence procedure on this page comes from the following publications of the German Federal Office for Information Security (BSI).
The information reflects the status of the sources named as of the review date stated above.
In the demo, we walk through your case: scope, mapping of the industry standard, gap analysis, measures with deadlines and the documents for the auditing body.
You are currently viewing a placeholder content from Facebook. To access the actual content, click the button below. Please note that doing so will share data with third-party providers.
More InformationYou need to load content from reCAPTCHA to submit the form. Please note that doing so will share data with third-party providers.
More InformationYou are currently viewing a placeholder content from Hubspot Embedded Content. To access the actual content, click the button below. Please note that doing so will share data with third-party providers.
More InformationYou are currently viewing a placeholder content from HubSpot. To access the actual content, click the button below. Please note that doing so will share data with third-party providers.
More InformationYou are currently viewing a placeholder content from Hubspot Meetings. To access the actual content, click the button below. Please note that doing so will share data with third-party providers.
More InformationYou are currently viewing a placeholder content from Instagram. To access the actual content, click the button below. Please note that doing so will share data with third-party providers.
More InformationYou are currently viewing a placeholder content from X. To access the actual content, click the button below. Please note that doing so will share data with third-party providers.
More Information