CRA Compliance Checklist: Edge Computing Devices & Gateways
Default class for most edge computing appliances. Important Class I for a gateway whose core functionality is a router, an internet modem or a switch (Annex III, point 12), or a VPN gateway (Annex III, point 5). Important Class II for a product whose core functionality is a firewall (Annex III, Class II, point 2)
Edge computing devices and gateways - including industrial IoT gateways, edge AI inference nodes, fog computing appliances, and protocol converters - sit at the boundary between operational technology and IT networks. They often aggregate sensitive data from many downstream devices and may have elevated privileges in industrial environments. Most edge computing appliances are default class, because their core functionality matches no Annex III category (Article 7(1)). A gateway whose core functionality is a router, an internet modem or a switch is Important Class I (Annex III, point 12). Critical downstream systems do not change the class. They raise the risk that the Article 13(2) cybersecurity risk assessment must address.
Last updated 26 October 2026
1. Scope & Classification
Confirm all edge gateways and edge computing appliances with network connectivity are in CRA scope
Every edge device with a network interface and updateable software is a product with digital elements. Map all product types in your portfolio.
Classify each edge product by its core functionality (Article 7(1))
An edge gateway whose core functionality is a router, an internet modem (including cellular) or a switch is Important Class I (Annex III, point 12). A VPN gateway is Important Class I (Annex III, point 5). A protocol converter or an edge AI appliance matches no listed category and is default class. An integrated operating system, container runtime, cellular modem module or TPM does not raise the class of the host (Article 7(1)). The OT/IT bridge role raises the risk that the Article 13(2) risk assessment must address.
Address critical infrastructure control loops in the cybersecurity risk assessment
Use in energy, water or transport control loops does not make an edge device Class II (Article 7(1)). Assess the downstream systems in the Article 13(2) risk assessment. A product whose core functionality is a firewall or an intrusion detection or prevention system is Important Class II (Annex III, Class II, point 2). A hypervisor or container runtime sold as a product is Important Class II (Annex III, Class II, point 1).
Compile SBOM for edge device OS (typically embedded Linux or RTOS), runtime environment, containerisation layer, and all application modules
Edge devices increasingly run containerised workloads. The SBOM must cover the host OS, container runtime (Docker, containerd), and all deployed container images.
2. Product Security (Annex I Part I)
Implement hardware-backed secure boot and trusted execution environment for sensitive key material and edge AI models
Edge devices are deployed in physically accessible locations. Hardware-backed secure boot and TEE (ARM TrustZone, Intel TDX) protect against physical attacks.
Enforce mutual TLS authentication for all communications between edge devices, cloud orchestration platforms, and downstream IoT devices
Edge-to-cloud and edge-to-device communications must be mutually authenticated and encrypted. Implement certificate-based identity for all devices.
Isolate edge workloads in containers or VMs - prevent workload breakout to host OS or cross-workload data access
Edge devices running multiple workloads (e.g. inference, data aggregation, VPN) must isolate each workload. A compromised container must not be able to access other workloads or the host OS.
Implement remote attestation to allow operators to verify edge device integrity before trusting its outputs
Remote attestation (using TPM or hardware attestation services) allows operators to cryptographically verify that an edge device is running untampered firmware. Increasingly important for critical edge deployments.
3. CVD Policy & Vulnerability Handling
Publish a CVD policy with a dedicated security contact for edge device and gateway vulnerabilities
Edge devices are increasingly targeted as IT/OT bridge points. A CVD policy with OT and IoT security expertise is essential.
Provide OTA update capability with support for scheduled maintenance windows and zero-downtime updates for critical edge deployments
Industrial edge gateways often cannot be taken offline for updates. Provide A/B update mechanisms supporting hitless updates with automatic rollback on failure.
Define security support lifecycle appropriate to industrial deployment - minimum 10 years for industrial edge gateways
Industrial edge devices are capital investments with long lifecycles. Use LTS Linux kernels and commit to 10-year minimum security support for industrial products.
4. Article 14 Incident Reporting
Define Article 14 triggers for edge device incidents - focus on exploitation enabling OT network access, data exfiltration, or edge AI model poisoning
An actively exploited edge gateway vulnerability that enables lateral movement into OT networks is a high-severity Article 14 trigger.
Prepare and test the Article 14 notification procedure with named owners at each milestone
Pre-prepare notification templates covering edge-specific incidents. Use the CVD Portal Article 14 timeline tool to plan your process.
5. CE Marking & Technical Documentation
Prepare technical file documenting edge security architecture, container isolation, attestation capability, and SBOM
Edge device technical files should include architecture diagrams showing the IT/OT boundary, container isolation model, and remote attestation design.
Issue EU Declaration of Conformity referencing the CRA for all edge computing products
DoC must reference the CRA. Default-class products can use Module A internal control (Article 32(1)). A Class I gateway can use Module A only when you fully apply a harmonised standard, a common specification or a European cybersecurity certification scheme at assurance level at least substantial (Article 32(2)). No CRA harmonised standard is cited yet, so today it needs a notified body. A Class II product always needs Module B plus Module C, Module H or a European cybersecurity certification scheme specified under Article 27(9) at assurance level at least substantial, for the requirements it covers (Article 32(3)).
Track your Edge Computing Devices & Gateways compliance progress in CVD Portal.
Classify each product, build the Annex VII technical file and prepare Article 14 notifications. The disclosure portal that receives vulnerability reports stays free.
Frequently asked
Our edge gateway runs third-party applications from customers - who is responsible for the security of those applications?+
You, as the platform manufacturer, are responsible for the security of the edge platform itself - the OS, runtime environment, and container isolation. Customers deploying their own applications on your platform are responsible for those applications. However, you must ensure your platform provides adequate isolation so a compromised application cannot escape to the host or other applications. Document your platform security model clearly.
We supply edge gateways to industrial OEMs who integrate them into their products - who holds CRA obligations?+
As the gateway manufacturer, you hold CRA obligations for the gateway as a standalone product. The OEM who integrates your gateway into their product and places it on the market takes on manufacturer obligations for the integrated product. Both parties have distinct obligations. Provide the OEM with your CRA technical documentation and SBOM to support their compliance.
Our edge AI model is updated frequently - does each model update trigger CRA obligations?+
AI model updates that do not change the firmware or software architecture are not typically considered new product placements under the CRA. However, if a model update introduces new capabilities, new data processing, or changes the security architecture, this should be assessed against your existing CRA compliance. If the update represents a substantial modification, the technical documentation and DoC should be reviewed and updated.
Related compliance checklists
Policy templates for Edge Computing Devices & Gateways
Free CRA tools
This checklist is part of the EU Cyber Resilience Act guide, which explains Regulation (EU) 2024/2847 article by article.
Need a CVD policy for Edge Computing Devices & Gateways?
Download a free CRA-compliant disclosure policy template and deploy it in minutes.