Definition

What is a CRA cybersecurity risk assessment?

Cybersecurity risk assessment · also: CRA risk assessment

Short answer

The documented assessment of a product's cybersecurity risks that drives which essential requirements apply and how.

Manufacturers must undertake an assessment of the cybersecurity risks associated with a product with digital elements and take its outcome into account during planning, design, development, production, delivery and maintenance. It must consider the intended purpose and reasonably foreseeable use, and it determines how each Annex I Part I requirement applies (or is documented as not applicable). The assessment is part of the technical documentation and is updated during the support period.

A defensible assessment names the product version and its intended use and environment, identifies assets and threat scenarios, rates likelihood and impact, records the controls chosen against each Annex I Part I requirement, states the residual risk and who accepted it, and says when it will be reviewed. It is a living record: new vulnerabilities, incidents and substantial modifications should send it back for review.

Reference: Art. 13(2)–(3); Annex VII(3)

Updated · Paraphrase for orientation, not legal advice.

Share:LinkedInXE-mail

Frequently asked questions

Is a CRA risk assessment the same as a GDPR DPIA or an ISO 27005 assessment?
No. The CRA assessment is about the product's cybersecurity risks across its lifecycle, not about personal-data processing or an organisation's information security. Existing methods (ISO/IEC 27005, IEC 62443-3-2, threat modelling) can be reused as the method, but the output must map to Annex I.
When must the risk assessment be updated?
Whenever the risk picture changes during the support period — new vulnerabilities, incidents, changes in use, substantial modifications — and as part of each release that changes the product's security properties.

In practice

Related terms

Keep the technical file current from real records.

Vellaci builds Annex VII documentation per product from SBOMs, decisions, risk assessment and test evidence, with version history.