European Union · RED 2014/53/EU + EN 18031
Wi-Fi 7 Router to the EU: RED 2014/53/EU + EN 18031 Cyber File That Clears Customs
Since 1 August 2025 the cybersecurity clauses of the Radio Equipment Directive apply to every connectable radio product sold in the EU. EN 18031-1/-2/-3 replace the old self-declaration route: no harmonised standard means no presumption of conformity.
Since 1 August 2025 the cybersecurity clauses of the Radio Equipment Directive apply to every connectable radio product sold in the EU. EN 18031-1/-2/-3 replace the old self-declaration route: no harmonised standard means no presumption of conformity.
Scope
Which products are caught
01
Any radio equipment that connects to the internet, processes personal data, or handles virtual money: Wi-Fi routers, mesh nodes, cameras, smart locks, BLE sensors, wearables, POS terminals.
02
Pure receivers, broadcast receivers and wired-only products stay outside Article 3.3, but they still need RED 3.1(a) safety, 3.1(b) EMC and 3.2 spectrum.
03
A product with an already-certified radio module still needs its own 3.3 assessment; module certificates do not carry over.
Test items
What EN 18031-1 actually checks
01
Access control: no default or guessable credentials, account lockout, secure pairing and commissioning.
02
Secure communication: TLS configuration, certificate handling, key storage, protection against replay and man-in-the-middle.
03
Secure update: signed firmware, rollback protection, update authenticity, protection against downgrade attacks.
04
Availability and resilience: resistance to flooding, resource exhaustion and denial of service; logging of security events.
Documents
The file a Notified Body will ask for
01
Security target and asset inventory — what data the device holds and where it flows.
02
Software architecture with the security mechanisms mapped to each EN 18031 clause.
03
Test evidence or a manufacturer self-assessment per EN 18031-1/-2/-3, plus a residual-risk statement for any clause not covered.
04
If no harmonised standard is fully applied, a Notified Body opinion is mandatory before the CE declaration.
Pitfalls
Where files get rejected
01
Default admin password still shipped in firmware, or a password policy left to the app rather than the device.
02
OTA update without signature verification — the single most common finding in 2025 reviews.
03
Open debug ports, UART shells or unauthenticated local APIs left enabled in production firmware.
04
No security logging and no way to export it, so incident response cannot be demonstrated.
Timeline
Plan the schedule before the launch date
01
Cyber assessment alone: 4–6 weeks for a well-documented device; 8–10 weeks if firmware fixes are needed.
02
Full RED package (safety, EMC, radio, cyber): 8–12 weeks from samples to declaration.
03
Add 2–3 weeks if a Notified Body opinion is required because no harmonised standard applies to the device category.
Inquiry / Request a quote
Tell us what you need, we reply within 24 hours.
×WeChat
17722522312
Same number as our phone. Search it in WeChat to add us, or call 17722522312

One-stop testing and certification for ESS and lithium batteries — UN38.3, IEC 62619, CE, UL, FCC and more.
Contact
+86 177 2252 2312- sunny.lcs@powcert.com
- Juji Industrial Park, Shajing, Bao'an District, Shenzhen, China
© 2026 LCS Testing Group. All rights reserved.