NIS2 for medical care centers and practice networks: obligations, thresholds, roadmap

Many medical care centers (MVZ) fall under NIS2 for the first time: thresholds, Section 30 BSIG obligations, incident reporting and an 8-week roadmap.

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

NIS2 for Medical Care Centers (MVZs) and Practice Networks: Who Is Affected and What Needs to Be Done by When

Since December 6, 2025, the German NIS2 Implementation Act (NIS2UmsuCG) has been in effect. For hospitals, cybersecurity as a mandatory discipline is nothing new—KRITIS facilities have been working with the sector-specific B3S security standard for years, while larger clinics have established ISMS frameworks and CISO roles. For outpatient structures, the situation is different: numerous Medical Care Centers (MVZs) fall directly under the scope of application for the first time—and thus under a compliance regime that did not previously exist in this form.

This guide is intended for managing directors, IT managers, and data protection officers in MVZs and practice networks. The goal: clarity on whether your facility is affected, what the obligations mean in concrete terms, and what implementation sequence makes sense—without turning the project into an 18-month lingering ordeal.

An important clarification upfront: NIS2 does not turn outpatient care centers into mini-hospitals. Operationally, most technical and organizational requirements can be met more leanly than in a KRITIS clinic. However: the ten-measure catalog under § 30 BSIG, the reporting obligations under § 32 BSIG, and the management's liability toward its own organization under § 38 BSIG apply unchanged. Anyone standing unprepared here in 2026 faces both an operational and a legal problem.

Who Is Affected? Thresholds and Classification

NIS2 distinguishes between two categories of obligated entities—both are relevant for MVZs and practice networks:

  • Important entity: medium-sized enterprise according to the EU SME definition (50–249 employees, with annual turnover up to €50 million or balance sheet total up to €43 million) in a NIS2 sector. Maximum fine: €7 million or 1.4% of total worldwide annual turnover (whichever is higher).

  • Essential entity: large enterprise (at least 250 employees or more than €50 million turnover and more than €43 million balance sheet total) in a NIS2 sector. Maximum fine: €10 million or 2%.

Concrete examples from MVZ practice:

  • MVZ with three locations and 60 full-time staff plus 15 part-time: important entity. Employees are counted in headcounts—75 people, clearly above the 50-person threshold.

  • Practice network with 220 employees and €28 million turnover: important entity—the employee threshold is in the medium range, as is the turnover.

  • Hospital group with an MVZ subsidiary: Here, nuances matter. If the MVZ is legally organized as an independent GmbH, its own metrics apply. If it is an integrated part of a NIS2-obligated clinic, it is covered via the parent group.

  • Large-scale practice MVZ with hospital-like structures (laboratory, imaging, surgical suite): regardless of employee headcount, potentially classified as a "practice with large-scale data processing"—this definition originates from § 75b SGB V (now § 390 SGB V) and serves as a strong indicator for NIS2 classification.

Anyone unsure whether the classification applies can use the official BSI NIS2 applicability assessment. It guides you through the threshold logic and provides an initial appraisal. Faster and tailored specifically to the healthcare sector: our NIS2 applicability check—3–4 questions, instant result. In cases of doubt, legal clarification is recommended—the classification directly impacts fine levels and regulatory scrutiny.

Important: Self-assessment is mandatory. No one will receive a polite letter from the BSI asking if they are affected. Those who fail to self-register risk not only fines in the event of a later incident—the management also stands without a documented protective shield regarding internal liability under § 38 BSIG.

§ 75b SGB V (§ 390 SGB V) and NIS2—Not an Either/Or

The biggest misconception in consulting practice in 2026: "We have already implemented the KBV IT Security Directive—surely that's enough for NIS2." It is not.

The IT Security Directive under § 75b SGB V (now codified in § 390 SGB V) has applied since January 1, 2021, to all statutory health insurance-accredited medical and psychotherapeutic practices. It distinguishes three practice sizes—small, medium, and large practices—as well as special cases for large-scale medical equipment and substantial data processing. The directive is structured like an operational catalog of measures: concrete technical and organizational measures per practice size, with sample policies and checklists from the KBV.

NIS2 (implemented through the new version of the BSIG) has a more generic structure. The law defines ten risk management areas (§ 30 BSIG), a three-stage reporting obligation (§ 32 BSIG), and management obligations (§ 38 BSIG). The law leaves the level of implementation detail to the facility—state of the art is the benchmark.

In practice, three constellations arise for a NIS2-obligated MVZ:

1. Identical requirements. Backup, antivirus, multi-factor authentication, network segmentation, access management—what the KBV directive already demands is covered by NIS2. Those who have cleanly implemented § 75b/§ 390 SGB V have already covered a large portion of NIS2 baseline measures.

2. NIS2 gaps compared to the KBV directive. The KBV directive does not feature a three-stage reporting regime with a 24-hour early warning. It does not establish management liability coupled with a training mandate. It does not require BSI registration. It does not mandate systematic supplier management. It does not define fines running into the millions.

