CADA vs NIS2 Poland
Where they overlap, where they differ and which asks more, topic by topic, with their deadlines and fines side by side.
At a Glance
They differ on 1 of 1 topics. Each verdict names what it rests on; read the wording before relying on it.
- CADA Asks more on 0 topics Alone on 0 topics More detailed on 0 topics
- NIS2 Poland Asks more on 0 topics Alone on 1 topic More detailed on 0 topics
| Topic | CADA | NIS2 Poland | Verdict |
|---|---|---|---|
| Detection and response | |||
| Reporting to authorities | CADA: – | NIS2 Poland: 5 | Only NIS2 Polandno specific requirement on the other side in the acts covered |
What This Covers
The obligations below are summarised from the acts listed here, grouped by topic. Where a side shows nothing on a topic, the acts covered have no specific requirement on it; an act not yet included, national guidance or a supervisor's expectations may still say more. Use it to see where the regimes differ, not as a compliance checklist.
Included
- CADA Proposal for a Regulation establishing a framework of measures for strengthening Europe's cloud and AI ecosystem, COM(2026) 502 final, 2026/0138 (COD)
Status
Reviewed against the official texts.
Included
- NIS2 Directive (EU) 2022/2555
- NIS2 Implementing Regulation Commission Implementing Regulation (EU) 2024/2690 Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers
National requirements
2 national requirements recorded, as departures from the Directive or additions to it. Everything else applies as the Directive has it.
Status
Reviewed against the official texts.
Key Numbers
Incident reports go to
CADA: Not in the acts covered
NIS2 Poland: CSIRTComputer Security Incident Response Team or competent authority
First notice of an incident
CADA: Not in the acts covered
NIS2 Poland: Immediately and no later than 24 hours after detecting the serious incident
Incident notification
CADA: Not in the acts covered
NIS2 Poland: Immediately and no later than 72 hours after detecting the serious incident (24 hours for trust service providers)
Intermediate report
CADA: Not in the acts covered
NIS2 Poland: On request
Final report
CADA: Not in the acts covered
NIS2 Poland: Within one month of the incident notification
Review of the risk framework
CADA: Not in the acts covered
NIS2 Poland: Risk assessmentA structured process for identifying risks, analysing their possible effects and judging which need attention. In information security, this means examining threats, weaknesses and existing safeguards to prioritise risks to information and business operations. The assessment informs decisions about reducing or accepting risk and should be reviewed as circumstances change. and treatment plan at planned intervals, at least annually, and after significant incidentsUnder NIS2, an incident that has caused or can cause severe operational disruption or financial loss for the entity, or considerable material or non-material damage to other people or organisations. Essential and important entities must report it to their CSIRT or authority, starting with an early warning without undue delay and no later than 24 hours after becoming aware of a significant incident. or changes (DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers)
Register of third-party arrangements
CADA: Not in the acts covered
NIS2 Poland: Directory of direct suppliers and service providers (DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers)
Registration with the authority
CADA: Not in the acts covered
NIS2 Poland: Required; changes without delay and in any event within two weeks
Management body training
CADA: Not in the acts covered
NIS2 Poland: Required
Management body liability
CADA: Not in the acts covered
NIS2 Poland: Yes, for infringements of Article 21
Maximum fines
CADA: Not in the acts covered
NIS2 Poland: Essential entitiesAn organisation that NIS2 places in its stricter tier, mainly large entities in the Annex I sectors of high criticality, plus some entities regardless of size such as qualified trust service providers, DNS service providers and critical entities under CER. Essential entities face proactive supervision and higher maximum fines than important entities.: maximum of at least EUR 10 million or 2% of the undertaking's total worldwide annual turnover in the preceding financial year, whichever is higher. Important entitiesAn organisation in an Annex I or Annex II sector of NIS2 that falls within scope but does not qualify as an essential entity, typically a medium-sized or large company. Important entities have the same risk management and reporting duties, but supervision is mainly reactive, after evidence of non-compliance.: maximum of at least EUR 7 million or 1.4%, whichever is higher.
Detection and response
Reporting to authorities
Only NIS2 Poland no specific requirement on the other side in the acts covered
NIST CSF 2.0 RS.CO · ISO/IEC 27001:2022 A.5.5
Nothing in the acts covered.
Notify significant incidents
Notify the CSIRTComputer Security Incident Response Team or competent authority without undue delay of any significant incidentUnder NIS2, an incident that has caused or can cause severe operational disruption or financial loss for the entity, or considerable material or non-material damage to other people or organisations. Essential and important entities must report it to their CSIRT or authority, starting with an early warning without undue delay and no later than 24 hours after becoming aware of a significant incident., with the information needed to judge any cross-border impact.
NIS2, Article 23(1) · applies as in the Directive
Early warning from detection Differs
The early warning is due immediately and no later than 24 hours after detecting the serious incident, not after becoming aware of it.
Incident notification from detection Differs
The incident notification is due immediately and no later than 72 hours after detecting the serious incident; trust service providers notify within 24 hours.
Intermediate report
An intermediate report on status updates, when the CSIRTComputer Security Incident Response Team or authority asks for one.
NIS2, Article 23(4)(c) · applies as in the Directive
Final report
A final report with a detailed description, the likely type of threat or root cause, the applied and ongoing mitigation and any cross-border impact. For an ongoing incident, a progress report at that time and the final report within one month of handling it.
NIS2, Article 23(4)(d) and (e) · applies as in the Directive
Requirements are summarised in plain words; the official text prevails. Verdicts compare what the acts covered state, not how a supervisor applies them. Most topics are cross-referenced to NIST CSF 2.0 and ISO/IEC 27001:2022. 30 topics where all apply the Directive as it is are not shown.
More Comparisons
Subject to more than one?
We run one control set for both, without doing the work twice. Ask what that saves you.