SectorHospitalsRisk Management

Hospital Risk Management and Poland's NIS2 Implementing Law: First Steps

Many hospitals have security procedures and systems but still lack a coherent risk management approach. Structuring these areas is what delivers greater security control and prepares the organisation for NIS2 requirements. This article shows how it works in practice.

Hospital risk management: a risk register and Poland's national law implementing NIS2 (KSC)

Why is hospital risk management essential today?

Modern healthcare facilities operate in increasingly complex environments. IT systems are multiplying while new requirements emerge, such as Poland’s national law implementing NIS2 (KSC). Cyber threats are also increasing, making continuity of medical services essential. Hospital coverage and category require an individual assessment. For a healthcare entity that is not an undertaking, Article 5(8) provides important status at 50 to 249 persons and essential status at 250 or more; undertakings follow the applicable criteria in Articles 5 and 5a.

Hospitals therefore need to manage risk actively. This cannot be restricted to IT, as it covers processes, assets, incidents and regulatory compliance.

Hypothetical example, not a customer implementation. This article shows how to structure hospital risk management step by step, using a typical Polish district hospital as an example.

Starting point: no coherent approach to risk

A typical district hospital has extensive IT infrastructure and numerous procedures.

Deadlines for hospitals under Poland’s NIS2 implementing law

Deadline Obligation
By 3 April 2027 Chapter 3 obligations for entities meeting the criteria on 3 April 2026, subject to special provisions
By 3 April 2028 First audit for essential entities covered by Article 33(2) of the amendment; Articles 24 and 25 exceptions
Within 24 hours of detection Early warning of a significant incident without delay under the general regime
Within 72 hours of detection Notification of a significant incident without delay under the general regime
Within one month of notification Final report; Article 12b applies if handling continues

In Poland, NIS2 is implemented through the Act of 5 July 2018 on the National Cybersecurity System, amended by the Act of 23 January 2026 (Journal of Laws 2026, item 252), as subsequently amended. For entities meeting the criteria on 3 April 2026 and required to self-register in Poland, the application deadline expired on 3 October 2026. Entities entered ex officio supply missing data on request. For entities qualifying later under Article 7c, applications are generally due within six months of meeting the criteria and data changes within 14 days. Late registration does not extend compliance deadlines. For later qualifying entities, Article 16 generally provides 12 months for Chapter 3 and 24 months for an essential entity’s first audit, from meeting the criteria; identification by decision requires consideration of Article 7l or 7m. Former operators of essential services maintain security during the transition; completed and ongoing audits require consideration of Articles 25 and 24 of the amendment. Periodic audits are required at least every three years under the applicable regime. Exceptions apply to the table’s reporting clocks: trust service providers notify within 24 hours of detection (Article 11(1a)); important public entities notify within 72 hours of detection, without an early warning or final report (Article 12c). Finance requires an Article 8i/DORA assessment. If incident handling continues, submit a progress report and the final report within one month after handling ends (Article 12b).

How to create a hospital risk register step by step

A risk register documents potential disruptions, likelihood, consequences and responsibility. Establish the ISMS scope and deadline for the hospital’s category using the rules above.

Step 1. Define scope and responsibilities. Management appoints the register owner, usually the cybersecurity lead, and approves the scope: the whole hospital or selected units.

Step 2. List services and processes. Record hospital services and the processes delivering them, including clinical processes: patient admission, diagnostic imaging, laboratory services, hospital pharmacy and payer billing.

Step 3. Inventory assets. Record the systems, equipment, information and people on which processes depend. Assign each asset an owner and confidentiality, integrity and availability ratings.

Step 4. Adopt an assessment method. This example multiplies integer likelihood and impact scores from 1 to 5, giving a result in the range 1 to 25. Not every number in that range is attainable. Management approves the method, full classification and acceptance threshold.

Step 5. Identify threats. For each important asset, consider what could happen, such as an attack, failure, error or supplier loss, and which weaknesses make it possible. Include IT service providers.

Step 6. Assess risk. Evaluate likelihood and consequences, taking existing controls into account. Assess consequences for patients, business continuity, data and legal requirements.

Step 7. Decide and plan action. For every risk above the threshold, choose reduction, transfer, for example contractually to a supplier, avoidance or informed acceptance. Every action needs an owner and deadline.

Step 8. Obtain management approval. Management accepts the risks remaining after treatment, and this is documented.

Step 9. Review. Review the register periodically and after every incident, system change or supplier change.

Example hospital risk register

Illustrative example. These values are fictional and do not come from any hospital.

ID Asset or process Threat Likelihood (1 to 5) Consequence (1 to 5) Level Owner Decision and action Deadline
R1 Hospital information system Ransomware encryption 3 5 15 Head of IT Reduce: offline backups and recovery testing 30.06.2027
R2 Remote maintenance access to diagnostic imaging system Supplier account compromise 3 4 12 Head of IT Reduce: access only during maintenance, documented in contract 31.03.2027
R3 Staff across all wards Password theft through a fraudulent message 4 3 12 Cybersecurity lead Reduce: e-learning for all staff 31.01.2027
R4 Server room Prolonged power failure 2 5 10 Head of technical services Reduce: emergency power testing in the continuity plan 30.04.2027
R5 Patient registration Configuration knowledge held by one person 3 3 9 Head of patient registration Reduce: instructions and a deputy 28.02.2027

