Software for hospitals
Hospitals and healthcare
CyberSonar24 is risk and compliance management software for hospitals, that is a GRC-class system (governance, risk, compliance). In one place it keeps hospital assets and processes, including clinical ones, IT service suppliers, risks, incidents, business continuity plans and data-protection documentation. The directorate sees the current security state, and the cybersecurity officer and the data protection officer work on the same data.
01
The problem: hospital security scattered across many places
In many hospitals the risk register is in a spreadsheet, supplier contracts are in the procurement department, incidents are in email, and data-protection documentation is with the officer. Each document is correct, but nobody sees the whole.
The effects show in three situations:
- A failure or an attack. It is not immediately clear which wards and processes a failure of one system will stop, or who is responsible for restoring it.
- A significant incident. An early warning must be given within 24 hours, and a notification within 72 hours. A public hospital that is an important entity submits only the notification. Gathering information from several places takes time that is then missing.
- An inspection or an audit. Evidence has to be reconstructed from email and file versions, instead of being shown from one register.
02
Hospital obligations under the Polish act implementing NIS2 (KSC)
Healthcare is one of the sectors in Annex 1 to the Polish act implementing NIS2 (KSC) (Dz.U. 2026 poz. 252), alongside among others energy, transport, water and public entities. The obligations are the same as in other sectors; the assets and risks differ. A hospital may be an essential or an important entity. The category depends among other things on size and legal form.
- By 3 April 2027 a security management system together with documentation.
- By 3 April 2028 the first security audit of the information system in an essential entity (art. 33 para. 2 of the amending Act), and subsequent audits at least once every 3 years (art. 15 para. 1).
- A significant incident. Deadlines: 24 hours, 72 hours and one month. An important entity that is a public entity submits only the notification within 72 hours (art. 12c).
A hospital processes health data, so alongside the Polish act implementing NIS2 (KSC) it applies the GDPR. That is why compliance management in a hospital covers two areas at once: information security and personal data protection.
03
What risk and compliance management software to choose for a hospital
The Act does not require a specific program. It requires a documented security management system, and in a hospital with hundreds of assets and dozens of suppliers it is hard to run it in spreadsheets. When choosing a risk-management program for a hospital it is worth checking eight things:
| What to check | Why it matters in a hospital | How it works in CyberSonar24 |
|---|---|---|
| An asset register linked to clinical processes | A system failure affects wards, not only the server room | Assets, processes and services joined in a dependency graph |
| A risk assessment with an owner and a deadline | A risk without an owner will not be reduced | Each risk has a treatment plan, an owner and a deadline |
| Monitoring of risk over time | Risk changes after an incident, a supplier change, a new vulnerability | A review schedule, a vulnerability register linked to assets, risk maps for the directorate |
| A supplier register with a risk assessment | A hospital depends on many system and service suppliers | Contracts, service-level agreements and certificates with validity dates, a reminder 30 days before a contract expires |
| Incidents and personal data breaches together | The same record serves a notification to CSIRT and an assessment of a notification to the President of the UODO | One module for incidents and breaches |
| Personal data protection | Health data requires special protection | GDPR module: a record of processing, authorisations, data processing agreements, patient requests, impact assessment |
| Training for shift staff | Staff will not come to classroom training at one time | Training in the phone browser, without creating an account, with a named certificate |
| Where data is stored | Hospital data cannot go to an unknown place | A dedicated instance in the European Union or an installation on the hospital’s servers |
04
How CyberSonar24 helps a hospital
Hospital systems and the processes that depend on them
The asset register covers systems, devices and information and the processes that depend on them, including clinical processes. The dependency graph shows how a failure of one system affects hospital services. Each asset has an owner and a confidentiality, integrity and availability assessment. Assets with personal data have a separate GDPR assessment.
Risk and its monitoring
Risks are assessed for likelihood and impact and linked to assets and processes. Each risk has a treatment plan, an owner, a deadline and a review date. The vulnerability register uses the NVD and links new gaps to specific assets, so a change in the risk level is visible without manually reviewing lists.
Business continuity in a failure or an attack
A process criticality analysis determines the acceptable downtime and the acceptable data loss. On that basis business continuity and disaster recovery plans aligned with ISO 22301 are produced. The plan contains a crisis team, recovery procedures and an escalation path. The system keeps a test schedule, reminds you of a test 14 days earlier and records the result.
IT service suppliers
The supplier register stores contracts, service-level agreements and certificates with validity dates. Suppliers are linked to the processes and assets they serve. A supplier risk assessment has a schedule of reassessments, and the system reminds you of an expiring contract 30 days earlier.
Incidents and personal data breaches
Security incidents and personal data breaches sit in one module. Incident handling has assigned accountability, a status and full documentation of the path. The system prompts a notification to the CSIRT team when a critical incident concerns an essential service. The same record lets you assess the duty to notify a breach to the President of the UODO.
Medical data and the GDPR
The GDPR module keeps a record of processing activities, authorisations, data processing agreements, patient requests and data protection impact assessments. Reviews of access rights to assets take place according to a schedule.
Staff training
CyberSonar24 E-learning works in the browser on a computer and a phone, without creating an account. The hospital course covers protection of medical data and what to do in an attack that locks hospital systems. After passing the test the participant receives a named certificate, and the directorate sees what share of staff has completed the training.
A management review for the directorate
The management review gathers risks, incidents and the compliance level in one place. The directorate takes decisions on current data, and the decisions are documented for the audit.

