# EU Cyber Resilience Act (CRA) Vulnerability Reporting Obligations — A Research Report on Preparing for the September 11, 2026 Effective Date

> The EU Cyber Resilience Act (CRA) brings its Article 14 reporting obligations into effect on September 11, 2026. This report, grounded in primary sources, sets out how Korean companies should prepare for the 24-hour, 72-hour, and 14-day notification deadlines and for SBOM and conformity assessment requirements.

---

LLMS index: [llms.txt](/llms.txt)

---

<div class="alert alert-info" role="alert">


This article was written with Claude Code, and the key facts cited here were cross-checked against primary sources.
</div>



> **Summary**
>
> The EU Cyber Resilience Act (CRA — Regulation (EU) 2024/2847) is the first comprehensive product security regulation in EU history, imposing horizontal cybersecurity obligations on every "product with digital elements" (PDE) placed on the EU market. Entering into force on December 10, 2024, the Regulation applies in phases. From September 11, 2026, the Article 14 reporting obligations take effect, requiring manufacturers, importers, and distributors to notify ENISA (the European Union Agency for Cybersecurity) and member state CSIRTs of actively exploited vulnerabilities and severe security incidents within a staged 24-hour, 72-hour, and 14-day deadline structure. If a reporting workflow is not operational by this date, a company risks a fine of up to €15 million or 2.5% of worldwide annual turnover, and a Korean company becomes subject to these obligations the moment it places a product on the EU market. <a id="a1-ref-1"></a>[A1](#a1), <a id="b1-ref-1"></a>[B1](#b1), <a id="e1-ref-1"></a>[E1](#e1)

---

## 1. Why September 11, 2026 Matters for Korean Companies

September 11, 2026 is the first application date for the CRA's Article 14 reporting obligations. On the same day, ENISA's Single Reporting Platform (SRP) also goes live. <a id="a1-ref-2"></a>[A1](#a1), <a id="b4-ref-1"></a>[B4](#b4) The CRA's remaining essential obligations, including CE marking and conformity assessment, are due by December 11, 2027, but the reporting workflow must be in place 15 months ahead of that deadline.

The weight this date carries for Korean companies comes from the CRA's legal character. The CRA is not a Directive that member states must transpose into national law; it is a Regulation with direct effect, applying immediately upon entry into the EU market without any separate national implementing legislation. <a id="a1-ref-3"></a>[A1](#a1) A company headquartered in Korea that exports directly to the EU without an EU legal entity does not escape coverage. It is also worth noting that legacy products — products already placed on the EU market — are covered as well. <a id="e1-ref-2"></a>[E1](#e1)

As of June 2026, about three months remain before the reporting obligation takes effect. ENISA has said it will hold a testing period but has not yet released an official schedule, and it has announced that an operations manual will be provided sometime in June 2026. ENISA has also stated explicitly that, at this stage, it does not provide an API for SRP integration. <a id="b4-ref-2"></a>[B4](#b4) Companies that assumed automated integration will need to redesign their reporting process around manual submission to the platform by a human operator.

---

## 2. Structure of the CRA

### 2.1 Legislative Background and Entry-into-Force Timeline

The CRA's official title is *Regulation (EU) 2024/2847 on horizontal cybersecurity requirements for products with digital elements*. It was first announced in President Ursula von der Leyen's State of the Union address in September 2021, and the European Commission proposed the legislative text on September 15, 2022. The European Parliament adopted it in plenary on March 12, 2024 by a vote of 517 in favor to 12 against, and the Council gave its final adoption on October 10 of the same year, followed by signature on October 23 and publication in the Official Journal of the EU on November 20. The Regulation entered into force on December 10, 2024. <a id="a1-ref-4"></a>[A1](#a1), <a id="b1-ref-2"></a>[B1](#b1)

![Legislative progression from the September 2021 State of the Union announcement to full application in December 2027. The reporting obligation takes effect first, in September 2026, with the remaining obligations following 15 months later](./legislative-timeline-en.png)

**Figure 1.** CRA legislative and implementation timeline *(Source: Regulation (EU) 2024/2847, EC Legislative Train)*

The open source community's advocacy stood out during the legislative process. During the 2022–2023 drafting stages, the Eclipse Foundation, the Open Source Initiative (OSI), the Document Foundation, and others warned that an unclear definition of "commercial activity" could push compliance burdens onto volunteer developers. The provisional agreement of December 2023 introduced the concept of an "open-source steward" along with exemption clauses, easing some of these concerns, but the scope of coverage for small-scale redistributors remains a matter of dispute. <a id="d1-ref-1"></a>[D1](#d1)

### 2.2 Scope of Application (Art. 2–3)

The CRA applies to "products with digital elements" (PDE). This covers hardware and software capable of logical or physical data connection to a device or network, and includes software components placed on the market independently. <a id="b3-ref-1"></a>[B3](#b3)

Some products fall outside the scope. The main examples are free and open-source software supplied without commercial activity, and products already covered by stricter sector-specific cybersecurity regulation, such as medical devices or automobiles. Even so, the CRA may apply in a "complementary" capacity to products already subject to existing cybersecurity regulation, so a sector-by-sector judgment is required. <a id="a1-ref-6"></a>[A1](#a1), <a id="e2-ref-1"></a>[E2](#e2)

![A decision flow that asks in turn whether the product is placed on the EU market, has digital elements, involves commercial activity, and is already covered by priority sector-specific legislation — a match on any of the exclusion questions removes the product from scope](./scope-decision-en.png)

**Figure 2.** CRA scope determination flow *(Source: CRA Art. 2–3, Implementing Regulation (EU) 2025/2392)*

### 2.3 Phased Application

Full application of the CRA does not occur at a single point in time.

| Date | Obligation | Legal Basis |
|---|---|---|
| 2024-12-10 | Entry into force | CRA Art. 71 |
| 2026-06-11 | Provisions on notification of conformity assessment bodies (Chapter IV) | CRA Art. 71(2) |
| **2026-09-11** | **Article 14 reporting obligation + SRP goes live** | CRA Art. 14, 16 |
| 2027-12-11 | Full application of CE marking, conformity assessment, and essential requirements | CRA Art. 71(2) |

<a id="a1-ref-8"></a>[A1](#a1), <a id="b3-ref-2"></a>[B3](#b3)

What must be in place by September 11, 2026 is not product certification but a vulnerability and incident reporting workflow. The deadline for CE marking and conformity assessment is 15 months later, on December 11, 2027.

---

## 3. Manufacturer Obligations (Art. 13)

### 3.1 Annex I Essential Requirements

Article 13 requires manufacturers to meet the essential cybersecurity requirements set out in CRA Annex I. These requirements fall into two broad groups. <a id="a1-ref-9"></a>[A1](#a1), <a id="b3-ref-3"></a>[B3](#b3)

**Part I — Product security requirements**: placed on the market without known exploitable vulnerabilities, no default passwords, provision of security updates, application of the principle of least privilege, data protection, minimization of attack surfaces, resilience-by-design, and provision of records of access to and modification of personal data.

**Part II — Vulnerability handling requirements**: identifying and documenting vulnerabilities, maintaining an SBOM, providing patches promptly and distributing them free of charge, a Coordinated Vulnerability Disclosure (CVD) policy, reporting of exploited vulnerabilities and incidents (Art. 14), and monitoring for vulnerabilities across the full product lifecycle.

No harmonized standards for these requirements have been finalized yet, so manufacturers must implement them directly against the functional requirements in the CRA text itself. The *CRA Requirements Standards Mapping* (2024), jointly published by ENISA and the JRC, maps these requirements to existing standards, with ISO/IEC 30111 (vulnerability handling), ISO/IEC 29147 (vulnerability disclosure), and NIST SP 800-218 (SSDF) serving as the main reference points. <a id="b5-ref-1"></a>[B5](#b5), <a id="c1-ref-1"></a>[C1](#c1), <a id="c2-ref-1"></a>[C2](#c2), <a id="c6-ref-1"></a>[C6](#c6)

### 3.2 Support Period

Manufacturers must provide security support for the product's expected lifetime after it is placed on the market, for a minimum of five years. For products with an expected lifetime of less than five years, that shorter period may serve as the support period. The support period must be stated explicitly on the product, and vulnerability handling and the provision of security updates are mandatory throughout it. <a id="a1-ref-10"></a>[A1](#a1), <a id="b3-ref-4"></a>[B3](#b3)

### 3.3 SBOM Requirements

CRA Annex I Part II mandates a Software Bill of Materials (SBOM). Manufacturers must generate an SBOM for every released version and keep it in a machine-readable format, ready for requests from a Market Surveillance Authority. There is no obligation to disclose the SBOM to third parties, but it must be provided to the Market Surveillance Authority on request. <a id="a1-ref-11"></a>[A1](#a1)

SPDX and CycloneDX have established themselves as the de facto standard formats. SPDX was standardized as ISO/IEC 5962:2021 (based on SPDX v2.2.1; the current specification is v3.0), <a id="c3-ref-1"></a>[C3](#c3), <a id="c4-ref-1"></a>[C4](#c4) and CycloneDX, a specification maintained by OWASP, saw ECMA-424 2nd Edition (based on v1.7) published on December 10, 2025. <a id="c5-ref-1"></a>[C5](#c5) No official CRA-level implementing act for an SBOM schema has been issued as of June 2026. Technical Guideline TR-03183-2 v2.1.0, published in August 2025 by Germany's Federal Office for Information Security (Bundesamt für Sicherheit in der Informationstechnik, BSI), serves as a practical reference point for field mapping to a CRA-conformant SBOM. <a id="g1-ref-1"></a>[G1](#g1)

---

## 4. Reporting Obligations (Art. 14) — Effective 2026-09-11

### 4.1 Notification Triggers

Article 14 defines two categories of events that trigger a manufacturer's notification obligation. <a id="a1-ref-12"></a>[A1](#a1), <a id="b2-ref-1"></a>[B2](#b2)

One is an actively exploited vulnerability. The trigger is not the vulnerability's mere theoretical existence but the confirmed point at which an attacker is actually exploiting it. The other is a severe incident — an event that has caused, or is likely to cause, serious operational disruption, loss, or damage affecting the security of the product.

Beyond manufacturers, importers and distributors must also notify the manufacturer of relevant information when they discover non-compliance or become aware of an incident.

### 4.2 The Three-Stage Deadline (24h/72h/14d)

![A timeline counting from the moment of awareness: an early warning within 24 hours, a notification within 72 hours, and a final report within 14 days for a vulnerability or one month for an incident](./reporting-deadlines-en.png)

**Figure 3.** CRA Article 14 reporting deadlines *(Source: CRA Art. 14, EC "CRA — Reporting obligations")*

The required content differs at each stage. <a id="a1-ref-14"></a>[A1](#a1), <a id="b2-ref-3"></a>[B2](#b2)

| Stage | Deadline | Required Content |
|---|---|---|
| Early Warning | Within 24 hours of awareness | Affected member states, whether linked to malicious activity |
| Notification | 72 hours | General nature of the vulnerability or incident, available mitigation measures, sensitivity assessment |
| Final Report — Vulnerability | 14 days after mitigation measures become available | Severity and scope of impact, threat actor information, content of the security update |
| Final Report — Incident | One month after Notification | Detailed description of the incident, threat type and root cause, mitigation measures applied |

The CRA text makes clear that the 24-hour deadline does not require vulnerability classification or full resolution. Its purpose is simply to flag the existence of the issue as an early warning. Microenterprises and small enterprises may be exempted from fines for failing to meet the 24-hour deadline. <a id="a1-ref-15"></a>[A1](#a1)

### 4.3 Single Reporting Platform (Art. 16)

All Article 14 notifications go through the Single Reporting Platform (SRP). Operated by ENISA, the SRP automatically routes a single manufacturer submission to both the coordinator Computer Security Incident Response Team (CSIRT) of the member state where the manufacturer's main establishment is located and to ENISA itself. <a id="b4-ref-3"></a>[B4](#b4), <a id="a1-ref-16"></a>[A1](#a1)

In procuring the SRP, ENISA required a forward-looking architecture capable of integrating with the incident and vulnerability reporting systems of NIS2 and DORA. The design goal extends beyond CRA obligations alone, aiming for a platform that can interoperate with adjacent regulatory regimes.

![A circular flow in which a manufacturer reports to ENISA's Single Reporting Platform, which fans out to the member state CSIRT and ENISA, and the Market Surveillance Authority orders the manufacturer to take corrective action or recall the product](./actor-flow-en.png)

**Figure 4.** Stakeholder interactions in the CRA reporting system *(Source: CRA Art. 13–16, Delegated Regulation (EU) 2026/881)*

### 4.4 Conditions for Delaying CSIRT-to-CSIRT Dissemination (Delegated Regulation 2026/881)

Delegated Regulation (EU) 2026/881, adopted on December 11, 2025 (published in the Official Journal on April 20, 2026), sets out the conditions under which a member state CSIRT need not immediately disseminate a notification it has received via the Single Reporting Platform to other CSIRTs. <a id="a2-ref-2"></a>[A2](#a2) Delay is permitted where an assessment of the nature of the notified information justifies it, where the receiving CSIRT cannot guarantee the confidentiality of the information, or where the Single Reporting Platform itself has been compromised or is temporarily unable to operate. Beyond that, delay is allowed only for the "period strictly necessary," and only when the risk cannot be mitigated through tools such as the Traffic Light Protocol (TLP) or the Permissible Actions Protocol (PAP).

The 24-hour deadline for a manufacturer's notification to a CSIRT is unaffected by this Delegated Regulation. What the Delegated Regulation touches is the further dissemination step between CSIRTs, where it introduces a security-based relief mechanism.

### 4.5 Parallel Application with GDPR and NIS2

A CRA reporting obligation can arise alongside reporting obligations under other regulations. Where the data compromised by a vulnerability or incident includes personal data, a CRA notification does not substitute for the 72-hour notification obligation to the supervisory authority under Article 33 of the General Data Protection Regulation (GDPR). <a id="a5-ref-1"></a>[A5](#a5) The two notifications must go through separate channels to separate recipients — the data protection authority on one side, the CSIRT/ENISA on the other.

The same holds for operators of essential and important services covered by the NIS2 Directive (Directive (EU) 2022/2555) that become aware of a vulnerability or incident in their own products. Both a CRA report and a NIS2 report may be required simultaneously. The Digital Omnibus package's "report once, share many" model is being discussed as a way to unify the two reporting obligations, but it has not yet been settled in legislation. <a id="a4-ref-1"></a>[A4](#a4), <a id="e2-ref-2"></a>[E2](#e2)

---

## 5. Conformity Assessment and CE Marking (2027-12-11)

December 11, 2027 is the deadline for conformity assessment. The pathway differs by risk class. Default-class products may self-assess to issue an EU Declaration of Conformity and affix the CE marking. Important Class I products may either self-assess by applying EU harmonized standards or obtain an assessment from a third-party Conformity Assessment Body (CAB). Important Class II and critical-class products require enhanced examination by a CAB. <a id="a1-ref-18"></a>[A1](#a1), <a id="b3-ref-5"></a>[B3](#b3)

In February 2025, ENISA published *Cyber Resilience Act implementation via EUCC and its applicable technical elements*, analyzing pathways for using EU Common Criteria (EUCC) certification in CRA conformity assessment. <a id="b6-ref-1"></a>[B6](#b6)

From June 11, 2026, the provisions on notification of conformity assessment bodies apply. Each member state must designate a notifying authority by this date, and the accreditation process begins so that a sufficient number of notified bodies to carry out third-party conformity assessment are in place by December 11, 2026. <a id="b3-ref-6"></a>[B3](#b3)

Penalties for non-compliance vary by the type of violation. The most serious violations — failure to meet essential requirements, breach of reporting obligations — can draw a fine of up to €15 million or 2.5% of worldwide annual turnover, whichever is greater, and can also result in an order to withdraw the product from the EU market. <a id="a1-ref-19"></a>[A1](#a1), <a id="e1-ref-3"></a>[E1](#e1)

---

## 6. Standards and Framework Mapping

The CRA sets out only essential requirements and delegates technical detail to harmonized standards. CEN/CENELEC JTC 13 WG 9 is developing European harmonized standards (EN) for the CRA, targeting publication of the horizontal standards by August 30, 2026 and the vertical standards by October 30, 2026. The horizontal standards proceed as the prEN 40000-1 series, consisting of vocabulary (prEN 40000-1-1), principles (prEN 40000-1-2), vulnerability handling (prEN 40000-1-3), and general security requirements (prEN 40000-1-4). The final list of cited standards has not yet been settled, so the table below can be used as a set of candidate mappings for the time being. <a id="b5-ref-2"></a>[B5](#b5)

| Standard / Framework | Steward | CRA Mapping |
|---|---|---|
| ISO/IEC 30111:2019 | ISO/IEC | Vulnerability handling procedures — Annex I Part II "vulnerability handling" requirements |
| ISO/IEC 29147:2018 | ISO/IEC | Coordinated Vulnerability Disclosure (CVD) — Art. 14 notification workflow |
| SPDX v3.0 (ISO/IEC 5962) | Linux Foundation / ISO | SBOM standard format |
| CycloneDX v1.7 (ECMA-424) | OWASP / Ecma | SBOM standard format — native support for Vulnerability Exploitability eXchange (VEX) |
| NIST SP 800-218 (SSDF) | NIST | Secure-by-design practices — functionally aligned with Annex I Part I requirements |
| prEN 40000-1-3 (draft) | CEN/CENELEC | CRA harmonized horizontal standard — vulnerability handling, targeting publication 2026-08-30 |
| BSI TR-03183-2 v2.1.0 | BSI (Germany) | Technical guideline for CRA-conformant SBOM field mapping |

<a id="c1-ref-2"></a>[C1](#c1), <a id="c2-ref-2"></a>[C2](#c2), <a id="c3-ref-2"></a>[C3](#c3), <a id="c4-ref-2"></a>[C4](#c4), <a id="c5-ref-2"></a>[C5](#c5), <a id="c6-ref-2"></a>[C6](#c6), <a id="g1-ref-2"></a>[G1](#g1), <a id="c7-ref-1"></a>[C7](#c7)

The European Vulnerability Database (EUVD), implementing Article 12 of the NIS2 Directive, was formally launched by ENISA on May 13, 2025. <a id="f1-ref-1"></a>[F1](#f1) It can serve as a primary monitoring source for the CRA's "vulnerability monitoring" requirement. The EUVD uses its own identifier (`EUVD-YYYY-NNNNNN`) while also recording the corresponding CVE ID and CVSS score. It is a separate system from the SRP: the SRP is the channel through which manufacturers notify authorities, while the EUVD is a public database. <a id="b4-ref-4"></a>[B4](#b4), <a id="f2-ref-1"></a>[F2](#f2)

---

## 7. Recent Developments (2025–2026)

Since entry into force in December 2024, the regulatory landscape has taken shape along three tracks: delegated regulations, implementing regulations, and guidance.

Implementing Regulation (EU) 2025/2392 was adopted on November 28, 2025 and entered into force on December 21. It finalized the technical definitions dividing "important" and "critical" products — as referenced in CRA Annexes III and IV — into 28 categories, placed across the three tiers of Class I, Class II, and critical. This Regulation is the primary legal basis manufacturers use to determine the conformity assessment pathway for their products. <a id="a3-ref-2"></a>[A3](#a3)

Delegated Regulation (EU) 2026/881 was adopted on December 11, 2025 and published in the Official Journal on April 20, 2026. It codifies the conditions under which CSIRT-to-CSIRT dissemination of notifications may be delayed (see §4.4). <a id="a2-ref-3"></a>[A2](#a2)

Guidance documents have arrived in two stages. The Commission's first official FAQ was published on December 3, 2025 (updated December 19), offering the first — non-binding — clarification of the scope and iterativeness of risk assessment and of the "intended purpose" concept. The first draft guidance under CRA Article 26 followed on March 3, 2026. Running to 75 pages, with roughly a quarter devoted to defining the open-source steward, the draft covered remote data processing solutions, free and open-source software, the support period, and the CRA's interrelationship with other regulations such as NIS2 and DORA. The consultation closed on March 31, but the final version has not been issued as of June 2026. <a id="e3-ref-1"></a>[E3](#e3)

The open source community's collective response became visible on April 2, 2024, when seven foundations — the Apache Software Foundation, the Blender Foundation, the Eclipse Foundation, OpenSSL, the PHP Foundation, the Python Software Foundation, and the Rust Foundation — announced they would jointly develop common standards for secure software development. The effort was led by the Eclipse Foundation AISBL in Brussels and evolved, on September 24 of the same year, into the Open Regulatory Compliance Working Group (ORC WG), which published a white paper laying out the scope of a steward's obligations. OpenSSF published its direction for aligning SBOM standards on October 22, 2025. <a id="f3-ref-1"></a>[F3](#f3), <a id="d1-ref-2"></a>[D1](#d1)

The most persistent point of contention is the practical value of 24-hour notification. Security researchers, HackerOne among them, have repeatedly argued since 2024 that notifying authorities of a vulnerability's existence before a patch is ready risks exposing an unmitigated vulnerability. <a id="e4-ref-1"></a>[E4](#e4) Delegated Regulation (EU) 2026/881 only introduced conditions for delaying CSIRT-to-CSIRT dissemination; it left the manufacturer's 24-hour deadline to the CSIRT itself untouched.

---

## 8. A Korean Company Perspective — What to Do in the Next Three Months

### 8.1 Determining Whether the CRA Applies

The first step is to determine whether the reporting obligation, due September 11, 2026, applies to the company at all. Check in turn: whether the product is distributed in the EU market, whether the product is a product with digital elements, and whether stricter sector-specific cybersecurity legislation already applies. EU distribution covers direct sales, resale, and OEM supply alike, and the CRA applies even without an EU legal entity if the Korean headquarters exports directly. Software or hardware capable of data connection with a network or a device qualifies as a product with digital elements. Areas already covered by stricter regulation, such as medical devices or automotive safety, may be excluded from CRA application.

Legacy products are covered too. Many companies overlook the fact that the reporting obligation, effective September 11, applies even to products already placed on the EU market. <a id="e1-ref-4"></a>[E1](#e1)

### 8.2 Preparation Steps

There is no need to have certification in place by September 11. What is needed is a reporting workflow. The company needs a human structure and technical connection able to send an early warning within 24 hours of becoming aware of a vulnerability or incident, and an on-call rotation, decision-making authority, and an external communications owner should all be designated in advance.

A pipeline that automatically generates and retains an SBOM in SPDX or CycloneDX format for every released version is also needed by September 11. The field mapping in BSI TR-03183-2 v2.1.0 can serve as a practical reference. <a id="g1-ref-3"></a>[G1](#g1)

ENISA has stated that it does not provide an API for SRP integration at this stage (as of June 2026). Since the operations manual is expected during June, companies should build a manual submission process rather than assuming automated integration, and watch for ENISA's manual and its announcements about the testing period.

A process for monitoring the EUVD (`https://euvd.enisa.europa.eu`) against the company's own product components is also needed. The company must be able to handle both the CVE ID and `EUVD-YYYY-NNNNNN` identifier schemes.

By December 11, 2027, companies need to go a step further: CE marking, conformity assessment, selecting a CAB matched to the product's class (for Class I and above), and issuing a declaration of conformity once the harmonized standards are published. Companies should track the publication of CEN/CENELEC's horizontal standards (targeting August 30, 2026) and vertical standards (targeting October 30, 2026).

### 8.3 Comparison with Other Jurisdictions

| Item | EU CRA | United States (EO 14028 / CISA KEV) | UK PSTI Act | Korea Software Supply Chain Guideline |
|---|---|---|---|---|
| Scope | All PDE in the EU market | Federal procurement software (advisory for the private sector) | Consumer connectable products | All software (non-mandatory) |
| Legal force | EU Regulation — direct effect | Executive Order / binding operational directive (BOD) | Statute | Administrative guideline |
| Reporting deadline | 24h/72h/14d | Deadline set per KEV entry | Obligation only to maintain a reporting channel | None |
| SBOM | Mandatory (SPDX/CycloneDX) | Recommended for federal procurement software (NTIA) | None | Recommended, based on SSDF |
| Effective | 2026-09-11 (reporting) / 2027-12-11 (full) | 2021-05 | 2024-04-29 | 2024-05 |

<a id="c6-ref-3"></a>[C6](#c6), <a id="e2-ref-3"></a>[E2](#e2)

The CRA's most notable feature is its horizontal application, cutting across IoT, software, and embedded systems alike, combined with direct effect. Korea's Software Supply Chain Guideline 1.0, based on NIST SSDF, recommends 30 checklist items and SBOM procedures; because the CRA's essential requirements are functionally aligned with the SSDF, a system built to follow the Korean guideline is a starting point for CRA readiness. That said, the Korean guideline is advisory, whereas the CRA is a legal obligation backed by a fine regime, and the CRA adds a separate reporting obligation on top.

---

## 9. Conclusion and Recommendations

September 11, 2026 is the day the CRA first imposes a substantive compliance obligation on manufacturers. CE marking and conformity assessment are due by December 11, 2027, but the reporting workflow must be complete before then.

For a Korean company, the priority is first to confirm whether its products fall within CRA scope, and if so, to determine — under the criteria of Implementing Regulation (EU) 2025/2392 — which class applies: default, important, or critical. The class determines both the 2027 conformity assessment pathway and the lead time required to prepare for it.

Building the reporting infrastructure and internal playbook comes next. The SRP operations manual has not yet been released, but the human structure and internal procedures can be designed right now regardless. Since ENISA has said it will not provide an integration API, companies should set up a manual submission process for the platform rather than automated integration, and watch for the manual and announcements about the testing period.

SBOM pipeline automation must be finished by September 11. Without an SBOM in SPDX or CycloneDX format automatically generated and retained for every released version, a company will find itself lacking the very software composition information the reporting obligation requires. <a id="a1-ref-20"></a>[A1](#a1), <a id="b2-ref-4"></a>[B2](#b2), <a id="e2-ref-4"></a>[E2](#e2), <a id="e4-ref-2"></a>[E4](#e4)

---

## References

### A. Primary Legislative and Regulatory Texts

<a id="a1"></a>**A1.** European Parliament and Council (2024). *Regulation (EU) 2024/2847 of 23 October 2024 on horizontal cybersecurity requirements for products with digital elements (Cyber Resilience Act)*. Official Journal of the European Union, OJ L, 2024/2847, 20.11.2024. <https://eur-lex.europa.eu/eli/reg/2024/2847/oj/eng> (accessed: 2026-05-12). <a href="#a1-ref-1" onclick="event.preventDefault(); history.back(); return false;" title="Back to text">↩</a>

<a id="a2"></a>**A2.** European Commission (2025). *Commission Delegated Regulation (EU) 2026/881 of 11 December 2025 supplementing Regulation (EU) 2024/2847 with regard to the conditions for delaying dissemination of notifications of actively exploited vulnerabilities and severe incidents*. Published 20 April 2026. <https://eur-lex.europa.eu/eli/reg_del/2026/881/oj> (accessed: 2026-05-12). <a href="#a2-ref-1" onclick="event.preventDefault(); history.back(); return false;" title="Back to text">↩</a>

<a id="a3"></a>**A3.** European Commission (2025). *Commission Implementing Regulation (EU) 2025/2392 of 28 November 2025 laying down technical descriptions of categories of important and critical products with digital elements*. OJ L, 2025/2392. <https://eur-lex.europa.eu/legal-content/EN/TXT/PDF/?uri=OJ:L_202502392> (accessed: 2026-05-12). <a href="#a3-ref-1" onclick="event.preventDefault(); history.back(); return false;" title="Back to text">↩</a>

<a id="a4"></a>**A4.** European Parliament and Council (2022). *Directive (EU) 2022/2555 of 14 December 2022 on measures for a high common level of cybersecurity across the Union (NIS2 Directive)*. OJ L 333, 27.12.2022. <https://eur-lex.europa.eu/eli/dir/2022/2555/oj/eng> (accessed: 2026-05-12). <a href="#a4-ref-1" onclick="event.preventDefault(); history.back(); return false;" title="Back to text">↩</a>

<a id="a5"></a>**A5.** European Parliament and Council (2016). *Regulation (EU) 2016/679 — General Data Protection Regulation (GDPR)*. OJ L 119, 4.5.2016. <https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CELEX:32016R0679> (accessed: 2026-05-12). <a href="#a5-ref-1" onclick="event.preventDefault(); history.back(); return false;" title="Back to text">↩</a>

---

### B. Official Documents from Issuing Bodies

<a id="b1"></a>**B1.** European Commission, DG CNECT (2026). *Cyber Resilience Act — Shaping Europe's digital future*. <https://digital-strategy.ec.europa.eu/en/policies/cyber-resilience-act> (accessed: 2026-05-12). <a href="#b1-ref-1" onclick="event.preventDefault(); history.back(); return false;" title="Back to text">↩</a>

<a id="b2"></a>**B2.** European Commission, DG CNECT (2026). *Cyber Resilience Act — Reporting obligations*. <https://digital-strategy.ec.europa.eu/en/policies/cra-reporting> (accessed: 2026-05-12). <a href="#b2-ref-1" onclick="event.preventDefault(); history.back(); return false;" title="Back to text">↩</a>

<a id="b3"></a>**B3.** European Commission, DG CNECT (2024). *The Cyber Resilience Act — Summary of the legislative text*. <https://digital-strategy.ec.europa.eu/en/policies/cra-summary> (accessed: 2026-05-12). <a href="#b3-ref-1" onclick="event.preventDefault(); history.back(); return false;" title="Back to text">↩</a>

<a id="b4"></a>**B4.** ENISA (2026). *Single Reporting Platform (SRP)*. <https://www.enisa.europa.eu/topics/product-security-and-certification/single-reporting-platform-srp> (accessed: 2026-05-12). <a href="#b4-ref-1" onclick="event.preventDefault(); history.back(); return false;" title="Back to text">↩</a>

<a id="b5"></a>**B5.** ENISA & Joint Research Centre (2024). *Cyber Resilience Act Requirements Standards Mapping — Joint Analysis*. April 2024. <https://www.enisa.europa.eu/publications/cyber-resilience-act-requirements-standards-mapping> (accessed: 2026-05-12). <a href="#b5-ref-1" onclick="event.preventDefault(); history.back(); return false;" title="Back to text">↩</a>

<a id="b6"></a>**B6.** ENISA (2025). *Cyber Resilience Act implementation via EUCC and its applicable technical elements*. 26 February 2025. <https://certification.enisa.europa.eu/publications/cyber-resilience-act-implementation-eucc-and-its-applicable-technical-elements_en> (accessed: 2026-05-12). <a href="#b6-ref-1" onclick="event.preventDefault(); history.back(); return false;" title="Back to text">↩</a>

---

### C. Standards and Frameworks

<a id="c1"></a>**C1.** ISO/IEC (2019). *ISO/IEC 30111:2019 — Information technology — Security techniques — Vulnerability handling processes*. Edition 2. <https://www.iso.org/standard/69725.html> (accessed: 2026-05-12). <a href="#c1-ref-1" onclick="event.preventDefault(); history.back(); return false;" title="Back to text">↩</a>

<a id="c2"></a>**C2.** ISO/IEC (2018). *ISO/IEC 29147:2018 — Information technology — Security techniques — Vulnerability disclosure*. Edition 2. <https://www.iso.org/standard/72311.html> (accessed: 2026-05-12). <a href="#c2-ref-1" onclick="event.preventDefault(); history.back(); return false;" title="Back to text">↩</a>

<a id="c3"></a>**C3.** ISO/IEC (2021). *ISO/IEC 5962:2021 — Information technology — SPDX® Specification V2.2.1*. <https://www.iso.org/standard/81870.html> (accessed: 2026-05-12). <a href="#c3-ref-1" onclick="event.preventDefault(); history.back(); return false;" title="Back to text">↩</a>

<a id="c4"></a>**C4.** The Linux Foundation / SPDX Project (2024). *SPDX Specifications (current: v3.0)*. <https://spdx.dev/specifications/> (accessed: 2026-05-12). <a href="#c4-ref-1" onclick="event.preventDefault(); history.back(); return false;" title="Back to text">↩</a>

<a id="c5"></a>**C5.** OWASP Foundation / Ecma International (2025). *CycloneDX Specification v1.7 / ECMA-424*, 2nd Edition. ECMA-424 published 2025-12-10. <https://cyclonedx.org/specification/overview/> (accessed: 2026-05-12). <a href="#c5-ref-1" onclick="event.preventDefault(); history.back(); return false;" title="Back to text">↩</a>

<a id="c6"></a>**C6.** Souppaya, M., Scarfone, K., Dodson, D. — NIST (2022). *Secure Software Development Framework (SSDF) Version 1.1: Recommendations for Mitigating the Risk of Software Vulnerabilities*. NIST SP 800-218. DOI: 10.6028/NIST.SP.800-218. <https://csrc.nist.gov/publications/detail/sp/800-218/final> (accessed: 2026-05-12). <a href="#c6-ref-1" onclick="event.preventDefault(); history.back(); return false;" title="Back to text">↩</a>

<a id="c7"></a>**C7.** OpenSSF Global Cyber Policy Working Group (2026). *CRA Standards Map*. <https://policy.openssf.org/CRA/standards.html> (accessed: 2026-06-09). — *Used to verify the numbering and status of CEN/CENELEC JTC 13 WG 9's prEN 40000-1 series (horizontal harmonized standards).* <a href="#c7-ref-1" onclick="event.preventDefault(); history.back(); return false;" title="Back to text">↩</a>

---

### D. Academic and Policy Research

<a id="d1"></a>**D1.** OpenSSF Best Practices WG / Global Cyber Policy WG (2025). *Cyber Resilience Act (CRA) Brief Guide for Open Source Software (OSS) Developers*. Lead author: David A. Wheeler. <https://best.openssf.org/CRA-Brief-Guide-for-OSS-Developers.html> (accessed: 2026-05-12). <a href="#d1-ref-1" onclick="event.preventDefault(); history.back(); return false;" title="Back to text">↩</a>

---

### E. Industry and Law Firm Analysis

<a id="e1"></a>**E1.** Bird & Bird LLP (2026). *CRA's phased entry into application starts in September 2026*. Bird & Bird Insights. <https://www.twobirds.com/en/insights/2026/cra%E2%80%99s-phased-entry-into-application-starts-in-september-2026> (accessed: 2026-05-12). <a href="#e1-ref-1" onclick="event.preventDefault(); history.back(); return false;" title="Back to text">↩</a>

<a id="e2"></a>**E2.** DLA Piper — Blum, L. & Moylan Burke, L. (2026). *Cyber Resilience Act: What you need to know and what you need to be doing*. 19 February 2026. <https://www.dlapiper.com/en/insights/publications/2026/02/cyber-resilience-act-what-you-need-to-know-and-what-you-need-to-be-doing> (accessed: 2026-05-12). <a href="#e2-ref-1" onclick="event.preventDefault(); history.back(); return false;" title="Back to text">↩</a>

<a id="e3"></a>**E3.** DLA Piper (2026). *Cyber Resilience Act: Commission unveils draft implementation guidance*. Law in Tech. <https://www.dlapiper.com/en-us/insights/publications/law-in-tech/2026/cyber-resilience-act> (accessed: 2026-05-12). <a href="#e3-ref-1" onclick="event.preventDefault(); history.back(); return false;" title="Back to text">↩</a>

<a id="e4"></a>**E4.** HackerOne — Eldering, B. (2026). *EU Cyber Resilience Act: Preparing Your VDP for 2026 Reporting Requirements*. <https://www.hackerone.com/blog/cyber-resilience-act-vdp-2026-reporting-readiness> (accessed: 2026-05-12). <a href="#e4-ref-1" onclick="event.preventDefault(); history.back(); return false;" title="Back to text">↩</a>

---

### F. Press and Official Announcements (Supplementary)

<a id="f1"></a>**F1.** ENISA (2025). *Consult the European Vulnerability Database to enhance your digital security!* News release, 13 May 2025. <https://www.enisa.europa.eu/news/consult-the-european-vulnerability-database-to-enhance-your-digital-security> (accessed: 2026-05-12). <a href="#f1-ref-1" onclick="event.preventDefault(); history.back(); return false;" title="Back to text">↩</a>

<a id="f2"></a>**F2.** European Commission (2025). *EU launches a European vulnerability database to boost its digital security*. <https://digital-strategy.ec.europa.eu/en/news/eu-launches-european-vulnerability-database-boost-its-digital-security> (accessed: 2026-05-12). <a href="#f2-ref-1" onclick="event.preventDefault(); history.back(); return false;" title="Back to text">↩</a>

<a id="f3"></a>**F3.** Eclipse Foundation (2024). *The Open Source Community is Building Cybersecurity Processes for CRA Compliance*. Life at Eclipse, 2 April 2024. <https://eclipse-foundation.blog/2024/04/02/open-source-community-cra-compliance/> (accessed: 2026-05-29). <a href="#f3-ref-1" onclick="event.preventDefault(); history.back(); return false;" title="Back to text">↩</a>

---

### G. Member State Technical Guidance

<a id="g1"></a>**G1.** Bundesamt für Sicherheit in der Informationstechnik (BSI) (2025). *Technical Guideline TR-03183-2 v2.1.0 — Cyber Resilience Requirements for Manufacturers and Products, Part 2: Software Bill of Materials (SBOM)*. August 2025. Summary compiled by: Sbomify, *EU Cyber Resilience Act (CRA) SBOM Requirements*. <https://sbomify.com/compliance/eu-cra/> (accessed: 2026-05-12). <a href="#g1-ref-1" onclick="event.preventDefault(); history.back(); return false;" title="Back to text">↩</a>