CyberSonar24 recalculates the risk value automatically when the record is saved as likelihood × impact. The 1 to 25 scale uses these classes: 1 to 4 Negligible, 5 to 9 Low, 10 to 14 Medium, 15 to 19 High, 20 to 25 Critical. The user selects and documents actions.

Possible uses of the tool are discussed here: hospital risk and compliance software.

Implementing hospital compliance: where to start

Hospital compliance starts by identifying obligations, not by buying a tool. In Poland, hospitals have two main sources of obligations: Poland’s national law implementing NIS2 (KSC) and GDPR, because they process health data. Hospital coverage and category require an individual assessment. For a healthcare entity that is not an undertaking, Article 5(8) provides important status at 50 to 249 persons and essential status at 250 or more; undertakings follow the applicable criteria in Articles 5 and 5a. Determine the ISMS requirements for the entity’s specific category. In particular, entities listed in Article 8(3), including important public entities, follow the special Annex 4 regime instead of Article 8(1).

  1. Inventory obligations under Poland’s national law implementing NIS2 (KSC), GDPR and applicable standards, with deadlines.
  2. Gap analysis: identify obligations already fulfilled and those not yet met.
  3. Risk register, as described above, because the law is based on risk assessment.
  4. Procedures: handle incidents under the applicable regime and deadlines described above, assess personal data breaches separately and maintain continuity plans.
  5. Staff training, including shift workers.
  6. An internal audit programme and corrective actions.
  7. Management review: leadership regularly evaluates risks, incidents and compliance, for example quarterly.

How to monitor hospital risk

Risk monitoring checks whether register ratings remain current. Three signals should always trigger a review: an incident, a system or supplier change, and a new vulnerability in a system the hospital uses. The register is also reviewed on schedule, and findings feed into the management review.

Summary

Risk management is now a key element of hospital operations.

A GRC system helps organise and structure processes.

In practice, it means better preparation for Poland’s national law implementing NIS2 (KSC), greater risk control and more predictable organisational operations.

Is your organisation subject to EU regulations?

Start Audit ZeroCyberSonar24 GRC

Frequently asked questions

FAQ

How do you create a hospital risk register?

List hospital processes and assets, adopt likelihood and consequence scales, assess threats to each important asset and assign each risk an owner, decision and deadline. Hospital management approves the register and reviews it periodically.

Who is responsible for the hospital risk register?

Usually the cybersecurity lead, while management is responsible for risk acceptance. Individual risks are owned by the heads of units responsible for the relevant asset or process.

Does Poland's NIS2 implementing law require a risk register?

A risk register documents the risk assessment within the ISMS. The 3 April 2027 deadline applies to Chapter 3 implementation by entities meeting the Polish law's criteria on 3 April 2026, subject to special provisions. For entities qualifying later, Article 16 generally provides 12 months from meeting the criteria; identification by decision requires consideration of Article 7l or 7m. Former operators of essential services must maintain security during the transition. Determine the ISMS requirements for the entity's specific category. In particular, entities listed in Article 8(3), including important public entities, follow the special Annex 4 regime instead of Article 8(1).

How often should a hospital risk register be updated?

According to the schedule approved by management, and after every incident, system change, supplier change or newly discovered vulnerability.

Where should a hospital start with compliance implementation?

Start by identifying obligations and gaps. CyberSonar24 Audit Zero is an initial self-assessment, not a statutory audit, certification or confirmation of compliance. Check the service terms before use.

How does hospital GRC software differ from a risk spreadsheet?

GRC software can help organise risks alongside asset, process, supplier and incident information. Check the relationships and data views offered by the specific solution.

Which risks commonly appear in a hospital risk register?

Common risks include ransomware encryption, compromise of medical equipment suppliers' remote access and phishing for staff passwords. Other frequent risks are prolonged server room power failure and critical system configuration knowledge held by only one person.

How does risk monitoring software help a hospital?

Software can support documentation of risk reviews. The organisation sets the schedule and reassessment triggers and reports findings to management. Check reminder and alert availability before selecting a tool.

Can CyberSonar24 serve as a hospital risk management system?

CyberSonar24 recalculates the risk value automatically when the record is saved as likelihood × impact. The 1 to 25 scale uses these classes: 1 to 4 Negligible, 5 to 9 Low, 10 to 14 Medium, 15 to 19 High, 20 to 25 Critical. The user selects and documents actions. In CyberSonar24, one incident form includes personal data breach fields for GDPR Article 33 and notification to Poland's UODO. Assess KSC and GDPR classification and deadlines separately. The user is responsible for submitting notifications through the appropriate channel; the form does not imply automatic submission to CSIRT or S46.

Knowledge base

More from this category