Back to the blog

Cybersecurity Reporting in Poland: The CRA’s 24-Hour Clock and Other 2026 Deadlines

For software suppliers in Poland: assess CRA product coverage, plan 24- and 72-hour reports, and keep GDPR breach and e-evidence responses distinct.

A vulnerability is confirmed at 17:40 on Friday. The technical analysis will not be finished before Monday. The 24-hour reporting clock started on Friday—and it does not pause for the weekend. From September 11, 2026, this scenario is no longer hypothetical for manufacturers covered by Regulation (EU) 2024/2847, the Cyber Resilience Act (CRA).

If your company sells software to businesses or public authorities in Poland, several distinct regulatory obligations may affect you in the second half of 2026. None applies simply because a company calls itself an “IT company.” Each has its own scope, which you need to assess. This article explains the CRA’s 24-hour and 72-hour reporting stages, why a CRA notification does not replace a GDPR notification, and what to prepare before an incident occurs.

Key terms for readers dealing with Poland

Term What it means
CRA (Cyber Resilience Act) Regulation (EU) 2024/2847, which sets EU cybersecurity rules for products with digital elements. As an EU regulation, it applies directly without national transposition.
Product with digital elements Software or computer hardware, including related remote data-processing solutions and components placed on the market separately—Article 3(1) CRA.
Actively exploited vulnerability A vulnerability that the manufacturer knows is already being used by attackers. That knowledge starts the 24-hour clock.
CSIRT A Computer Security Incident Response Team. CRA notifications go to a designated CSIRT and ENISA. Poland has CSIRT NASK, CSIRT GOV and CSIRT MON; the relevant allocation must be confirmed under national rules.
ENISA The European Union Agency for Cybersecurity, which receives CRA notifications through the single reporting platform.
Articles 33 and 34 GDPR Rules on notifying a personal data breach to the supervisory authority and, where the risk is high, informing affected individuals. In Poland, the supervisory authority is UODO, the Personal Data Protection Office.
EPOC (European Production Order) An order under Regulation (EU) 2023/1543 addressed directly to a service provider. The compliance deadline is 10 days, or eight hours in urgent cases.

Regulation (EU) 2024/2847—Polish text

What changes under the CRA from September 2026

The 24-hour and 72-hour reporting stages

From September 11, 2026, manufacturers of products with digital elements must report actively exploited vulnerabilities and severe incidents affecting product security. Article 14 CRA sets out three reporting stages:

Stage Deadline Information to provide
Early warning 24 hours after becoming aware The existence of the vulnerability and the EU Member States where the product has been made available.
Notification 72 hours after becoming aware General product information, the nature of the exploitation, remedial measures taken and measures available to users.
Final report 14 days after a corrective measure is made available for an actively exploited vulnerability; one month for a severe incident A description of the vulnerability, including severity and impact; information about those exploiting it; and details of updates made available.

Notifications go to the CSIRT designated as coordinator and to ENISA through a single reporting platform under Article 16 CRA. Delegated Regulation (EU) 2026/881 addresses the platform’s details.

The clock starts with awareness, not a completed investigation

The operational point is the starting time. The 24-hour period runs from when the manufacturer becomes aware of an actively exploited vulnerability—not from completion of a technical investigation or a management decision.

In the Friday 17:40 scenario, if the security team has received credible information, the clock is running. The analysis may take three days, but the early warning must be sent by Saturday at 17:40.

You do not need to know the full extent of the problem at the early-warning stage. The CRA and GDPR allow information to be provided in stages: report what you know, then supplement it as the facts develop.

Notification alone does not increase liability

Article 17(4) CRA states that the mere act of notifying under Article 14 or 15 does not increase the liability of the person making the notification. A notification should not be treated as an admission simply because it was submitted.

Regulation (EU) 2024/2847—Polish text on EUR-Lex

Which products fall within the CRA?

Assess CRA coverage product by product, not company by company. One part of your portfolio may be covered while another is not. Inventory each item and document the reason for its classification.

