Timeline
The reporting obligations in Article 14 apply from 11 September 2026. The rest of the Regulation applies from 11 December 2027.
Regulation (EU) 2024/2847 · CRA
Tell Audexa whether you manufacture, import, distribute or steward open-source software, and which class your product falls into. You only see the controls that apply to you: essential requirements, vulnerability handling, SBOM, reporting to ENISA, technical documentation and CE marking, with an action plan to close each gap.
What the CRA requires
The Cyber Resilience Act sets cybersecurity requirements for products with digital elements, from design to the end of the support period. Obligations depend on each operator's role and the product's class.
The reporting obligations in Article 14 apply from 11 September 2026. The rest of the Regulation applies from 11 December 2027.
Annex I sets requirements for the product (secure by default, data protection, updates) and for vulnerability handling throughout the support period.
Manufacturers report actively exploited vulnerabilities and severe incidents through the single reporting platform, with an early warning within 24 hours and a notification within 72 hours.
Important products in class I and II and critical products follow stricter conformity assessment routes than default products.
Technical documentation, EU declaration of conformity and CE marking before the product is placed on the market.
They must check that the product complies, carries the CE marking and documentation, and act when they spot a risk.
Sources: Regulation (EU) 2024/2847 (EUR-Lex)
How Audexa helps
The same workflow as every other Audexa audit, adapted to companies that place digital products on the European market.
Only what applies to you.
Pick one or more roles and the product class, and see how many questions your questionnaire will have.
Mark which controls apply, which do not and which are out of scope, and record why.
When you create the audit you see how much your ISO 27001 or NIS2 audits already cover.
Every gap with its next step.
Yes, Partial, No or Not applicable for each control, with guidance on how to assess it.
Concrete steps, expected evidence, suggested owner, closure criterion and when to review it.
Findings turned into tasks with subtasks, owners and dates.
All your evidence in one place.
SBOMs, test reports, reporting procedures or technical documentation, with review and expiry dates.
A library of 67 templates. 6 are linked to the CRA: “Product Security and Coordinated Vulnerability Disclosure Policy”, “Product Conformity and CE Marking Procedure (CRA)”, “Secure Development Policy”, “Vulnerability and Patch Management Policy”, “Regulatory Incident Notification Procedure” and “Procedure for Handling Authority Requests and Data Disclosure”. They are a starting point to adapt and approve.
Score, findings and a PDF and Excel report. Assess again and compare progress.
Some features depend on your plan and active modules.
Profile question
Before the questionnaire you state your role, and you can tick several because many companies manufacture some products and import or distribute others. Then you choose the class of your main product, which sets the conformity assessment route. If you don't know it yet, start with the product unclassified and change it later.
Reporting
One section checks whether you can detect an actively exploited vulnerability or a severe incident and report it through the single reporting platform to the coordinating CSIRT and ENISA. Another covers vulnerability handling: SBOM, coordinated disclosure, security updates and the support period.
How it works
Choose your roles and the product class, and see how much your existing work covers.
Assess the controls that apply and review the answers proposed from ISO 27001 or NIS2.
Work through the task plan, gather evidence and assess again before each milestone.
Plans
The Cyber Resilience Act is included in Premium and Diamond. It is not part of Free or Core. We give you a fixed proposal during the demo.
For product and security teams that want the full cycle.
For manufacturers with many products or large teams.
Frequently asked questions
The Regulation entered into force in December 2024. The obligations to report actively exploited vulnerabilities and severe incidents apply from 11 September 2026, and the rest, including the essential requirements and CE marking, from 11 December 2027.
Yes, with different obligations. You select your role in the profile question and the questionnaire includes the importers and distributors section. If you substantially modify a product or sell it under your own brand, you may take on manufacturer obligations: there is a control to check this.
No. Audexa helps you prepare: self-assessment, action plan and evidence. The conformity assessment is done by you or by a notified body, depending on the product class, and CE marking is the manufacturer's responsibility. The Audexa result is for guidance only and is not legal advice.
The class sets the conformity assessment route. That is why the profile asks for the class of your main product and one questionnaire section reviews the matching assessment. If you don't know the class yet, start with the product unclassified and change it later.
Yes. There are 57 mappings to ISO 27001:2022 and 44 to NIS2. High-coverage answers arrive as proposals marked “Review it” and a person confirms them. They are not legal equivalences.
Spanish, English, French, Italian and German, like every other Audexa framework.
Request a demo
In 30 minutes we walk through the role and class profile, the questionnaire, the task plan and the evidence.