Section 30 BSIG: Awareness Training and Vulnerability Management

Section 30 BSIG requires training and vulnerability management. What that means in practice - from phishing simulation to prioritized vulnerability scans.

Digitale Hand reicht aus einem Laptop-Bildschirm einer echten Hand die Hand - Sinnbild für Phishing und Social Engineering

Awareness Training and Vulnerability Management: What § 30 BSIG Requires Operationally

§ 30 BSIG is the normative backbone of NIS2 - ten mandatory areas that every affected entity must implement. From the risk register to supply chain security and multi-factor authentication. Most of these ten points remain abstract for management boards and IT leadership: What does "risk analysis" mean in practice? How deep does "supply chain security" have to go?

Two obligations are different. They are operationally immediately tangible, they produce measurable data on a weekly basis, and they form the interface where cybersecurity meets everyday clinical operations: Training and awareness (Point 7) and security in the acquisition, development, and maintenance of network and information systems (Point 5). In practice, this translates into two central disciplines: Awareness Training and Vulnerability Management.

This guide shows what § 30 BSIG operationally demands for these two areas - and what a NIS2-compliant implementation practically means in a clinic, a medical center (MVZ), or a pharmaceutical company. Not as an abstract compliance discussion, but as an actionable playbook.

Three preliminary remarks. First: Awareness training and vulnerability management are not two independent obligations, but two halves of the same task. Humans and machines are the two major attack surfaces - securing only one does not solve the problem. Second: In the event of an audit, both areas are the first to be scrutinized because they yield tangible artifacts (training records, scan reports). Third: NIS2 has raised the standard - a one-off e-learning session or an annual vulnerability scan is no longer sufficient.

Awareness Training - What § 30 BSIG Requires

§ 30 (2) No. 7 BSIG requires "basic training and awareness-raising measures in the field of information technology security." The NIS2 Directive formulates this in Art. 21 (2) lit. g as basic cyber hygiene practices and cybersecurity training.

This sounds broad - and is frequently interpreted too broadly. In practice, BSI auditors, certified public accountants, and cyber insurers ask for concrete evidence:

  • Who was trained, when, with what content, and for what duration?

  • How is the learning effect measured?

  • What adjustments are made when click rates increase?

  • How are new employees onboarded into the system?

  • How is the management board itself trained (obligation pursuant to § 38 BSIG)?

What is not enough. A one-off 30-minute mandatory onboarding video with a checkbox confirmation. That may have been standard in 2018, but by 2026 it is neither regulatorily nor practically sufficient. Yesterday's typical phishing victim does not learn from today's quiz questions - they learn from concrete, realistic simulations that occur in everyday clinical routines.

What is enough. A combination of three components:

  1. Annual core course with consistent content (phishing detection, password hygiene, data privacy, reporting channels) and documented participation.

  2. Regular phishing simulations (typically monthly) that reflect real attack patterns from the healthcare sector - spoofed HIS emails, fake duty roster changes, fraudulent e-prescription notifications.

  3. Microlearning spotlights several times a year on current topics (cloud phishing, MFA bypass, AI-generated emails, sector-specific threats).

This three-part combination practically documents itself: LMS logs for point 1, phishing platform reports for point 2, spotlight completion rates for point 3. Compiled into an audit report - done.

Important: Awareness is not the task of IT, but of human resources development. IT provides the platform, but content, frequency, and tone belong in HR's hands. Otherwise, awareness quickly devolves into technical compliance theater that staff perceive as patronizing.

Awareness Training in Operational Implementation

What does this look like in practice? Four components that together form a NIS2-compliant awareness architecture:

Format: Microlearning instead of frontal lecturing. A 60-minute webinar once a year that nobody listens to is not proof of training - it is a compliance fiction. A proven approach: four short modules of about 5 minutes each, completed directly on the user's device, with a brief knowledge check per module. Staff can integrate this during downtime or breaks - acceptance is significantly higher than with mandatory scheduled sessions.

