Digital providers: obligations under the Polish act implementing NIS2 (KSC)
In Annex 2 to the Polish act implementing NIS2 (KSC), the digital providers sector covers providers of online marketplaces, online search engines and social networking services platforms. For these entities the Act refers to the detailed risk management measures of Commission Implementing Regulation (EU) 2024/2690.
An online marketplace, a search engine and a social network serve large numbers of users, sellers and advertisers, and their operation relies almost entirely on cloud services and external components. An outage or a data leak is visible immediately and affects many people. CyberSonar24 lets you describe services and dependencies on suppliers, manage risks and incidents within the statutory deadlines and connect this with your GDPR obligations.
01
NIS2 digital providers: what sets the sector apart
- An entirely digital service. The whole process, from user registration to payment and handling of requests, runs in IT systems. Every asset has a direct effect on the service.
- Dependence on cloud and component providers. Infrastructure, payments, email, analytics and customer service usually come from many external suppliers.
- Frequent changes. New system versions are deployed often, so the asset register and the risk assessment must keep up with the changes.
- Users’ personal data. The platform processes account, transaction and communication data, so it applies the GDPR alongside the KSC Act.
- Specific criteria for a significant incident. Implementing Regulation 2024/2690 specifies for these providers when an incident is considered significant.
02
Typical threats and incidents
- Takeover of user and seller accounts after password leaks from other services.
- Denial-of-service attacks during peak traffic periods.
- A data leak caused by a misconfiguration of cloud services.
- A vulnerability in an external library or component.
- An incident at a payment or cloud service provider.
03
Obligations under the KSC Act
- Category. A provider from Annex 2 that is at least a medium-sized enterprise is an important entity (art. 5 para. 2 point 2).
- Risk management measures. Providers of online marketplaces, online search engines and social networking services platforms apply, within the system under art. 8 para. 1, the measures of Commission Implementing Regulation (EU) 2024/2690 (art. 8b para. 1).
- Entry in the register. Application for entry within 6 months of meeting the conditions (art. 7c para. 1). For entities covered by the Act from the date the amendment entered into force, the communication of the Minister of Digital Affairs of 8 April 2026 set the period from 7 May to 3 October 2026.
- Users of the service. The entity gives users access to knowledge about cyber threats related to the service and a way to report a cyber threat, an incident or a vulnerability (art. 9 para. 1 points 2 and 3).
- 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), via the S46 system.
- Deadlines and management. The obligations of chapter 3 by 3 April 2027 (art. 33 para. 1 of the amending Act). The management board is responsible for fulfilling them (art. 8c) and completes documented training once a year (art. 8e).
04
How CyberSonar24 helps
Services and dependencies (CyberSonar24 GRC).
A service register with processes and assets: applications, databases, cloud services and external components. The dependency graph shows which services stop when a specific supplier or component fails.
Cloud and service providers.
A supplier register with contracts, service level agreements and certificates with validity dates, and a reminder 30 days before a contract expires. The supplier risk assessment covers six areas and has a reassessment schedule.
Vulnerabilities.
The vulnerability register checks the NVD database daily for the technologies recorded in assets, and scanner results can be imported from CSV or XML files.
Risk.
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, owner and review schedule.
Incidents and personal data breaches (CyberSonar24 GDPR).
One module for security incidents and personal data breaches, with report templates and deadline countdowns. The GDPR module keeps records of processing activities, data processing agreements and data-subject requests with a response deadline.
Policies and audit.
A policy repository with versioning, an audit programme with ISO 27001:2022 checklists and a management review for the management board.
05
Typical rollout
- 01
Presentation. We show the service register, the dependency graph with suppliers and the shared incident module on sample data.
- 02
Deployment model. In the cloud or on the client’s servers (on-prem), with login via SSO.
- 03
Registers. The company enters services, components 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, training and management review. The team sets up the reporting path, staff complete training in CyberSonar24 E-learning, and the management board receives the management review.
06 · Frequently asked questions
FAQ
Which online platforms are subject to the Polish act implementing NIS2 (KSC)?
Providers of online marketplaces, online search engines and social networking services platforms (Annex 2), if they are at least medium-sized enterprises. They are important entities (art. 5 para. 2 point 2).
What technical measures does a platform provider apply?
The risk management measures of Commission Implementing Regulation (EU) 2024/2690, within the system under art. 8 para. 1 (art. 8b para. 1). The regulation also specifies when an incident at such a provider is considered significant.
What must a platform provide to its users?
Access to knowledge about cyber threats related to the service, for example on its website, and a way to report a cyber threat, an incident or a vulnerability (art. 9 para. 1 points 2 and 3).
How do you combine the obligations of the KSC Act and the GDPR?
In CyberSonar24, security incidents and personal data breaches are in one module shared with CyberSonar24 GDPR, which also keeps records of processing activities and data processing agreements.
