Regulatory Radar is now quarterly. This edition covers everything since Edition 004 (May 2026) through mid-November 2026, and the five and a half months it spans were heavier than any single month this year. Two long-scheduled dates passed — the Cyber Resilience Act's reporting obligations and the AI Act's general application — while the EU legislature both delayed parts of the AI Act and began rewriting the incident-reporting landscape through the Digital Omnibus. The Netherlands finally brought its NIS2 law into force, and Ireland's DPC issued two decisions that are worth reading side by side.
Eight items, all traceable to primary regulator, institutional, or Official Journal sources. Press-only material has been excluded.
1. EU — Cyber Resilience Act reporting obligations now apply, and the Single Reporting Platform is live
11 June and 11 September 2026 — Regulation (EU) 2024/2847 / European Commission
Two of the CRA's staged dates passed in this window. Under Article 71(2), Chapter IV (Articles 35 to 51, on the notification of conformity assessment bodies) applied from 11 June 2026, and Article 14 — the manufacturer reporting obligations — applied from 11 September 2026. The rest of the Regulation still applies from 11 December 2027.
Article 14 sets two parallel tracks, one for actively exploited vulnerabilities and one for severe incidents affecting product security. Both start with an early warning within 24 hours of the manufacturer becoming aware, followed by a fuller notification within 72 hours. The final report is due no later than 14 days after a corrective or mitigating measure is available (vulnerabilities) or within one month of the incident notification (severe incidents). Article 69(3) makes clear that these obligations cover in-scope products placed on the market before 11 December 2027 — in other words, the installed base, not only new products.
The Commission confirms that ENISA's Single Reporting Platform is operational as of 11 September 2026. A notification is addressed to the CSIRT of the Member State where the manufacturer has its main establishment and, save in exceptional circumstances, is made available to ENISA at the same time; that CSIRT then shares it with the CSIRTs of the other Member States where the product has been made available.
Why it matters: this is the first CRA obligation with day-to-day operational teeth, and it applies to products already in customers' hands. A manufacturer with no CRA reporting procedure today is already exposed. The 24-hour clock runs from awareness, so PSIRT intake, triage and legal sign-off need to be wired together, not run as separate queues. See our CRA regulatory page for the full timeline.
Sources: EUR-Lex — Regulation (EU) 2024/2847, Articles 14, 69 and 71; European Commission — CRA reporting
2. EU — The AI Act becomes applicable, as the Digital Omnibus on AI moves the high-risk deadlines
24 July (publication), 27 July (entry into force) and 2 August 2026 — Official Journal / European Commission
Regulation (EU) 2026/1744 — the Digital Omnibus on AI, dated 8 July 2026 — was published in the Official Journal on 24 July and entered into force on 27 July 2026. Its amended Article 113 changes the dates that matter most to deployers and providers:
- High-risk systems under Article 6(2) and Annex III (for example biometrics, employment, education): Chapter III, Sections 1 to 3 now apply from 2 December 2027.
- High-risk systems under Article 6(1) and Annex I (AI in regulated products): from 2 August 2028.
- Two new prohibitions in Article 5(1) — AI systems that generate or manipulate non-consensual intimate imagery of identifiable people, and AI systems that generate child sexual abuse material — apply from 2 December 2026.
- Synthetic-content marking (Article 50(2)): providers whose generative systems were placed on the market before 2 August 2026 have until 2 December 2026 to comply (amended Article 111(4)).
Separately, the Commission's AI Act page states that the Act became applicable on 2 August 2026, with some exceptions, and that the AI Office and Member State authorities are responsible for supervision and enforcement from that date.
Why it matters: the Omnibus buys time on high-risk compliance, but it does not pause the Act. Transparency, governance and the general-purpose AI regime are already live, and the two new prohibitions arrive in a few weeks. Organisations that paused their AI inventory work when the delay was proposed should restart it now: Annex III classification work takes longer than the 2027 date suggests. Our AI Act page has the updated timeline.
Sources: EUR-Lex — Regulation (EU) 2026/1744 (Digital Omnibus on AI); European Commission — AI Act
3. Netherlands — Cyberbeveiligingswet and Wwke enter into force
15 August 2026 — Dutch Government
The Netherlands' NIS2 and CER transpositions — the Cyberbeveiligingswet (Cbw) and the Wet weerbaarheid kritieke entiteiten (Wwke) — entered into force on 15 August 2026, closing the parliamentary path tracked in Edition 003. The Cbw replaces the Wbni. The government describes the Cbw as covering thousands of organisations, which must register in a national register maintained by the NCSC; the Wwke covers around 500 organisations, which are designated as critical entities by the responsible ministry. For designated critical entities, the Wwke allows nine months from designation for the risk assessment and ten months for resilience measures, with incident reporting within 24 hours.
Why it matters: the NIS2 transposition deadline was 17 October 2024, so Dutch entities have moved from preparation to live obligations almost two years later. Multinationals with Dutch establishments should confirm registration in the NCSC-maintained register and confirm the reporting deadlines that apply to them. The NIS2 Netherlands page has the full chronology.
4. EU — Data Act design obligations reach new connected products
12 September 2026 — Regulation (EU) 2023/2854
Under Article 50 of the Data Act, the Article 3(1) obligation — designing connected products and related services so that their data is accessible to the user by default — applies to connected products and related services placed on the market after 12 September 2026. The Regulation as a whole has applied since 12 September 2025, with this and other staged exceptions set out in Article 50.
Why it matters: this is a product-design obligation, not a contract clause, and it lands on the same engineering teams now absorbing CRA reporting. Manufacturers launching connected products should treat data-access-by-design as a release gate alongside security requirements, and check that access paths are authenticated and logged, so that complying with the Data Act does not open a new attack surface. See our Data Act page.
Source: EUR-Lex — Regulation (EU) 2023/2854, Article 50
5. EU — Council agrees its Digital Omnibus mandate, replacing the EU single entry point with national ones
21 October 2026 — Council of the EU
The Council agreed its position on the digital part of the Omnibus — amendments to the GDPR, the ePrivacy cookie rules, the data acquis and incident reporting. The points most relevant to security and privacy teams:
- Incident reporting: the Council replaces the Commission's proposed EU-level single entry point with a national entry point in each Member State, supported by an EU-level incident-reporting information point and provisions towards harmonised and cross-border notification.
- GDPR breach notification: the Council backs the Commission's proposal to extend the deadline for notifying personal-data breaches, together with an EU-level list of high-risk processing categories and common templates.
- Personal data: the current definition is kept, with a new provision on pseudonymisation and identifiability.
- Cookies: the rules stay in the ePrivacy Directive, with additional purposes — such as audience measurement and device security — that will not require consent.
Negotiations with the European Parliament start once Parliament adopts its own position.
Why it matters: the Council's choice of national entry points means the "report once, to one EU portal" model is not guaranteed. Cross-border entities should plan for a reporting architecture that can feed several national portals from one internal incident record. The Commission's proposal (COM(2025) 837) would extend the GDPR breach-notification deadline to 96 hours; the Council's press release backs an extension without restating the figure, so we will confirm the final number once the trilogue text is available. Our Digital Omnibus page tracks both halves of the package.
6. EDPB — Draft guidelines on anonymisation and web scraping for generative AI; blockchain guidelines finalised
8 July 2026 (consultation closed 30 October 2026) — European Data Protection Board
The EDPB published three documents:
- Anonymisation guidelines (draft). Building on the CJEU's EDPS v SRB judgment (C-413/23 P), the draft accepts that whether data is anonymous can differ between entities, and proposes a three-part test — no record isolation, no linkage, no inference. Data that passes all three can be treated as anonymous; data that fails any of them needs further analysis.
- Web scraping for generative AI (draft). The draft applies the GDPR to scraping operations that involve personal data, and addresses purpose limitation, transparency, accuracy (reliable sources, timestamps, validation before training), minimisation and legitimate interest. Special-category data still needs both an Article 6 basis and an Article 9(2) exception, assessed case by case.
- Blockchain guidelines (final). Adopted after public consultation.
Both drafts were open for consultation until 30 October 2026.
Why it matters: the anonymisation test is the practical yardstick DPOs will be held to when a dataset is shared with vendors or used for analytics as "anonymous". AI teams sourcing training data from the open web now have an EDPB-level reference for their legitimate-interest assessments. Final versions should follow the consultation.
7. Ireland — Two DPC decisions: HSE (€645,000) and Google (€403 million)
2 September and 21 September 2026 — Data Protection Commission
HSE. The DPC announced its decision on unauthorised access to paper medical records at two disused former psychiatric hospitals, St. Loman's and St. Conal's. Fines totalled €645,000: €300,000 under Articles 5(1)(f) and 32(1) (security of paper records), €300,000 under Article 5(1)(e) (records kept in identifiable form longer than necessary), €30,000 under Article 33(1) (late notification to the DPC) and €15,000 under Article 34(1) (failure to inform data subjects). The DPC also issued a reprimand and orders to audit paper-record facilities, enforce retention and track record locations. Prior similar infringements were treated as an aggravating factor.
Google. The DPC fined Google Ireland Limited €403 million following an own-volition inquiry opened in February 2020 after consumer-organisation complaints, including from BEUC. The EDPB's notice (published 23 September 2026) records a final decision dated 21 September 2026 covering Web & App Activity, Location History and Location Accuracy for the period 25 May 2018 to 4 February 2020. For Web & App Activity and Location History, the decision found infringements of the lawfulness and fairness, transparency and retention requirements; for Location Accuracy, it found transparency and accountability infringements. Google has six months to bring processing into compliance.
Why it matters: the two decisions sit at opposite ends of the risk spectrum, and both are instructive. The HSE decision is a reminder that GDPR security and storage-limitation duties apply fully to paper archives and decommissioned sites, and it continues the 2026 pattern (see Permanent TSB in Edition 004) of fining notification failures separately. The Google decision shows that the age of the processing — 2018 to 2020 — does not shield it from enforcement.
Sources: DPC — Final Decision following Inquiry into the HSE; EDPB — The Irish DPC fines Google €403,000,000 following inquiry
8. United Kingdom — Cyber Security and Resilience Bill completes its Lords stages
2 November 2026 — UK Parliament
The Cyber Security and Resilience (Network and Information Systems) Bill was reintroduced in the new session on 14 May 2026, completed its Commons third reading on 16 June and its Lords third reading on 2 November 2026. Parliament's record lists Commons consideration of Lords amendments for 24 November 2026 (provisional). The Bill has not yet received Royal Assent.
Why it matters: the Bill is the UK's update to its NIS regime. Groups operating on both sides of the Channel should expect two parallel but non-identical regimes. Rather than assume EU NIS2 mapping will satisfy UK obligations, plan for a gap analysis once the final text and the secondary legislation that follows are published.
Source: UK Parliament — Cyber Security and Resilience (Network and Information Systems) Bill, stages
What we did not include
- The NIS2 incident-reporting implementing act. Edition 004 reported the Cooperation Group's common templates and the Commission's plan to make them binding through an implementing act. We could not locate an adopted implementing act in the Official Journal by the close of this window, so there is nothing new to report yet. The Council's Omnibus mandate (item 5) now overlaps with this work.
- Lords amendments to the UK Bill. The Commons is due to consider them on 24 November 2026. We have not reviewed the amendment texts against Hansard, so we have not summarised them.
- Other GDPR enforcement reported by commercial fine trackers. Several trackers list decisions in this window that we could not trace to a regulator's own publication. They are excluded.
- EDPB October plenary. The 13–14 October agenda listed guidelines on the interplay between the AI Act and EU data-protection law as an item for discussion, not adoption. We found no adopted guidelines on that topic in the window.
What to do now
- Product manufacturers (CRA): CRA reporting is live and covers products already on the market. Confirm that your PSIRT can file an early warning within 24 hours through ENISA's Single Reporting Platform, that someone owns the account, and that legal sign-off cannot stall the clock.
- AI providers and deployers: use the Omnibus delay to finish Annex III classification, not to defer it. Check generative systems against the Article 50(2) marking deadline and the new Article 5 prohibitions, both due on 2 December 2026.
- Entities with Dutch establishments: confirm registration in the NCSC-maintained register under the Cbw and the reporting deadlines that apply to you. Wwke-designated entities should diarise the nine- and ten-month deadlines from designation.
- Connected-product teams: make Data Act data-access-by-design a release gate for products launched after 12 September 2026, with security review of the access paths.
- Cross-border incident-response leads: design reporting tooling around one internal incident record that can feed several national entry points. The Council's mandate makes a single EU portal less certain.
- DPOs and data teams: test datasets labelled "anonymous" against the EDPB's three-part test, and audit paper archives and decommissioned sites for retention and physical security.
- UK–EU groups: budget for a UK gap analysis once the Cyber Security and Resilience Bill receives Royal Assent and its secondary legislation is published.