
In an increasingly interconnected world, digital products serve as critical entry points into networks and infrastructures. The CRA responds to growing cybersecurity concerns by transforming security-by-design from a recommendation into a legal obligation.
Manufacturers must now demonstrate that their products meet essential cybersecurity requirements from design and development to deployment, maintenance, and end-of-life.
The CRA ensures:
Security throughout the entire product lifecycle
Consistent requirements across the EU’s internal market
Greater consumer and business confidence
Clear, transparent accountability for manufacturers, importers, and distributors
The CRA applies to any product with digital elements, including:
Consumer IoT devices
Industrial control systems
Embedded software
Enterprise applications
Cloud-based solutions
To ensure consistent security, the CRA introduces requirements based on:
Lifecycle risk management and mandatory cybersecurity risk assessments
Secure design and development to ensure products are placed on the market with fewer vulnerabilities
Vulnerability handling and updates throughout a support period that generally defaults to at least 5 years
Technical documentation and transparency
Our services are tailored for:
Manufacturers of consumer IoT, industrial or embedded devices
Software developers and platform providers
Importers and distributors seeking to understand obligations
A key compliance pathway is Module A – Internal Production Control, where manufacturers verify conformity internally and document every step. This is typically used for "Default" or uncategorized products.
Products aligned with harmonized European standards (hENs) may benefit from Presumption of Conformity, simplifying the path to market. However, where standards remain incomplete, additional assessments and risk analyses are required.
While no harmonised standards have been officially published in the Official Journal of the EU as of early 2026, several key standards are expected soon. The horizontal standards for principles of cyber resilience and vulnerability handling have a deadline of 30 August 2026. Vertical standards for important and critical products are expected by 30 October 2026. However, CCLab actively tracks the development of candidate standards, such as the EN 18031 series, and helps clients align early.
As an accredited evaluation laboratory with extensive industry experience, CCLab provides full-spectrum support for organizations preparing for CRA compliance. We help you translate regulatory obligations into practical, actionable processes.
Identify gaps between your product’s current security posture and CRA Annex I essential requirements, including "secure by design" and "no known vulnerabilities"
We guide you through the Internal Production Control process, including:
Our experts apply up-to-date knowledge of standards under development within CEN,
CENELEC, and ETSI (M/606).
Ensure your vulnerability management, update mechanisms, and incident response procedures meet Annex I expectations.
We provide tailored training programs to help your teams integrate CRA requirements from the earliest development stages. At CCLab, we act not only as evaluators but as strategic partners, supporting you from concept to market placement.
The CRA imposes clear responsibilities, including:
Security-by-design integration
Documented risk management
Regular security updates
Vulnerability handling and notification processes
Technical documentation per Annex II
EU Declaration of Conformity and CE marking
Compliance is continuous, not a one-time event. Manufacturers must also adhere to strict reporting timelines: an early warning within 24 hours of becoming aware of an actively exploited vulnerability or severe incident, followed by a detailed notification within 72 hours. Our experts help you maintain ongoing conformity in line with regulatory expectations.


