> FADP vs NIS2 Cyprus side by side, topic by topic: where they overlap, where they differ and which asks more, with incident deadlines, testing, third parties and fines.

# FADP vs NIS2 Cyprus

Where they overlap, where they differ and which asks more, topic by topic, with their deadlines and fines side by side.

[FADP](https://grc.plus/regulation/swiss-federal-act-on-data-protection-fadp/)

[NIS2 Cyprus](https://grc.plus/regulation/nis2/cyprus/)Essential and important entities

## At a Glance

They differ on 9 of 9 topics. Each verdict names what it rests on; read the wording before relying on it.

- **FADP** Asks more on 0 topics Alone on 8 topics More detailed on 0 topics
- **NIS2 Cyprus** Asks more on 1 topic Alone on 0 topics More detailed on 0 topics

| Topic | FADP | NIS2 Cyprus | Verdict |
| --- | --- | --- | --- |
| Protection |  |  |  |
| Data security | FADP: 1 | NIS2 Cyprus: – | **Only FADP**no specific requirement on the other side in the acts covered |
| Detection and response |  |  |  |
| Reporting to authorities | FADP: – | NIS2 Cyprus: 5 | **NIS2 Cyprus asks more**national law departs from the Directive |
| Privacy and data protection |  |  |  |
| Lawful processing | FADP: 1 | NIS2 Cyprus: – | **Only FADP**no specific requirement on the other side in the acts covered |
| Transparency | FADP: 1 | NIS2 Cyprus: – | **Only FADP**no specific requirement on the other side in the acts covered |
| Rights of individuals | FADP: 1 | NIS2 Cyprus: – | **Only FADP**no specific requirement on the other side in the acts covered |
| Privacy by design and by default | FADP: 1 | NIS2 Cyprus: – | **Only FADP**no specific requirement on the other side in the acts covered |
| Impact assessment | FADP: 1 | NIS2 Cyprus: – | **Only FADP**no specific requirement on the other side in the acts covered |
| Records of processing | FADP: 1 | NIS2 Cyprus: – | **Only FADP**no specific requirement on the other side in the acts covered |
| International transfers | FADP: 1 | NIS2 Cyprus: – | **Only FADP**no 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

- [FADP](https://grc.plus/regulation/swiss-federal-act-on-data-protection-fadp/) Federal Act on Data Protection of 25 September 2020, SR 235.1; Data Protection Ordinance, SR 235.11 Articles 6 to 8, 12, 16, 17, 19, 21, 22, 25, 29 · 8 requirements

Status

Reviewed against the official texts.

Included

- [NIS2](https://grc.plus/regulation/nis2/) Directive (EU) 2022/2555 Articles 3, 20, 21, 23, 27, 29, 34 · 31 requirements
- [NIS2 Implementing Regulation](https://grc.plus/regulation/nis2-implementing-regulation-2024-2690/) Commission Implementing Regulation (EU) 2024/2690 Articles 3 to 14 · Annex · 17 requirements 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](https://grc.plus/regulation/nis2/cyprus/)
- 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.

## Key Numbers

### Incident reports go to

FADP: Not in the acts covered

NIS2 Cyprus: CSIRT or competent authority

### First notice of an incident

FADP: Not in the acts covered

NIS2 Cyprus: Without undue delay and in any event within 6 hours of becoming aware

### Incident notification

FADP: Not in the acts covered

NIS2 Cyprus: Without undue delay and in any event within 72 hours of becoming aware (24 hours for trust service providers, for incidents affecting their trust services)

### Intermediate report

FADP: Not in the acts covered

NIS2 Cyprus: On request

### Final report

FADP: Not in the acts covered

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

### Review of the risk framework

FADP: Not in the acts covered

NIS2 Cyprus: Risk assessment and treatment plan at planned intervals, at least annually, and after significant incidents 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

FADP: Not in the acts covered

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)

### Registration with the authority

FADP: Not in the acts covered

NIS2 Cyprus: Required; changes without delay and in any event within two weeks

### Management body training

FADP: Not in the acts covered

NIS2 Cyprus: Required

### Management body liability

FADP: Not in the acts covered

NIS2 Cyprus: Yes, for infringements of Article 21

### Maximum fines

FADP: Not in the acts covered

NIS2 Cyprus: Essential 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 entities: maximum of at least EUR 7 million or 1.4%, whichever is higher.

## Protection

### Data security

**Only FADP** no specific requirement on the other side in the acts covered

NIST CSF 2.0 PR.DS · ISO/IEC 27001:2022 A.5.12, A.8.10 to A.8.12

- Data security
  Security appropriate to the risk.
  [FADP, Article 8](https://grc.plus/regulation/swiss-federal-act-on-data-protection-fadp/#requirements)

Nothing 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

Nothing in the acts covered.

- Notify significant incidents
  Notify the CSIRT or competent authority without undue delay of any significant incident, with the information needed to judge any cross-border impact.
  [NIS2, Article 23(1)](https://grc.plus/regulation/nis2/#requirements) · 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.
  [NIS2 Cyprus, K.D.P. 281/2026, Article 4(6)(b)](https://grc.plus/regulation/nis2/cyprus/#requirements)
- 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)](https://grc.plus/regulation/nis2/#requirements) · applies as in the Directive
- Intermediate report
  An intermediate report on status updates, when the CSIRT or authority asks for one.
  [NIS2, Article 23(4)(c)](https://grc.plus/regulation/nis2/#requirements) · 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.
  [NIS2 Cyprus, K.D.P. 281/2026, Article 4(6)(e) and (f)](https://grc.plus/regulation/nis2/cyprus/#requirements)

## Privacy and data protection

### Lawful processing

**Only FADP** no specific requirement on the other side in the acts covered

NIST Privacy Framework CT.PO-P

- Principles
  Lawful, good faith, proportionate processing for purposes that are recognisable, with accurate data kept only as long as needed.
  [FADP, Article 6](https://grc.plus/regulation/swiss-federal-act-on-data-protection-fadp/#requirements)

Nothing in the acts covered.

### Transparency

**Only FADP** no specific requirement on the other side in the acts covered

NIST Privacy Framework CM.AW-P

- Duty to inform
  Inform people when collecting their data, including about automated individual decisions.
  [FADP, Articles 19-21](https://grc.plus/regulation/swiss-federal-act-on-data-protection-fadp/#requirements)

Nothing in the acts covered.

### Rights of individuals

**Only FADP** no specific requirement on the other side in the acts covered

NIST Privacy Framework CT.DM-P

- Rights of the people concerned
  Access, delivery or transfer of data, and the right to have data corrected or deleted.
  [FADP, Articles 25-29](https://grc.plus/regulation/swiss-federal-act-on-data-protection-fadp/#requirements)

Nothing in the acts covered.

### Privacy by design and by default

**Only FADP** no specific requirement on the other side in the acts covered

NIST Privacy Framework CT.DP-P

- Privacy by design and by default
  Technical and organisational measures built in from the start, with data-protection-friendly defaults.
  [FADP, Article 7](https://grc.plus/regulation/swiss-federal-act-on-data-protection-fadp/#requirements)

Nothing in the acts covered.

### Impact assessment

**Only FADP** no specific requirement on the other side in the acts covered

NIST Privacy Framework ID.RA-P

- Impact assessments
  A data protection impact assessment for processing likely to lead to a high risk.
  [FADP, Article 22](https://grc.plus/regulation/swiss-federal-act-on-data-protection-fadp/#requirements)

Nothing in the acts covered.

### Records of processing

**Only FADP** no specific requirement on the other side in the acts covered

NIST Privacy Framework ID.IM-P

- Records of processing
  A record of processing activities, with an exemption for smaller companies.
  [FADP, Article 12](https://grc.plus/regulation/swiss-federal-act-on-data-protection-fadp/#requirements)

Nothing in the acts covered.

### International transfers

**Only FADP** no specific requirement on the other side in the acts covered

- Transfers abroad
  Transfers to countries on the Federal Council's list, under appropriate safeguards, or under exceptions.
  [FADP, Articles 16-17](https://grc.plus/regulation/swiss-federal-act-on-data-protection-fadp/#requirements)

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

- [Compare FADP](https://grc.plus/compare/fadp/)
- [Compare NIS2 Cyprus](https://grc.plus/compare/nis2-cyprus/)

Source: https://grc.plus/compare/fadp-vs-nis2-cyprus/
