Attack Detection Systems (SzA): Obligation and Implementation
Under Section 31 (2) BSIG (the BSI Act), operators of critical facilities must use attack detection systems (Systeme zur Angriffserkennung, SzA) for all IT systems, components and processes that are relevant to their critical facility. This does not mean a single product, but the interplay of logging, detection and response, supported by technology and embedded in the organisation. The BSI (Federal Office for Information Security) sets out the requirements in its Orientierungshilfe zum Einsatz von Systemen zur Angriffserkennung (guidance on the use of attack detection systems) and expects at least implementation level 3 in the evidence. Without audit results on attack detection, KRITIS evidence is not complete.
This article explains the obligation, the requirements and the assessment. How the evidence process works overall is described in the article KRITIS audit under Section 39 BSIG.
What attack detection systems are
Section 2 no. 41 BSIG defines attack detection systems as processes for detecting attacks on IT systems that are supported by technical tools and organisational integration. Detection is carried out by comparing the data processed with information and technical patterns that indicate attacks.
It follows that a purchased SIEM or intrusion detection system alone does not fulfil the obligation. What matters is that events are recorded, evaluated and assessed, and that someone responds in an emergency.
Who must use attack detection systems
| Question | Answer |
|---|---|
| Who? | Operators of critical facilities (Section 31 (2) BSIG) |
| For what? | For the IT systems, components and processes that are relevant to the functioning of the critical facility; according to the Orientierungshilfe, this expressly includes OT, i.e. control and automation technology |
| Since when? | The obligation has existed since 1 May 2023, at that time under Section 8a (1a) of the former BSIG, and was carried over into the new BSIG. |
| What exactly? | Continuously and automatically record and evaluate parameters and characteristics from ongoing operations; continuously identify and avoid threats; provide remedial measures for disruptions that have occurred; comply with the state of the art |
| Limit? | The effort should not be disproportionate to the consequences of a failure of the critical facility. |
Special rules from the Energiewirtschaftsgesetz (EnWG, the German Energy Industry Act) apply to energy facilities and energy supply networks. According to the BSI FAQ, evidence there has had to be provided to the Bundesnetzagentur (Federal Network Agency) since the NIS2 Implementation Act.
Non-KRITIS companies: Important and particularly important entities under NIS2 are not subject to an express obligation to use attack detection systems. However, Section 30 BSIG requires the handling of security incidents, and that presupposes that you notice attacks in the first place. The Orientierungshilfe is therefore a good benchmark for them too. More on this in the NIS2 checklist.
The three areas: logging, detection, response
The Orientierungshilfe divides the requirements into three areas. As a minimum, it names the basic requirements of the IT-Grundschutz modules OPS.1.1.5 Logging, DER.1 Detection of security-relevant events and DER.2.1 Handling of security incidents.
Logging
- Document the planning: The planning documents must cover all network areas, data sources and data flows.
- Record relevant events: on systems, in the network and in OT, stored centrally and protected against manipulation.
- Make coverage visible: The network structure plan for the scope must show which network segments and components are monitored and which are not.
Detection
- Network-based detection: Network-based intrusion detection systems (NIDS) must be provided at the transitions defined in the network plan, in particular between internal and external networks.
- Continuous evaluation: Events are evaluated on an ongoing basis, and anomalies trigger an automatic alert.
- Personnel: Staff must be designated for the evaluation. This can be your own staff or a service provider.
- Methodology: The BSI recommends aligning detection rules with MITRE ATT&CK or ATT&CK for ICS.
Response
- Automatic response, provided it does not endanger the critical service; if you rule it out, give your reasons.
- Incident handling: Detected attacks are assessed, contained and eliminated.
- Check reporting obligations: Every detected incident is checked to see whether it must be reported. How reporting works is shown in the article NIS2 reporting obligations.
- Interface with emergency management: An attack can quickly turn into an emergency. See building BCM.
Implementation levels: how the BSI assesses
The Orientierungshilfe rates attack detection using an implementation level model from 0 to 5. The requirements are graded as MUST (MUSS), SHOULD (SOLLTE) and MAY (KANN):
| Implementation level | Meaning |
|---|---|
| 0 to 2 | MUST requirements not yet fully met |
| 3 | All MUST requirements met |
| 4 | SHOULD requirements met as well |
| 5 | MAY requirements met as well |
The minimum target is implementation level 3. If you remain below it, you must give reasons, and the gaps appear as deficiencies in the evidence. Since April 2025, auditors have also rated attack detection according to the BSI's RUN scheme (Reife- und Umsetzungsgradbewertung, the maturity and implementation level assessment), which applies to audits ending after 1 April 2025. There, attack detection is one of seven topic areas; implementation level 0 does not exist in the RUN scheme.
Details on the RUN scheme in the article RUN: maturity and implementation levels.
Attack detection systems in KRITIS evidence
- Cycle: Operators of critical facilities demonstrate implementation every three years under Section 39 (1) BSIG. Attack detection under Section 31 (2) BSIG is expressly part of this. Older sources still mention two years; that was the rule under the former law.
- Completeness: According to the BSI, the evidence is not complete without audit results on attack detection, including the deficiencies found.
- No self-assessment: The audit must be carried out by an independent auditing body.
- Responsibility: If you use an operations manager or service provider, the obligation to provide evidence still remains with the operator, according to the BSI FAQ.
- Scope and network structure plan: Only what is within the scope is audited. Network areas that are not monitored must be marked in the network structure plan.
How to document the scope is shown in the article Scope in the KRITIS evidence.
How to build the network structure plan is shown in the article Network structure plan.
Old and new section numbers
The Orientierungshilfe, the RUN scheme and the BSI FAQ still use the section numbers of the former version of the BSIG. Since the NIS2 Implementation Act, a new numbering applies:
| Content | BSIG former version | BSIG new version |
|---|---|---|
| Definition of attack detection systems | Section 2 (9b) | Section 2 no. 41 |
| Obligation to use attack detection systems | Section 8a (1a) | Section 31 (2) |
| Evidence to the BSI | Section 8a (3) | Section 39 (1) |
How SDG supports you
- Gap analysis against the Orientierungshilfe: where do you stand on logging, detection and response, and which implementation level is realistic?
- Concept and planning documentation: network areas, data sources, data flows and sensor placement, coordinated with your IT
- Requirements for service providers: specification of services and management when an external service provider takes over the evaluation
- Incident handling and reporting process: procedures, roles and interface with emergency management
- Preparation for the evidence: scope, network structure plan and documents, so that the audit runs without surprises. More in the article KRITIS audit under Section 39 BSIG
- External information security officer who manages attack detection on an ongoing basis: external information security officer
Frequently asked questions about attack detection systems
What are attack detection systems?
Under Section 2 no. 41 BSIG, processes for detecting attacks on IT systems that are supported by technical tools and organisational integration. Detection is carried out by comparing the data processed with patterns that indicate attacks.
Who must use attack detection systems?
Operators of critical facilities under Section 31 (2) BSIG, for all IT systems, components and processes that are relevant to the functioning of the critical facility. There is no express obligation for important and particularly important entities under NIS2.
Since when has the obligation applied?
Since 1 May 2023, at that time under Section 8a (1a) of the former BSIG. The new BSIG carried the obligation over into Section 31 (2).
Is a SIEM or an intrusion detection system sufficient?
No. The obligation covers logging, detection and response, including organisational integration, i.e. designated staff, evaluation and incident handling. A tool alone does not fulfil it.
Which implementation level is expected?
At least implementation level 3, i.e. all MUST requirements of the Orientierungshilfe met. Falling below this must be justified, and the gaps appear as deficiencies in the evidence.
Does the obligation also apply to OT?
Yes. According to the Orientierungshilfe, in addition to conventional IT, control and automation technology, data centres and embedded systems must also be covered, insofar as they are relevant to the critical facility.
May a service provider operate attack detection?
Yes. Evaluation and alerting may be handled by your own staff or by a service provider. Responsibility and the obligation to provide evidence remain with the operator.
How often must attack detection be demonstrated?
Every three years with the KRITIS evidence under Section 39 (1) BSIG. Without audit results on attack detection, the evidence is not complete.
Sources: Section 2 BSIG, Section 31 BSIG, Section 39 BSIG, BSI: FAQ on attack detection systems
Note: This article provides general information and does not replace legal advice in individual cases. According to the BSI itself, its Orientierungshilfe is not a binding requirement, but it serves as the benchmark in the audit under Section 39 BSIG.