Frequency: Annual core course plus three spotlights per year. The core course covers the fundamentals (phishing, passwords, data protection, reporting channels). The spotlights complement the program with three short refreshers - one to two minutes, in quarters without a core course, without repeating the previous year. This ensures that the training obligation applies year-round, not just once in January.

Target groups: Differentiated, not one-size-fits-all. Nursing staff, physicians, administration, IT, and executive management have different attack vectors and different learning needs. Nursing staff need examples from ward routines (fake HIS warnings, spoofed duty roster updates). Administration requires CEO fraud scenarios and invoice manipulation. IT needs privileged account risks. Executive management needs whaling examples plus a regulatory overview.

Phishing simulation as an efficacy metric. Training without subsequent measurement is training in the dark. Phishing simulations are the only method that reliably demonstrates whether training content has been internalized. The key metrics:

  • Click rate: Who clicks on simulated phishing links? (Expected progression: 25 to 35% baseline → below 10% after 12 months)

  • Reporting rate: Who actively reports suspicious emails? (Expected progression: below 5% baseline → over 30% after 12 months)

  • Trend by department: Is the click rate dropping in areas that have already received training feedback? (Indicator of structural risk in individual teams - strictly aggregated)

Important to know: In Germany, phishing simulations are subject to co-determination under § 87 (1) No. 6 BetrVG (Works Constitution Act). A clean works agreement with strictly aggregated reporting, defined purposes, and a ban on using data for personnel measures is a mandatory prerequisite before launch.

Documentation for an audit. Tangible artifacts that must be in the ISMS file:

  • List of conducted training sessions including date, content, duration, and participants

  • Individual training certificates/records (participation, module, date)

  • Quarterly evaluations of phishing simulations showing trends

  • Annual evaluation of the awareness program's effectiveness

  • Training records for executive management pursuant to § 38 BSIG (with agenda and attendee list)

Vulnerability Management - What § 30 BSIG Requires

Vulnerability management is not designated as a standalone obligation in § 30 BSIG. It is distributed across two points:

  • Point 5: Security measures in the acquisition, development, and maintenance of information technology systems, including vulnerability handling and disclosure. This includes patch management, vulnerability remediation, and secure configuration.

  • Point 10: Multi-factor authentication and secured voice, video, and text communications. This encompasses MFA hygiene and secured remote access - both tightly intertwined with vulnerability management.

What the standard leaves open: frequency, depth, SLAs. NIS2 deliberately avoids detailed specifications in favor of the "state of the art." That is regulatorily elegant - but operationally confusing, because "state of the art" is not an audit checkbox.

In practice, the following interpretation has become established:

Asset inventory as a mandatory foundation. Vulnerability management without an asset inventory is blind. If you do not know which devices are on the network - servers, workstations, medical devices, IoT, mobile endpoints - you cannot scan for vulnerabilities. A complete asset inventory with categorization (type, OS, patch status, location, owner) is the first mandatory requirement.

Scanning frequency. State of the art is continuous scanning for IT infrastructure, not point-in-time checks. External (internet-facing) systems: daily. Internal systems: weekly. Anyone scanning only once a year fails to meet the state of the art. Medical devices, on the other hand, are not actively scanned - common practice is passive network discovery combined with CVE cross-referencing and SBOM analysis, as active scans on IoMT devices can cause outages in clinical operations.

Authenticated scanning. Not all vulnerabilities are visible from the outside. Authenticated scanning - meaning: with valid login credentials on the target systems - uncovers configuration flaws, outdated libraries, local patch levels, and default credentials. Unauthenticated scanning only sees the exterior surface and consistently underestimates the real risk.

Clinically weighted prioritization. A CVSS score of 9.8 on an office printer's web interface is less critical than a CVSS 7.2 on a PACS server. Generic CVSS ratings must be contextualized clinically - patient proximity, criticality to care, failover options. Otherwise, IT teams will patch spectacular but non-critical gaps first, leaving moderate but care-critical vulnerabilities for last.

