Incident to report to a regulator?Incident to report? Intake Line

ePrivacy Spain vs SecNumCloud

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

ePrivacy SpainProviders of publicly available electronic communications services; Article 5(3) and Article 13 also reach other organisations

SecNumCloud

At a Glance

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

  • ePrivacy Spain Asks more on 0 topics Alone on 0 topics More detailed on 0 topics
  • SecNumCloud Asks more on 0 topics Alone on 0 topics More detailed on 0 topics
Requirements per topic and verdict
Topic ePrivacy SpainSecNumCloud Verdict

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

  • ePrivacy Directive 2002/58/EC of the European Parliament and of the Council of 12 July 2002, as amended by Directive 2009/136/EC; Commission Regulation (EU) No 611/2013 Articles 2, 4 to 6, 9, 13, 15 · 18 requirements

National requirements

  • LSSI Articles 2, 21, 22

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

  • SecNumCloud SecNumCloud requirements framework v3.2 (8 March 2022), approved by order of 12 August 2026; Law No. 2024-449 of 21 May 2024 (SREN), Article 31; Decree No. 2026-272 of 14 April 2026 5 requirements

Status

Reviewed against the official texts.

Key Numbers

Deadline

ePrivacy Spain: Without undue delay after detection (Providers of publicly available electronic communications services); Immediately (Providers contracted by a provider of publicly available electronic communications services)

SecNumCloud: Not in the acts covered

Goes to

ePrivacy Spain: Subscribers (Providers of publicly available electronic communications services); Subscribers and individuals affected (Providers of publicly available electronic communications services); Contracting provider (Providers contracted by a provider of publicly available electronic communications services)

SecNumCloud: Not in the acts covered

Evidence to keep

ePrivacy Spain: Inventory of personal data breachesPersonal Data Breach Under the ePrivacy Directive (Providers of publicly available electronic communications services)

SecNumCloud: Not in the acts covered

Incident reports go to

ePrivacy Spain: Competent national authority (Providers of publicly available electronic communications services)

SecNumCloud: Not in the acts covered

First notice of an incident

ePrivacy Spain: Within 24 hours of detection, where feasible (Providers of publicly available electronic communications services)

SecNumCloud: Not in the acts covered

Incident notification

ePrivacy Spain: Within three days of the initial notification (Providers of publicly available electronic communications services)

SecNumCloud: Not in the acts covered

Maximum fines

ePrivacy Spain: Set by each Member State; no EU maximum (Member States and competent national authorities)

SecNumCloud: Not 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. 13 topics where all apply the Directive as it is are not shown.

Subject to more than one?

We run one control set for both, without doing the work twice. Ask what that saves you.

Loading the form…