05
The course of implementation in a hospital
- 01
Audit Zero. A free questionnaire with no account. A PDF report with the result and recommendations is sent to the email address you provide.
- 02
Presentation. We show the registers on sample data and agree the scope: modules (GRC, GDPR, e-learning), the number of units and the installation model.
- 03
Choice of model. A cloud service on a dedicated instance in the European Union or an installation on the hospital’s servers.
- 04
Services, processes and assets. We enter hospital processes and the assets they use. Existing lists of assets and suppliers can be imported from Excel files.
- 05
Risks, suppliers, continuity plans. The hospital assesses risks, assigns owners, completes the supplier register and business continuity plans.
- 06
Training and incidents. Staff take training, the team starts recording incidents and breaches in one module.
- 07
Management review. The directorate receives the first review with risks, incidents and the compliance level. From then on documentation for the auditor is produced as you go.
06
Data security in the system
CyberSonar24 is available as a cloud service on a dedicated instance in the European Union or as an installation on the hospital’s servers. For large clients, in an installation on the organisation’s servers, the number of users is not limited. Depending on the plan (local or central) one instance can serve several hospitals or units. In the cloud service we conclude a data processing agreement for personal data.
07 · Frequently asked questions
Questions from hospitals
Does the Polish act implementing NIS2 (KSC) apply to every hospital?
It applies to hospitals that meet the criteria of an essential or important entity. Healthcare is a sector covered by the Act, and the category depends among other things on the size and legal form of the hospital. The classification should be confirmed with a lawyer, and a first picture is given by the free Audit Zero.
What must a hospital have by 3 April 2027?
A security management system together with documentation. In practice that is among other things an asset register, a risk assessment, a risk treatment plan, incident-handling procedures and business continuity plans. CyberSonar24 keeps these registers in one place and reminds you of reviews.
Must a hospital undergo an audit by 3 April 2028?
Yes, if it is an essential entity. It carries out its first security audit of the information system by 3 April 2028 (art. 33 para. 2 of the amending Act), and subsequent audits at least once every 3 years (art. 15 para. 1). A hospital that is an important entity carries out an audit only when the authority orders one (art. 15 para. 1b). A hospital that was an operator of an essential service and carried out an audit before 3 April 2026 counts 3 years from the report of the last audit (art. 25 of the amending Act). An audit programme, checklists and corrective actions in CyberSonar24 let you prepare evidence before the auditor’s visit.
Can incidents and GDPR breaches be kept in one register?
Yes. In CyberSonar24 security incidents and personal data breaches sit in one module. The same record serves an assessment of a notification to the CSIRT team and to the President of the UODO.
Can hospital data stay on our servers?
Yes. Besides the cloud service on a dedicated instance in the European Union we offer an installation on the hospital’s servers, with Active Directory integration and priority support.
How to train shift staff?
Through training in the phone or computer browser, without creating an account. Staff take the course at any point in the shift and after the test receive a named certificate.
From how many employees is a hospital an essential entity under the Polish act implementing NIS2 (KSC)?
A healthcare entity that is not an undertaking is an important entity if it employs from 50 to 249 persons, and an essential entity if it employs at least 250 persons (art. 5 para. 8). A hospital run by an undertaking is an essential entity when it exceeds the thresholds of a medium-sized enterprise, and an important entity when it is a medium-sized enterprise (art. 5 para. 1 point 1 and para. 2 point 1). Size is assessed as at the date of preparation of the financial statements (art. 5 para. 5).
Must a hospital itself apply for entry in the register of essential and important entities?
As a rule yes, because ex officio the minister enters only telecommunications undertakings, trust service providers, public entities and critical entities (art. 7a para. 2) and former operators of essential services (art. 34 para. 2 of the amending Act). Other entities submit an application within 6 months of meeting the conditions (art. 7c para. 1), and entities covered by the Act from the date the amendment entered into force according to the schedule in the minister’s communication (art. 33 para. 3 and art. 34 para. 3 of the amending Act). The application is submitted electronically in the ICT system, with a statement of the head, and a healthcare entity that is not an undertaking states the number of employees in it (art. 7c para. 5 and 6, art. 7 para. 2 point 13). For failure to submit the application on time the authority may impose a financial penalty (art. 73 para. 1a point 1).
To which CSIRT team does a hospital report a significant incident?
The early warning, the notification and the reports go to the competent sectoral CSIRT through the ICT system under art. 46 para. 1 (art. 11 para. 1 point 4 to 4c and para. 2). Until the sectoral CSIRT announces operational capability, incidents are reported to the competent CSIRT MON, CSIRT NASK or CSIRT GOV (art. 44 para. 1 of the amending Act), unless a sectoral cybersecurity team was established before 2025 (art. 44 para. 3 of the amending Act). The competent team is indicated in the hospital’s entry in the register (art. 7 para. 2 point 21 and 22). In the early warning you can ask for guidelines or technical support, which the sectoral CSIRT provides within 24 hours (art. 12 para. 2).
Who in the hospital is accountable for the obligations under the Polish act implementing NIS2 (KSC)?
The head of the entity, that is the hospital director or the board, also when they have entrusted the duties to another person, for example a cybersecurity officer (art. 8c para. 1 and 3). If the head is a multi-person body and no responsible person has been indicated, all its members are accountable (art. 8c para. 2). The head plans financial resources for cybersecurity and supervises the tasks (art. 8d), once in a calendar year takes documented training (art. 8e) and may be fined up to 300% of remuneration (art. 73a para. 4).
What penalties does a hospital face for failing to meet the obligations under the Polish act implementing NIS2 (KSC)?
An essential entity may be fined up to 10 million euro or 2% of revenue from business activity, whichever is higher, and not less than 20 000 PLN (art. 73 para. 3). An important entity may be fined up to 7 million euro or 1.4% of revenue, not less than 15 000 PLN (art. 73 para. 4). If the breach causes a direct and serious cyber threat among other things to life and health, the penalty may be up to 100 million PLN (art. 73 para. 5). Penalties under art. 73 para. 1 to 4 and penalties for the head (art. 73a) may be imposed for the first time after 2 years from the amendment entering into force, that is from 3 April 2028 (art. 35 of the amending Act).
08
List of functions for hospitals
- A register of assets and processes, including clinical ones, with a dependency graph
- A process criticality analysis
- A risk register with an owner, a deadline and a review schedule
- A vulnerability register linked to assets
- Business continuity and disaster recovery plans with a test schedule
- A register of IT service suppliers with a risk assessment
- An incident register shared by security and data protection
- A record of processing activities, authorisations, patient requests, impact assessment
- Reviews of access rights to assets
- An audit programme and corrective actions
- A management review for the directorate
- Staff training with a certificate
09
Who it is for
- Directorates of hospitals and healthcare entities
- Cybersecurity officers
- Hospital IT departments
- Data protection officers
- Quality and internal-audit departments
All sectors covered by the Act
Water supply and water infrastructure
Local government and local-government units
Let us talk about information security in your hospital
During the presentation we will show the registers on sample data and discuss where to start before the 3 April 2027 deadline.