The CRA becomes fully applicable on 11 December 2027, but early preparation is essential. Critical milestones occur in 2026: on 11 June 2026, provisions for notifying Conformity Assessment Bodies begin to apply, and on 11 September 2026, the mandatory reporting obligations for vulnerabilities and incidents commence.
Organizations that begin integrating CRA requirements today will:
Simplify future compliance efforts
Reduce costs and development delays
Strengthen cybersecurity resilience
Gain a strategic market advantage
CCLab is here to support you at every step.
The Cyber Resilience Act (CRA) is a European Union regulation that sets horizontal cybersecurity requirements for all products with digital elements — including connected hardware and software, from IoT devices to standalone software applications. Unlike sector-specific laws, the CRA ensures a unified minimum level of cybersecurity across the entire EU market.
It requires manufacturers to consider cybersecurity throughout the entire product lifecycle — from design and development to maintenance and vulnerability handling. This means security can no longer be treated as an afterthought but must be built into products by design (“security by design” and “security by default”).
Although the CRA formally entered into force on 10 December 2024, it will only become fully applicable as of 11 December 2027. However, reporting obligations for vulnerabilities and incidents apply starting 11 September 2026. This transition period allows manufacturers and other stakeholders to adjust their development, compliance, and support processes in line with the new cybersecurity requirements. This transition period allows manufacturers and other stakeholders to adapt their development, quality assurance, and compliance processes to the new legal requirements.
After this date, any product with digital elements that is not compliant with CRA requirements cannot be legally placed on the EU market. Companies should therefore already start preparing by identifying which of their products fall under the CRA, and how existing standards and risk management processes can be aligned with it.
The RED Delegated Act (EU) 2022/30 — which currently defines cybersecurity requirements for certain radio-connected products — will be repealed on 11 December 2027, the same day the CRA becomes fully applicable.
From that point onward, the CRA will serve as the overarching legal framework for product cybersecurity, avoiding duplication of obligations. Until then, manufacturers must still comply with the RED-DA, and existing RED-DA compliance work will still support future CRA compliance.
Both the RED-DA and the CRA impose mandatory cybersecurity requirements enforceable via CE marking.
Many devices fall under both frameworks (e.g., smart home devices, routers, industrial gateways). Once the CRA applies, it will take precedence, creating a single streamlined cybersecurity framework.
“Module A” refers to the Internal Production Control conformity assessment procedure under EU law. Under the CRA, it allows manufacturers to self-declare conformity if they fully implement relevant harmonised standards. This is the typical assessment method for "Default" or uncategorized products like smart speakers or photo editors. If no applicable standards exist or are only partially relevant, third-party involvement or additional justification may be necessary to demonstrate compliance.
Manufacturers using Module A must implement an internal process to ensure their product meets all essential cybersecurity requirements. They then issue an EU Declaration of Conformity, taking full legal responsibility for the product’s compliance. This declaration confirms the product meets all applicable EU harmonization legislation, including the CRA.However, this simplified route is only possible if the manufacturer fully applies harmonised standards (hEN) referenced in the Official Journal of the EU. Without such standards, achieving full conformity becomes much more complex and riskier.
“Presumption of Conformity” means that a product is presumed to meet CRA requirements if it complies with harmonised standards (hENs) published in the Official Journal of the European Union. These standards are developed by recognised bodies like ETSI and CENELEC, based on a Standardisation Request (M/606). However, PoC only applies to the elements covered by the standard — manufacturers must address any remaining risks separately.
By following these standards, manufacturers can demonstrate compliance in a straightforward, recognised way — avoiding the need to prove from scratch that every security measure meets CRA requirements.
However, PoC only applies to the aspects covered by the standards. The presumption is "proportional"; if harmonized standards only partially cover the essential requirements, the manufacturer must prove compliance for the remaining requirements through other technical specifications or solutions. If a harmonised standard does not address a specific security risk, the manufacturer must perform additional assessments and document them in their technical file.
Note: As of now, no harmonised standards have been officially published under the CRA. This means that full Presumption of Conformity is not yet possible for any product. Manufacturers must either wait for these standards to be published in the Official Journal or use other assessment methods to demonstrate compliance in the interim.The list of references for harmonized standards can be monitored through the European Commission's dedicated summary page.
No, not all products can currently achieve full Presumption of Conformity. Under the CRA, only Class I products listed in Annex III (so-called “important products with digital elements”) can achieve full PoC by applying harmonised standards. If a Class I product manufacturer does not apply (or only partially applies) harmonized standards, they must use a third-party assessment procedure involving a Notified Body (Module B+C or H).
For other product classes (e.g., Class II or those not listed in Annex III/IV), only partial PoC can be achieved through standards, meaning only certain requirements are covered. This is mainly because the full set of CRA-related harmonised standards is still being developed and will take time to finalise.
Currently, no harmonised standards are available under the CRA. This means that even Class I products listed in Annex III cannot yet claim full Presumption of Conformity. The European Commission is in the process of mandating and reviewing candidate standards (e.g., EN 18031 series), but until they are formally published in the OJEU, manufacturers must rely on alternative conformity methods and maintain appropriate documentation.
Harmonised standards serve as the technical backbone for demonstrating CRA compliance. The well-known EN 18031 series, originally created for the RED-DA, will likely form the basis for the CRA’s future harmonised standards. Additionally, new horizontal standards are being drafted specifically for the CRA, including prEN 40000-1-2 (Principles for Cyber Resilience) and prEN 40000-1-3 (Vulnerability Handling).
This continuity ensures that current efforts to align with RED-DA are not lost; on the contrary, they position manufacturers well for the upcoming CRA framework.
By applying harmonised standards, manufacturers can more easily prove that their products meet the CRA’s cybersecurity and vulnerability management requirements, ensuring both legal certainty and consumer trust across the EU market.
Important: While several candidate standards (such as the EN 18031-1/-2/-3 series) are being developed to support CRA compliance, none have yet been harmonised. The Official Journal of the EU will list recognised standards once they are approved. Until then, CRA compliance must be demonstrated through custom technical documentation and risk assessments.
The European Union Cybersecurity Certification (EUCC) scheme serves as a key compliance pathway for the CRA. While the CRA sets the legal requirements, the EUCC provides a standardized, Common Criteria-based framework to certify that ICT products meet unified security benchmarks.
For "Critical" products listed in Annex IV of the CRA, the European Commission may mandate the use of European cybersecurity certification, such as the EUCC, to demonstrate conformity. Furthermore, achieving an EUCC certificate at the "substantial" or "high" assurance level grants a presumption of conformity for the CRA requirements it covers. The EUCC also aligns with CRA expectations by integrating proactive vulnerability management and patch management protocols.
What to do next: Manufacturers of high-risk or critical digital products should evaluate if their current certification goals align with EUCC to streamline their future CRA compliance path.