NIS2 Spain vs POPA
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 4 of 5 topics. Each verdict names what it rests on; read the wording before relying on it.
- NIS2 Spain Asks more on 0 topics Alone on 0 topics More detailed on 1 topic
- POPA Asks more on 0 topics Alone on 3 topics More detailed on 0 topics
| Topic | NIS2 Spain | POPA | Verdict |
|---|---|---|---|
| Governance | |||
| Management accountability | NIS2 Spain: 1 | POPA: 1 | Both cover itread the wording below |
| Protection | |||
| Data security | NIS2 Spain: – | POPA: 1 | Only POPAno specific requirement on the other side in the acts covered |
| Detection and response | |||
| Reporting to authorities | NIS2 Spain: 5 | POPA: 1 | NIS2 Spain more detailedmore requirements on this, not necessarily stricter |
| Privacy and data protection | |||
| Lawful processing | NIS2 Spain: – | POPA: 2 | Only POPAno specific requirement on the other side in the acts covered |
| Impact assessment | NIS2 Spain: – | POPA: 1 | Only POPAno 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
- 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.
Included
- POPA Protection of Privacy Act, SA 2024, c P-28.5
Status
Reviewed against the official texts.
Key Numbers
Incident reports go to
NIS2 Spain: CSIRTComputer Security Incident Response Team or competent authority
POPA: Not in the acts covered
First notice of an incident
NIS2 Spain: Without undue delay and in any event within 24 hours of becoming aware
POPA: Not in the acts covered
Incident notification
NIS2 Spain: 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.)
POPA: Not in the acts covered
Intermediate report
NIS2 Spain: On request
POPA: Not in the acts covered
Final report
NIS2 Spain: Within one month of the incident notification
POPA: Not in the acts covered
Review of the risk framework
NIS2 Spain: 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)
POPA: Not in the acts covered
Register of third-party arrangements
NIS2 Spain: 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)
POPA: Not in the acts covered
Registration with the authority
NIS2 Spain: Required; changes without delay and in any event within two weeks
POPA: Not in the acts covered
Management body training
NIS2 Spain: Required
POPA: Not in the acts covered
Management body liability
NIS2 Spain: Yes, for infringements of Article 21
POPA: Not in the acts covered
Maximum fines
NIS2 Spain: 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.
POPA: Not in the acts covered
Governance
Management accountability
Both cover it read the wording below
NIST CSF 2.0 GV.RR, GV.OV · ISO/IEC 27001:2022 Clause 5.1, A.5.4
Management approves and oversees the measures
The management body approves the cybersecurityThe activities needed to protect network and information systems, their users and other persons affected by cyber threats. NIS2 and the CRA adopt this Cybersecurity Act definition, so it frames most EU cybersecurity obligations. risk-management measures, oversees their implementation and can be held liable for infringements of Article 21 by the entity. National liability requirements for public institutions and officials are unaffected.
NIS2, Article 20(1) · applies as in the Directive
Privacy management program
Establish and implement a documented privacy management program proportional to the volume and sensitivity of the personal information held, meeting the Ministerial Regulation (section 6: a privacy officer, policies and procedures, a security classification system, mandatory training and periodic review); give anyone who asks a copy within 30 business days.
Protection
Data security
Only POPA 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
Nothing in the acts covered.
Security arrangements
Protect personal information with reasonable security arrangements against unauthorized access, collection, use, disclosure or destruction.
Detection and response
Reporting to authorities
NIS2 Spain more detailed more requirements on this, not necessarily stricter
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
An early warning, saying where applicable whether the incident is suspected to be caused by unlawful or malicious acts or could have a cross-border impact.
NIS2, Article 23(4)(a) · applies as in the Directive
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
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
Breach notification
Notify the individual, the Commissioner and the Minister without unreasonable delay when an incident creates a real risk of significant harm; the notices are written and contain the information set by the Protection of Privacy (Ministerial) Regulation (section 4).
Privacy and data protection
Lawful processing
Only POPA no specific requirement on the other side in the acts covered
NIST Privacy Framework CT.PO-P
Nothing in the acts covered.
Accuracy for decisions
Make every reasonable effort to keep personal information used for decisions, including automated ones, accurate and complete, and keep it for at least one year after using it, or a shorter period agreed in writing by the individual, the public body and any body that approves its retention schedule.
No sale of personal information
Never sell personal information.
Impact assessment
Only POPA no specific requirement on the other side in the acts covered
NIST Privacy Framework ID.RA-P
Nothing in the acts covered.
Privacy impact assessment
Prepare a privacy impact assessment for a new or substantially changed practice, program, project or service involving personal information where a loss could cause significant harm or a submission factor applies, and submit it to the Commissioner where the information is highly sensitive, a significant share of the population is involved, data is matched between public bodies, the program is common or integrated, it uses innovative technology or the Commissioner asks (Ministerial Regulation, section 7).
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. 29 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.