EUTechRegResearch
MenuClose menu
Digital Omnibus legislative tracker
Texts to 22 Oct 2026

Digital Omnibus proposal· Recital 52

Text

Recital 52 Digital Omnibus proposal as printed in the Council text of 22 October 2026

Source Council, 22 October 2026. Recital 52: ST 14756/26, page 55 · exact text page

Dropped

How the recital changed

Each text against the text before it

Recital Commission19 Nov 2025Rec 52Council21 May 2026Council10 Jun 2026Council18 Jun 2026Council3 Sep 2026Council2 Oct 2026Rec 52Council22 Oct 2026Rec 52
Compared withlaw in forcethe proposal21 May text10 Jun text18 Jun text3 Sep text2 Oct text
Recital 52 52 Added In neither text In neither text In neither text In neither text 52 Dropped 52 Dropped

Each text against the text before it: +Added in this text, not in the text before−Dropped drops a provision the text before added— in neither text

Parliament amendments propose other recitals under these numbers: Recital 52a (new).

Parliament amendments

2 amendments to this recital

2 propose alternative wording.

By political group; co-sponsored amendments count for each group
TypeS&DECRPfE
~ Alternative111

By political group

  • ~ Alternative S&D 1 ECR 1 PfE 1
  1. 135 Alternative Victor NegrescuS&D · JURI “Those measures should be aligned with state-of-the-art cybersecurity practices and ensure a high level of security by design and by default…”

    (52) To ensure the continuity and interoperability with existing national technical solutions that facilitate incident reporting, to the extent feasible, ENISA should take into account such national technical solutions when developing the specifications on the technical, operational and organisational measures necessary to establish, maintain and securely operate the single-entry point. Further, ENISA should consider technical protocols and tools such as application programming interfaces and machine-readable standards that enable entities to integrate reporting obligations into business processes, and authorities to connect the single-entry point with their national reporting systems. Those measures should be aligned with state-of-the-art cybersecurity practices and ensure a high level of security by design and by default, including robust access control, encryption and logging, so that simplification of reporting does not create new vulnerabilities or weaken the protection of sensitive incident information.

    Tabled by
    Victor Negrescu
    Group
    S&D
    Targets
    Digital Omnibus proposal Recital 52
    Document
    JURI amendments 69–296 to the draft opinion
    Printed header
    Recital 52
  2. 506 Alternative Julie Rechagneux +8ECR, PfE · ITRE–LIBE “To ensure the continuity and interoperability with existing national technical solutions that facilitate incident reporting, to the extent feasible…”

    (52) To ensure the continuity and interoperability with existing national technical solutions that facilitate incident reporting, to the extent feasible, ENISA should take into account such national technical solutions when developing the specifications on the technical, operational and organisational measures necessary to establish, maintain and securely operate the single-entry point. Further, ENISA should consider technical protocols and tools such as application programming interfaces and machine-readable standards that enable entities to integrate reporting obligations into business processes, and authorities to connect with the single-entryEU entry point withthrough their national reporting systems.

    Tabled by
    Julie Rechagneux, Mélanie Disdier, Aleksandar Nikolic, Ewa Zajączkowska-Hernik, Pierre-Romain Thionnet, Alexandre Varaut, Fabrice Leggeri, Marion Maréchal, Christophe Bay
    Group
    ECR, PfE
    Targets
    Digital Omnibus proposal Recital 52
    Document
    ITRE–LIBE amendments 401–526 to the draft report
    Printed header
    Recital 52