3. KBV requirements that NIS2 does not cover in such depth. Specific mandates regarding telematics infrastructure, large-scale medical devices, and patient data protection are articulated in greater detail in the KBV directive. Those launching a NIS2 compliance project should not discard the KBV directive—instead, both regulatory frameworks should be maintained in parallel.

The pragmatic consequence: a unified information security policy serving as an umbrella, an operational measures catalog based on § 75b/§ 390 SGB V, and a NIS2-specific supplementary document covering the gaps (reporting system, supply chain, proof of executive training, registration).

The Ten Obligations Under § 30 BSIG—Translated for MVZs

§ 30 BSIG lists ten mandatory risk management areas. In MVZ terms:

  1. Risk analysis and security concept. Which systems process which data? Where are the critical vulnerabilities? A one-page risk register with 15 to 25 risks is sufficient to start. For an independent and audit-ready analysis, see our Cyber Risk Assessment.

  2. Incident handling. Who is alerted and when? Who decides on system isolation? Which authorities are informed? A two-page incident response plan is mandatory.

  3. Business continuity. If the practice management system or connector fails—how does patient care continue? Manual paper forms, emergency phone list, alternative pathways for diagnostic findings.

  4. Supply chain security. Which IT service providers have access to patient data? Connector vendors, PVS manufacturers, MFA maintenance providers. Data processing agreements (DPA) under Art. 28 GDPR are mandatory, complemented by concrete security agreements and baseline audit rights.

  5. Security in acquisition, development, and maintenance. Patch management, vulnerability handling, secure configuration of new hardware and software. This is often the largest gap in MVZs—no one feels structurally responsible.

  6. Effectiveness assessment of measures. Is what you have set up actually working? Quarterly internal reviews, annual audits of critical systems.

  7. Cyber hygiene and training. Phishing awareness is explicitly anchored here. Staff must be trained regularly, and sessions must be documented. Art. 21(2)(g) of the NIS2 Directive expressly requires this.

  8. Cryptography. Encryption in transit (TLS), at rest (hard drives, backups), and for email communication containing patient data. KIM and ePA cover parts of this, but not the entire spectrum.

  9. Personnel security, access control, and asset management. Who has access to which systems? Are permissions revoked when employees leave? Does a complete inventory of deployed systems exist?

  10. Multi-factor authentication and secured voice/video communications. MFA for all administrative accounts and remote access is the single most effective individual measure. Period.

In practice, items 1, 2, 5, and 7 are the most common weak points—this is where implementation efforts should focus.

Specific Risks in MVZ Structures

MVZs face a different threat landscape than acute-care hospitals. Four recurring patterns:

Telematics infrastructure as an attack surface. KIM, ePA, e-prescriptions (eRezept), and electronic sick notes (eAU) run through connectors and gematik components. While these are generally certified, local access to them (PVS workstations, smart cards, health professional cards/eHBA) is not automatically secure. A successful phishing attack on a medical assistant can lead to manipulated e-prescriptions or unauthorized ePA access.

Distributed locations with centralized IT. Practice networks with three or more locations often operate a centralized server infrastructure—VPN connections, shared Active Directory, unified backup strategy. If the central server is compromised, all sites are affected. This is not hypothetical—the cyberattack on MVZ Tirschenreuth/Kemnath in autumn 2025 affected both locations simultaneously and forced their temporary closure.

High staff turnover, numerous endpoints. In outpatient settings, nursing staff, medical assistants, and physicians turn over more frequently than in hospital structures. Onboarding and offboarding are often not standardized on the IT side—former staff can retain system access for weeks or months. Tablets, smartphones, and mobile devices broaden the attack surface further.

Billing as a financial target. Outpatient structures are attractive targets for targeted CEO fraud attacks and invoice manipulation—diverting cash flow is easier compared to large hospitals. A mid-sized MVZ chain with five locations quickly processes seven-figure monthly reimbursements.

Incident Reporting Under § 32 BSIG—24 Hours, 72 Hours, 1 Month in Practice

§ 32 BSIG mandates a three-stage reporting obligation:

  • Early warning within 24 hours of becoming aware of a significant incident: concise description of the incident, affected systems, suspected origin.

  • Incident notification within 72 hours: detailed assessment of the impact, measures taken, severity classification.

  • Final report after one month: comprehensive post-incident review, root cause, consequences, lessons learned, and adaptations to the security concept.

Reporting is carried out via the BSI reporting portal, accessed through the "Mein Unternehmenskonto" (MUK) business account. Both registration and incident submissions are processed there.

Operationally, this translates to three preparation steps for an MVZ:

1. Set up the MUK account before the first incident occurs. Scrambling to obtain access credentials during a crisis costs critical hours. Access credentials should be stored with management and the IT lead, with a clearly defined deputy structure.

