KRITIS Network Structure Plan: Requirements N01 to N12
The network structure plan (Netzstrukturplan) is the graphical representation of your scope in the KRITIS evidence. At a glance, it shows which IT and OT systems belong to the critical facility, how they are networked, where networks are separated, which external connections exist and which areas are monitored by attack detection systems. The BSI (Federal Office for Information Security) requires it as part of the scope documentation (requirement G12) and sets eleven separate requirements for it (N01 to N12). What is needed is not a complete network diagram, but an appropriately abstracted overview that third parties can understand.
How to document the scope as a whole is shown in the article Scope in the KRITIS evidence. This article looks at the network structure plan in more depth.
What the network structure plan is
According to the BSI, the scope documentation includes a network structure plan that summarises the basic relationships in the critical facility with regard to the IT network. It is usually a separate document and mainly takes up the content of the information technology section of the written description.
- For whom: for the auditing body, which uses it to understand the boundaries and components of the facility, and for the BSI, which assesses the evidence. For you, it is the shared view of the facility.
- How it is structured: According to the BSI, a breakdown by rooms or sites has proved its worth in many cases. Other representations are permitted if they aid clarity and comprehensibility.
- How detailed: appropriately abstracted. The BSI names the right level of abstraction as the most important success factor for the entire scope documentation.
- How often: Under Section 39 (1) BSIG (the BSI Act), the evidence is due every three years. However, the plan should be updated whenever there are changes to the network, systems or service providers.
What belongs in it and what does not
Belongs in it
- The scope, separately delimited and highlighted
- The relevant IT and OT systems, grouped where appropriate
- Network and functional areas and the points at which networks are separated
- All external communication interfaces, for example the internet, VPN to head office
- Permanently enabled maintenance access
- Sites and their IT connections to each other
- Outsourced services
- Connection and coverage of the attack detection systems
- A legend for symbols, colours and lines
Does not belong in it
- IP addresses
- Host names
- Ports
- Comparable confidential details
- A complete, extensive network diagram showing every device
- Areas outside the scope, unless they are relevant as an interface or connection
Requirements N01 to N12
The requirements come from the BSI's Orientierungshilfe zu Nachweisen (guidance on evidence). N04 has been dropped, leaving eleven. In addition, there are G12 (the scope is shown in a network structure plan) and G13 (written additions necessary for understanding are available).
| No. | Requirement | What this means in practice |
|---|---|---|
| N01 | The network structure plan provides an overview of the scope. | Delimit the scope with colour or graphics |
| N02 | All relevant systems, components and, where applicable, applications are shown. | The same systems as in the information technology section, grouped the same way |
| N03 | An appropriate level of abstraction has been chosen. | Overview instead of device detail |
| N05 | All external communication interfaces are shown. | Internet, VPN, connections to head office and partners |
| N06 | Maintenance interfaces are shown if they are permanently enabled. | Remote maintenance access for manufacturers and service providers |
| N07 | The network structure plan reflects any existing division into sites. | Separate sites recognisably from each other |
| N08 | The IT connections between different sites are shown. | Draw in the site connections |
| N09 | Outsourced services are shown. | Mark externally operated systems and services |
| N10 | Functional names and legends are provided where necessary and are understandable. | Legend for symbols, colours and lines |
| N11 | The network structure plan shows at which points networks have been separated or segregated. | Make firewalls, zones and segments visible |
| N12 | It is apparent which network segments and KRITIS-relevant IT components are monitored by attack detection systems; areas that are not monitored are marked. | Draw in attack detection coverage |
How to build the network structure plan
The BSI's Hilfestellung (guidance document) shows the structure using the example of a fictitious tank farm. A practical approach can be derived from it:
- Clarify the basis The starting point is the written description of the scope with processes, system list and interfaces. The plan shows nothing that is missing there and leaves out nothing that is included there.
- Choose a structure Organise by rooms, sites or functional areas. In the BSI example, these are functional blocks such as office IT, visualisation, remote metering and facility control.
- Delimit the scope Highlight the scope visibly; in the BSI example, it has a grey background. Still draw in connections to areas outside, for example to head office.
- Draw in the systems Show the relevant systems with pictograms. Group similar systems, but in exactly the same way as in the rest of the documentation.
- Show connections and separations Represent networks, network connections and types of communication with lines and colours, and make firewalls and segment boundaries recognisable.
- Add external interfaces Draw in the internet, VPN, permanently enabled remote maintenance, site connections and outsourced services.
- Enter attack detection Draw in the connection of the attack detection systems and mark areas that are not monitored.
- Legend and additions Create a legend for all symbols, colours and lines. For complex facilities, explain the functional names in the written description (G13).
Making attack detection coverage visible
Since operators of critical facilities have been required to use attack detection systems (Systeme zur Angriffserkennung, SzA), N12 requires the network structure plan to show their coverage: which network segments and KRITIS-relevant components such as servers, routers and firewalls are monitored. Areas that are not monitored must be marked.
In the BSI example, logging, IDS and IPS are arranged centrally, and a separate line type shows their connection to the relevant components. The Orientierungshilfe on attack detection also requires you to use the network plan to determine which network segments are protected by additional detection systems. Network-based intrusion detection systems must be provided at the transitions between internal and external networks. More on this in the article Attack detection systems.
A network structure plan without the attack detection coverage drawn in does not meet N12. Concealing gaps in monitoring does not help: areas that are not monitored must be marked.
Distinction from other network documentation
In the KRITIS context, you will encounter several requirements for network documentation. They serve different purposes and cannot simply be substituted for one another:
| Document | Requirement | Purpose |
|---|---|---|
| Network structure plan | G12 and N01 to N12 of the Orientierungshilfe zu Nachweisen | Abstracted representation of the scope for auditors and the BSI |
| Network topology documentation | KdA no. 40 (KOS-06), in the RUN scheme technical measures, implementation level 2 | Comprehensible, up-to-date network architecture including environments and data flows, to avoid errors in operation and enable timely recovery |
| Logging planning documentation | Orientierungshilfe on attack detection, requirement 101.7 (implementation level 3) | Document all network areas, logging data sources, their relationships and the flow of logging data |
All three should be based on the same inventory and use the same names. How implementation levels are rated in the RUN scheme (the BSI's maturity and implementation level assessment) is shown in the article RUN: maturity and implementation levels.
Typical mistakes
- Too much detail: a complete network diagram with every switch, IP addresses and ports instead of an overview. This contradicts N03 and discloses confidential information.
- Too little detail: individual boxes without recognisable separations, so that N11 cannot be audited.
- Missing external interfaces: forgotten remote maintenance access, mobile routers or connections to service providers.
- Inconsistent grouping: systems are grouped or named differently in the plan than in the system list. According to the BSI, grouping must be consistent across all documents.
- No legend: colours and line types without explanation.
- No attack detection coverage: monitored and unmonitored areas cannot be recognised.
According to the BSI, interfaces and outsourced services in particular require special care. A consistent presentation in the network structure plan makes it comprehensible and reduces queries about the documents submitted.
How SDG supports you
- Inventory with your IT: Together, we record systems, network areas, interfaces and service providers and clarify what belongs to the scope.
- Preparing or reviewing the network structure plan: appropriately abstracted, with a legend, external interfaces and attack detection coverage, checked against N01 to N12.
- Ensuring consistency: We align the network structure plan, the written description of the scope, the network topology and the logging planning.
- Preparation for the evidence: scope, documents and the process of the KRITIS audit under Section 39 BSIG.
- External information security officer who updates the plan whenever there are changes: external information security officer
Frequently asked questions about the network structure plan
What is a network structure plan in the KRITIS evidence?
The graphical representation of the scope of a critical facility with its IT and OT systems, network areas and connections. It is part of the scope documentation and usually a separate document.
Is the network structure plan mandatory?
Yes. Under requirement G12 of the BSI's Orientierungshilfe zu Nachweisen, the scope must be shown in a network structure plan. Requirements N01 to N12 apply to the plan itself.
What requirements does the BSI set for the network structure plan?
Eleven requirements, N01 to N12, with N04 having been dropped. They concern, among other things, the overview, level of abstraction, external and maintenance interfaces, sites, outsourced services, network separation and coverage by attack detection systems.
Do IP addresses belong in the network structure plan?
No. According to the BSI, the plan should show the facility in an appropriately abstracted way. Detailed internal information such as IP addresses, host names, ports or comparable confidential information does not belong in it.
Does remote maintenance have to be drawn in?
Yes, if the maintenance access is permanently enabled (N06). All external communication interfaces must be shown in any case (N05).
How do I show coverage by attack detection systems?
Under N12, it must be clear which network segments and KRITIS-relevant components are monitored. Areas that are not monitored must be marked. In the BSI example, a separate line type shows the connection of central logging and attack detection.
Is the network structure plan the same as the network topology documentation?
No. The network structure plan shows the scope in abstracted form for auditors and the BSI. The network topology documentation under KdA no. 40 (KOS-06) serves secure operation and recovery. However, both should be based on the same inventory.
How often must the network structure plan be updated?
The evidence is due every three years under Section 39 (1) BSIG. You should update the plan whenever there are changes to the network, systems, interfaces or service providers, so that it is up to date for the audit.
Sources: BSI: Zur Dokumentation des Geltungsbereiches bei KRITIS-Betreibern, Hilfestellung und Beispiel (guidance and example on documenting the scope for KRITIS operators), version 2.0 of 15.08.2024; BSI: mapping of the KdA requirements to the implementation levels, annex to RUN, version 1.0 of 28.05.2025; Section 39 BSIG
Note: This article provides general information and does not replace legal advice in individual cases. According to the BSI itself, its Hilfestellung is a guide and not a normative requirement. It still cites the former version of the BSIG (Section 8a).