CRA Compliance Checklist: Drones & Unmanned Aerial Vehicles
Default class for most drones, because Annex III lists no drone or unmanned aircraft category. Important Class I for an internet connected toy drone covered by Directive 2009/48/EC with filming or location tracking features (Annex III, point 18). Outside the CRA when certified in accordance with Regulation (EU) 2018/1139 (Article 2(3))
Drones and unmanned aerial vehicles operate in a complex regulatory environment combining the CRA and EU Drone Regulation (EU) 2019/947. Most drones are default class under the CRA, whatever their C class, because Annex III lists no drone category (Article 7(1)). BVLOS operations, remote identification and UTM integration raise the risk that the Article 13(2) cybersecurity risk assessment must address. An internet connected toy drone covered by Directive 2009/48/EC with filming or location tracking features is Important Class I (Annex III, point 18). Manufacturers must map each product to both regulatory frameworks.
Last updated 26 October 2026
1. Scope & Classification
Classify each drone by its core functionality, separately from its EU drone class (C0 to C6)
Annex III lists no drone category, so most drones are default class whatever their C class. BVLOS capability and critical operations raise the risk that the Article 13(2) risk assessment must address. An internet connected toy drone covered by Directive 2009/48/EC with filming or location tracking features is Important Class I (Annex III, point 18).
Check whether the Article 2(3) aviation exclusion applies to each drone
The CRA does not apply to products certified in accordance with Regulation (EU) 2018/1139 (Article 2(3)). Record for each drone whether it holds such a certification. The EU Drone Regulation (2019/947) does not currently provide comprehensive cybersecurity requirements equivalent to CRA Annex I. Most drone manufacturers should plan for full CRA compliance.
Choose the CRA conformity assessment procedure for each drone by its class
A default-class drone can use Module A internal control (Article 32(1)). A Class I toy drone 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. Check that the body is designated under the CRA. A notified body under the EU drone rules can be a different entity.
Compile SBOM covering flight controller firmware, ground control software, remote ID module, and telemetry systems
Drone firmware stacks include flight controller firmware (ArduPilot, PX4, or proprietary), companion computer software, and remote ID modules. All must be tracked.
2. Product Security (Annex I Part I)
Implement authenticated and encrypted command and control links - prevent unauthorised control takeover
Unauthenticated or unencrypted C2 links are exploitable for drone hijacking. Implement mutual authentication and encryption for all command and control communications. Consider FHSS and anti-jamming measures.
Implement EU Remote Identification (Remote ID) securely - protect the integrity of Remote ID broadcasts
Remote ID broadcasts must be tamper-resistant. Implement cryptographic signing of Remote ID messages where technically feasible to prevent spoofing.
Implement geo-fencing with integrity protection - prevent software bypass of airspace restrictions
Geo-fencing must be robust against software bypass. Cryptographic zone data and fail-safe behaviour (land or return-to-home) when zone data integrity fails must be implemented.
Implement signed firmware updates with rollback protection for all drone firmware
Drone firmware updates must be signed and verified before installation. Rollback to a safe known-good firmware version must be possible if a new version causes issues.
3. CVD Policy & Vulnerability Handling
Publish a CVD policy for flight controller, ground control, and companion software vulnerabilities
Drone security research is an active field. Remote control hijacking and geo-fence bypass vulnerabilities are of particular public safety interest. A responsive CVD policy is essential.
Define security support lifecycle appropriate to drone operational lifecycles - minimum 3 years for consumer, 7 years for professional drones
Consumer drones have shorter lifecycles; professional inspection and commercial drones are used for many years. Publish per-product support end dates.
4. Article 14 Incident Reporting
Define Article 14 triggers for drone incidents - focus on C2 link hijacking, geo-fence bypass, Remote ID spoofing, and fleet-scale exploitation
An actively exploited vulnerability enabling mass drone hijacking or geo-fence bypass near airports is a critical Article 14 trigger with national security implications.
Coordinate Article 14 ENISA reporting with EASA and national aviation authority notifications for safety-critical drone incidents
Safety-critical drone cybersecurity incidents may require parallel notifications to ENISA (CRA Article 14) and national aviation authorities (safety incident reporting). Pre-plan coordination.
5. CE Marking & Technical Documentation
Prepare integrated CRA and EU Drone Regulation technical file - coordinate CE marking requirements across both frameworks
Drone technical files must satisfy both EU Drone Regulation category requirements and CRA cybersecurity requirements. Integrate documentation to avoid duplication.
Issue EU Declaration of Conformity referencing both the CRA and EU Drone Regulation
A single DoC can reference both frameworks. Affix the C-class label as required by EU Drone Regulation alongside CRA CE marking requirements.
Track your Drones & Unmanned Aerial Vehicles 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
My drone uses open-source flight controller firmware (ArduPilot/PX4) - how do I handle the SBOM and CVE obligations?+
Using open-source flight controller firmware does not exempt you from CRA obligations as the product manufacturer. You must include ArduPilot or PX4 and all their dependencies in your SBOM. Both projects publish security advisories and have security teams. Subscribe to their advisories, monitor CVEs for all included components, and deliver patches to your customers. You may also contribute security fixes upstream.
Do racing drones and FPV drones require CRA compliance?+
This depends on whether they are placed on the EU market as products. Racing drones sold as consumer products are in scope. FPV drones built by individuals for personal use (not sold commercially) may be outside scope as non-commercial hobby products. However, any FPV or racing drone sold as a finished product or kit to the EU market is in scope. Check whether your product qualifies as C0 or a higher drone category.
We manufacture drones for military use - does CRA apply?+
Products developed or modified exclusively for national security or defence purposes are excluded from CRA scope under Article 2(7). However, if you also sell commercial or civilian variants of the same drone platform to the EU market, those commercial variants are in scope. Dual-use products require careful classification.
Related compliance checklists
Policy templates for Drones & Unmanned Aerial Vehicles
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 Drones & Unmanned Aerial Vehicles?
Download a free CRA-compliant disclosure policy template and deploy it in minutes.