Product type Generally within the CRA? Point to assess
Application installed locally by a customer Yes, as a rule A product with digital elements under Article 3(1) CRA.
Separately licensed library, module or SDK Yes, as a rule The component is placed on the market separately.
Pure SaaS, without a local component No, as a rule The source identifies NIS2, rather than the CRA, as the relevant framework.
Local component with a SaaS backend Requires analysis The answer depends on what is made available on the market.
Open source made available noncommercially No, as a rule Monetization by the manufacturer may bring the CRA into play (recital 18).

A business selling both a desktop application and pure SaaS may therefore have CRA reporting duties for only the desktop product. Its reporting procedure must nevertheless be ready for each covered product.

Cyber Resilience Act—European Commission

Why CRA reporting does not replace GDPR breach reporting

One event can trigger two independent assessments and notifications. An actively exploited product vulnerability, for example, might also lead to a personal data breach. Reporting the vulnerability under the CRA does not discharge a GDPR obligation, or vice versa.

Question CRA, Article 14 GDPR, Articles 33–34
What is reported? An actively exploited vulnerability or severe product security incident. A personal data breach.
Who receives the report? The designated CSIRT and ENISA, through the single platform. The relevant supervisory authority—UODO in Poland.
Initial deadline 24 hours after becoming aware. Within 72 hours after becoming aware of the breach, without undue delay.
When are individuals informed? The CRA does not provide for this notification. Where the breach is likely to result in a high risk to individuals’ rights and freedoms, under Article 34 GDPR.
Penalties The amounts and turnover thresholds require verification against the Polish-language text of Article 64 CRA and the relevant national act. Up to EUR 20 million or 4% of annual global turnover, as stated in the approved source.

A manufacturer’s warning also matters to its customers. If a customer is the data controller—the party responsible for deciding how personal data is processed—it needs timely information to assess whether the vulnerability caused a breach in its own systems and whether Articles 33 or 34 GDPR apply. Enterprise customers will expect notice early enough to make that assessment.

For Polish incident classification, the PESEL number needs particular attention. PESEL is Poland’s personal identification number. Poland’s Supreme Administrative Court held that disclosure of a person’s first name, surname, address and PESEL number may in itself create a high risk to that person’s rights, triggering notification to the individual without undue delay under Article 34(1) GDPR (judgment of July 1, 2022, in the CBOSA case database). The source’s practical recommendation is to make a PESEL number combined with identifying information an automatic risk escalator in incident-classification rules.

You do not need two entirely separate internal processes. Use one incident assessment form to check the CRA and GDPR in parallel, but maintain separate routes for submitting notifications. State expressly in the procedure that neither notification replaces the other.

Contact us if you need a procedure that coordinates both tracks without conflating them.

The third clock: eight hours under the EU e-evidence rules

Regulation (EU) 2023/1543 on European Production Orders and European Preservation Orders for electronic evidence applies from August 18, 2026. It creates an operational issue for providers of SaaS, hosting and platforms where storing or processing data is an essential part of the service.

EPOC requirement Standard case Urgent case
Compliance deadline 10 days Eight hours
Issuing authority A judicial authority of an EU Member State A judicial authority, with the order marked urgent
Recipient responsible for compliance The service provider or its legal representative in the EU The service provider

If the rules apply to your business, prepare four capabilities:

  1. A point of contact: designate a person or team able to receive and route orders within hours, not days.
  2. Order verification: establish how to check authenticity and integrity. An EPOC uses the form in Annex I to the regulation; recital 87 refers to eIDAS mechanisms. The source identifies authenticity, integrity, missing required formal information and conflicts with third-country law as possible grounds to raise. These are not a general right to refuse an order. Suspending compliance requires the competent authorities to be informed without delay.
  3. Precise data extraction: be able to retrieve exactly the data covered by the order—neither more nor less.
  4. An EU legal representative where required: a provider without an establishment in an EU Member State must designate a legal representative in writing under Directive (EU) 2023/1544.

