Cybersecurity in transport: obligations under the Polish act implementing NIS2 (KSC)
In the Polish act implementing NIS2 (KSC), the transport sector covers four subsectors listed in Annex 1: air, rail, water and road transport. It includes carriers, infrastructure managers, ports and airports, as well as entities providing intelligent transport system services.
Today the continuity of transport services depends on IT systems as much as on rolling stock and infrastructure. Timetables, traffic control, ticket sales, cargo handling and communication with partners run in many locations and with many suppliers. CyberSonar24 organises these dependencies in one system: services, processes, assets, suppliers, risks and incidents.
01
NIS2 in the transport sector in Poland: what sets the sector apart
- Many entities in one chain. A carrier uses the infrastructure of a manager, an airport uses ground handling services, a port uses terminal operators. A failure at one participant stops the others, so dependencies must also be described beyond the boundary of your own organisation.
- Office systems and operational systems. Alongside sales, billing and HR systems, there are systems for traffic control, signalling, navigation, access control and monitoring. They have different owners and different service suppliers.
- Geographic dispersion. Stations, junctions, terminals, quays and road sections are hundreds of sites with equipment that runs for years without replacement.
- Shift and field work. Dispatchers, train drivers, port and airport staff rarely work at a desk, yet they are the first to see the effects of an incident.
- Strict time requirements. An outage of the timetable or traffic control system immediately leads to delays, cancelled services and risks to passenger safety.
02
Typical threats and incidents
- Ransomware encrypting data in sales, billing or planning systems.
- Denial-of-service attacks on passenger information and ticket sales websites.
- Unauthorised access through remote service connections of control system suppliers.
- A failure at an IT service provider that stops several carriers at the same time.
03
Obligations under the KSC Act
- Who is covered. The entities listed in Annex 1 in the transport sector, among others air carriers, airport managing bodies, air navigation service providers, railway infrastructure managers, licensed railway undertakings, shipowners, managing bodies of ports and port facilities, the VTS service, the manager of national roads and entities providing ITS services.
- Category. An entity that exceeds the thresholds of a medium-sized enterprise is an essential entity (art. 5 para. 1 point 1). A medium-sized enterprise is an important entity (art. 5 para. 2 point 1). Regardless of size, essential entities include among others critical entities and entities that are not undertakings and are indicated in Annex 1 by name or type (Article 5(1)(4)(c) and (g)).
- Information security management system under art. 8 para. 1: risk assessment, supply chain security, business continuity and recovery plans, staff training, incident handling, normative and operational documentation (art. 10).
- Significant incident: early warning within 24 hours of detection, notification within 72 hours, final report within one month of the notification (art. 11 para. 1 point 4, 4a and 4c), through the S46 ICT system (art. 11 para. 2).
- Audit. An essential entity carries out a security audit at least once every 3 years (art. 15 para. 1).
- Deadlines. Entities covered by the Act from the date the amendment entered into force fulfil the obligations of chapter 3 by 3 April 2027 (art. 33 para. 1 of the amending Act). An essential entity carries out its first audit by 3 April 2028 (art. 33 para. 2 of the amending Act).
- Management. The head of the entity is responsible for fulfilling the obligations even when they have been delegated (art. 8c), and completes documented training once every calendar year (art. 8e).
04
How CyberSonar24 helps
Services, processes and assets in one register (CyberSonar24 GRC).
The register of key services links transport, passenger services and cargo handling with processes and assets. The dependency graph shows which services stop when a specific system, server or link fails. The criticality analysis sets the maximum tolerable downtime and the maximum tolerable data loss for each process.
Suppliers and the supply chain.
The supplier register retrieves data from GUS by NIP number and stores contracts, service level agreements and certificates with expiry dates. Each supplier is assigned to the systems it supports. The supplier risk assessment covers six areas and has a reassessment schedule, and the system reminds you of an expiring contract 30 days in advance.
Risk and vulnerabilities.
The risk register assesses likelihood and impact on a scale from 1 to 25 (1–4 Negligible, 5–9 Low, 10–14 Medium, 15–19 High, 20–25 Critical). Each risk has a treatment plan, an owner and a review date. The vulnerability register checks the NVD database every day for the technologies recorded in the assets.
Incidents within 24 and 72 hours.
The incident register handles each case in steps: report, response, remediation and analysis. Report templates organise the data required at each stage, and the system prompts a notification to the CSIRT team when a critical incident affects a key service.
Continuity of transport services.
Business continuity and disaster recovery plans are based on templates aligned with ISO 22301. The system keeps a test schedule, reminds you of a test 14 days in advance and records its result.
Training for shift staff (CyberSonar24 E-learning).
Courses run in a computer or phone browser and end with a test with automatic grading and a named certificate. Management sees the training level in every unit.
CyberSonar24 does not monitor networks or traffic control systems. It is used to manage risk, compliance and documentation.
05
Typical rollout
- 01
Audit Zero. A free questionnaire without creating an account, with a PDF report sent by email.
- 02
Demo. We show the dependency graph of services, processes and assets on sample data and agree the scope: modules, companies or branches and the deployment model, in the cloud or on the client’s servers (on-prem).
- 03
Services and processes. The organisation enters its transport services and processes, from planning to passenger or cargo handling.
- 04
Assets and suppliers. Office systems, operational systems and suppliers are added to the registers. Existing lists can be imported from Excel files.
- 05
Risks and continuity plans. Owners assess risks and prepare continuity plans for critical processes.
- 06
Incidents, training and management review. The team records incidents, staff complete training, and the management board receives the first management review.
06 · Frequently asked questions
FAQ
Is every carrier subject to the Polish act implementing NIS2 (KSC)?
No. The Act covers the types of entities listed in Annex 1 in the transport sector, for example air carriers, licensed railway undertakings and shipowners. An undertaking that exceeds the thresholds of a medium-sized enterprise is an essential entity, and a medium-sized one is an important entity (art. 5 para. 1 point 1 and para. 2 point 1).
Is the manager of national roads covered by the Act?
Yes. In the road transport subsector, Annex 1 lists the road manager referred to in art. 19 para. 2 point 1 of the Public Roads Act and entities providing ITS services.
How do we describe a carrier’s dependency on an infrastructure manager or an airport?
In CyberSonar24 GRC, the external entity is entered in the supplier register and assigned to the processes that depend on it. The dependency graph then shows which transport services would stop in the event of a failure on the partner’s side.
Does CyberSonar24 monitor traffic control systems?
No. CyberSonar24 records and assesses control systems together with office systems, and manages risks, incidents and continuity plans. Continuous monitoring of systems requires separate tools.
