Skip to content
Governance, Risk and Compliance

NIS2 for hospitals — implementation and compliance

Health is a sector in NIS2 Annex I. In Poland, the amended KSC Act has applied since 3 April 2026; a hospital that met the criteria for an essential or important entity on that date has 12 months to meet the obligations of Chapter 3 of the Act (Art. 33(1) of the amending act), including an information security management system with tested business continuity plans and an early warning to the sector CSIRT within 24 hours of detecting a significant incident. nFlo delivers complete implementation — from gap analysis to support during regulatory inspection.

Does a hospital fall under NIS2?

Yes, if it meets the size criterion. Health is a sector in NIS2 Annex I, and healthcare providers are listed in it. Annex I entities that exceed the ceilings for medium-sized enterprises are essential entities, and medium-sized ones are important entities (Art. 3). In Poland, the amended KSC Act (Journal of Laws 2026, item 252) adds a rule for healthcare entities that are not businesses: essential with at least 250 employees, important with 50–249 (Art. 5(8)). NIS2 requires maximum fines for essential entities of at least €10 million or 2% of total worldwide annual turnover, whichever is higher (Art. 34(4)).

Healthcare expertise
Sector experience
Hospital templates
Customized policies
NIS2 funding
Application support
NIS2 qualifier

Where to start with NIS2?

Answer a few short questions — we will point you to the service worth starting with and fill in the description in the contact form for you.

The qualifier requires JavaScript. If it does not appear, write to us via the contact page. Go to contact

Hospital under ransomware attack — systems down, patient safety at risk

Complete NIS2 implementation for hospitals

Medical gap analysis

Compliance + HIS/RIS/LIS specifics

NIS2-compliant DR

RTO and RPO set per system

Incident response

Procedure + 24 h early warning to CSIRT

Hospital under attack — systems down, patient safety at risk

For a hospital, NIS2 is governance, risk and compliance with a clinical deadline attached: the directive lists the health sector in Annex I (sectors of high criticality), and what a supervisor asks for — a signed security policy, a tested recovery plan, an early warning to CSIRT within 24 hours — is the same list that keeps patient systems running during an attack.

A hospital is a target where downtime forces a decision faster than in any other sector — and attackers know it. Ransomware on HIS (Hospital Information System) causes:

  • Fallback to manual patient registration (paper forms)
  • Loss of access to EHR (medical history) — doctors treat “blind”
  • Suspension of planned operations
  • Redirection of acute cases to other hospitals
  • Risk of patient data leaks (GDPR — fines up to 4% of revenue)

NIS2 mandates readiness for such scenarios. Whether a hospital is an essential or an important entity depends on its size; risk-management measures, including business continuity (Art. 21), and incident reporting (Art. 23) apply to both.

Does your hospital fall under NIS2?

NIS2 Annex I, point 5 (Health), lists the following types of entity:

  • healthcare providers as defined in Article 3(g) of Directive 2011/24/EU
  • EU reference laboratories
  • entities carrying out research and development activities of medicinal products
  • entities manufacturing basic pharmaceutical products and pharmaceutical preparations (NACE Rev. 2, section C, division 21)
  • entities manufacturing medical devices considered critical during a public health emergency

Essential or important? Annex I entities that exceed the ceilings for medium-sized enterprises are essential entities; medium-sized ones are important entities (NIS2 Art. 2(1) and Art. 3). In Poland, the amended KSC Act (Journal of Laws 2026, item 252) adds a rule for healthcare entities that are not businesses: essential with at least 250 employees, important with 50–249 (Art. 5(8)). The entity itself applies for entry in the register of essential and important entities within 6 months of meeting the criteria (Art. 7c(1)).

Consequences of non-compliance (NIS2 and the Polish KSC Act):

  • NIS2 minimum standard: maximum fines of at least €10 million or 2% of total worldwide annual turnover for essential entities and at least €7 million or 1.4% for important entities, whichever is higher (Art. 34(4)–(5))
  • in Poland: essential entities up to €10 million or 2% of business revenue, whichever is higher; important entities up to €7 million or 1.4% (Art. 73(3)–(4) of the KSC Act)
  • in Poland: up to PLN 100 million where an infringement causes a direct and serious cyber threat, including to human life and health (Art. 73(5))
  • management bodies can be held liable for infringements (NIS2 Art. 20(1)); in Poland the head of the entity can be fined up to 300% of remuneration, or up to 100% in a public entity (Art. 73a(4)–(5))
  • in Poland: an essential entity that does not comply with an order or decision of the authority may have its activity suspended in whole or in part and its head barred from management functions; this does not apply to public entities (Art. 53(9)–(10))
  • in Poland: fines under Art. 73(1)–(4) and Art. 73a can first be imposed 2 years after the amendment entered into force (Art. 35 of the amending act)

10 NIS2 areas in a hospital — checklist

#AreaHow we do it in a hospital
1Security policyApproved by director, updated annually
2Risk managementAssessment every 12 months, active risk register
3Incidents → CSIRTEarly warning 24 h, notification 72 h, final report within one month
4Business continuityBCP + DRP, annual tests
5Supply chainContracts with HIS, cloud, medical equipment vendors
6Access controlRBAC, MFA for doctors + administration
7EncryptionAt-rest (EHR databases), in-transit (PACS, exchange)
8MonitoringSIEM + 24/7 SOC (especially HIS, PACS)
9Backup + restore3-2-1-1-0, RTO and RPO set per system
10TrainingAnnual for staff + management

