Skip to content
PodSubs
ShowsPeopleGuestsJobsNewsEvents
More
BlogPodCred
Menu
ShowsPeopleGuestsJobsNewsEventsBlogPodCredNetworksSign in
Join nowSign in
  • Shows
  • People
  • Jobs
  • News
  • More
    • Guests
    • Events
    • Blog
    • PodCred
    • Networks
    Join nowSign in

Diritto al Digitale

Diritto al Digitale artwork

How to deal with a vulnerability and an incident under the Cyber Resilience Act?

Oct 8, 20266 minAudio
ShareXLinkedInFacebookWhatsAppEmail

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 Coraggio, a technology and data lawyer, discusses with the journalist Antonio Ravenna how companies should deal with vulnerabilities and cybersecurity incidents under the Cyber Resilience Act (CRA), including the new reporting obligations, the role of ENISA and the CRA Single Reporting Platform, and the importance of having the right internal processes in place before an incident occurs. We look at the key practical questions companies need to address: when does a vulnerability have to be reported, when does an incident trigger a notification, what are the applicable deadlines, and who needs to be involved? The CRA is changing the way manufacturers need to approach cybersecurity, moving from reactive incident response towards continuous vulnerability management and security throughout the product lifecycle. If you manufacture, distribute or work with products with digital elements, understanding these obligations is becoming increasingly important. 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. We're gonna discuss about how to deal with an actively exploited vulnerability and an incident under the Cyber Resilience Act.

SPEAKER_00And we're gonna make it during the time of a coffee break. So, Julio, since September 11, 2026, under the Cyber Resilience Act, a company that learns that its products is under an active attack has had a legal countdown to follow. And uh can you break down that countdown for us? What's due at 24 hours and what at 72 hours and what at 14 days?

SPEAKER_01The timing is very challenging. It is similar to the timing that is provided by other European legislations on cybersecurity. The goal by the authorities is to be immediately informed of incident of the vulnerability in order to notify whoever might be affected. This means that within 24 hours from the knowledge, which doesn't mean the occurrence of the event, you need to be able to provide a preliminary notification to an Isam of an actively exploited vulnerability or of an incident.

SPEAKER_01It seems tight, it refers to the knowledge, but the experience that we have with other similar legislation means that you cannot delay the notification just arguing that you became aware of that event later on. Because if that delay is due to a lack of organizational measure or lack of technological solutions that were not able to detect that event, then you might have a problem because authorities might argue that the delay in the notification is due to your negligence.

SPEAKER_01It's not just due to the sophistication of the attack. Then once you've done the preliminary notification, you have a bit of a breed, and then you need to provide the additional details within the following 72 hours and then a final notification within 14 days from always the knowledge. You can then argue that the investigation is uh taking more time.

SPEAKER_01Bear in mind that we're not talking about incidents that affect personal data, the GDPR is a completely separate set of legislation, but we're talking about an incident that affects your data or your technological infrastructure, can provide a downtime and impact on the functioning of the product. And as I said, the product is uh a very broad definition of products, not just IoT products. So you need to have a team that uh is able to quickly assess what happened, or you need to have vendors that are ready to investigate on the event.

SPEAKER_01Also, because it's true that the sanctions will not be applicable for another year, but they might be applicable to events occurred from the 11th of September 2026, even though the sanctions will apply from December 2027, because that is not uh a free pass, it's not an exemption from the applicability of fines.

SPEAKER_00And these violations sit in the lowest highest fine brackets. And so, how much money is actually on the line?

SPEAKER_01Well, we're talking about uh potentially millions of euros because, as um, all the new legislation issued by the European Union, the calculation is based on the turnover of the fishing entity. In practice, we still don't know how the authorities are gonna parameter the fine. Unlike what happened with the NISTU, that is a directive, therefore, the fines are different between a country and another. This is a regulation, so the criteria are determined uh at EU level, and um we expect that there would be some sort of consistency uh between jurisdictions.

SPEAKER_00Is there an exception?

SPEAKER_01No, there are no exceptions for fines. Obviously, that doesn't mean that uh a fine needs to be issued for whatever breach. You need to prove that there was no negligence, and uh, for instance, uh uh and there is no strict liability uh regime. In many cases, some incidents are due to very sophisticated attacks, but in uh also frequent cases they are due to human errors that didn't update the uh latest firewall that was exploited by traductors or similar scenarios.

SPEAKER_00So 24 hours, 72 hours and 14 days at that schedule.

SPEAKER_01That's a threatening uh uh schedule, definitely, but uh if uh properly planned in the operations of the company definitely it's possible to handle this process. Thank you, Julia. Thank you.

Open the transcript file

Hosts and Guests

Nobody is credited on this episode yet.

Credit the people on this episode

Be the first to rate this episode

More episodes

All episodes
  1. Italy’s New AI Law: What Changes for Corporate Liability?

    Oct 29, 20266 minAudio

    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...

    Credit the people on this episode

  2. Cyber Resilience Act: What Incidents and Vulnerabilities Must Be Reported?

    Oct 1, 20265 minAudio

    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...

    Credit the people on this episode

  3. Cyber Resilience Act: What Does the September 11 Deadline Mean?

    Sep 30, 20265 minAudio

    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...

    Credit the people on this episode

  4. Prediction Markets in Europe: Are They Gambling?

    Sep 16, 20266 minAudio

    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...

    Credit the people on this episode

  5. EDPB Anonymisation Guidelines: What They Mean for AI Systems & GDPR

    Sep 4, 20268 minAudio

    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...

    Credit the people on this episode