Remediation SLAs. State of the art does not dictate "patch everything immediately," but rather "risk-prioritized treatment with SLAs." Common in NIS2-compliant setups: critical vulnerabilities (CVSS ≥ 9, exploitable, exposed) within 7 to 14 days; high vulnerabilities within 30 days; medium within 90 days. If you document an exception to patching, you must document compensating controls - additional network segmentation, intensified monitoring, restricted access.

Vulnerability Management in Operational Implementation

In practical implementation, four critical components emerge:

Continuous asset discovery, not periodic snapshots. Hospital networks change daily. New medical devices are plugged in, maintenance personnel bring in laptops, cloud workloads come and go. A classic Excel inventory is outdated 24 hours after creation. State of the art: agent-based asset tracking combined with network discovery.

Medical devices as a special case (IEC 80001-1). A special rule applies in clinical environments: Patches to medical devices are subject to the MDR and may affect the manufacturer's conformity assessment. An unauthorized security patch applied by clinic IT can technically constitute an alteration of the medical device - carrying legal liability consequences. Solution: Document patch requests to the manufacturer, track response times, and implement compensating measures (network segmentation, monitoring) in the event of patch delays.

Authenticated scanning of critical systems. HIS, PACS, LIS, Active Directory, backup systems - the core infrastructure must be scanned using authentication, not just from the outside. Common findings in clinical setups:

  • Outdated libraries in Java- and Python-based applications (Log4Shell class)

  • Missing patches on workstations because updates only run during maintenance windows

  • Default credentials on medical devices ("admin/admin", "service/service")

  • Insecure management interfaces (Telnet, legacy SMB versions)

  • Inconsistent permissions in Active Directory

Remediation with SLA and escalation. Every critical vulnerability is assigned an owner, an SLA, and an escalation path. If the vendor does not deliver a patch within 14 days, the clinic escalates to compensating controls - additional network segmentation, intensified monitoring, or, if necessary, temporarily taking the affected system out of service.

Documentation for an audit. Concrete artifacts:

  • Asset inventory with patch status and designated owners

  • Weekly scan reports with diffs compared to the previous month

  • Quarterly trend reports categorized by department/clinical area

  • List of open vulnerabilities with risk assessment, SLA, and compensating controls

  • Vendor correspondence regarding medical device patches

  • Annual penetration test or external validation

The distinction between "we scan" and "we manage vulnerabilities" is essential here. Scanning is the easier half. The harder half is tracking from discovery through to remediation - and documenting that while not everything can be fixed, everything has been evaluated.

Awareness Training and Vulnerability Management as a Dual Lever

Why not just one of the two? Because humans and machines represent two structurally different attack surfaces that cannot compensate for one another.

Humans are the initial vector. According to the ENISA Threat Landscape 2025, approximately 60 percent of observed attacks in the EU begin with phishing - via email, telephone, or malicious advertising. Awareness training without vulnerability management means: employees recognize phishing emails, but if an attacker breaches the perimeter nonetheless, they encounter an unpatched system in which they can move laterally at will.

Machines are the amplifier. According to ENISA, exploiting vulnerabilities is the second most common entry vector at 21.3 percent. In its 2025 Situation Report, the BSI counts an average of 119 new vulnerabilities per day - roughly 24 percent more than in the previous year. Vulnerability management without awareness training means: systems are patched, but a single phishing click hands the attacker valid credentials - providing a bypass around any patch management efforts.

Both serve § 32 BSIG incident preparedness. In the event of an incident, BSI auditors ask for both training documentation and vulnerability handling reports. Those who cannot produce awareness documentation during an incident have no shield against fines - and the same applies to those lacking vulnerability management data.

Connection to § 38 BSIG management liability. In the event of a dispute, management liability toward the organization itself is judged not on abstract strategies, but on concrete operational evidence. Awareness training and vulnerability management are the two areas that produce the most evidence - clean reports prove supervisory duties were fulfilled; missing reports demonstrate a breach of duty.

Operational synergy. Awareness training and vulnerability management complement each other in analysis: Aggregated click rates by department combined with open vulnerabilities by department together reveal where the greatest risk lies. The two disciplines complement each other not only regulatorily, but operationally - provided they are designed as a unified system, not as two isolated projects.