Typical NIS2-compliant architecture for a hospital

[Patients] → [HIS/EHR main] → [DR site (warm standby)] — RTO per BIA
                ↓
          [PACS/RIS] → [Backup 3-2-1-1-0: local + S3 + tape offline]
                ↓
          [LIS (laboratory)] → [SIEM + 24/7 SOC]
                ↓
[Medical IoMT devices] → [OT/IT microsegmentation]
                ↓
[Staff] → [MFA + RBAC + Security Awareness]

What you get from nFlo

  • NIS2 qualification — essential vs important entity
  • Gap analysis against 10 NIS2 areas + facility specifics (HIS, EHR, PACS, IoMT)
  • Cyber maturity assessment — maturity model
  • Implementation roadmap with priorities and timeline
  • Funding application — assistance in preparation
  • Technical controls implementation — DR, SIEM, MFA, encryption, IoMT segmentation
  • NIS2 documentation — policies, procedures, registers (hospital templates ready)
  • Incident reporting procedure to CSIRT (24h/72h compliant)
  • Training — for board (NIS2 obligations), staff (security awareness), IT (technical)
  • Readiness audit — regulator inspection simulation
  • Audit support — assistance in regulator communication

We have supported a hospital in preparing for the requirements of the Polish KSC Act — the client’s name is confidential.

How we work

Our proven service delivery process.

01

Qualification

Essential vs important entity + scope

02

Gap analysis

10 NIS2 areas + HIS/EHR specifics

03

Roadmap

Plan with priorities and funding sources

04

Implementation

DR, SIEM, policies, staff training

05

Readiness audit

Regulator inspection simulation

Benefits for your business

What you gain by choosing this service.

Lower penalty risk

Essential entities: maximum fines of at least €10 million or 2% of turnover (NIS2 Art. 34(4))

Care continuity

Patients safe — systems work even during attack

Funding support

Help preparing an application in an open funding call

Inspection readiness

Documentation and evidence for the supervisory authority (in Poland: the health minister)

Frequently Asked Questions

Common questions about NIS2 for hospitals — implementation and compliance.

Does my hospital fall under NIS2?

Yes, if it meets the size criterion. NIS2 Annex I (point 5, Health) lists healthcare providers, EU reference laboratories, entities carrying out research and development of medicinal products, manufacturers of basic pharmaceutical products and preparations, and manufacturers of medical devices considered critical during a public health emergency. NIS2 applies to Annex I entities that qualify as medium-sized enterprises or exceed those ceilings (Art. 2(1)); size is assessed under Recommendation 2003/361/EC by staff headcount and annual turnover or balance sheet total. Entities exceeding the medium-sized ceilings are essential, medium-sized ones are important (Art. 3). In Poland, a healthcare entity that is not a business is essential with at least 250 employees and important with 50–249 (Art. 5(8) of the amended KSC Act, Journal of Laws 2026, item 252), and the hospital itself applies for entry in the register of essential and important entities within 6 months of meeting the criteria (Art. 7c(1)).

What are NIS2 requirements for a hospital?

NIS2 Art. 21(2) lists at least: (a) policies on risk analysis and information system security, (b) incident handling, (c) business continuity, such as backup management and disaster recovery, and crisis management, (d) supply chain security, (e) security in system acquisition, development and maintenance, including vulnerability handling, (f) policies and procedures to assess the effectiveness of cybersecurity risk-management measures, (g) basic cyber hygiene practices and cybersecurity training, (h) cryptography and, where appropriate, encryption, (i) human resources security, access control policies and asset management, (j) multi-factor authentication and secured communications, where appropriate. Significant incidents are reported to the CSIRT: an early warning within 24 hours, an incident notification within 72 hours and a final report within one month of the notification (Art. 23(4)). Neither NIS2 nor the Polish KSC Act sets RTO or RPO values — the hospital sets them for each system.

How long does NIS2 implementation take in a hospital?

Typically 6-12 months: (1) Gap analysis — 4-6 weeks (assessment of HIS, EHR, PACS, billing systems, medical IoMT devices), (2) Roadmap + funding application — 4-6 weeks, (3) Technical control implementation (DR, SIEM, MFA, encryption) — 3-6 months, (4) Documentation and procedures — in parallel, (5) Staff training — 2-4 weeks, (6) Readiness audit + corrections — 4-6 weeks. RTO and RPO targets for critical systems (HIS, EHR) are set by the hospital in a business impact analysis — neither NIS2 nor the Polish KSC Act specifies them.

How much does NIS2 implementation cost in a hospital?

Cost depends on scope and phases. NIS2/national cyber law audit alone (nFlo net pricing): BASIC €6-11k, STANDARD €13-21k, ADVANCED €31-50k, ENTERPRISE from €65k. Full implementation (gap analysis + documentation + DR + SIEM/SOC + training) is multi-component — exact quote after scoping intake. Part of the cost may be covered by public funding — the co-financing level and eligible costs are set by the rules of each call. nFlo assists with funding applications.

What funding is available for hospitals on NIS2?

We do not publish a fixed list: calls open and close, and the rules of each call determine who can apply and the co-financing level. When preparing the action plan, we check current calls in which the hospital can be the applicant and help prepare the application.

Want to Reduce IT Risk and Costs?

Book a consultation - we respond within 24h

Response in 24h Custom quote No obligations