BSI RUN: Maturity and Implementation Levels in KRITIS Evidence
RUN stands for Reife- und Umsetzungsgradbewertung im Rahmen der Nachweisprüfung, the maturity and implementation level assessment in the audit under Section 39 BSIG (the BSI Act). Since April 2025, auditors have used this scheme to rate seven topic areas of your critical facility on a scale of 1 to 5: your ISMS and your BCMS with maturity levels, and organisational, personnel, physical and technical measures as well as attack detection with implementation levels. You submit the results to the BSI (Federal Office for Information Security) together with the evidence. The BSI's aim is to make the assessment more transparent and consistent and to highlight priorities for further development. According to the BSI, a low level means a greater need for action.
This article explains the structure and logic of the scheme. How the evidence process works overall is described in the article KRITIS audit under Section 39 BSIG.
What RUN is and when it applies
The BSI published the document "Reife- und Umsetzungsgradbewertung im Rahmen der Nachweisprüfung (RUN)" on 2 January 2025. It ties the auditors' assessment to defined criteria. Since then, in addition to the ISMS, BCMS and attack detection, auditors have rated further topic areas made up of mandatory audit topics.
- 7 topic areas rated by the audit team
- 5 levels per topic area, from 1 to 5
- 1.4.2025 audit end date from which RUN must be applied at the latest
- Application: at the latest for audit results with an audit end date after 1 April 2025. You submit the levels determined in a form revised for this purpose together with the evidence.
- Annex: A mapping assigns all measures from the KdA to the maturity and implementation levels. The current version is version 1.0 of 28 May 2025.
- Cycle: Under Section 39 (1) BSIG, the evidence is due every three years. The RUN assessment is part of every evidence submission.
- Scope: The audit team expressly assesses only within the scope of the audit, i.e. with a view to the critical service. How to define the scope properly is shown in the article Scope in the KRITIS evidence.
- An assessment, not a science: The levels are a summary assessment by the audit team. The BSI does not require any more extensive scientific methods.
The seven topic areas
RUN distinguishes two types of assessment: maturity levels for the management systems and implementation levels for the categories of measures.
| Topic area | Assessment | Subtopics (selection) |
|---|---|---|
| Information security management system (ISMS) | Maturity level | Scope, strategy, security organisation, risk management, document management, audit and review, continual improvement |
| Business continuity management system (BCMS) | Maturity level | Scope, maintaining operations, crisis management, data backup and recovery, emergency communication, testing emergency plans |
| Organisational measures (OrgM) | Implementation level | Asset management, service provider and supplier management, change management, vulnerability management |
| Personnel measures (PerM) | Implementation level | Personnel security, roles and competences, identity and access management, awareness and training |
| Physical measures (PhyM) | Implementation level | Physical access, structural measures, maintenance, utilities |
| Technical measures (TecM) | Implementation level | Network security, patch management, cryptography, authentication, remote access, hardening, industry-specific IT and OT, vulnerability scans and penetration tests |
| Detection and response (SzA) | Implementation level | Logging, incident management with reporting and point of contact, attack detection |
According to the BSI, the subtopics serve as context and as an aid to identifying further measures.
Maturity levels for ISMS and BCMS
For the ISMS and BCMS, RUN describes five maturity levels. Each level distinguishes between process, documentation and measures. According to the BSI, this breakdown is not a mandatory requirement but is intended to make the levels easier to understand.
| Maturity level | Name | Process | Documentation | Measures |
|---|---|---|---|---|
| 1 | Planned | No process or only an informal one | None or incomplete | None or isolated; set-up planned and budgeted |
| 2 | Managed | Partly established | Basic, evidence as at a reference date | Partly implemented and documented |
| 3 | Established | Fully established standard process with documented interfaces | Complete, evidence over an appropriate period | Mostly implemented and documented |
| 4 | Measurable | Key figures and thresholds (KPIs) monitor effectiveness | Measurements, KPIs and audit reports over a period | Measures to evaluate the measurements |
| 5 | Continually improved | Improvement is a key objective, with dedicated resources | Including documentation of the improvements | Improvements are identified and implemented |
Two details are decisive in practice:
- Scope from maturity level 2: At maturity level 1, a defined scope is missing or incompletely documented. From maturity level 2, the process must take into account the complete scope of the critical facility. This applies equally to the ISMS and the BCMS.
- Period from maturity level 3: Maturity level 2 can be demonstrated with evidence as at a reference date. Maturity level 3 requires evidence that the process has been implemented and actively used over a period, for example risk analyses, audits and tested emergency plans.
For the BCMS, the audit team checks, among other things, maintaining operations, crisis management, secure emergency communication, the handling of continuity risks and the testing of emergency plans. How to build a BCMS under BSI Standard 200-4 is shown in the article building BCM.
Implementation levels for measures
For OrgM, PerM, PhyM and TecM, RUN describes a general method. Each level presupposes the previous one.
| Implementation level | Meaning |
|---|---|
| 1 | Only the planning of a measure or process exists; nothing has been implemented yet. |
| 2 | Individual measures are implemented that cover only part of a process, for example rules, policies or individual technical measures. |
| 3 | Measures for an entire process or management system are implemented, for example asset management or incident management. |
| 4 | In addition, measures are implemented that check the execution and make it measurable. |
| 5 | In addition, measures are implemented that improve measures, processes and management systems, usually on the basis of the measurement results from level 4. |
For attack detection (SzA), RUN adopts the implementation level model from the Orientierungshilfe zu Systemen zur Angriffserkennung (the BSI guidance on attack detection systems), without the former implementation level 0. The requirements of the Orientierungshilfe are fully integrated and assigned to levels 3 to 5. Details in the article Attack detection systems.
The role of the KdA
The "Konkretisierung der Anforderungen an die gemäß § 8a Absatz 1 und Absatz 1a BSIG umzusetzenden Maßnahmen" (KdA, the BSI's specification of the measures to be implemented under the former Section 8a (1) and (1a) BSIG) describes a minimum level by way of example. The annex to RUN assigns each KdA measure to an implementation level. Some examples (IL = implementation level, ML = maturity level):
| KdA measure (extract) | Topic area | Level |
|---|---|---|
| Company management is informed about risks and measures at least quarterly (no. 14.2) | OrgM | IL 2 |
| Risk analysis is carried out at least annually (no. 14.1) | OrgM | IL 3 |
| Annual internal audit of the compliance of IT processes (no. 86.1) | OrgM | IL 4 |
| Access rights are revoked no later than 30 days after changes in employment (no. 61) | PerM | IL 2 |
| Multi-factor authentication for administrators when accessing via public networks (no. 27) | TecM | IL 2 |
| Automated check for known vulnerabilities at least monthly (no. 84) | SzA | IL 5 |
| Penetration tests of the critical infrastructure components at least annually (no. 95) | SzA | IL 5 |
| Emergency plans are reviewed, updated and tested at least annually (no. 19) | BCMS | ML 4 |
The following rules apply:
- Firm guidance: The level determined via the KdA is firm guidance for the audit team. Only in justified exceptional cases may it consider a level met without all assigned measures being implemented. It must mark this in the form and give reasons.
- Equivalent measures count: You can also reach a level with other measures if they offer a comparable level of protection. Branchenspezifische Sicherheitsstandards (B3S, industry-specific security standards) whose suitability has been confirmed by the BSI can define acceptable alternative measures.
- No KdA requirement: For PerM, PhyM and TecM, no KdA measures are assigned to levels 4 and 5. There, you need your own, more advanced measures, which you present in the audit.
- Management systems: The KdA measures for the ISMS and BCMS serve only as guidance. The maturity level method is decisive.
- Not the sole audit basis: According to the BSI, RUN and the KdA are not exhaustive. You must also identify and address individual risks.
The BSI reserves the right to check how individual maturity and implementation levels were derived on the basis of the documents submitted. The derivations must therefore be documented in a comprehensible way.
How to prepare
- Clarify the scope Without a fully documented scope, the ISMS and BCMS remain at maturity level 1. The scope is also the boundary within which the assessment takes place.
- Self-assessment per topic area Compare your status with the maturity level descriptions and the KdA mapping. This shows you early on where levels are missing.
- Practise and document processes From maturity level 3, evidence over a period counts: records of risk analyses, audits, changes, exercises and management reports. Start long before the audit.
- Make effectiveness measurable For maturity level 4 and implementation level 4, you need key figures and thresholds that are measured and evaluated regularly.
- Justify deviations Where you use equivalent measures instead of KdA measures, document the equivalence.
- Dress rehearsal An internal audit or friendly audit a few months before the audit shows whether the derivation of the levels holds up.
How SDG supports you
- RUN self-assessment: Together with you, we assess all seven topic areas against the maturity level descriptions and the KdA mapping and prioritise the gaps.
- Building an ISMS and BCMS: From documentation to processes that are practised and evidenced, in the ISMS based on ISO 27001 and in the BCMS under BSI Standard 200-4, with an external BC officer on request.
- Key figures and effectiveness: We develop KPIs and thresholds with you that suit your facility.
- Scope and evidence: Delimitation of the facility, documents and the process of the KRITIS audit under Section 39 BSIG.
- Penetration tests for web applications, interfaces (APIs) and cloud environments, insofar as they are within the scope: penetration test
- External information security officer who manages the ISMS and evidence on an ongoing basis: external information security officer
Frequently asked questions about RUN
What is RUN?
The Reife- und Umsetzungsgradbewertung im Rahmen der Nachweisprüfung, the maturity and implementation level assessment in the audit under Section 39 BSIG. With this BSI scheme, auditors rate seven topic areas of a critical facility on a scale of 1 to 5 according to defined criteria.
When does RUN apply?
At the latest for audit results submitted to the BSI with an audit end date after 1 April 2025. The levels determined are submitted together with the evidence in a revised form.
Which seven topic areas does RUN assess?
The ISMS and BCMS with maturity levels, and organisational, personnel, physical and technical measures as well as detection and response (attack detection systems) with implementation levels.
What is the difference between maturity level and implementation level?
Maturity levels rate the ISMS and BCMS management systems according to how established, measurable and improved the process, documentation and measures are. Implementation levels rate the categories of measures according to how completely measures are implemented, checked and improved.
Which maturity level do I have to reach?
RUN itself does not set a minimum value for all topic areas. According to the BSI, however, a low level indicates a greater need for action. For attack detection, the BSI expects at least implementation level 3 under the Orientierungshilfe.
What is the KdA?
The Konkretisierung der Anforderungen, the BSI's specification of the measures to be implemented by operators of critical facilities. It describes a minimum level by way of example. The annex to RUN assigns each KdA measure to an implementation level.
Do I have to implement every KdA measure exactly as described?
No. Equivalent measures with a comparable level of protection also count. You should document the equivalence in a comprehensible way, as the BSI can check how the levels were derived.
Is RUN sufficient as an audit basis?
No. According to the BSI, RUN and the KdA are not exhaustive and are not suitable as the sole audit basis. Individual risks and industry-specific requirements must be considered in addition.
Sources: BSI: Reife- und Umsetzungsgradbewertung im Rahmen der Nachweisprüfung (RUN), version 1.0 of 02.01.2025; 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. RUN and the KdA still cite the former version of the BSIG (Section 8a). The obligations for operators of critical facilities are now set out in Sections 30 and 31 BSIG, and the evidence in Section 39 BSIG.