Cyber Resilience Act · CRA
Prepare your product for a market that demands security throughout its service life.
Product security accompanies the design, every update and the relationship with your customers. We connect the CRA requirements with engineering work so that development, support and management move forward with a shared approach.
01 / 07
The launch is only part of the responsibility
A vulnerable dependency, a reporting channel with no owner or poorly defined support can affect versions that are already in customers' hands. We work with you to anticipate those situations and turn the applicable requirements into tasks and evidence tied to the product.
02 / 07
Product security with continuity
- 01
Well-founded classification
We analyse the product, how it is marketed and your company's role.
- 02
Engineering and compliance connected
We link architecture, components, testing and documentation.
- 03
Support that is ready
We review vulnerability management, updates and notification scenarios.
03 / 07
A path connected to the product's life
Get to know the product
Release, interfaces, dependencies and associated remote services.
Define readiness
Applicability, classification, gaps and evidence.
Integrate the work
Engineering, support and conformity actions in the roadmap.

04 / 07
What you take away from the work
- Applicability and classification analysis.
- Requirements matrix and evidence preparation.
- Improvement plan for the vulnerability lifecycle and support.
05 / 07
Designed for your reality
Manufacturers of software and connected products
Coordination between engineering, quality, support and product management.
Industry and SaaS Technology
Specific analysis where there is distributed software, equipment or associated remote solutions; a SaaS does not automatically fall within scope.

06 / 07
Frequently asked questions
Not automatically. The definition of product, associated remote solutions, exclusions and the way the product is marketed must be studied.
It provides technical evidence for a specific scope. Conformity also requires analysing requirements, documentation and vulnerability management.
General application is scheduled for 11 December 2027; the reporting obligations under Article 14 apply from 11 September 2026. We review those that apply to the product.
07 / 07
Services that complement this work
The best phase to prepare your product's security is the one you are working on now.
Let's review what you sell, how you maintain it and what you need to be able to demonstrate.