Consider a SaaS provider receiving an urgent order on Friday evening. If it has no contact point or verification route, the eight-hour period may be consumed deciding who can act. The resulting risks include missing the deadline or disclosing more data than the order covers.

Two further issues for software supplied to Polish organizations

UODO inspections and Public Information Bulletin systems

UODO’s 2026 sectoral inspection plan includes entities operating a Biuletyn Informacji Publicznej (BIP), Poland’s Public Information Bulletin used by public bodies to publish official information. The plan focuses in part on anonymizing data and publishing recordings of meetings of local government decision-making bodies.

The public authority is formally the data controller. But a supplier may still face a practical product problem if its system cannot anonymize part of a recording after publication, set a publication expiry date or preserve an audit trail of changes to recordings. UODO inspects the customer; missing functionality can then become an item in the supplier’s backlog.

Check whether your product can:

  1. Anonymize material after publication.
  2. Set an expiry date for publication.
  3. Record an audit trail of operations on recordings.

Put any gaps into the next product sprint.

Assess AI use by process, not just by tool

On August 6, 2026, UODO published four sets of initial questions on developing and using AI systems: for SMEs, the public sector, organizations building their own models, and an extended version covering AI Act obligations.

Assess AI use separately for each process in which it is deployed. A single assessment of an “AI module” completed two years ago does not cover its actual uses if that module now supports six processes, including profiling.

Where you integrate an external model, such as a third-party language model, establish the parties’ data-protection roles. Is the model provider your subprocessor or a separate controller? Check whether your customer data processing agreements authorize subprocessing.

Checklist: what to prepare before September 11, 2026

The product and security teams can review these actions together. Each should produce a concrete deliverable.

No. Action Deliverable Priority
1 Inventory the portfolio, classify each product under the CRA and document the reasoning. CRA/non-CRA product list. Essential
2 Write a one-page vulnerability-reporting procedure covering the 24-hour and 72-hour stages. Name a decision-maker and alternate, and define when the company becomes aware. Reporting procedure. Essential
3 Connect CRA triage with GDPR breach response. Assess both regimes for the same event without treating one notification as a substitute for the other. Integrated incident assessment form. Essential
4 Check whether the e-evidence rules apply. If they do, designate a contact point and establish order verification and eight-hour data-extraction processes. Order-handling procedure. Essential
5 Review public-sector products for post-publication anonymization, publication expiry dates and audit trails for recordings. Product-backlog gap list. Essential
6 Make a PESEL number combined with identifying data an automatic risk escalator. Updated incident-classification rules. Recommended
7 Inventory AI-enabled processes and assess each separately using UODO’s question lists. AI process register and assessments. Recommended
8 Determine the roles of external model providers and update agreements where subprocessing authorization is needed. Updated agreements. Recommended
9 Consider a rapid incident-reporting feature showing the breach scope, affected individuals and access history. Product feature. Recommended
10 Run an exercise combining an actively exploited vulnerability after 17:00 on a Friday with an urgent eight-hour production order. Tested procedures. Recommended

How the CRA fits alongside NIS2, DORA and the AI Act

The CRA does not operate in isolation. A software manufacturer may face several reporting frameworks, with different triggers, recipients and deadlines. DORA is another framework to consider where relevant, although the approved source does not set out its reporting timetable.

Framework Initial reporting deadline identified in the source Recipient Entities identified in the source
CRA 24 hours for an early warning. CSIRT and ENISA. Manufacturers of products with digital elements.
GDPR 72 hours after becoming aware of a personal data breach. UODO in Poland. Personal data controllers.
NIS2 Must be checked against national implementing rules. National CSIRT. Essential and important entities, including certain cloud and platform services.
AI Act 15 days after becoming aware. Market surveillance authority. Providers of high-risk AI systems.

There is no single notification under these four frameworks that automatically satisfies them all. Nor does reporting to one authority, by itself, remove obligations under the others.

The practical model is one internal incident assessment form that checks each potentially relevant framework, followed by separate submission routes. A deadline register should also distinguish the different events that start a clock: awareness, detection, confirmation or determination that a breach has occurred.

