EU Cyber Resilience Act Guide for Drone & UAV Manufacturers
Default class for most drones, ground control stations and drone docks. Important Class I for an internet-connected toy drone covered by Directive 2009/48/EC that can film or track location (Annex III, point 18). Excluded when the UAS is certified in accordance with Regulation (EU) 2018/1139
Drone and UAV manufacturers placing commercial and consumer unmanned aircraft systems on the EU market face CRA obligations that run in parallel with the EU UAS Regulation (EU 2019/945) and EASA airworthiness requirements. Annex III lists no drone category, so most drones, ground control stations and drone docks are default-class products under the CRA (Article 7(1)). The physical and safety consequences of compromised drone operation raise the risk that the Article 13(2) cybersecurity risk assessment has to address. A UAS certified in accordance with Regulation (EU) 2018/1139 is outside the CRA (Article 2(3)).
Last updated 26 October 2026
CRA Scope and Classification for UAS Products
Consumer and commercial drones, ground control stations (GCS) software and hardware, drone dock/hangar systems, BVLOS (beyond visual line of sight) management platforms, and flight control software are products with digital elements. They are within CRA scope unless they are certified in accordance with Regulation (EU) 2018/1139 (Article 2(3)).
Classification follows core functionality (Article 7(1)). Annex III lists no drone category, so drones with RF control links, GPS navigation, and telemetry data transmission are default class. Physical mobility and network connectivity raise the risk that the Article 13(2) cybersecurity risk assessment has to address. They do not change the class. An internet-connected toy drone covered by Directive 2009/48/EC that can film or track location is Important Class I (Annex III, point 18). Drone products in Class C1 and above under EU UAS Regulation already require adherence to specific technical standards; CRA adds cybersecurity-specific obligations on top. Manufacturers must distinguish between the drone airframe/avionics (UAS Regulation scope) and the digital elements - flight controller firmware, communication protocols, GCS software - which are the CRA's focus. Both regulatory frameworks require CE marking for EU market placement; they must be satisfied concurrently.
Technical Security Requirements for Drone Products
Drone cybersecurity vulnerabilities have been demonstrated to enable flight hijacking, data exfiltration from onboard cameras, and interference with drone traffic management systems. CRA Annex I requirements for drone products must address these attack vectors:
- Authenticated control links: The RF or IP link between the GCS and the drone must use authenticated, integrity-protected communication. Unencrypted MAVLink connections on consumer drones are a known weakness that must be remediated.
- Firmware integrity: Drone flight controller firmware updates must be cryptographically authenticated. Over-the-air update mechanisms must resist injection of malicious firmware.
- GPS security: Where drones rely on GPS for navigation, manufacturers should consider GPS spoofing risks and implement detection or mitigations where technically feasible.
- Data protection: Camera footage, flight logs, and telemetry data stored on the drone or transmitted to the GCS must be encrypted.
- Remote ID compliance: EU UAS Regulation Remote ID requirements include broadcast of drone identity; the security of the Remote ID broadcasting mechanism must be protected against spoofing.
CVD Policy and Article 13 for UAS Manufacturers
Drone manufacturers have faced significant security research attention, with multiple disclosed vulnerabilities in popular consumer drone platforms. Article 13 requires a formal, publicly accessible CVD policy for all products with digital elements - formalising what responsible manufacturers should already be practising.
- Cover the drone hardware, flight controller firmware, companion app, and GCS software
- Define a submission channel for security researchers, and also for drone operators who may identify anomalous flight behaviour suggesting exploitation
- Include a process for escalating vulnerabilities with potential flight safety implications to the appropriate authorities (EASA, national aviation authority)
- Commit to coordinated disclosure timelines that allow patch development before public disclosure - particularly important for flight safety vulnerabilities
CVD Portal enables UAS manufacturers to manage the full CVD workflow from intake through to advisory publication, including CSAF 2.0 record generation for advisories that can be monitored by enterprise drone fleet operators.
Article 14 Incident Reporting for Drone Manufacturers
- Systematic remote hijacking of drones in flight using known communication vulnerabilities
- Mass compromise of drone companion apps or GCS software for data exfiltration
- Active exploitation of flight controller vulnerabilities to interfere with drone operations
Drone incidents with flight safety implications trigger additional reporting obligations to national aviation authorities (NAAs) and EASA under aviation safety reporting requirements. The parallel notification tracks - ENISA (CRA Article 14), aviation authority (safety incident), and potentially national CSIRT - must be coordinated. Drone manufacturers should establish pre-agreed protocols for multi-track incident reporting and should brief both their security team and their aviation safety team on the parallel obligations.
Conformity Assessment and UAS Regulation Alignment
A default-class drone product can use Module A self-assessment (Article 32(1)). An Important Class I toy drone can use Module A only when the manufacturer fully applies a harmonised standard, a common specification or a European cybersecurity certification scheme at assurance level substantial or higher (Article 32(2)). No CRA harmonised standard is cited in the Official Journal yet, so today a Class I product needs a notified body. Manufacturers of drones in Class C1 and above under EU UAS Regulation already know third-party technical assessment from the UAS Regulation conformity process. The CRA assessment is a separate requirement for cybersecurity.
- Flight controller and communication security architecture
- OTA update mechanism integrity
- GCS software security architecture
- SBOM for all firmware and software components
- CVD policy operational status
Vendors should investigate whether the notified bodies they use for UAS Regulation assessment are also accredited for CRA conformity assessment, potentially enabling a coordinated assessment process. EASA's cybersecurity roadmap for aviation - including cybersecurity requirements for airborne systems - is developing in parallel with CRA; drone manufacturers should monitor both regulatory streams.
Work through the CRA for each product in one workspace.
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
Does EASA's UAS Regulation cover cybersecurity for drones, or is the CRA additional?+
EU UAS Regulation (EU 2019/945) and EASA's implementing regulations cover the airworthiness and operational requirements for drones, including some cybersecurity-relevant provisions such as Remote ID. The CRA is additional and separate, covering cybersecurity of the digital elements in drone products as standalone requirements - including CVD policy, SBOM, incident reporting, and vulnerability management obligations not addressed by the UAS Regulation. CE marking for drones must satisfy both the UAS Regulation's product standards and the CRA's cybersecurity requirements. A UAS certified in accordance with Regulation (EU) 2018/1139 is outside the CRA (Article 2(3)). For in-scope drones, CRA Article 14 reporting applies from 11 September 2026, and the other CRA obligations apply from 11 December 2027.
Are drone delivery services and drone-as-a-service operators subject to the CRA?+
The CRA applies to manufacturers placing products on the EU market, not to operators using those products. Drone-as-a-service operators are not subject to CRA product obligations for the drones they operate. However, they are subject to NIS2 if they operate as essential service operators (e.g., logistics). Operators should require CRA-compliant products from their drone hardware suppliers as part of their NIS2 supply chain security obligations. Drone manufacturers selling to drone-as-a-service operators must ensure their products are CRA-compliant at the point of sale.
Are hobby drones subject to the CRA?+
Yes. Consumer hobby drones with digital elements - flight controllers, RF communication, companion apps - are within CRA scope when placed on the EU market. Consumer hobby drones in Class C0 (under 250g) under the UAS Regulation have limited regulatory obligations under aviation law but are still subject to CRA cybersecurity requirements as connected consumer products. CRA classification follows the core functionality of the product (Article 7(1)), and the UAS Regulation class does not change it. Annex III lists no drone category, so hobby drones with smartphone app control and cloud connectivity are default class, and the self-assessment conformity pathway is open. A hobby drone that is a toy under Directive 2009/48/EC, communicates on the internet and can film or track location is Important Class I (Annex III, point 18).
Key CRA articles for Drone & UAV Manufacturers
Free CRA tools
This industry guide is part of the EU Cyber Resilience Act guide, which explains Regulation (EU) 2024/2847 article by article.
Start a CRA risk assessment for Drone & UAV Manufacturers
A pre-filled classification, asset inventory and STRIDE threat analysis for this product type, free to copy or seed into the app.