NIS2 Cyprus vs RAISE Act
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.
- NIS2 Cyprus Asks more on 1 topic Alone on 0 topics More detailed on 0 topics
- RAISE Act Asks more on 0 topics Alone on 0 topics More detailed on 0 topics
| Topic | NIS2 Cyprus | RAISE Act | Verdict |
|---|---|---|---|
| Detection and response | |||
| Reporting to authorities | NIS2 Cyprus: 5 | RAISE Act: – | NIS2 Cyprus asks morenational law departs from the Directive |
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
- 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
- CY-NIS2
- K.D.P. 281/2026
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.
Included
- RAISE Act New York General Business Law Article 44-B, sections 1420 to 1429, as added by Chapter 699 of the Laws of 2025 and replaced by Chapter 96 of the Laws of 2026 (S8828)
Status
Reviewed against the official texts.
Key Numbers
Incident reports go to
NIS2 Cyprus: CSIRTComputer Security Incident Response Team or competent authority
RAISE Act: Not in the acts covered
First notice of an incident
NIS2 Cyprus: Without undue delay and in any event within 6 hours of becoming aware
RAISE Act: Not in the acts covered
Incident notification
NIS2 Cyprus: Without undue delay and in any event within 72 hours of becoming aware (24 hours for trust serviceAn electronic service, normally provided for payment, such as issuing and validating certificates, creating and validating electronic signatures and seals, electronic registered delivery, electronic archiving, attestation of attributes or recording data in electronic ledgers. Trust service providers are regulated by eIDAS and in scope of NIS2. providers, for incidents affecting their trust servicesAn electronic service, normally provided for payment, such as issuing and validating certificates, creating and validating electronic signatures and seals, electronic registered delivery, electronic archiving, attestation of attributes or recording data in electronic ledgers. Trust service providers are regulated by eIDAS and in scope of NIS2.)
RAISE Act: Not in the acts covered
Intermediate report
NIS2 Cyprus: On request
RAISE Act: Not in the acts covered
Final report
NIS2 Cyprus: Within one month of the incident notification; for an ongoing incident, a progress report every 15 days and the final report within 15 days of restoring the affected system
RAISE Act: Not in the acts covered
Review of the risk framework
NIS2 Cyprus: 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)
RAISE Act: Not in the acts covered
Register of third-party arrangements
NIS2 Cyprus: 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)
RAISE Act: Not in the acts covered
Registration with the authority
NIS2 Cyprus: Required; changes without delay and in any event within two weeks
RAISE Act: Not in the acts covered
Management body training
NIS2 Cyprus: Required
RAISE Act: Not in the acts covered
Management body liability
NIS2 Cyprus: Yes, for infringements of Article 21
RAISE Act: Not in the acts covered
Maximum fines
NIS2 Cyprus: 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.
RAISE Act: Not in the acts covered
Detection and response
Reporting to authorities
NIS2 Cyprus asks more national law departs from the Directive
NIST CSF 2.0 RS.CO · ISO/IEC 27001:2022 A.5.5
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 within 6 hours Stricter
The early warning is due without undue delay and in any event within 6 hours of becoming aware of the significant incident.
Incident notification
An incident notification updating the early warning with an initial assessment of severity and impact and, where available, indicators of compromise.
NIS2, Article 23(4)(b) · applies as in the Directive
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
Progress reports every 15 days Stricter
A final report within one month of the incident notification. If the incident is still ongoing, a progress report every 15 days and the final report within 15 days of restoring the affected network or information system.
Nothing in the acts covered.
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.