FADP vs NIS2 Austria
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 8 of 8 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 Austria Asks more on 0 topics Alone on 0 topics More detailed on 0 topics
| Topic | FADP | NIS2 Austria | Verdict |
|---|---|---|---|
| Protection | |||
| Data security | FADP: 1 | NIS2 Austria: – | Only FADPno specific requirement on the other side in the acts covered |
| Privacy and data protection | |||
| Lawful processing | FADP: 1 | NIS2 Austria: – | Only FADPno specific requirement on the other side in the acts covered |
| Transparency | FADP: 1 | NIS2 Austria: – | Only FADPno specific requirement on the other side in the acts covered |
| Rights of individuals | FADP: 1 | NIS2 Austria: – | Only FADPno specific requirement on the other side in the acts covered |
| Privacy by design and by default | FADP: 1 | NIS2 Austria: – | Only FADPno specific requirement on the other side in the acts covered |
| Impact assessment | FADP: 1 | NIS2 Austria: – | Only FADPno specific requirement on the other side in the acts covered |
| Records of processing | FADP: 1 | NIS2 Austria: – | Only FADPno specific requirement on the other side in the acts covered |
| International transfers | FADP: 1 | NIS2 Austria: – | Only FADPno 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 Federal Act on Data Protection of 25 September 2020, SR 235.1; Data Protection Ordinance, SR 235.11
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
None recorded yet, so the Directive is shown as it is. The national law may go further.
Status
Reviewed against the official texts.
Key Numbers
Incident reports go to
FADP: Not in the acts covered
NIS2 Austria: CSIRTComputer Security Incident Response Team or competent authority
First notice of an incident
FADP: Not in the acts covered
NIS2 Austria: Without undue delay and in any event within 24 hours of becoming aware
Incident notification
FADP: Not in the acts covered
NIS2 Austria: 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.)
Intermediate report
FADP: Not in the acts covered
NIS2 Austria: On request
Final report
FADP: Not in the acts covered
NIS2 Austria: Within one month of the incident notification
Review of the risk framework
FADP: Not in the acts covered
NIS2 Austria: 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
FADP: Not in the acts covered
NIS2 Austria: 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 Austria: Required; changes without delay and in any event within two weeks
Management body training
FADP: Not in the acts covered
NIS2 Austria: Required
Management body liability
FADP: Not in the acts covered
NIS2 Austria: Yes, for infringements of Article 21
Maximum fines
FADP: Not in the acts covered
NIS2 Austria: 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.
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.
Nothing in the acts covered.
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.
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.
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.
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.
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 assessmentAn assessment of the impact of planned processing on the protection of personal data, carried out before processing that is likely to result in a high risk to people's rights and freedoms. Article 35 of the GDPR makes it mandatory in those cases. for processing likely to lead to a high risk.
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.
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.
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. 31 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.