{"id":5339,"date":"2026-11-17T13:45:15","date_gmt":"2026-11-17T13:45:15","guid":{"rendered":"https:\/\/sawaryn.com\/?p=5339"},"modified":"2026-11-17T14:18:05","modified_gmt":"2026-11-17T14:18:05","slug":"cyber-resilience-act-reporting-gdpr","status":"publish","type":"post","link":"https:\/\/sawaryn.com\/en\/publikacje\/cyber-resilience-act-reporting-gdpr\/","title":{"rendered":"Cyber Resilience Act from September 2026. You have 24 hours to report a vulnerability &#8211; and that does not exempt you from the GDPR"},"content":{"rendered":"<p>Vulnerability confirmed on Friday at 17:40. The technical analysis will not be completed until Monday at the earliest. The 24-hour clock started on Friday &#8211; and it will not stop for the weekend. From 11 September 2026, this will no longer be a hypothetical scenario, but an obligation arising from Regulation (EU) 2024\/2847, the <strong>Cyber Resilience Act (CRA)<\/strong>.<\/p>\n<p>If your company develops software sold to businesses or public authorities, the second half of 2026 will bring several independent regulatory changes at once. None of them is addressed explicitly to an \u201cIT company&#8221; &#8211; each defines a category of entity that you must determine for yourself whether you fall within. This article explains how the two CRA reporting clocks work (24 h and 72 h), why one notification does not replace the other (CRA \u2260 GDPR), and what you need to prepare before the first incident occurs.<\/p>\n<hr \/>\n<h2>Key terms before we move on<\/h2>\n<p>Before discussing the obligations, it is worth clarifying the terminology. The following terms will appear throughout the article.<\/p>\n<table>\n<thead>\n<tr>\n<th style=\"text-align: left;\">Term<\/th>\n<th style=\"text-align: left;\">Meaning<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td style=\"text-align: left;\"><strong>CRA (Cyber Resilience Act)<\/strong><\/td>\n<td style=\"text-align: left;\">Regulation (EU) 2024\/2847 \u2014 EU rules on the cyber resilience of products with digital elements. It applies directly, without requiring national implementation.<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><strong>Product with digital elements<\/strong><\/td>\n<td style=\"text-align: left;\">Software or computer hardware (and related remote data processing solutions), including components placed on the market separately \u2014 Article 3(1) CRA.<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><strong>Actively exploited vulnerability<\/strong><\/td>\n<td style=\"text-align: left;\">A vulnerability that the manufacturer knows is already being used by attackers \u2014 the 24-hour clock starts from that moment.<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><strong>CSIRT<\/strong><\/td>\n<td style=\"text-align: left;\">Computer Security Incident Response Team \u2014 the recipient of notifications under the CRA (in Poland: CSIRT NASK, CSIRT GOV or CSIRT MON \u2014 the allocation must be confirmed under national legislation).<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><strong>ENISA<\/strong><\/td>\n<td style=\"text-align: left;\">European Union Agency for Cybersecurity \u2014 a co-recipient of CRA notifications through the single reporting platform.<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><strong>Articles 33 and 34 GDPR<\/strong><\/td>\n<td style=\"text-align: left;\">The obligation to notify a personal data breach to the supervisory authority (UODO) within 72 h and to inform individuals where the risk is high.<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><strong>EPOC (European Production Order)<\/strong><\/td>\n<td style=\"text-align: left;\">An instrument under Regulation (EU) 2023\/1543 \u2014 an order addressed directly to a service provider, with a compliance deadline of 10 days (in urgent cases \u2014 8 hours).<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><a href=\"https:\/\/eur-lex.europa.eu\/legal-content\/PL\/ALL\/?uri=OJ:L_202402847\" target=\"_blank\" rel=\"noopener\">Regulation (EU) 2024\/2847 \u2014 Polish text<\/a><\/p>\n<hr \/>\n<h2>What the Cyber Resilience Act changes from September 2026<\/h2>\n<h3>Two clocks: 24 hours and 72 hours<\/h3>\n<p>From <strong>11 September 2026<\/strong>, manufacturers of products with digital elements will be required to report actively exploited vulnerabilities and severe incidents affecting the security of the product. Article 14 CRA introduces a three-stage reporting structure:<\/p>\n<table>\n<thead>\n<tr>\n<th style=\"text-align: left;\">Stage<\/th>\n<th style=\"text-align: left;\">Deadline<\/th>\n<th style=\"text-align: left;\">What it includes<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td style=\"text-align: left;\">Early warning<\/td>\n<td style=\"text-align: left;\"><strong>24 hours<\/strong> after becoming aware<\/td>\n<td style=\"text-align: left;\">The existence of the vulnerability and identification of the Member States in which the product has been made available<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\">Full notification<\/td>\n<td style=\"text-align: left;\"><strong>72 hours<\/strong> after becoming aware<\/td>\n<td style=\"text-align: left;\">General information about the product, the nature of the exploitation, remedial measures taken and measures available to users<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\">Final report<\/td>\n<td style=\"text-align: left;\"><strong>14 days<\/strong> after a corrective measure is made available (actively exploited vulnerability) or <strong>1 month<\/strong> (severe incident)<\/td>\n<td style=\"text-align: left;\">Description of the vulnerability (severity, impact), information about the entities exploiting the vulnerability and details of the updates made available<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>You submit notifications simultaneously to the CSIRT designated as coordinator and to ENISA \u2014 through a <strong>single reporting platform<\/strong> (Article 16 CRA). Details of the platform are governed by Delegated Regulation <a href=\"https:\/\/eur-lex.europa.eu\/eli\/reg_del\/2026\/881\/oj\/pol\" target=\"_blank\" rel=\"noopener\">(EU) 2026\/881<\/a>.<\/p>\n<h3>The clock starts when you become aware, not when the analysis is complete<\/h3>\n<p>This is the most important operational point in the entire article. The 24-hour deadline runs <strong>from the moment the manufacturer becomes aware<\/strong> of an actively exploited vulnerability \u2014 not from the moment it is confirmed, the technical analysis is completed or management makes a decision.<\/p>\n<p>Returning to the Friday at 17:40 scenario: if your security team received credible information about the vulnerability, the clock is already running. The technical analysis may take three days \u2014 but you must submit the early warning by Saturday at 17:40.<\/p>\n<p>You do not need to know the full extent of the problem. Both the CRA and the GDPR allow information to be provided in stages. You must report what you know and supplement it in subsequent steps.<\/p>\n<h3>Notification alone does not increase liability<\/h3>\n<p>Article 17(4) CRA expressly states that <strong>the mere act of notification<\/strong> in accordance with Article 14 or Article 15 does not result in increased liability for the person submitting it. This is important \u2014 it removes concerns that a notification amounts to an \u201cadmission&#8221; of the problem.<\/p>\n<p><a href=\"https:\/\/eur-lex.europa.eu\/legal-content\/PL\/TXT\/?uri=CELEX:32024R2847\" target=\"_blank\" rel=\"noopener\">Regulation (EU) 2024\/2847 \u2014 Polish text on EUR-Lex<\/a><\/p>\n<hr \/>\n<h2>Which products are subject to the CRA and which are not<\/h2>\n<p>The scope of the CRA is determined <strong>per product, not per company<\/strong>. Some of your portfolio may be covered, while some may not. This requires an inventory and a reasoned decision for each item.<\/p>\n<table>\n<thead>\n<tr>\n<th style=\"text-align: left;\">Product type<\/th>\n<th style=\"text-align: center;\">Subject to the CRA?<\/th>\n<th style=\"text-align: left;\">Comments<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td style=\"text-align: left;\">Application installed locally on the customer\u2019s premises<\/td>\n<td style=\"text-align: center;\">As a rule, <strong>yes<\/strong><\/td>\n<td style=\"text-align: left;\">A product with digital elements within the meaning of Article 3(1) CRA<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\">Separately licensed component (library, module, SDK)<\/td>\n<td style=\"text-align: center;\">As a rule, <strong>yes<\/strong><\/td>\n<td style=\"text-align: left;\">Placed on the market separately<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\">Pure SaaS (cloud service without a local component)<\/td>\n<td style=\"text-align: center;\">As a rule, <strong>no<\/strong><\/td>\n<td style=\"text-align: left;\">Covered by <a href=\"https:\/\/sawaryn.com\/en\/publikacje\/nis2-cybersecurity-directive-poland\/\">NIS2<\/a>, not the CRA<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\">Hybrid model (local component + SaaS backend)<\/td>\n<td style=\"text-align: center;\"><strong>Requires analysis<\/strong><\/td>\n<td style=\"text-align: left;\">The decision depends on what exactly is being made available on the market<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\">Open source made available on a non-commercial basis<\/td>\n<td style=\"text-align: center;\">As a rule, <strong>no<\/strong><\/td>\n<td style=\"text-align: left;\">Monetisation by the manufacturer may trigger the CRA (recital 18)<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>If your company sells both a desktop application and pure SaaS, the CRA reporting obligations may apply only to the former. However, the procedure must be ready separately for every product covered by the CRA.<\/p>\n<p><a href=\"https:\/\/digital-strategy.ec.europa.eu\/pl\/policies\/cyber-resilience-act\" target=\"_blank\" rel=\"noopener\">Cyber Resilience Act \u2014 European Commission<\/a><\/p>\n<hr \/>\n<h2>Why the CRA does not replace the GDPR (and vice versa)<\/h2>\n<p>This is where companies most often make mistakes. A single event \u2014 for example, an actively exploited vulnerability that leads to a personal data leak \u2014 may trigger <strong>two independent reporting obligations<\/strong>. One notification does not replace the other.<\/p>\n<table>\n<thead>\n<tr>\n<th style=\"text-align: left;\">Feature<\/th>\n<th style=\"text-align: left;\">CRA (Article 14)<\/th>\n<th style=\"text-align: left;\">GDPR (Articles 33\u201334)<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td style=\"text-align: left;\">What you report<\/td>\n<td style=\"text-align: left;\">An actively exploited vulnerability or a severe product security incident<\/td>\n<td style=\"text-align: left;\"><a href=\"https:\/\/sawaryn.com\/publikacje\/zgloszenie-naruszenia-rodo-wyciek-danych-osobowych\/\">Personal data breach<\/a><\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\">Who you report it to<\/td>\n<td style=\"text-align: left;\">CSIRT + ENISA (single platform)<\/td>\n<td style=\"text-align: left;\">UODO (President of the Personal Data Protection Office)<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\">Deadline for the initial notification<\/td>\n<td style=\"text-align: left;\">24 hours after becoming aware<\/td>\n<td style=\"text-align: left;\">72 hours after becoming aware of the breach (without undue delay)<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\">When you inform individuals<\/td>\n<td style=\"text-align: left;\">Not applicable (the CRA does not provide for such an obligation)<\/td>\n<td style=\"text-align: left;\">Where the breach is likely to result in a high risk to the rights and freedoms of the individual (Article 34 GDPR)<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\">Penalties<\/td>\n<td style=\"text-align: left;\">Requires verification against the Polish-language text of Article 64 CRA and the national implementing legislation<\/td>\n<td style=\"text-align: left;\">Up to EUR 20 million or 4% of annual global turnover<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h3>The mechanism works both ways<\/h3>\n<p>Information from the manufacturer about a vulnerability triggers the customer\u2019s (data controller\u2019s) assessment of its obligations under Articles 33 and 34 GDPR. If you sell software to businesses, your enterprise customers expect you to notify them of a vulnerability quickly enough for them to assess whether a personal data breach has occurred in their systems.<\/p>\n<p>The Supreme Administrative Court confirmed that the disclosure of a set comprising a person\u2019s <strong>first name, surname, address and PESEL number<\/strong> may in itself create a high risk of infringement of the individual\u2019s rights \u2014 triggering the obligation under Article 34(1) GDPR to inform the individual without undue delay (<a href=\"https:\/\/orzeczenia.nsa.gov.pl\/doc\/41E49BE3A3\" target=\"_blank\" rel=\"noopener\">Supreme Administrative Court judgment of 1 July 2022 \u2014 CBOSA<\/a>). For the team classifying incidents, this means that a PESEL number combined with identifying data should automatically increase the risk level under the classification rules, without reassessing it from scratch for each event.<\/p>\n<h3>Two tracks, one internal procedure<\/h3>\n<p>You do not need to build two separate processes from scratch. A safe organisational model is <strong>one internal incident assessment form<\/strong> that checks both regimes in parallel \u2014 with separate notification submission paths. State explicitly that a CRA notification does not replace a GDPR notification. And vice versa.<\/p>\n<p><a href=\"https:\/\/sawaryn.com\/en\/contact\/\">Contact us<\/a> \u2014 we will help you design a procedure that combines both tracks without conflating them.<\/p>\n<hr \/>\n<h2>The third clock: 8 hours under the e-evidence rules<\/h2>\n<p>Regulation <a href=\"https:\/\/eur-lex.europa.eu\/legal-content\/PL\/ALL\/?uri=CELEX:32023R1543\" target=\"_blank\" rel=\"noopener\">(EU) 2023\/1543<\/a> on European Production Orders and European Preservation Orders for electronic evidence will apply from <strong>18 August 2026<\/strong>. For providers of SaaS, hosting services and platforms where data storage or processing is an essential component of the service, this creates a new operational obligation.<\/p>\n<table>\n<thead>\n<tr>\n<th style=\"text-align: left;\">Parameter<\/th>\n<th style=\"text-align: left;\">Standard procedure<\/th>\n<th style=\"text-align: left;\">Urgent procedure<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td style=\"text-align: left;\">Deadline for complying with an EPOC<\/td>\n<td style=\"text-align: left;\">10 days<\/td>\n<td style=\"text-align: left;\">8 hours<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\">Who issues the order<\/td>\n<td style=\"text-align: left;\">Judicial authority of an EU Member State<\/td>\n<td style=\"text-align: left;\">Judicial authority \u2014 marked as urgent<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\">Who complies with it<\/td>\n<td style=\"text-align: left;\">Service provider (or its legal representative in the EU)<\/td>\n<td style=\"text-align: left;\">Service provider<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h3>What this means for your company<\/h3>\n<ol>\n<li>You must designate a <strong>point of contact<\/strong> to receive orders \u2014 a person or team available within hours, not days.<\/li>\n<li>You need a <strong>process for verifying the authenticity<\/strong> of an order. An EPOC is the form set out in Annex I to the Regulation; verification is based on eIDAS mechanisms (recital 87). You may challenge the authenticity and integrity of the document, the absence of required formal information or a conflict with the law of a third country \u2014 but this is not a discretionary refusal. Suspending compliance requires the competent authorities to be informed immediately.<\/li>\n<li>You need a <strong>technical mechanism for extracting data<\/strong> precisely within the scope covered by the order \u2014 no more and no less.<\/li>\n<li>A service provider without an establishment in an EU Member State must designate a <strong>legal representative<\/strong> in writing (Directive <a href=\"https:\/\/eur-lex.europa.eu\/legal-content\/PL\/TXT\/HTML\/?uri=CELEX:32023L1544\" target=\"_blank\" rel=\"noopener\">(EU) 2023\/1544<\/a>).<\/li>\n<\/ol>\n<p>Scenario: a SaaS provider receives an order marked as urgent on Friday evening. It has no point of contact or verification process. Eight hours are spent determining who within the company is authorised to make the decision. The risk: disclosing data beyond the scope of the order or missing the deadline.<\/p>\n<hr \/>\n<h2>What else changes in the second half of 2026 \u2014 context for software manufacturers<\/h2>\n<p>In addition to the CRA and e-evidence rules, a software manufacturer selling to public authorities and businesses should take account of two further regulatory issues.<\/p>\n<h3>UODO inspections: entities operating a BIP<\/h3>\n<p><a href=\"https:\/\/bip.uodo.gov.pl\/pl\/138\/4029\" target=\"_blank\" rel=\"noopener\">UODO\u2019s sectoral inspection plan for 2026<\/a> covers, among other things, entities operating a Public Information Bulletin (BIP) \u2014 particularly the anonymisation of data and the publication of recordings from meetings of the decision-making bodies of local government units.<\/p>\n<p>Formally, the public authority is the data controller. But if the system you provide does not allow the authority to anonymise part of a recording after publication, set an expiry date for its publication or retain an audit trail of operations performed on recordings \u2014 the problem comes back to you as the supplier. The UODO inspection ends with the customer, but the discussion about missing features ends up in your product backlog.<\/p>\n<p>Check three things:<\/p>\n<ol>\n<li>Does your product allow content to be anonymised after publication?<\/li>\n<li>Can an expiry date be set for publication?<\/li>\n<li>Do operations performed on recordings leave an audit trail?<\/li>\n<\/ol>\n<p>Add any gaps to the next sprint.<\/p>\n<h3>AI assessment: per process, not per tool<\/h3>\n<p>On <strong>6 August 2026<\/strong>, UODO published four sets of initial question lists concerning the development and use of AI systems \u2014 <a href=\"https:\/\/bip.uodo.gov.pl\/pl\/138\/4533\" target=\"_blank\" rel=\"noopener\">for SMEs, the public sector, entities building their own models and an extended version covering AI Act obligations<\/a>.<\/p>\n<p>The use of AI must be assessed <strong>separately for each process<\/strong> in which AI is used \u2014 not once \u201cfor the tool&#8221;. If your company carried out a single impact assessment for an \u201cAI module&#8221; two years ago and considered the matter closed, but the model now supports six different processes (including profiling), the assessment does not cover its actual uses.<\/p>\n<p>For external models (e.g. integration with an external language model), determine the parties\u2019 roles: is the model provider your sub-processor or an independent controller? Check whether the <a href=\"https:\/\/sawaryn.com\/en\/publikacje\/safely-entrust-personal-data-processor\/\">data processing agreements<\/a> with customers include authorisation for sub-processing.<\/p>\n<hr \/>\n<h2>Checklist: what to prepare before 11 September 2026<\/h2>\n<p>You can discuss the following measures at a single meeting of the product and security teams. Each has a specific deliverable.<\/p>\n<table>\n<thead>\n<tr>\n<th style=\"text-align: left;\">No.<\/th>\n<th style=\"text-align: left;\">Action<\/th>\n<th style=\"text-align: left;\">Deliverable<\/th>\n<th style=\"text-align: center;\">Priority<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td style=\"text-align: left;\">1<\/td>\n<td style=\"text-align: left;\">Take an inventory of your portfolio and identify which products are products with digital elements within the meaning of the CRA \u2014 make the decision per product and document the rationale<\/td>\n<td style=\"text-align: left;\">List of products classified as CRA\/non-CRA<\/td>\n<td style=\"text-align: center;\">Mandatory<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\">2<\/td>\n<td style=\"text-align: left;\">Draft a one-page vulnerability reporting procedure covering the 24 h and 72 h clocks, naming the decision-maker and their designated alternate<\/td>\n<td style=\"text-align: left;\">Procedure defining the moment of \u201cbecoming aware&#8221;<\/td>\n<td style=\"text-align: center;\">Mandatory<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\">3<\/td>\n<td style=\"text-align: left;\">Combine the CRA procedure with the GDPR breach response process \u2014 a single event triggers two parallel assessments, and one notification does not replace the other<\/td>\n<td style=\"text-align: left;\">Integrated incident assessment form<\/td>\n<td style=\"text-align: center;\">Mandatory<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\">4<\/td>\n<td style=\"text-align: left;\">Verify whether the company falls within the scope of the e-evidence rules; if so, designate a point of contact, an order verification process and a mechanism for extracting data within 8 h<\/td>\n<td style=\"text-align: left;\">Order handling procedure<\/td>\n<td style=\"text-align: center;\">Mandatory<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\">5<\/td>\n<td style=\"text-align: left;\">Review products for public authorities: anonymisation after publication, publication expiry date and an audit trail of operations performed on recordings<\/td>\n<td style=\"text-align: left;\">List of gaps in the product backlog<\/td>\n<td style=\"text-align: center;\">Mandatory<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\">6<\/td>\n<td style=\"text-align: left;\">Add PESEL number + identifying data to the incident classification rules as a combination that automatically increases the risk level<\/td>\n<td style=\"text-align: left;\">Updated classification rules<\/td>\n<td style=\"text-align: center;\">Recommended<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\">7<\/td>\n<td style=\"text-align: left;\">Take an inventory of AI processes and conduct a separate assessment for each process (UODO checklists)<\/td>\n<td style=\"text-align: left;\">Register of AI processes with assessments<\/td>\n<td style=\"text-align: center;\">Recommended<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\">8<\/td>\n<td style=\"text-align: left;\">For external models, determine the parties\u2019 roles and update data processing agreements to cover sub-processing<\/td>\n<td style=\"text-align: left;\">Updated agreements<\/td>\n<td style=\"text-align: center;\">Recommended<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\">9<\/td>\n<td style=\"text-align: left;\">Build a rapid incident reporting feature into the product: scope of the breach, list of individuals, access history<\/td>\n<td style=\"text-align: left;\">Product feature<\/td>\n<td style=\"text-align: center;\">Recommended<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\">10<\/td>\n<td style=\"text-align: left;\">Conduct a dry run: an actively exploited vulnerability on Friday after 17:00 + an urgent data production order with an 8 h deadline<\/td>\n<td style=\"text-align: left;\">Tested procedure<\/td>\n<td style=\"text-align: center;\">Recommended<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<hr \/>\n<h2>How the CRA interacts with NIS2, DORA and the AI Act<\/h2>\n<p>The CRA does not operate in a vacuum. A software manufacturer may be subject to several reporting regimes at the same time \u2014 with different recipients, deadlines and scopes.<\/p>\n<table>\n<thead>\n<tr>\n<th style=\"text-align: left;\">Regime<\/th>\n<th style=\"text-align: left;\">Deadline for the initial notification<\/th>\n<th style=\"text-align: left;\">Recipient<\/th>\n<th style=\"text-align: left;\">Entities covered<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td style=\"text-align: left;\"><strong>CRA<\/strong><\/td>\n<td style=\"text-align: left;\">24 h (early warning)<\/td>\n<td style=\"text-align: left;\">CSIRT + ENISA<\/td>\n<td style=\"text-align: left;\">Manufacturers of products with digital elements<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><strong>GDPR<\/strong><\/td>\n<td style=\"text-align: left;\">72 h after becoming aware of the breach<\/td>\n<td style=\"text-align: left;\">UODO<\/td>\n<td style=\"text-align: left;\">Personal data controllers<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><strong>NIS2<\/strong><\/td>\n<td style=\"text-align: left;\">Requires verification under national implementing legislation<\/td>\n<td style=\"text-align: left;\">National CSIRT<\/td>\n<td style=\"text-align: left;\">Essential and important entities (including cloud services and platforms)<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><strong>AI Act<\/strong><\/td>\n<td style=\"text-align: left;\">15 days after becoming aware<\/td>\n<td style=\"text-align: left;\">Market surveillance authority<\/td>\n<td style=\"text-align: left;\">Providers of <a href=\"https:\/\/sawaryn.com\/en\/publikacje\/high-risk-ai-systems-eu-ai-act\/\">high-risk AI systems<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>There is no provision establishing a single joint notification for all four regimes. Nor is there any provision that exempts you from the remaining obligations after you report to one authority.<\/p>\n<p>A safe model: one internal incident assessment form that checks all four regimes in parallel \u2014 with separate submission paths. The deadline register must account for different starting points (becoming aware, detection, confirmation, determining that a breach has occurred).<\/p>\n<p><a href=\"https:\/\/eur-lex.europa.eu\/legal-content\/pl\/LSU\/?uri=CELEX:32024R2847\" target=\"_blank\" rel=\"noopener\">Regulation (EU) 2024\/2847 \u2014 EUR-Lex summary<\/a> | <a href=\"https:\/\/eur-lex.europa.eu\/legal-content\/EN\/ALL\/?uri=CELEX:32024R1689\" target=\"_blank\" rel=\"noopener\">Regulation (EU) 2024\/1689 \u2014 AI Act on EUR-Lex<\/a><\/p>\n<hr \/>\n<h2>Coordinated vulnerability disclosure \u2014 an obligation, not an option<\/h2>\n<p>The CRA requires manufacturers to implement a <strong>coordinated vulnerability disclosure policy<\/strong> (recital 76) \u2014 a structured process under which vulnerabilities are reported to the manufacturer in a way that enables it to diagnose and remedy them before detailed information is publicly disclosed.<\/p>\n<p>This means that the 24\/72 h reporting procedure is only one element. In addition, the manufacturer needs:<\/p>\n<ol>\n<li>A channel for receiving reports from external security researchers (e.g. a dedicated email address, form or security.txt file).<\/li>\n<li>Rules for communicating with the reporting person \u2014 including a commitment to respond within a specified time.<\/li>\n<li>Optionally: a bug bounty programme as an incentive for responsible reporting.<\/li>\n<\/ol>\n<p>Manufacturers may use bug bounty programmes, but the CRA does not explicitly require them. It does, however, require a vulnerability reporting channel to exist and be documented.<\/p>\n<hr \/>\n<h2>Preparing for the new reporting obligations \u2014 what we can do for you<\/h2>\n<p>Preparing for the CRA, the e-evidence rules and changing GDPR requirements is not a project for the legal department in isolation. It is a project that brings together the product, security, legal and operations teams.<\/p>\n<p>We support software manufacturers and SaaS providers through three service options \u2014 depending on their stage and scale:<\/p>\n<table>\n<thead>\n<tr>\n<th style=\"text-align: left;\">Option<\/th>\n<th style=\"text-align: left;\">What it includes<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td style=\"text-align: left;\"><strong>Operational minimum<\/strong><\/td>\n<td style=\"text-align: left;\">Classification of products under the CRA and e-evidence rules + a single reporting procedure covering the 24\/72 h and 8 h deadlines, aligned with the GDPR breach response process<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><strong>Solid foundation<\/strong><\/td>\n<td style=\"text-align: left;\">Procedures + updates to data processing agreements and incident classification rules + review of notification clauses in agreements with enterprise customers<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><strong>Comprehensive protection<\/strong><\/td>\n<td style=\"text-align: left;\">All of the above + audit of product features (anonymisation, retention, audit trail) + AI assessment per process + a tabletop exercise with the team<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>We do not create documents \u201cjust in case&#8221;. We design procedures where risks actually arise \u2014 and test them against scenarios that could occur in your company.<\/p>\n<p><a href=\"https:\/\/sawaryn.com\/en\/contact\/\">Contact us<\/a> \u2014 together, we will determine which of your company\u2019s products are covered by the new obligations and provide a ready-to-use set of procedures before 11 September 2026.<\/p>\n<hr \/>\n<h2>Three clocks, two tracks, one decision to make now<\/h2>\n<p>The CRA introduces reporting obligations that cannot be handled without a designated decision-maker, an alternate and a ready-to-use reporting process. Alongside the CRA\u2019s 24 h and 72 h clocks is the 8 h clock under the e-evidence rules \u2014 and the separate 72 h GDPR track. None of these notifications replaces the others.<\/p>\n<p>The scope of the CRA is determined per product. You must have the procedure ready before the first incident \u2014 because when the first incident occurs, there will be no time to write it.<\/p>\n<p>If you want to organise your reporting obligations, update your agreements and test your procedures against scenarios relevant to your company \u2014 <a href=\"https:\/\/sawaryn.com\/en\/contact\/\">contact us<\/a>.<\/p>\n<hr \/>\n<h2>Frequently asked questions<\/h2>\n<p><strong>Which of my products are subject to the CRA and which are not?<\/strong><br \/>\nThe CRA covers products with digital elements \u2014 software or hardware intended to be connected to a device or network, including separately licensed components. Pure SaaS services (without a local component) are generally subject to NIS2, not the CRA. Hybrid models (local component + SaaS backend) require individual analysis. You make the decision per product, not per company \u2014 and it is worth documenting the rationale in writing.<\/p>\n<p><strong>When does the 24-hour deadline for the early warning begin?<\/strong><br \/>\nFrom the moment the manufacturer becomes aware of the actively exploited vulnerability. Not from confirmation, not from the completion of the technical analysis and not from a management decision. If your security team has received credible information, the clock is running. The CRA allows information to be provided in stages: you report what you know and supplement it in subsequent steps.<\/p>\n<p><strong>Does one notification satisfy both the CRA and the GDPR?<\/strong><br \/>\nNo. These are two separate obligations to different authorities (CSIRT + ENISA vs. UODO), with different deadlines and triggering conditions. A single event may trigger both obligations \u2014 but one notification does not replace the other. A safe model is one internal incident assessment form with two separate submission paths.<\/p>\n<p><strong>What do I submit within 24 hours if I do not yet know the scale of the problem?<\/strong><br \/>\nAn early warning \u2014 information that an actively exploited vulnerability exists, identifying the Member States in which the product has been made available. You submit a more complete notification (the nature of the exploitation, measures taken and measures available to users) within 72 hours. The final report is due within 14 days after a corrective measure is made available.<\/p>\n<p><strong>As a SaaS provider, can I receive a direct data production order with an 8-hour deadline?<\/strong><br \/>\nYes \u2014 from 18 August 2026 under Regulation (EU) 2023\/1543 on European Production Orders. In urgent cases, the deadline for complying with an EPOC is 8 hours. A service provider without an establishment in an EU Member State must designate a legal representative. The lack of a point of contact and a process for verifying the order\u2019s authenticity is an operational risk that should be eliminated in advance.<\/p>\n<p><strong>What penalties apply for failing to report a vulnerability within the CRA deadline?<\/strong><br \/>\nThe CRA requires Member States to establish rules on penalties (Article 64), but the specific amounts and percentage-of-turnover thresholds must be verified against the Polish-language text of the act and the national implementing legislation. Under the GDPR, penalties for breaching the obligations to report a personal data breach and inform individuals can reach EUR 20 million or 4% of annual global turnover. Liability for breaching the CRA reporting obligations is separate from liability for breaching the essential cybersecurity requirements.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Learn which software products fall under the CRA, when its 24- and 72-hour reporting clocks start, and why GDPR breach notifications remain separate.<\/p>\n","protected":false},"author":13,"featured_media":3814,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":"","sip_alt_url":"","sip_en_pl_url":"","sip_pair_uuid":"1f0968b5-0ade-4da1-812a-188aedb6668c","sip_pair_state":"draft_ready"},"categories":[1578],"tags":[1533,1446,1540,1543,1531,1546,1534],"specialization":[1215],"practice_area":[],"class_list":["post-5339","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-gdpr","tag-data-breach","tag-gdpr","tag-internal-procedure","tag-it-ai-and-ip-law","tag-personal-data-protection","tag-risk-assessment","tag-uodo-en","specialization-gdpr"],"acf":[],"_links":{"self":[{"href":"https:\/\/sawaryn.com\/en\/wp-json\/wp\/v2\/posts\/5339","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/sawaryn.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/sawaryn.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/sawaryn.com\/en\/wp-json\/wp\/v2\/users\/13"}],"replies":[{"embeddable":true,"href":"https:\/\/sawaryn.com\/en\/wp-json\/wp\/v2\/comments?post=5339"}],"version-history":[{"count":8,"href":"https:\/\/sawaryn.com\/en\/wp-json\/wp\/v2\/posts\/5339\/revisions"}],"predecessor-version":[{"id":5400,"href":"https:\/\/sawaryn.com\/en\/wp-json\/wp\/v2\/posts\/5339\/revisions\/5400"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/sawaryn.com\/en\/wp-json\/wp\/v2\/media\/3814"}],"wp:attachment":[{"href":"https:\/\/sawaryn.com\/en\/wp-json\/wp\/v2\/media?parent=5339"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/sawaryn.com\/en\/wp-json\/wp\/v2\/categories?post=5339"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/sawaryn.com\/en\/wp-json\/wp\/v2\/tags?post=5339"},{"taxonomy":"specialization","embeddable":true,"href":"https:\/\/sawaryn.com\/en\/wp-json\/wp\/v2\/specialization?post=5339"},{"taxonomy":"practice_area","embeddable":true,"href":"https:\/\/sawaryn.com\/en\/wp-json\/wp\/v2\/practice_area?post=5339"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}