Regulation (EU) 2024/2847—EUR-Lex summary · Regulation (EU) 2024/1689—the AI Act

Coordinated vulnerability disclosure is part of the preparation

The CRA requires manufacturers to implement a coordinated vulnerability disclosure policy (recital 76): a structured way for vulnerabilities to be reported so the manufacturer can investigate and remedy them before details become public.

The 24-hour and 72-hour authority-reporting procedure is therefore only part of the system. Manufacturers also need:

  1. A channel for reports from external security researchers, such as a dedicated email address, form or security.txt file.
  2. Rules for communicating with reporters, including a stated response period.
  3. Optionally, a bug bounty program to encourage responsible reporting.

The CRA does not expressly require a bug bounty program. The source does, however, identify a documented vulnerability-reporting channel as required.

How we can help

CRA reporting, e-evidence orders and GDPR breach response require coordination across product, security, legal and operations teams. We support software manufacturers and SaaS providers at three levels:

Option Scope
Operational minimum Product classification under the CRA and assessment of the e-evidence rules, plus a procedure covering the CRA’s 24-hour and 72-hour stages and urgent eight-hour orders, aligned with GDPR breach response.
Solid foundation Procedures, updated data processing agreements and incident-classification rules, and a review of notification clauses in enterprise customer contracts.
Comprehensive preparation The above, plus a product-feature review covering anonymization, retention and audit trails; AI assessments by process; and a team tabletop exercise.

We focus on procedures where operational risk arises and test them against realistic scenarios, rather than producing documents for their own sake. Contact us to establish which products and services are covered and prepare workable procedures before September 11, 2026.

The decision to make before an incident

The CRA’s 24-hour and 72-hour stages need a named decision-maker, an alternate and a submission route that works outside ordinary business hours. The e-evidence rules may add an eight-hour order deadline, while a personal data breach can start a separate GDPR track. None of these notifications replaces the others.

Start by classifying your products and services, then test who will make and carry out each decision. Once an incident occurs, there may be no time to design the process. If you need to coordinate reporting, update agreements or test procedures, contact us.

Frequently asked questions

Which of my products are covered by the CRA?
Assess each product separately. Locally installed applications and separately marketed components are generally covered; pure SaaS without a local component generally is not, with NIS2 identified in the source as the relevant framework. Hybrid offerings need individual analysis. Record the reasoning for each classification.

When does the CRA’s 24-hour clock begin?
When the manufacturer becomes aware of an actively exploited vulnerability—not when management approves a response or the technical analysis is complete. Credible information received by the security team can start the clock. Report the information available and supplement it later.

Can one notification satisfy both the CRA and GDPR?
No. The triggers, recipients and deadlines differ. Use one internal assessment to identify both obligations, then follow separate submission routes where each applies.

What can I report within 24 hours if the investigation is incomplete?
Send the early warning with the information then available, including the existence of the actively exploited vulnerability and the Member States where the product was made available. The fuller notification follows within 72 hours; for an actively exploited vulnerability, the final report follows within 14 days after a corrective measure is made available.

Can a SaaS provider receive a direct order with an eight-hour deadline?
Yes, where Regulation (EU) 2023/1543 applies and the European Production Order is urgent. From August 18, 2026, an applicable provider should be ready to receive and verify an order, determine who can act and extract only the data within its scope. A provider without an establishment in an EU Member State must designate a legal representative in writing.

What penalties apply if a CRA vulnerability report is late?
The source states that Article 64 CRA requires Member States to set penalty rules, while the specific amounts and turnover thresholds require verification against the Polish-language text and the relevant national act. It separately states that GDPR penalties for breach-reporting and individual-notification obligations can reach EUR 20 million or 4% of annual global turnover. Liability for CRA reporting obligations is distinct from liability for the CRA’s substantive cybersecurity requirements.

RECOMMENDED

this could be interesting to you

Real work, real outcomes - compliance, technology, transactions, and the everyday legal support businesses run on.