CRA · Engineering and traceability
EU Cyber Resilience Act: An Engineering Guide for Manufacturers
The Cyber Resilience Act sets cybersecurity requirements for products with digital elements. For engineering teams, the practical question is how product risks, requirements, implementation and verification stay connected as a product changes.
CRA timeline: distinguish reporting from the main requirements
The regulation enters into force; obligations apply in stages.
Provisions on notification of conformity-assessment bodies apply.
Article 14 manufacturer reporting obligations already apply to in-scope products.
The main provisions apply. Check transitional rules and your product role.
The main provisions generally concern products placed on the market from 11 December 2027. For products placed earlier, consider the transitional rule on substantial modification. Article 14 is an exception: reporting duties can already cover older in-scope products.
Start with the product and your role
Regulation (EU) 2024/2847 concerns products with digital elements made available on the EU market whose intended or reasonably foreseeable use includes a direct or indirect data connection to a device or network. It can cover hardware, software and separately marketed components, including integral remote data-processing solutions as defined by the regulation.
Scope is not the same as ‘every digital service’. Free and open-source software supplied outside commercial activity is excluded. Sector-specific exclusions include products covered by the EU medical-device and in-vitro diagnostic regulations. Other exclusions and special rules must be checked against Article 2; do not assume all products in a manufacturer’s portfolio have the same status.
Identify who is the manufacturer, importer or distributor and which obligations follow from that role. Open-source software stewards have a distinct regime. This guide focuses on manufacturers’ engineering preparation, not a determination of your product’s legal classification.
Translate security risks into engineering requirements
Manufacturer duties include a cybersecurity risk assessment that informs design, development, production and maintenance. Security-by-design and security-by-default are engineering activities, not labels to add at the end of a project.
For each relevant risk, identify the security behavior the product must provide, the implementation owner and how the behavior will be tested. Access control, integrity, updates and reduction of attack surfaces are examples of areas to evaluate according to the product’s risks and applicable Annex I requirements.
A requirements-to-test relationship helps an engineer locate verification evidence. It does not prove the risk analysis is complete, the test is sufficient or the product is secure.
Plan vulnerability handling throughout support
Manufacturers need processes for receiving, assessing and addressing vulnerabilities, including those in integrated components. Define ownership for coordinated disclosure, corrective work, testing and security updates. Product support obligations should inform engineering planning, not sit only in a contractual document.
Maintain an inventory of components and use appropriate tools for vulnerability discovery and software bills of materials where required. AroTrace does not provide those functions. AroTrace connects selected engineering information after the responsible teams have identified the work.
Distinguish the reporting triggers and deadlines
Since 11 September 2026, Article 14 manufacturer reporting obligations cover actively exploited vulnerabilities and severe incidents affecting the security of in-scope products. These obligations can apply to products placed on the market before the main 2027 application date. A discovered vulnerability is not automatically an actively exploited vulnerability; the responsible security team must evaluate the trigger.
For either trigger, notify without undue delay: the early warning is due within 24 hours of awareness, followed by the vulnerability or incident notification within 72 hours. The final-report clock differs: for an actively exploited vulnerability, no later than 14 days after a corrective or mitigating measure becomes available; for a severe incident, within one month after the 72-hour notification. Check Article 14 for required content and the rule for an incident still ongoing at that point.
Use ENISA’s Single Reporting Platform and the designated coordinating CSIRT process. AroTrace does not submit these notifications. Open-source software stewards’ Article 24(3) reporting duties start on 11 December 2027, rather than the manufacturer start date.
Build technical documentation from controlled engineering records
Technical documentation must explain the product and how the applicable cybersecurity requirements are addressed. Articles 13 and 31 and Annex VII define the relevant framework, including design and development information, risk assessment and evidence supporting conformity.
Useful engineering preparation includes identifying the current requirement, implementation records, test definition, execution result and reviewed product context. Keep the distinction between a test case and a result: one describes what should be checked; the other records a particular execution.
Connected records are inputs to the documentation process, not an automatically complete technical file. Decide how versions, access, retention and evidence completeness will be managed. Check the regulation’s retention and support obligations for your product rather than assuming an integration log is the legally required archive.
Choose the applicable conformity-assessment route
Not every product requires a third-party assessment. The default category can use internal control. Important and critical products follow stricter routes; the applicable options depend on classification and, where relevant, the use of harmonised standards or other recognized specifications.
Determine the route before promising certification or selecting a tool. The manufacturer remains responsible for the applicable assessment, declaration of conformity and CE-marking duties. AroTrace does not perform conformity assessment or certify the product.
Prepare one end-to-end evidence path
Choose one product and one security requirement before expanding the integration scope. Following one requirement through implementation and testing helps identify missing connections and evidence.
- Confirm scope, product classification, responsible roles and applicable dates with the regulatory owner.
- Name the authoritative requirement, implementation and test systems and the owners of their records.
- Define field direction, counterpart identities and the verification relationship.
- Check that the execution evidence refers to the intended test cases and reviewed requirement state.
- Review failed updates, missing mappings, permissions and manual evidence gaps.
- Agree how humans accept evidence and how the controlled technical documentation is assembled and maintained.
Sources and scope
This content provides engineering orientation, not legal advice or a determination of conformity. Review the current rules and your product’s classification with qualified specialists.
Regulatory sources reviewed on 23 October 2026.
Your next engineering step
Discuss Your CRA Engineering Readiness
Tell us the systems involved and one evidence gap. We can review mappings, ownership and a practical demonstration of your workflow. Please do not send confidential vulnerability details through the contact form.
Product names identify the systems discussed; trademarks belong to their owners. No certification or endorsement by the named vendors or EU institutions is implied.