2. Document the escalation path. Who triggers the notification during an incident should be defined in advance. Standard chain: IT lead detects → management decides → data protection officer verifies GDPR reporting duties in parallel.

3. Prepare templates for the three reports. The 24-hour early warning often happens in crisis mode. A pre-drafted text template where only case-specific details need to be inserted saves time and mitigates errors.

Important: The NIS2 notification does not replace GDPR breach notification under Art. 33 GDPR in the event of patient data loss. In typical ransomware incidents, both notification channels must be triggered concurrently—the BSI portal under § 32 BSIG and the competent data protection authority under GDPR.

§ 38 BSIG—Management Liability

Perhaps the most uncomfortable element of NIS2: management is liable to its own entity for implementing and complying with risk management measures. In § 38, the BSIG explicitly establishes:

  • Management must oversee the implementation of § 30 measures.

  • Management must regularly participate in cybersecurity training.

  • In cases of culpable breach of duty, management is liable to the entity for resulting damages.

The law leaves open the exact format and frequency implied by "regularly." An annual documented training session with an agenda and proof of attendance, supplemented by written quarterly cybersecurity status reports, has proven effective.

In MVZ structures with multiple managing directors, the obligation applies to all of them. Delegating this "to IT" is not legally permissible—operational responsibilities can be delegated, but supervisory and oversight duties cannot.

8-Week Roadmap for a Typical MVZ

In practice, the following workflow has proven reliable—more compact than a hospital roadmap, as outpatient facilities are generally less complex and rarely run hundreds of care-critical systems in parallel.

Weeks 1 to 2: Baseline Assessment. Scope clarification (which locations, subsidiaries, and practice units), asset inventory (servers, workstations, connectors, mobile devices), vendor mapping (PVS vendors, IT service providers, cloud hosts). A simple spreadsheet suffices—completeness is what matters.

Weeks 3 to 4: Quick Wins. MFA across all administrative accounts (Active Directory, PVS, backup systems, VPN, RDP, Microsoft 365). Verify backup strategy against the 3-2-1 rule, ensuring at least one copy is offline or immutable. Launch phishing awareness for all staff—a concise kickoff format with documented attendance.

Weeks 5 to 6: Establish Documentation. Information security policy as an umbrella for § 75b/§ 390 SGB V and NIS2. Risk register with 15 to 25 risks. A two-page contingency plan. Vendor register with DPA status and risk classification. Incident response flow diagram with escalation path and reporting templates.

Week 7: Management Training. Documented session on the cybersecurity landscape, introduction to duties under § 38 BSIG, overview of the security concept. File with agenda and participant roster.

Week 8: BSI Registration. Via the "Mein Unternehmenskonto" (MUK) platform, providing master data, classification, and contact details for inquiries. With good preparation, the portal process takes 30 to 60 minutes.

Afterwards: No project phase is ever "finished." Perform quarterly updates of the risk register and contingency plan, conduct regular phishing simulations, run a tabletop exercise at least once a year, and commission a biennial external assessment of measures.

Common Pitfalls

"Our IT service provider handles everything." That is not a NIS2-compliant answer. Responsibility cannot be outsourced—the provider executes measures, but oversight, risk evaluation, and management liability remain with the MVZ.

"We'll wait and see if the BSI inspects us." Fines are not only triggered by BSI audits; they are levied after incidents where protective measures were not documented. And in the event of an incident, the deadlines of 24 hours, 72 hours, and one month are unforgiving.

"Phishing simulations? The works council will never agree." True—including in MVZ structures. However, with a clean works agreement that strictly guarantees aggregated analysis, clear purpose limitation, and an explicit ban on using results for disciplinary actions, employee codetermination becomes a catalyst rather than a blocker.

"We write documentation first, then implement measures." The wrong way around. Documentation arises from living practice—implement measures, document during rollout, and then consolidate into a quarterly structure.

Conclusion

In 2026, NIS2 for MVZs and practice networks is no longer optional—it is mandatory. Operational implementation is achievable: eight weeks are enough to establish a robust framework if scope, prioritization, and resource allocation are aligned from day one.

The biggest levers: MFA on all administrative accounts, a documented emergency plan, a vetted supplier list, and annual documented training for management. Much of the rest follows naturally from an already implemented KBV IT Security Directive under § 75b/§ 390 SGB V.

Typical stumbling blocks: supplier management (often completely unstructured), awareness programs (rarely run systematically), and incident response with 24-hour alerting logic (rarely in place). This is precisely where our services for phishing simulation, awareness training, vulnerability management, and incident response come in—delivering the operational building blocks required by § 30 BSIG without requiring MVZs to build out their own internal security teams.

At Entropy CS, we support MVZs and practice networks with precisely these services—the operational pillars of NIS2-compliant security operations. Our free Risk Check takes 30 minutes and provides an honest baseline evaluation for your facility—including actionable next steps.