Cyber Resilience ActAn EU regulation establishing cybersecurity requirements for covered software and hardware products. It sets duties concerning product design, vulnerability handling and demonstrating conformity, subject to its exclusions and staged application provisions.
Cyber Resilience Act Readiness Assessment
The Cyber Resilience ActAn EU regulation establishing cybersecurity requirements for covered software and hardware products. It sets duties concerning product design, vulnerability handling and demonstrating conformity, subject to its exclusions and staged application provisions. sets security requirements for hardware and software products sold in the EU, from design to the end of support, and asks manufacturers to report actively exploited vulnerabilitiesA vulnerability for which there is reliable evidence that a malicious actor has exploited it in a system without the owner's permission. Under the CRA, manufacturers must send an early warning within 24 hours of becoming aware of one in their product, through the single reporting platform. and severe incidents. We assess your products and your development and vulnerabilityA weakness, susceptibility or flaw that a threat can exploit. NIS2 applies it to ICT products and services, the CRA to products with digital elements and DORA to any asset, system, process or control. Coordinated vulnerability disclosure and handling duties build on this definition. handling against Annex I, confirm each product's class and conformity route, and give you a plan your management can approve.
WHY ASSESS NOW
Products that miss the CRA requirements cannot carry the CE marking
The Act applies to hardware and software with digital elements placed on the EU market, wherever the manufacturer is based.
The problem
The requirements reach back into design
Annex I covers how a product is designed, built and supported, not only how it is tested at the end.
- Reporting duties apply before the rest of the Act
- Support periods and security updates to plan
- Fines up to EUR 15 million or 2.5% of worldwide turnover
The solution
A readiness assessment per product
We classify your products, check them and your processes against Annex I, and plan what must change.
- Scope and class per product
- Annex I Parts I and II
- A plan against the dates that apply
The outcome
A clear route to the CE marking
You know what to fix, in what order, and which conformity route each product takes.
- Gaps closed in the right order
- A documented conformity route
- Evidence for customers and authorities
Does a requirement ask for it?
The laws and standards that ask for it
We scope the work to what your requirement asks for, so the result serves that audit or supervisor too.
What we check
What we assess
For each requirement we review the evidence and check that the control works, so you know exactly where you stand.
Scope and product class
Whether each product is in scope, its class (default, important or critical) and the conformity route that follows.
Security requirements
The requirements of Annex I Part I, from secure defaults and access controlRequirements and safeguards that decide who or what may use information, systems or facilities, and what actions they may perform. Access control can grant or refuse access to people, software or devices. Examples include restricting a user account to permitted systems and limiting its privileges. In the plural, access controls are the measures used to enforce these requirements. to data protection and secure updates, tested on the product and its documentation.
Vulnerability handling
The processes of Annex I Part II: the software bill of materialsA formal record of the details and supply chain relationships of the components included in the software of a product. Under the CRA, manufacturers must draw up an SBOM in a commonly used, machine-readable format covering at least the top-level dependencies., coordinated disclosure, security updates and reporting.
Technical documentation
The risk assessmentA structured process for identifying risks, analysing their possible effects and judging which need attention. In information security, this means examining threats, weaknesses and existing safeguards to prioritise risks to information and business operations. The assessment informs decisions about reducing or accepting risk and should be reviewed as circumstances change., documentation and support periodThe period during which a manufacturer must ensure that vulnerabilities of a product with digital elements are handled effectively and in line with the CRA vulnerability handling requirements. It must reflect the expected time of use and is generally at least five years. your EU declaration of conformity rests on.
HOW THE ASSESSMENT RUNS
From scoping to a plan
The phases follow your products and their versions; your proposal gives the dates.
-
Scoping
Scoping
Products, versions, markets and your role.
-
Scope
Classification
Product class and conformity route.
-
Testing
Documents and testing
Records, processes and the product, against Annex I.
-
Findings
Draft findings
Gaps discussed before the report is final.
-
Report
Report and plan
The readiness report and the plan.
A guide, not a fixed promise: the length of each phase depends on the number of products and on how quickly evidence and people are available.
YOUR ASSESSMENT
Start well before your next release
Tell us your products, your role and when they reach the EU market. We send a written proposal with scope, dates and a fixed fee within two working days.
WORKING WITH US
What it takes from your side
Your team's time, how quickly we start, and how the work is organised.
From your go-ahead to kick-off
We start within days, so the work fits your dates.
No travel costs
Interviews and evidence by video call; on-site days where they are needed.
An hour or two per owner
We plan sessions around your teams and ask each only for its own part.
What you receive
Readiness report
Scope, method and a conclusion for each requirement of Annex I, with the evidence behind it.
Product classification
Each product's class, the reasoning and its conformity route: internal control, a notified bodyA conformity assessment body that a Member State has notified to the Commission as competent to carry out third-party assessment under EU legislation. Whether a manufacturer or provider must involve one depends on the applicable act, system or product classification and conformity assessment route; not every high-risk AI system requires a notified body. or a certification scheme.
Table
Gaps and plan
Each gap with its risk, the requirement concerned and a practical fix, in the order the dates require.
Excel gap list
Management summary
The result and the decisions management needs to take.
Presentation and a closing call
Why work with GRC+ on the Cyber Resilience Act
Product and process together
We assess the product and the development and vulnerabilityA weakness, susceptibility or flaw that a threat can exploit. NIS2 applies it to ICT products and services, the CRA to products with digital elements and DORA to any asset, system, process or control. Coordinated vulnerability disclosure and handling duties build on this definition. handling behind it, as Annex I asks.
Reporting covered too
The Incident Reporting Desk can draft the vulnerabilityA weakness, susceptibility or flaw that a threat can exploit. NIS2 applies it to ICT products and services, the CRA to products with digital elements and DORA to any asset, system, process or control. Coordinated vulnerability disclosure and handling duties build on this definition. and incident reports the Act asks manufacturers to make.
What you already have counts
We build on IEC 62443-4-1Security for Industrial Automation and Control Systems - Part 4-1: Secure Product Development Lifecycle Requirements and 4-2, ISO 27001Information Security, Cybersecurity and Privacy Protection: Information Security Management Systems: Requirements and your existing security testing, so evidence you hold is used.
Independent of the build
We do not design or build your product's security, so the assessment stays objective.
Credentials
Who does the work
Certified practitioners
Every engagement is led by a senior, certified practitioner.
25+
years in regulated sectors
Banks, insurers, payments, healthcare and the public sector across the globe.
Insured
Professional indemnity cover on every engagement.
FAQ
Cyber Resilience Act readiness: frequently asked questions
Something else? Ask us in a 30-minute call.
Does the Cyber Resilience Act apply to us?
It applies to products with digital elements placed on the EU market: hardware and software that connect to a device or a network. Products covered by their own sector requirements, such as medical devices, vehicles and aviation, are excluded. It applies to manufacturers, importers and distributors, wherever they are based.
Is this a conformity assessment?
No, it prepares you for one. Most products use internal control by the manufacturer; important and critical products may need a notified body or a certification scheme. We tell you which route each product takes and get you ready for it.
What do we have to report, and when?
Manufacturers report actively exploited vulnerabilities and severe incidents to their CSIRT and ENISA: an early warning within 24 hours and a notification within 72 hours. Our Incident Reporting Desk can draft those reports for you.
Does it cover the open-source components we use?
Yes. Open-source software made outside a commercial activity is excluded from the Act, but the components you build into a product you sell are your responsibility. The assessment covers how you track and update them.
What does the assessment cost?
A fixed fee, set in your written proposal before any work starts. It follows the number of products, versions and sites in scope.
Want to know more about CRA?
Our guide to CRA explains who it applies to, what it requires, the deadlines and what happens if you do not comply. Cyber Resilience Act (CRA) →
Plan your CRA readiness assessment
Tell us your products, your role and when they reach the EU market. We send a written proposal with scope, dates and a fixed fee. sales@grc.plus +31 20 241 66 00
Related: Source Code ReviewPenetration TestingIncident Reporting Desk