Where does EN 18031 come from?
The Radio Equipment Directive (2014/53/EU) always had three optional cybersecurity clauses, articles 3(3)(d), (e) and (f). Delegated Regulation (EU) 2022/30 switched them on for most wireless devices, from 1 August 2025. CEN and CENELEC then published EN 18031-1, -2 and -3 as the harmonised standards for those clauses, and the Commission cited them in the Official Journal in January 2025. A product that applies them is presumed to meet the requirements, which means you can assess it yourself instead of going to a notified body.
What does it check?
Each part lists security mechanisms and, for each one, requirements with a decision tree: a series of questions that leads to "pass", "fail" or "not applicable", with the reasons written down. The mechanisms you will meet most:
- Access control. Only authorised users and services can reach security and network assets.
- Authentication. Passwords must be unique per device or set by the user, meet strength rules, and be protected against brute force.
- Secure update. Firmware and software updates are authenticated and their integrity checked before they install.
- Secure storage. Security and privacy assets, such as keys and credentials, are protected on the device.
- Secure communication. Data in transit is protected with current, well-reviewed cryptography.
- Resilience. The device resists denial of service and keeps working when the network misbehaves.
- Network monitoring and traffic control. For network equipment: detecting and limiting malicious traffic.
- Confidential cryptographic keys. Keys are generated, stored and used so they cannot be read out.
- Logging, deletion and user notification. In parts 2 and 3: security events are logged, users can delete their data, and users are told about security-relevant changes.
The standard is mostly assessed on documentation: an asset list, the security mechanisms you implement, the decision-tree answers with evidence, and test results where the standard asks for them.
The restrictions you must know
When the Commission cited EN 18031 in the Official Journal, it added restrictions. If your product falls into one of them, the standard no longer gives a presumption of conformity for that requirement, and a notified body has to examine the product. The two that catch most teams:
- The product lets the user choose not to set a password, or not to use one, for access to the device's security or network functions.
- In part 2, for toys and childcare equipment: parental or guardian control options that the standard leaves to the manufacturer's choice.
Read the citation itself, Commission Implementing Decision (EU) 2025/138, against your design before you choose self-assessment. Removing an optional "no password" path is often cheaper than a notified-body examination.
A practical route to conformity
- Decide which parts apply. Internet connection, personal data, toys or wearables, and money each switch a part on.
- List the assets. Network functions, security functions, personal data, credentials and keys, and where each one lives.
- Walk the decision trees. For each mechanism, record the answer and the evidence: design documents, code references, test results.
- Check the restrictions. If one applies, change the design or plan for a notified body.
- Fix and test. Typical fixes are unique credentials, signed updates, encrypted storage and closing debug interfaces.
- Write the technical file and the declaration of conformity, then affix the CE mark.
Plan the firmware fixes first. They take the longest and they are the same work the Cyber Resilience Act will ask for.
How does it lead into the CRA?
The Cyber Resilience Act applies in full from 11 December 2027 and covers the same risks for every connected product, wireless or not. The Radio Equipment Directive's cybersecurity rules are expected to give way to it at that point. Everything you build for EN 18031, from secure updates to key storage, counts towards the CRA's product requirements. What the CRA adds is mostly process: a software bill of materials, vulnerability handling, a declared support period, and reporting of exploited vulnerabilities within 24 hours, which has applied since 11 September 2026.
How we work with this
We implement the mechanisms EN 18031 checks: secure boot, signed over-the-air updates, unique credentials, key storage in secure elements or TrustZone, encrypted communication, and the evidence that goes into the technical file. We write new firmware in Rust where we can. See our delivered device work, or take the device CRA check to see where your product stands.
FAQ
Q01Is EN 18031 mandatory?
The Radio Equipment Directive's cybersecurity requirements are mandatory for in-scope wireless devices since 1 August 2025. EN 18031 is the harmonised standard that gives a presumption of conformity with them. You may meet the requirements another way, but then a notified body has to examine the product.
Q02Does EN 18031 apply to devices without internet access?
Part 1 applies to radio equipment that can communicate over the internet, directly or through another device such as a phone or a gateway. A Bluetooth device that talks to an app which talks to the cloud usually counts. A purely local radio device may fall outside part 1, but check parts 2 and 3.
Q03What happens to EN 18031 when the CRA applies?
The Cyber Resilience Act covers the same risks more broadly, and the Radio Equipment Directive's cybersecurity rules are expected to give way to it once it applies on 11 December 2027. The engineering work you do for EN 18031 carries over; the CRA adds process duties such as the SBOM, vulnerability handling and reporting.
Q04Is EN 18031 the same as ETSI EN 303 645?
No. EN 303 645 is a baseline standard for consumer IoT security and is not harmonised under the Radio Equipment Directive. The two overlap a lot, so work done for one helps with the other.
Sources
This guide is a summary for engineering teams, not legal advice. Check your product's conformity route with your compliance team or a notified body.
