Cybersecurity and the new Radio Equipment Directive

So, manufacturers, get your cybersecurity capes on. The EU is coming for your gadgets—and it means business.

Brace Yourselves: The EU Is Mandating Cyber Hygiene for Wireless Devices

Starting August 1, 2025, the EU is tightening the screws on anything with an antenna or IP address. If your device transmits via radio and talks to the internet—even once—it now falls under the revised Radio Equipment Directive (RED 2014/53/EU). In short: your hardware just got a cybersecurity to-do list.

Yes, this applies to a wide array of products: routers, wearables, smart toys, baby monitors, fitness trackers, and any IoT thingamajig you’ve designed to be “smart.” Now it also has to be “secure.”

What’s In Scope?

If it’s radio-equipped and internet-connected, it’s in. Think:

  • Smartphones, tablets, wireless cameras
  • Routers and modems
  • Sensors, wearables, home automation gadgets
  • Basically, anything with Wi-Fi, LTE, Bluetooth, Zigbee, etc.

If it sends packets or listens for them, you should assume RED applies.


The Three Cyber Must-Haves

Here’s what the Directive now explicitly requires at the engineering level:

1. Network Safeguards (Art.3.3(d)) – Cybersecurity

Your device must not compromise the network it connects to. That means:

  • Implement rate limiting and request throttling
  • Avoid open ports and insecure default configs
  • Prevent DDoS amplification (yes, that includes securing UPnP and STUN misconfigurations)
  • Validate firmware updates properly—no unsigned OTA madness

Basically, stop your devices from turning into network bullies or zombie bots.


2. Data Protection (Art.3.3(e)) – Privacy

If your product handles any personal or location data—even if it’s indirect (say, via cloud sync or a companion app)—you need:

  • Strong access control
  • Data encryption at rest and in transit
  • Local storage isolation
  • Privacy-by-design baked into the firmware and UI

Bonus: If it’s a children’s product (e.g. smart toys or wearables), you really need to lock it down. Think COPPA-level security or higher.


3. Fraud Prevention (Art.3.3(f)) – Fraud Prevention

Devices that facilitate payments or virtual currency? You’re now responsible for:

  • Secure user authentication (multi-factor, biometrics, hardware tokens, etc.)
  • Transaction verification layers
  • Anti-spoofing and tamper resistance
  • No hardcoded secrets or reused cryptographic keys, please

This especially applies to mobile wallets, NFC payment gadgets, and wearables that act like debit cards.


But Wait—Where Are the Standards?

Here’s the fun part: no harmonized standards yet. That’s right. As of now, there’s no pre-approved checklist to mark as “compliant.”

You’ll likely need a Notified Body to evaluate compliance unless your implementation clearly aligns with best practices from:

  • ETSI EN 303 645 (IoT security baseline)
  • IEC 62433-1 (embedded system threat mitigation)

Translation: Just being “secure” won’t cut it unless you can prove it.


Non-Compliant? No CE Mark = No EU Market

If your product doesn’t meet these new cybersecurity requirements, forget about affixing that CE mark. Customs will be scanning for this, and regulators are expected to ramp up enforcement.

No CE = No sales in the EU. Period.


Engineering Teams:

  • Audit your devices now for radio+internet exposure
  • Revisit firmware and protocol stack designs with RED compliance in mind
  • Document your security measures—you’ll need the paperwork
  • Build with security as a core requirement, not a post-hoc patch

EU’s message to engineers: If you’re connecting it, you’re protecting it.

CONTACT F2 LABS FOR HELP, THIS IS WHAT WE DO.

Want to discuss your project with us?

You can contact us at this link. Our phone number is 877-405-1580 and we are here to help you.

This entry was posted in CE marking. Bookmark the permalink.