KRITIS Scope: Requirements and Documentation
The scope defines where your critical facility begins and ends: which processes, IT and OT systems, interfaces and service providers belong to the facility, and which parts of your company are clearly delimited and left out. The BSI (Federal Office for Information Security) calls the scope documentation one of the most important documents for KRITIS evidence. It is one of the first documents to be audited, and only what it contains is audited. Eleven requirements (G01 to G13) apply to the documentation, and a further eleven to the associated network structure plan.
This article explains how to build the scope and which mistakes the BSI sees again and again. How the audit works overall is described in the article KRITIS audit under Section 39 BSIG.
What the scope defines
With the scope, the operator defines in binding form which part of its operations and its information technology belongs to the critical facility. The documentation describes the boundaries of the facility, its function and processes, the IT required for them and its separation from the rest of the IT, as well as external parties and interfaces. The BSI documents still refer to the KRITIS facility and the critical service (kritische Dienstleistung, kDL).
According to the BSI, the documentation has three audiences:
Operator
You define the boundaries of the facility and its IT and thereby make clear which measures must apply where, long before the audit.
Auditing body
The auditors use the scope as the basis for the audit and for selecting the components to be audited. It must describe the facility correctly, completely and in a way that third parties can follow.
BSI
For the BSI, the scope summarises the facility for which the evidence is submitted. It must show that the requirements are met for all relevant IT.
The evidence itself must be provided every three years under Section 39 (1) BSIG (the BSI Act). You should therefore not create the scope once only, but update it whenever there are changes to the facility, the network or service providers.
Structure in six sections
The BSI's Hilfestellung (guidance document) divides the documentation into six sections and illustrates them with the example of a fictitious tank farm. The structure is a guide, not an obligation. Operators should adapt the breakdown and level of abstraction to their own facility.
- Context Briefly summarise the operator's business and classify the facility: sector, industry, critical service, facility category. Describe the facility itself with its sites, surroundings and individual parts, ideally in a separate subsection on the facility description. (G01, G02, G06)
- Processes List the main processes that support the operation of the facility, plus the supporting processes that are essential for the critical service. Describe multiple sites, including cross-site processes. At the end, delimit what does not belong. (G04, G07)
- Information technology Record all IT and OT systems, components and, where necessary, applications on which the facility relies to a significant extent, and assign them to the processes. (G05, G11)
- Interfaces Describe access across the boundary of the scope, for example remote maintenance by service providers, remote working by your own staff and dependencies on processes and IT outside the scope, for example on head office. (G08)
- External parties List all parts of the facility, processes and IT systems that are provided or operated by service providers, IT providers, cloud providers or manufacturers. (G10)
- Network structure plan Show the scope with IT systems and connections graphically, usually as a separate document, with written additions where they are needed for understanding. (G12, G13)
Requirements G01 to G13
The requirements come from the BSI's Orientierungshilfe zu Nachweisen (guidance on evidence). G03 and G09 have been dropped, leaving eleven.
| No. | Requirement | Section |
|---|---|---|
| G01 | The facility is described in a recognisable and comprehensible way. | Context |
| G02 | The parts of the critical service provided by the operator are described in a recognisable and comprehensible way. | Context |
| G04 | All processes relevant to the critical service are recorded. | Processes |
| G05 | All relevant systems, components and, where applicable, applications are recorded. | Information technology |
| G06 | All parts of the critical facility are apparent from the scope submitted. | Context |
| G07 | The boundaries of the scope are clearly recognisable. | Processes |
| G08 | The interfaces to processes, systems, components and applications outside the scope are described in a recognisable and comprehensible way. | Interfaces |
| G10 | Parts of the facility operated by third parties are described in a recognisable and comprehensible way. | External parties |
| G11 | Processes can be assigned to the associated systems, components and applications. | Information technology |
| G12 | The scope is shown in a network structure plan. | Network structure plan |
| G13 | Written additions to the network structure plan that are necessary for understanding are available. | Network structure plan |
Attach a table to your documentation that assigns each requirement to the relevant section of your document. This way you check completeness yourself while writing.
Drawing the boundaries correctly
- Delimitation only with IT separation: Administration, head office or other facilities on the same site may be left out if they are not needed for the critical service and can be clearly delimited. According to the BSI, this requires in particular separation or segmentation at IT level. Without it, these parts of the business belong in the scope even though they have no function for the facility.
- IT and OT: All IT and OT systems on which the facility relies to a significant extent are recorded, including control, measurement and automation technology.
- Record the selection criteria: The BSI recommends setting out in writing the criteria by which systems are included in the scope, for example through a criticality assessment in business continuity management or in IT service continuity management. In the BSI example, the assignment to processes serves as the criterion.
- Sites: If the facility is spread across several sites, describe site-specific and cross-site processes and their IT connections.
- Service providers stay in: Outsourced operations do not move the boundary. Whatever a third party operates for the facility belongs in the scope as an external party.
An ISO 27001 certificate helps, but it does not replace a properly defined KRITIS scope. The company defines the scope of an ISMS itself. You should therefore check whether it fully covers the critical facility. More on the scope of an ISMS in the article Implementing an ISMS.
The network structure plan as a mandatory component
The scope includes a network structure plan (G12). It shows the facility with its IT systems, network areas and connections graphically and takes up the content of the information technology section. According to the BSI, it does not have to be a complete network diagram but should show the facility in an appropriately abstracted and understandable way. IP addresses, host names and ports do not belong in it.
Separate requirements (N01 to N12) apply to the network structure plan. They include that it must be clear which network segments and components are monitored by attack detection systems and which are not.
All requirements and a step-by-step structure in the article Network structure plan.
Typical mistakes
From the audits of recent years, the BSI identifies these weaknesses in particular:
- Wrong level of abstraction: so detailed that nobody keeps an overview, or so rough that boundaries and systems cannot be recognised. According to the BSI, the right level of abstraction is indispensable for an effective audit.
- Gaps in interfaces and outsourcing: remote maintenance access, connections to head office or systems operated by service providers are missing or only superficially described.
- Inconsistent presentation: systems are grouped or named differently in the text than in the network structure plan. Groupings must be consistent across all documents.
- Delimitation without separation: administration is excluded even though it is on the same network as the facility.
- Not comprehensible to third parties: internal abbreviations and names without explanation. The BSI recommends writing the documentation so that an independent third party can understand the facility, its supply function, its IT and its boundaries.
According to the BSI, consistent and complete documentation reduces queries about the documents submitted to a minimum.
How SDG supports you
For us, defining the scope properly is the most important first step in any security project. Whatever is missing here will catch up with you later in the audit.
- Delimitation workshop: Together with you, we work out the facility, critical service, processes and boundaries and clarify which parts of the business can be left out.
- Preparing or reviewing the documentation: context, processes, information technology, interfaces and external parties, checked against G01 to G13, including the assignment table.
- Network structure plan: coordination with your IT, the appropriate level of abstraction and marking of monitoring by attack detection systems.
- Assessing segmentation: is the IT separation sufficient to delimit administration and other parts of the business?
- Preparation for the evidence: scope, documents and the process of the KRITIS audit under Section 39 BSIG.
- External information security officer who updates the scope whenever there are changes: external information security officer
Frequently asked questions about the scope in the KRITIS evidence
What is the scope in the KRITIS evidence?
The binding definition of which processes, IT and OT systems, interfaces and service providers belong to the critical facility. The documentation describes these boundaries and is the basis for the audit under Section 39 BSIG.
What requirements does the BSI set for the scope?
Eleven requirements for the documentation (G01 to G13; G03 and G09 have been dropped) and eleven for the network structure plan. They are set out in the BSI's Orientierungshilfe zu Nachweisen.
May I exclude administration from the scope?
Yes, if it is not needed for the critical service and can be clearly delimited. According to the BSI, this requires in particular separation or segmentation at IT level. Without this separation, it belongs in the scope.
Do outsourced systems belong to the scope?
Yes. Parts of the facility, processes and IT systems operated by service providers, IT providers, cloud providers or manufacturers must be described in a recognisable and comprehensible way (G10) and must appear in the network structure plan.
Does OT also belong in the scope?
Yes. All IT and OT systems, components and, where necessary, applications on which the critical facility relies to a significant extent are recorded, including control, measurement and automation technology.
Does the network structure plan have to include IP addresses?
No. According to the BSI, it should show the facility in an appropriately abstracted way. Detailed internal information such as IP addresses, host names or ports does not belong in it.
Is the scope of our ISO 27001 certificate sufficient?
Not automatically. The company defines the scope of an ISMS itself. For KRITIS evidence, the scope must fully cover the critical facility. You should therefore check whether the two match.
How often must the scope be updated?
The evidence is due every three years under Section 39 (1) BSIG. However, you should update the scope whenever there are changes to the facility, the network 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; 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).