InnerWeb
Skip to main content

NIS2 recommendations for a railway operator for 2026–2028

The Polish act implementing NIS2 entered into force on 3 April 2026 under Article 49, and by 3 April 2027 a railway operator must have the obligations of Chapter 3 in place. The seven recommendations below set the work in an order that lets you build audit evidence before the first inspection in 2028. They are addressed to the depot director, the NIS2 officer, the head of rolling stock maintenance and the CISO.

3.04.2027
deadline for the obligations of Chapter 3
8 367
unique OT hosts visible on the internet

Who these recommendations are for

The recommendations apply to railway operators and to entities running technical depots that, after assessment under the act, turn out to be essential or important entities. In a critical sector, an essential entity is usually one with 250 or more employees, or with turnover above EUR 50 million and a balance sheet total above EUR 43 million. An important entity is a medium-sized entity in a critical sector: 50–249 employees, or turnover or balance sheet total within the ranges set by the act.

Legal status at the date of publication: the act (Journal of Laws 2026 item 252) is in force, the transition period is running, and most penalties can be imposed from 3 April 2028. The President referred to the Constitutional Tribunal a motion concerning the provisions on high-risk suppliers, but it does not affect the obligations described below.

Recommendation 1: self-assessment as the first document

Start with a written assessment of whether the organization is an essential entity, an important entity, or outside the act. The act imposes a duty of self-assessment and of filing an electronic application for entry in the register, and the deadline depends on the schedule in the Minister of Digital Affairs' notice for the entity category. A sector regulator can enter an entity by decision, so delay does not change the status, it only takes away control over the timing.

Rationale: the assessment underpins every later decision, including the budget. The evidence for the auditor is a document analyzing thresholds, capital links and scope of activity, signed by the head of the entity.

NIS2 implementation window in Poland (months from 3 April 2026)

NIS2 implementation window in Poland (months from 3 April 2026)Horizontal bar chart: 12 months for the obligations and 24 months to the first audit and penalties0510152025monthsChapter 3 obligationsChapter 3 obligations: 12 months12First audit and penaltiesFirst audit and penalties: 24 months24
Source: Article 33 of the act (12 months), Article 33(2) and Article 35 (24 months)

Recommendation 2: inventory of OT assets

Build an asset register that covers not only servers and workstations but also hall controllers, operator panels, diagnostic stations, service laptops, power supply equipment and access control systems. Each asset should have an owner, a location, a software version and defined connections.

Rationale: the act requires an analysis of assets, and the 2025 OT trends card shows that attacks on the energy and water sectors did not need advanced exploits. Weak remote access and a lack of segmentation were enough. The Snitch database identified 8,367 unique OT hosts visible on the internet. An asset register is the precondition for checking whether your own devices are among them.

Recommendation 3: a risk policy covering OT and physical access

The risk assessment policy should name scenarios for the depot: a stoppage of the inspection hall, loss of diagnostic data, unauthorized access to a controller, an error by a service contractor. Describe each scenario by likelihood, impact and protective measure.

Rationale: the auditor looks for consistency between risk and measures. Physical access by external companies to technical zones is part of the supply chain and belongs in this policy, not only in the gatehouse rules.

Recommendation 4: choosing standards as the backbone of evidence

You do not need one standard for everything. For OT, apply IEC 62443, which organizes zones, conduits and security levels SL 1–4. For the information security management system choose ISO 27001:2022, and for business continuity ISO 22301.

Rationale: a certificate does not mean compliance with NIS2, but the standards provide a framework in which evidence is organized and clear to the auditor. Use them as a backbone, not as a goal in themselves.

Recommendation 5: incident reporting procedure at 24 h, 72 h and one month

Describe who reports a significant incident through the S46 system, who stands in for them and where the data comes from. The act requires an early warning without undue delay and no later than 24 hours after detection, a notification within 72 hours and a final report within one month. Appoint at least two people as contacts for the bodies of the national cybersecurity system.

Rationale: a report with wrong data on the scope of the event is worse than one an hour late. Rehearse the procedure in an exercise based on, for example, loss of connectivity to the inspection hall.

Recommendation 6: the supply chain and external companies in the halls

Keep a register of external companies with their scope of access and training expiry dates, and confirm access to technical zones with a record. An electronic work permit with a qualification check, a gate with a QR badge and an entry and exit log create this record as a natural by-product of the work. Such a solution supports meeting the supply chain requirement and provides evidence for the audit.

Rationale: the recommendation in the OT card calls for separate credentials for IT administration, OT engineering and vendor support, and for a register of external access. Physical and logical access should share a common trail.

Recommendation 7: management, training and budget

Plan mandatory annual cybersecurity training for the head of the entity and include funds for the information security management system in the budget. The act provides for a personal penalty for the head of an essential or important entity of up to 300% of remuneration, calculated like the holiday pay equivalent.

Rationale: calculate without assuming a grant. The Cyber-Secure Water Utilities call was decided on 10 February 2026 (688 grants for 896 applications), and the Digital Europe calls closed by 31 March 2026. Other programs are uncertain, so treat a grant as an additional scenario.

The timeline at a glance

The layout below shows what should be ready by each successive date in the act.

  • by the end of 2026: self-assessment, application for entry as set out in the notice, asset register
  • first half of 2027: risk policy, incident procedure, register of external companies, management training
  • by 3 April 2027: obligations of Chapter 3 of the act
  • 2027–2028: trial internal audit, corrections, collection of evidence
  • from 3 April 2028: first audit of an essential entity and the possibility of most penalties

Video

Frequently asked questions

Where to start if nothing has been done yet?

With a written assessment of the entity's status and an asset register. Without these two documents you cannot reliably estimate risk or budget.

Is ISO 27001 enough to meet NIS2?

No. ISO 27001 is a management system framework and organizes evidence well, but it does not replace obligations arising from the act, such as incident reporting in S46.

Can we count on a grant?

Do not assume one in the calculation. Some calls are closed and others are unconfirmed. Check the current rules before building the financial plan.

Sources

Let us build audit evidence together

We will show how permits, training and access control create records that support NIS2 in a railway depot. Book a conversation.

Let's talk