Cybersecurity in digital infrastructure: obligations under the Polish act implementing NIS2 (KSC)
In Annex 1 to the Polish act implementing NIS2 (KSC), the digital infrastructure sector covers providers of internet exchange points, DNS services, cloud computing, data centres and content delivery networks, trust service providers, top-level domain name registries and entities providing domain name registration services, as well as providers of electronic communications, to which a separate telecoms page is dedicated. All other sectors use the services of these entities.
An incident at a cloud, data centre or DNS provider does not affect one organisation but all of its customers. That is why the KSC Act, which implements the NIS2 Directive, covers some of these entities regardless of size and, for most of them, specifies detailed measures from an EU implementing regulation. CyberSonar24 lets you describe services, customers, assets and suppliers in one register and handle incidents within the statutory deadlines.
01
NIS2 for digital infrastructure in Poland: what sets the sector apart
- Services others depend on. Each service has many recipients, including essential and important entities from other sectors. The assessment of an incident’s impact must take customers into account, not only your own processes.
- Category regardless of size. A DNS service provider, a qualified trust service provider, a top-level domain name registry and an entity providing domain name registration services are essential entities regardless of size.
- Detailed technical measures. For DNS service providers, TLD registries, cloud computing service providers, data centre service providers and content delivery networks, the Act specifies risk management measures from Implementing Regulation 2024/2690.
- Physical and logical infrastructure. Server rooms, power supply, cooling, connections, network management systems and customer platforms form one chain of dependencies.
- Short deadlines. A trust service provider reports a significant incident within 24 hours of detection.
02
Typical threats and incidents
- Denial-of-service attacks on network infrastructure and DNS services.
- Takeover of administrator accounts and service management panels.
- A configuration error that interrupts the service for many customers at once.
- A power or cooling failure in a data centre.
- An incident at a subcontractor, for example a software supplier or hardware service provider.
03
Obligations under the KSC Act
- Category. Regardless of size, the following are essential: a DNS service provider, a qualified trust service provider, a top-level domain name registry and an entity providing domain name registration services (Article 5(1)(4)(a), (b), (i) and (j)). A non-qualified trust service provider that is a micro, small or medium-sized enterprise is an important entity (art. 5 para. 2 point 3). Other providers in this sector, including cloud computing service providers and data centre service providers, are essential if they exceed the thresholds of a medium-sized enterprise, and important if they are medium-sized enterprises (art. 5 para. 1 point 1 and para. 2 point 1).
- Risk management measures. DNS service providers, TLD registries, cloud computing service providers, data centre service providers and content delivery network providers apply, within the system under art. 8 para. 1, the measures of Commission Implementing Regulation 2024/2690 (art. 8b para. 1).
- Entry in the register. The minister enters trust service providers in the register ex officio (art. 7a para. 2) and then summons them to complete the data within 6 months (art. 7b para. 2). Other entities submit an application themselves within 6 months of meeting the conditions (art. 7c para. 1). The obligations of telecom operators are described on the telecoms page.
- Significant incident. Early warning within 24 hours, notification within 72 hours, final report within one month (art. 11 para. 1 point 4, 4a and 4c). A trust service provider reports a significant incident within 24 hours of detection (art. 11 para. 1a).
- Audit and deadlines. An essential entity carries out an audit at least once every 3 years (art. 15 para. 1). Entities covered from the date the amendment entered into force fulfil the obligations of chapter 3 of the Act by 3 April 2027 (art. 33 para. 1 of the amending Act).
04
How CyberSonar24 helps
Services and customers (CyberSonar24 GRC).
A register of services with assigned processes and assets: data centre, platform, servers, network and management systems. Assets can be grouped, for example into a data centre or a composite system, and mutual safeguards can be described: redundancy, backups and monitoring.
Dependency graph and completeness check.
The graph shows which services stop when one element fails. The link check points out gaps, for example a process without assets or an asset without an owner.
Risk and vulnerabilities.
A risk register on a scale from 1 to 25 (1–4 Negligible, 5–9 Low, 10–14 Medium, 15–19 High, 20–25 Critical) with a treatment plan and an owner. The vulnerability register checks the NVD database every day, and scanner results can be imported from CSV or XML files.
Incidents within the statutory deadlines.
Recording an incident starts the countdown to the early warning, notification and final report deadlines. Report templates organise the required data.
Suppliers and subcontractors.
A supplier register with data from GUS by NIP number, service level agreements and certificates. The supplier risk assessment covers six areas and has a reassessment schedule.
Continuity and recovery.
Business continuity and disaster recovery plans based on templates aligned with ISO 22301, with a test schedule according to criticality.
05
Typical rollout
- 01
Presentation. We show the service register, asset grouping and the dependency graph on sample data.
- 02
Scope. We agree the services covered by the Act, the locations and the deployment model, in the cloud or on the client’s servers (on-prem).
- 03
Registers. The organisation enters services, assets and suppliers, including by import from Excel files.
- 04
Risks and vulnerabilities. Owners assess risks, and the vulnerability register starts its daily check of the NVD database.
- 05
Incidents and continuity plans. The team defines the reporting path within the statutory deadlines and tests the recovery plans.
06 · Frequently asked questions
FAQ
Which digital infrastructure providers are essential regardless of size?
A DNS service provider, a qualified trust service provider, a top-level domain name registry and an entity providing domain name registration services (Article 5(1)(4)(a), (b), (i) and (j)).
Is a hosting company subject to the Polish act implementing NIS2 (KSC)?
It may be covered as a data centre service provider, that is a provider of a service comprising structures intended for the centralised hosting, interconnection and operation of ICT products (art. 2 point 4h), or as a cloud computing service provider. In that case an undertaking larger than medium-sized is an essential entity, and a medium-sized one is an important entity.
What technical measures does a cloud or data centre provider apply?
The risk management measures of Commission Implementing Regulation 2024/2690, within the system under art. 8 para. 1 (art. 8b para. 1). This also applies to DNS service providers, TLD registries and content delivery networks.
How can we show which customers are affected by the failure of one infrastructure element?
In CyberSonar24 GRC, services, processes and assets are connected in a dependency graph. When you select an asset, for example a server room or a platform, the graph shows the services that depend on it.
