Express + expert help

View pricing →
Skip to main content
tutorialCRA4 min read

CRA Cybersecurity Risk Assessment for an IoT Gateway

Create an IoT gateway risk register that connects product boundaries, abuse cases, security controls and verifiable release evidence.

By CenitiaUpdated

Fact-checked against the law as of Reviewed by Vladimír Vician on How we check

A CRA cybersecurity risk assessment should connect the actual product and its intended use to credible abuse scenarios, controls and verification evidence. A generic list of threats with every row marked “low risk” does not explain why the released gateway is appropriately protected.

This walkthrough uses an invented industrial gateway. Its risk register is a worked planning example, not a tested device assessment.

Define the product boundary

The model gateway bridges Ethernet sensors to a manufacturer designed remote management application. It has local commissioning, signed firmware updates and a service port. We assume deployment in a managed industrial network, but assess reasonably foreseeable misuse such as exposed management access and reused credentials.

Draw the interfaces and trust boundaries. Identify who can issue commands, provision credentials, sign updates and access collected data. Separate assumed environmental protections from controls the product itself provides.

Article 13(2) of the Cyber Resilience Act (Regulation (EU) 2024/2847) requires the manufacturer to assess the cybersecurity risks of the product and to take the outcome into account from planning through to maintenance. Article 13(3) requires the assessment to be documented, updated as appropriate during the support period and based on the intended purpose, the reasonably foreseeable use and the conditions of use. Article 13(4) requires it to be included in the technical documentation.

Section 7 of the Commission guidance on the application of the Cyber Resilience Act (C/2026/6013) explains how to evaluate and treat risks and how to handle integrated components and external dependencies. The Regulation governs. The guidance is non-binding, and the register in this article is one way to organise the work.

Write abuse cases that can drive design decisions

Model abuse caseExposure to investigateCandidate controlEvidence needed
Attacker reaches commissioning after installationInterface remains remotely reachableLimit commissioning state and require authenticationState transition and network access tests
Attacker substitutes an update packageUpdate input and trust anchorSigned package validation and protected keysPositive and negative signature tests
Compromised backend sends device commandsDevice trusts remote requestsAuthorisation, command bounds and loggingBackend and device permission tests
Service port exposes secretsPhysical or maintenance accessRestricted service design and secret handlingDebug configuration and extraction review
Dependency loses upstream supportPatch availability during expected useMigration or maintained patch planDependency ownership and support decision

The controls are candidates. Writing them into the register does not show they are implemented. Mark the evidence status honestly: proposed, implemented, verified or unresolved.

Explain likelihood and impact

Choose a scoring method that your team can use consistently. Define the meaning of each likelihood and impact level, including the environmental assumptions. Score the scenario before and after the control using the same definitions.

Avoid treating a numerical score as an objective measurement. “Impact 4” means little without explaining the possible harm: unauthorised command execution, loss of availability or exposure of credentials. Also record uncertainty, especially when proprietary components cannot be inspected.

A low estimated likelihood should not erase a severe plausible impact. Ask whether the estimate depends on an installation instruction customers may not follow. Where your control relies on network isolation, document how that requirement is communicated and what happens if it is absent.

Map each scenario and selected control to the relevant essential cybersecurity requirements in Annex I to the Cyber Resilience Act and to the supporting technical evidence. Where a requirement does not apply to the product, Article 13(4) requires a clear justification in the technical documentation. A standards checklist can support the assessment; it should not replace the product specific reasoning.

Keep component and service dependencies visible. Article 13(5) requires due diligence when integrating components sourced from third parties. A commercial cloud provider's security statement is useful context but does not prove that your device's command authorisation is correct. The guidance expects risks from back-end systems outside the product to be addressed by measures in the product itself, such as cryptographic authentication of remote commands (paragraph 169). Assess the integration, including failures and misuse at the boundary.

Make verification falsifiable

For the commissioning row, define the expected result before testing: an unauthenticated remote request cannot enter commissioning after the product is enrolled. Record the firmware hash, state, network setup, request and observed response.

Test a permitted path too. A negative test that always fails because the interface was broken cannot establish that the authorisation control behaves correctly. Retain raw evidence and distinguish a failed test from an accepted residual risk.

Record the release decision and reassessment triggers

Name the risk owner and approver. Open high consequence gaps need a documented treatment decision, not an empty “accepted” checkbox. A manufacturer's internal risk tolerance, commercial strategy or cost considerations do not decide whether a risk has been addressed under the Cyber Resilience Act; the guidance sets out that limit in paragraphs 157 to 163. Identify triggers such as a new radio option, remote control feature, dependency vulnerability, cloud interface change or support plan revision.

The gateway is invented and none of the model controls has been tested on a real device. The assessment method does not decide whether the product is an important or critical product under Annexes III and IV to the Cyber Resilience Act, or which conformity assessment procedure applies; those questions need their own review.

CRA applicability and timing

Most Cyber Resilience Act obligations apply to products placed on the market from 11 December 2027; a product placed on the market earlier becomes subject to them only if it is substantially modified from that date (Article 69(2)). Article 14 reporting is already a current duty: it has applied since 11 September 2026 to every in-scope product, including products placed on the market before 11 December 2027 (Article 69(3)), and it continues after the support period ends. Check the product’s scope, your role and the transitional provisions. See the Commission page for manufacturers, the Commission page on reporting and the Commission guidance on the application of the Cyber Resilience Act (C/2026/6013).

Continue reading

Related guides

Put this into practice

Free tools & references

New to the terminology? Browse the compliance glossary — plain-English, citation-backed definitions of every term above.