Digital Omnibus: welcome simplification or a step back for GDPR and cyber?
The Digital Omnibus aims to lighten GDPR, cookie rules and incident reporting. What the Commission and Council propose, what is debated, and what to do in the meantime.
The Digital Omnibus is the package to simplify EU digital law that the Commission presented in November 2025. Its data part directly affects CISOs and DPOs: data breaches notified within 96 hours, a single gateway to report incidents, changes to GDPR. On 21 October 2026, member states agreed their position. For some, it ends administrative duplication; for others, it is a step back for data protection. Here is what would change, what is debated, and why you should not change your deadlines yet.
The Digital Omnibus in brief
Presented on 19 November 2025, the digital omnibus has two proposed regulations. The first, on AI, has already been adopted: after the 7 May 2026 agreement between the Council and Parliament, it postponed some AI Act obligations to 2 December 2027 (see our AI Act article). The second, on data, amends GDPR, the ePrivacy directive that governs cookies, the NIS 2 directive and the Data Act. That is the one under discussion.
The Commission claims savings of up to €5 billion by 2029 for the data, AI and cyber part, according to its Q&A. The Council of the EU adopted its negotiating mandate on 21 October 2026. The European Parliament still has to agree its own before the trilogues, the three-way negotiations between Commission, Council and Parliament.
What the Digital Omnibus would change for cyber and data
- Data breach notification. Today, Article 33 GDPR requires notifying the supervisory authority within 72 hours unless the breach is unlikely to result in a risk. The Commission proposes notifying only high-risk breaches, within 96 hours. The Council keeps both points; other breaches would still be assessed and recorded internally, explains the Journal du Net.
- Single incident gateway. The same incident can fall under several laws today: an early warning within 24 hours under NIS 2 (Article 23), a breach notification under GDPR, a major ICT-related incident report under DORA (Article 19). The Commission proposes a single entry point run by ENISA to file these reports in one go, which it says would halve the reporting effort for most organisations. The Council replaces it with a national entry point in each member state, plus a mere European information point.
- Definition of personal data. The Commission wanted data to be personal only for an entity reasonably able to identify the person. The Council removed this change and frames pseudonymisation in a separate article: pseudonymised data remains personal for any recipient able to re-identify.
- Artificial intelligence. A new article would allow legitimate interest as a legal basis for developing and running AI systems, with a balancing test, a right to object and safeguards.
- Cookies. The Commission wanted to move them into GDPR; the Council leaves them in the ePrivacy directive, but exempts security, services requested by the user, audience measurement and contextual advertising from consent, under conditions.
The case for: less duplication
For a security team, the argument is concrete. After a cyberattack with a data leak at a bank covered by NIS 2 and DORA, you currently fill in several forms, for several authorities, with different deadlines, while handling the crisis. Lawyers François-Pierre Lani and Alexandre Renou, writing in CIO, see a "unification of incident notifications" that will require better coordination between the SOC, the CISO, compliance and legal, but will make the job simpler.
On breach notification, there is broad agreement. In their February 2026 joint opinion, the European Data Protection Board (EDPB) and the European Data Protection Supervisor (EDPS) support raising the risk threshold, reports Clusif, the French information security association. The French Senate's European affairs committee, highly critical of the rest, welcomes the move from 72 to 96 hours as a genuine simplification. The Council justifies the whole package by lower compliance costs and the competitiveness of European businesses.
The criticism: rights, AI and sovereignty
- A weaker GDPR? The privacy group noyb, founded by Max Schrems, calls it a "digital expropriation of Europeans" in Solutions Numériques: in its view, legitimate interest for AI would make mass processing lawful by default, benefiting the large players that already hold the data. The French Senate rejects any AI "privilege" for sensitive data such as health or biometrics.
- The definition of personal data. This was the most contested point: the EDPB and EDPS, like the Senate, opposed the proposed change. The Council dropped it, but Parliament may reopen it.
- An EU gateway as a single point of failure. The Senate opposes centralising incident reports with ENISA: a single gateway would become a target and a single point of failure, and national security remains a member-state competence. The Council's position goes the same way. The debate echoes the one on digital sovereignty.
- One more timetable. French organisations are still waiting for NIS 2 to be transposed through the resilience bill. Another layer of change, even a simplifying one, takes time to absorb in procedures and tools.
What it means for you in the meantime
- Do not change your deadlines. The text has not been adopted. Once published, most provisions would apply after 6, 24 or 48 months, according to the Journal du Net: GDPR breach notification stays at 72 hours. Clusif recommends following the negotiations without pre-emptive changes.
- Unify your incident procedure now. For each type of incident, know which law applies, which authority to alert and by when: useful today, and exactly what a future gateway will require. Our article on incident management under ISO 27035 walks through the process; the recent PHP2Shell case shows how quickly decisions must be made.
- Keep the internal breach register. Even with a higher threshold, every breach will still have to be assessed and documented.
- Document pseudonymised data and AI projects. Future rules will rely on the ability to re-identify and on a balancing of interests: an up-to-date inventory and written assessments will be the best evidence. See our articles on data security and shadow AI.
- Add the omnibus to your regulatory watch. Parliament's position, then the trilogue agreement, will set the actual rules. Our article on cybersecurity regulatory watch explains how to organise it.
To keep your record of processing and track data breaches in one place, explore our GDPR compliance module.
Summary
A text still under negotiation
The Council adopted its position on 21 October 2026; the European Parliament has not yet. Nothing changes before adoption, followed by application phased over 6 to 48 months.
Real gains for cyber teams
A single incident gateway and a 96-hour deadline for high-risk data breaches would help teams that report the same incident several times.
A fundamental debate on data
The definition of personal data, legitimate interest for AI and the location of the EU gateway pit competitiveness advocates against rights defenders.
Frequently asked questions
What is the Digital Omnibus?
It is a package to simplify EU digital legislation, proposed by the Commission on 19 November 2025. It has an AI part, adopted in 2026, which postponed some AI Act obligations, and a data part that amends GDPR, the ePrivacy directive (cookies), NIS 2 and the Data Act. The data part is still being negotiated.
Is the data breach notification deadline moving to 96 hours?
Not yet. The Commission proposes notifying the authority only of breaches likely to result in a high risk, within 96 hours, and the Council kept this in its 21 October 2026 position. Until the text is adopted and applies, the current rule stands: notify the supervisory authority within 72 hours unless the breach is unlikely to result in a risk (Article 33 GDPR).
What is the single entry point for incidents?
The Commission proposes one interface, run by ENISA, to report in one go an incident falling under NIS 2, GDPR, DORA, the Critical Entities Resilience directive and the European Digital Identity regulation. The Council prefers an entry point in each member state, with a European information point on top. Recipient authorities and substantive obligations stay the same.
Does the omnibus weaken GDPR?
That is the heart of the debate. Supporters speak of targeted clarifications and lower costs. Critics, including the privacy group noyb, the French Senate's European affairs committee and, on some points, the EU data protection authorities, fear lower protection, especially with legitimate interest for training AI. The Council dropped the change to the definition of personal data.
Should procedures change right now?
Not for deadlines and obligations, which remain those of GDPR, NIS 2 and DORA. It is, however, a good time to unify your incident procedure: knowing for each type of incident what to report, to which authority and by when will make the move to a future gateway much easier.
Sources (13)
- Commission européenne — Simpler digital rules to help EU businesses grow, 19 novembre 2025
- Commission européenne — Digital Package, questions et réponses
- Conseil de l'UE — Digital rulebook: Council agrees position to simplify data protection, privacy and cyber reporting rules, 21 octobre 2026
- Conseil de l'UE — Artificial Intelligence: Council and Parliament agree to simplify and streamline rules, 7 mai 2026
- EDPB et CEPD — Avis conjoint 2/2026 sur la proposition de Digital Omnibus, 11 février 2026
- Sénat, commission des affaires européennes — Omnibus numérique européen : un risque pour la protection des droits numériques des citoyens, mai 2026
- Clusif — Les deux omnibus numériques européens, 19 mai 2026
- Journal du Net — Digital Omnibus : ce que change le mandat du Conseil de l'UE du 21 octobre 2026, 29 octobre 2026
- Solutions Numériques — Omnibus numérique : le Conseil simplifie, noyb dénonce une expropriation numérique, 28 octobre 2026
- CIO — Digital Omnibus : une simplification qui bouscule la gouvernance des SI, 21 janvier 2026
- EUR-Lex — Règlement (UE) 2016/679 (RGPD), article 33
- EUR-Lex — Directive (UE) 2022/2555 (NIS 2), article 23
- EUR-Lex — Règlement (UE) 2022/2554 (DORA), article 19
A platform and service that adapt to you
Our platform is designed for fine-tuned configuration and broad adaptability to your needs.