
5
min reading time
Under the traditional Common Criteria framework, certification was often treated as a linear ladder. EAL5 was "better" than EAL4.
The EUCC changes the focus. It aligns directly with the EU Cybersecurity Act (CSA), classifying products based on the risk associated with their intended use.
This means your certification strategy must now start with a risk profile, not just a target number.
Crucially, achieving these levels grants you a "presumption of conformity" with upcoming regulations. As we explored in Cyber Resilience Act & EUCC Explained: Key Differences, Overlaps and Compliance Pathways, this alignment is key for long-term market access under the Cyber Resilience Act (CRA).
If your product targets general commercial use, "Substantial" is likely your new baseline.
This category maps to Evaluation Assurance Levels EAL1 through EAL3. But the EAL number is only half the story. The real driver here is AVA_VAN (Vulnerability Analysis).
For Substantial assurance, you must meet AVA_VAN.1 or AVA_VAN.2.
What this means for your engineering team:
This level effectively filters out "low-hanging fruit" vulnerabilities. It proves your door is locked, but it doesn't guarantee the lock is pick-proof against a professional thief.

This is where the game changes.
"High" assurance is not just "Substantial Plus." It requires a completely different rigorous approach to design and testing.
This category maps to EAL4 through EAL7. The critical difference lies in the vulnerability analysis, which must reach AVA_VAN.3, AVA_VAN.4, or AVA_VAN.5.
The "High" Assurance Reality Check:
If you are building smartcards, hardware security modules (HSMs), or critical network components, "High" is not optional. It is the entry ticket. This mirrors the strict requirements seen in the digital identity sector, as discussed in EUCC Behind eIDAS 2.0, where devices like Qualified Signature Creation Devices (QSCDs) mandate high-assurance evaluations to guarantee legal validity.
There is a trap in the EUCC that many manufacturers miss.
In the old world, you certified a product version and walked away. Under EUCC, particularly for Substantial and High levels, you must demonstrate continuous vulnerability management.
You cannot just pass the test once. You must have a process to:
If you fail to maintain this lifecycle security, your certificate can be revoked. The "fire and forget" era of certification is over.
Checklist: Which Level Do You Need?
Choosing between Substantial and High defines your budget and timeline. Use this quick check:
Misinterpreting these levels is expensive. We see developers aim for EAL5 when EAL4+ is sufficient, or target "Substantial" without realizing their specialized device requires "High" level domain testing.
CCLab acts as your navigator through this transition.
We ensure your documentation isn't just a paperwork exercise but a valid proof of security that stands up to EU scrutiny.

The transition to EUCC is not just a regulatory update. It is a market reset.
"Substantial" proves you have covered the basics against common threats. "High" proves you are ready for the frontline of cyber warfare.
Understanding the difference, and specifically the AVA_VAN requirements, is the only way to build a certification strategy that works.
The takeaway: Do not guess your assurance level. Align your EAL and vulnerability analysis strategy with your market's risk profile today to secure your place in the European market tomorrow.
Need a visual overview?Download our EUCC Study 2026 for the most up-to-date information on the new scheme.


Download EUCC Study 2026 for the most important and up-to-date information about the new European Union Cybersecurity Certification Scheme


This downloadable infographics introduces the Common Criteria Evaluation process to you. Explore now for free.

The era of unregulated smart devices has officially come to an end. With the European Union having rolled out stringent regulations like the Cyber Resilience Act (CRA), manufacturers can no longer treat cybersecurity as an afterthought. Whether you are producing smart cameras, wearable health trackers, or connected home appliances, navigating this evolving regulatory landscape is critical. Fortunately, a globally recognized standard has emerged to cut through the complexity: ETSI EN 303 645. This guide breaks down exactly how this foundational standard acts as your security passport, ensuring your devices meet the rigorous compliance demands of today's market.
min reading time

This article provides a comprehensive guide to meeting consumer IoT security standards using the ETSI EN 303 645 framework. It explains why this standard has become the global baseline for compliance, serving as a critical foundation for regulations like the UK PSTI Act and the upcoming EU Cyber Resilience Act (CRA). The post breaks down the 13 essential security provisions, such as banning default passwords and securing software updates, and outlines a structured assessment path from scope definition to accredited testing. Learn how to treat security as a design constraint to avoid market delays, leverage gap analysis for early detection of vulnerabilities, and turn technical compliance into a trusted competitive edge for your smart devices.
min reading time

The Cyber Resilience Act (CRA) is a landmark EU regulation that establishes a horizontal framework for the cybersecurity of products with digital elements (hardware and software). This sweeping EU cybersecurity law represents a massive shift for the industry. Its goal is to ensure that products are placed on the market without known exploitable vulnerabilities and that manufacturers remain responsible for cybersecurity throughout the product's entire lifecycle. With all requirements of the CRA becoming fully applicable on December 11, 2027, the window for preparation is closing. Manufacturers who view this simply as a regulatory hurdle are missing a critical opportunity. By prioritizing CRA readiness now, you can transform a mandatory product compliance strategy into a distinct market differentiator.
min reading time