What Auditors Will Ask

In a BSI audit or during a public accountant's NIS2 review, awareness training and vulnerability management are the first areas examined - because they produce operationally tangible artifacts. Typical questions:

Awareness Training:

  • Who was trained in the past year? Present a list showing dates and content.

  • How do you measure the effectiveness of your training sessions? Present phishing simulation reports from the past 12 months.

  • How has the management board itself been trained? Present training logs including the agenda and attendee list.

  • How do you respond to departments with persistently high click rates? Show a concept for targeted, voluntary supplementary training - without individual evaluation.

  • How are new employees incorporated into the awareness system? Document the onboarding process.

Vulnerability Management:

  • Is an asset inventory available? Is it complete and up to date?

  • When was the last scan performed? Authenticated or unauthenticated?

  • How are vulnerabilities prioritized? Present a list of currently open critical findings.

  • What does SLA compliance look like? Show the trend for the past twelve months.

  • How are medical devices handled? Present vendor correspondence.

  • When was the last penetration test conducted? Present the report and remediation status.

Three issues typically lead to audit findings:

1. Training without efficacy measurement. Organizations that distribute content without running phishing simulations cannot demonstrate effectiveness.

2. Incomplete asset inventory. Forgotten medical devices, uninventoried mobile endpoints, cloud workloads existing outside the inventory scope.

3. Patch SLAs existing only on paper. A 14-day SLA on paper, but a 90-day reality in practice without documented compensating measures.

These findings are not identified out of malice - they are the most common real-world vulnerabilities.

Common Mistakes

"We already have an awareness platform." Owning a license is not the same as having an awareness program. If you have a platform but do not run it systematically, you have not resolved your compliance risk.

"Our MSSP handles vulnerability management." A common assumption, and often false. Many managed service contracts only cover detection, not remediation. Clarify in the contract: Who scans, who prioritizes, who patches, and who documents?

"Awareness is just a tick-box exercise." Staff detect this within weeks. Treating awareness as a formal compliance chore yields formal compliance - not behavioral change.

"Patches disrupt clinical operations." Sometimes this is true. But the rule remains: risk assessment, compensating measures, documentation. Not: ignore the patch and hope for the best.

"We don't want the overhead of audit theater." Understandable - and misguided. Without documentation, there is neither insurance coverage nor a viable defense against § 38 BSIG liability in the event of an incident.

"We'll do management training next year." § 38 BSIG has not been deferred - the obligation has been in effect since December 6, 2025. Organizations without documented training will have no proof of compliance in the event of an incident.

Conclusion

Awareness training and vulnerability management are the two halves of operational NIS2 implementation that become visible first in an audit. § 30 BSIG mandates them, Art. 21 NIS2 details them, and § 38 BSIG sharpens accountability through executive management liability toward the organization itself.

What both areas share: They only work as continuous ongoing operations, not as projects with a beginning and an end. Awareness training without monthly phishing simulations and quarterly spotlights fizzles out. Vulnerability management without weekly scanning and SLA tracking is mere compliance theater.

What both areas share: They produce data that serves as the most important evidence during an audit. Having the data means you are regulatorily sound. Lacking it leaves you without a defense during penalty proceedings.

What both areas share: They are demanding to implement internally because they require continuous operations. A clinic with three IT staff members can rarely manage continuous vulnerability management alongside day-to-day operations - and running a systematic awareness program with differentiated target groups, monthly campaigns, and executive reporting is even less feasible. This is precisely where external services come in: They provide continuous operations without requiring the facility to employ dedicated specialists in-house.

At Entropy CS, we provide Awareness Training and Vulnerability Management tailored for healthcare, utilities, and industry - industry-specific phishing scenarios, monthly cadence, NIS2-compliant documentation, and reporting for executive management and audits. Our free Risk Check takes 30 minutes and delivers an honest appraisal of your current maturity level in both disciplines - including actionable priorities for the next 12 months. For the first mandatory requirement - the risk analysis itself - we offer our Cyber Risk Assessment.