Cybersecurity in the space sector: obligations under the Polish act implementing NIS2 (KSC)
In Annex 1 to the Polish act implementing NIS2 (KSC), the space sector covers operators of ground-based infrastructure that supports the provision of space-based services, and the Polish Space Agency. The Act excludes from this sector the operators referred to in Article 2(40)(b) of the Polish Electronic Communications Law.
Ground stations, control centres and satellite data processing systems provide communications, navigation and Earth observation for public administration, emergency services and businesses. The sector is small, but the obligations are the same as in other essential sectors. CyberSonar24 lets you describe services, infrastructure and suppliers in one register and document the security management system.
01
NIS2 in the space sector: what sets the sector apart
- Ground infrastructure as an access point. Receiving stations, antennas, control systems and data transmission networks are elements through which a service can be disrupted without access to the satellite itself.
- Specialised suppliers. Hardware and software often come from a few specialised manufacturers, including foreign ones. Supplier risk assessment is particularly important here.
- Public sector customers. The services support public administration, emergency services and other essential sectors, so the effects of an outage go beyond the organisation itself.
- Long system life cycle. The infrastructure operates for years, and some devices are hard to update quickly.
- International cooperation. Projects are run with foreign partners, which requires a clear description of responsibility for assets and data.
02
Typical threats and incidents
- Jamming or spoofing of the signal on the link between the station and the satellite.
- Unauthorised access to the control systems of a ground station.
- Vulnerabilities in the software of specialised equipment suppliers.
- Phishing for login credentials targeted at project teams.
- A power or link failure at a ground facility.
03
Obligations under the KSC Act
- Category. An operator of ground-based infrastructure is an essential entity if it exceeds the thresholds of a medium-sized enterprise, and an important entity if it is a medium-sized enterprise (art. 5 para. 1 point 1 and para. 2 point 1). An entity that is not an undertaking and is indicated in Annex 1 by name or type is essential regardless of size (Article 5(1)(4)(g)).
- Information security management system under art. 8 para. 1, including risk assessment, supply chain security, business continuity plans, continuous system monitoring, cryptography and staff training, as well as normative and operational documentation (art. 10).
- Entry in the register. The entity submits the application for entry within 6 months of meeting the conditions (art. 7c para. 1).
- 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), through the S46 system.
- Audit. An essential entity at least once every 3 years (art. 15 para. 1), the first by 3 April 2028 for entities covered from the date the amendment entered into force (art. 33 para. 2 of the amending Act).
- Management. The head of the entity is responsible for fulfilling the obligations (art. 8c) and completes documented training once a year (art. 8e).
04
How CyberSonar24 helps
Services, stations and systems (CyberSonar24 GRC).
A register of services with processes and assets: stations, antennas, control systems, servers and links. Each asset has a confidentiality, integrity and availability rating and a business and technical owner.
Dependency graph.
Shows which services and recipients are affected by the failure of one facility or system. The dependency map can be exported to PDF.
Hardware and software suppliers.
A supplier register with contracts, certificates and expiry dates, with data from GUS by NIP number for domestic suppliers. The supplier risk assessment covers six areas and has a reassessment schedule.
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). The vulnerability register checks the NVD database every day for the technologies recorded in the assets.
Incidents and continuity.
An incident register with report templates and a deadline countdown, and continuity and recovery plans with a test schedule.
Audit and documentation.
An audit programme with ISO 27001:2022 checklists, corrective actions with an owner and deadline, and a document repository with versioning.
05
Typical rollout
- 01
Presentation. We show the service register and the dependency graph on sample data.
- 02
Deployment model. In the cloud or on the client’s servers (on-prem). Login can use LDAP, Kerberos or SSO.
- 03
Registers. The organisation enters services, ground facilities, systems and suppliers.
- 04
Risks and continuity plans. Owners assess risks and prepare plans for critical processes.
- 05
Audit and management review. The team prepares the audit programme, and management receives the management review.
06 · Frequently asked questions
FAQ
Who in the space sector is subject to the Polish act implementing NIS2 (KSC)?
Operators of ground-based infrastructure that supports the provision of space-based services, except the operators referred to in Article 2(40)(b) of the Polish Electronic Communications Law, and the Polish Space Agency (Annex 1).
Is a ground station operator an essential or an important entity?
That depends on size. An operator 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). It is advisable to confirm the category with a lawyer.
How do we assess the risk of a foreign supplier of specialised equipment?
The supplier is entered in the supplier register in CyberSonar24 GRC, assigned to the assets it supports, and assessed for risk in six areas. The system sets the reassessment date and reminds you of expiring contracts.
Is an audit mandatory for an operator of ground-based infrastructure?
For an essential entity, yes, at least once every 3 years (art. 15 para. 1). The authority may order an important entity to carry out an audit in the event of a significant incident or a breach of the Act (art. 15 para. 1b).
