Since 1 August 2025, internet-connected radio equipment placed on the EU market has to meet cybersecurity requirements under RED Article 3.3 points (d), (e) and (f). A certified Wi-Fi or Bluetooth module does not make a product compliant. The requirements apply to the finished product, and most of the work sits in your firmware, your app and your update process.
This post covers what the rules require, which standards apply, and where a module helps.
What the Delegated Act Covers
Delegated Regulation (EU) 2022/30 activated three essential requirements of the Radio Equipment Directive (2014/53/EU). Delegated Regulation (EU) 2023/2444 moved the application date from 1 August 2024 to 1 August 2025.
| Point | Requirement | Applies to | Harmonised standard |
|---|---|---|---|
| 3.3 (d) | Does not harm the network or misuse network resources | Radio equipment that can communicate over the internet, directly or through other equipment | EN 18031-1:2024 |
| 3.3 (e) | Protects personal data and privacy | Internet-connected radio equipment that processes personal, traffic or location data. Also childcare equipment, toys and wearables that process such data, connected or not | EN 18031-2:2024 |
| 3.3 (f) | Protects against fraud | Internet-connected radio equipment that lets the user transfer money, monetary value or virtual currency | EN 18031-3:2024 |
“Through other equipment” matters. A Bluetooth sensor that reaches the cloud through a phone app or gateway generally counts as internet-connected.
Some categories covered by their own EU rules, such as certain medical devices and vehicles, are excluded from some or all of these points. Check the regulation text for your category.
The date applies per unit placed on the market, not per design. A product launched in 2023 that is still shipping into the EU today has to comply for every unit placed on the market after 1 August 2025.
EN 18031 and Its Restrictions
The three EN 18031 parts were cited in the Official Journal on 30 January 2025, with restrictions. Applying a cited standard gives you presumption of conformity, but not for clauses covered by a restriction, for example some of the options the standards allow around authentication. That decides your conformity route.
| Your situation | Conformity route |
|---|---|
| EN 18031 applied in full, no restricted clauses used | Internal production control (Module A). You self-declare. |
| Restricted clause used, standard applied in part, or no standard | Notified body: EU-type examination (Module B plus C) or full quality assurance (Module H) |
EN 18031-1 is organized around security mechanisms: access control, authentication, secure update, secure storage, secure communication, resilience, network monitoring, traffic control, cryptographic key protection and cryptography. EN 18031-2 adds data-focused mechanisms such as logging, data deletion and user notification. Each comes with a decision tree that records whether the mechanism applies to your product and why.
What a Module Covers and What You Own
The answer depends on the module architecture. On a hosted module, the radio sits beside your application processor, and that processor handles boot, storage and updates. On a hostless module, your application runs on the module’s own MCU, so the module’s security hardware becomes your platform.
| Area | What the module can provide | What the OEM still owns |
|---|---|---|
| Wi-Fi link security | WPA2 and WPA3 on the CEL Wi-Fi modules named here | Shipping WPA3 or WPA2 as the default, no open networks |
| Secure boot and root of trust | Hostless: CMP4612 has secure boot, a hardware root of trust, TRNG, PUF, a trusted execution environment and crypto accelerators. CMP4020 and CMP4010 have secure boot, TrustZone and an AES/DES/SHA engine | Turning it on, provisioning keys, locking debug ports in production |
| Hosted platform | CMP9605, CMP9610 and CMP961x provide the radio. The CMP9605 lists a secured host interface | Secure boot, storage and update on your host processor |
| Credentials | None | Unique per device, no shared default passwords |
| Updates | CMP4612 lists secure software update and debug | Signing keys, update server, vulnerability handling |
| App and cloud | None | All of it |
| Risk assessment and technical file | Security documentation as input | The assessment, test evidence and EU Declaration of Conformity |
The CMP4612 also lists SESIP3 and PSA Certified Level 3. Those certify the chip platform. They are useful evidence in your risk assessment, but they are not EN 18031 conformity for your product.
An Order of Work
- List every SKU that ships to the EU and mark which of 3.3(d), (e) and (f) apply.
- Run a risk assessment across device, app, cloud and update path. Map each risk to the EN 18031 mechanisms.
- Close the design gaps: unique credentials, secure boot, signed updates, locked debug, encrypted communication.
- Check whether you rely on any restricted clause. If you do, book a notified body early.
- Update the technical file and the EU Declaration of Conformity to reference 3.3(d), (e) and (f) and the standards applied.
Next: The Cyber Resilience Act
The Cyber Resilience Act, Regulation (EU) 2024/2847, covers products with digital elements, including the same connected radio products. Its reporting obligations for actively exploited vulnerabilities apply from 11 September 2026, and most other requirements apply from 11 December 2027. It adds obligations such as vulnerability handling across a support period. Security work you do now for EN 18031 is a start on it, not the whole job.
Choosing a module for an EU product and want to compare its security features? Use the form below and a CEL engineer will follow up.




