The September 11 deadline under the Cyber Resilience Act has passed, and the reporting platform is already operational. Companies within the CRA’s scope need to understand what the new reporting obligations mean and what action is required. Watch my latest video for a practical overview of the CRA reporting requirements and the key implications for companies. Send us Fan Mail
Audio and video play straight from the show's own hosting. PodSubs stores and serves no media.
Transcript
From the show. Tap a time to play from there.
SPEAKER_00Hello everyone, I'm Giulio Coraggio, a technology and data lawyer. And I'm Antonio Rovenda, a journalist. Today we're gonna discuss about the deadline of the 11th of September 2026 under the Cyber Resilience Act. What changes, what obligations apply.
SPEAKER_01And we're gonna make it during the time of a coffee break. So, Julio, most compliance plans for uh the new EU law, the Cyber Resilience Act, point to one date, December 11, 2027. That's when connected products uh need to be marked for cybersecurity. But there is uh an uh earlier deadline, September 11, 2026, that most plans uh missed completely. So, uh what obligation actually came into force that day?
SPEAKER_00That is very interesting. We noticed that uh the coming into force of the first obligations under the Cyber Resilience Act were kind of overlooked by many businesses that uh were kind of busy because of the implementation of the measures to comply with NIST II or DORA obligations. These obligations are applicable on top of the framework that set out by uh other cyber-related uh legislation set out by the EU.
SPEAKER_00From the 11th of September 2026, the first obligations under the Cyber Resilience Act become applicable because uh they require to identify the products that are under the regime of the Cyber Resilience Act and to report exploited vulnerabilities and uh incidents to the single reporting platform set out by ENISA.
SPEAKER_01There's a safeguard rule in this law that was supposed to be a good news, and this rule protects products already on the market from the lowest technical requirement. But it also covers the duty to report incidents.
SPEAKER_00This is uh another misunderstanding because uh we've been approached by many clients stressing out that uh probably their products are already marketed, they were kind of free from obligations under the CRA. It's not the case. Uh you're right, the obligations that will be applicable from 2027 in building the product they apply only to new products or to existing products to which significant changes have been implemented.
SPEAKER_00But the reporting obligations apply to both new and old products, so even products that are marketed before December 2027 will be subject to these um reporting obligations, which require that companies first of all identify the products that are within the scope. So it's not an obligation at the level of the company, it's per product. Secondly, they set out a policy identifying when an incident or a vulnerability needs to be reported.
SPEAKER_00Thirdly, they identify the roles within the organization, who's in charge of uh mapping the products, identifying the vulnerability of the incident, who's in charge of deciding as to whether the vulnerability needs to be reported, who's in charge of uh performing the actual notification to ENISA or to the affected individuals, and then testing this procedure because sometimes we see that procedures are very nice on the paper, but they're never been tested.
SPEAKER_00And since the first porting obligation uh starts within 24 hours from the identification of the vulnerability or the incident, the procedure needs to be very well tested in order to make sure that you're null.
SPEAKER_01And this rule uh has been defined as uh asymmetric rather than retroactive. Can you walk us through that distinction?
SPEAKER_00Well, it's uh asymmetric because uh it's um product specific and because um the sanctions don't apply now, they will apply from December 2027. That doesn't mean that uh you have a sort of free pass for the coming uh 12 months because what we have seen for other types of legislation like the UAI Act, authorities can retrospectively apply sanctions in relation to conducts that uh were perpetrated before the coming into force of the provisions on uh fines provided by uh the legislation.
SPEAKER_00And so companies have to prepare. Yes, definitely. And uh if you have not done it yet, feel free to reach out to us because we are advising many companies along all the process to become compliant. Thank you, Giulia. Thank you. Arrivederci
How does Italy’s new Artificial Intelligence Law change the liability risks for businesses, and what should companies do to protect themselves? In this episode of The Legal Break Podcast, Giulio Coraggio, technology and...
What should a company do when it discovers a vulnerability in a product covered by the EU Cyber Resilience Act? And what happens when that vulnerability becomes a cybersecurity incident? In this episode, Giulio...
What incidents and vulnerabilities must be reported under the Cyber Resilience Act (CRA)? Since 11 September 2026, the CRA reporting obligations are in force, with companies required to assess and report certain...
Prediction markets are expanding rapidly, allowing users to trade contracts linked to the outcome of future events, from elections and sports competitions to economic and other real-world events. But how should these...
The EDPB has issued its new Guidelines on Anonymisation, and they could have major implications for AI systems, AI training data and GDPR compliance. In this episode of the Legal Break, Giulio Coraggio discusses the new...