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 cybersecurity incidents and actively exploited vulnerabilities through the ENISA reporting platform. In this video, I explain: * What events and vulnerabilities need to be reported * How companies should assess whether a report is required * What internal processes should be put in place * What companies need to do to comply with the CRA And yes, there is also a brief appearance by my Neapolitan horn socks. 😉 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_01Hello everyone, I'm Giulio Coraggio, a technology and data lawyer. And I'm Antonio Rovenda, a journalist. And we're gonna discuss about the scope of applicability of the Cyber Resilience Act.
SPEAKER_00And we're gonna make it during the time of a coffee break. So, Julio, since September 11, 2026, the Cyber Resilience Act, the Use Cybersecurity Law for Connected Products, has required companies to report vulnerabilities to regulators. But the duty doesn't apply to every vulnerability a company finds, only to some narrow cases. And so, Julio, when does a vulnerability actually cross into this reporting duty versus staying a normal bug that a team quietly patches?
SPEAKER_01I mean, first of all, you need to identify which products are. We're not just talking about IoT products, products with digital elements, this is the definition under the CRA, maybe your mobile app, they may be even your website if connected to a mobile app. For instance, gaming and gambling apps, if downloadable, are really within the scope of the Cyber Resilience Act. So once you identified the products, you need to identify what is a vulnerability that triggers the obligation.
SPEAKER_01This is an actively exploited vulnerability. So it's not just, as you mentioned, a bug that could be exploited. You need to have a reasonable evidence that that bug, that vulnerability, has been exploited. This may be very tricky because when you use the technology of a third party and that technology is embedded in your product with significant changes, you entity might become the manufacturer also of that component.
SPEAKER_01In that scenario, if the vulnerability has been notified to an ISA by other companies in the market, and you don't have evidence of an exploitation in your system, you can have to take into consideration two possible conducts. Having a prudent approach, you so you're gonna do a voluntary notification, or you are gonna collect evidence internally that that vulnerability has not been exploited so that when the uh competent authorities come after you and challenge the lack of notification, you can prove that there wasn't an event triggering the reporting um obligation.
SPEAKER_01The scenario is different in relation to incidents because an incident doesn't necessarily is an incident that caused harm uh or caused the possible damages in terms of the integrity of uh data. It's more a step back. If an incident has occurred enabling uh the occurrence of those events, even at that stage you are subject to a reporting obligation.
SPEAKER_01So basically, two events the vulnerability and the incident that uh in a way might be kind of um connected between each other and need to be qualified according to different parameters, and that's why you need to have an internal procedure that sets out the criteria to evaluate within 24 hours this kind of event and allow the company to report the occurrence when it's through the dedicated platform.
SPEAKER_00And so a serious incident uh is separate from exploitation and an active attack, it's not the only trigger.
SPEAKER_01No, again, the perimeter is much broader. Obviously, uh we will have to see how authorities are gonna interpret it more in detail. Uh, my personal experience, Dora, we need to is that authorities are gonna uh adopt a kind of prudent approach, at least the first months of application. So this prudent approach is likely to lead to an interpretation of the legislation that um is more likely to trigger a kind of over-reporting rather than a cautious approach.
SPEAKER_01Obviously, uh companies need to do a self-assessment, so Eliza will not expect uh that any possible activity is uh reported. But if you don't report, you need to have an internal assessment justifying uh your decision.
SPEAKER_00So, a discovery is a warning, an attack is an emergency, and right now companies have to prepare.
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...
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...
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...