IoT regulations: the security and radio rules for connected devices in the EU, UK and US

Marc HaddadForward Deployed Regulatory Engineer
IoT regulations are the radio and cybersecurity rules a connected product has to meet before it can be sold. In the EU, that means the Radio Equipment Directive’s cybersecurity requirements now and the Cyber Resilience Act from December 11, 2027. In the UK, it means the PSTI product security regime. In the US, it means FCC radio authorization plus procurement and state laws.
Key points
- A radio or network connection adds radio and security rules on top of a product’s ordinary safety rules. It does not replace them.
- In the EU, internet-connected radio products have had to meet cybersecurity requirements since August 1, 2025. The Cyber Resilience Act takes over that job on December 11, 2027, and it covers wired products too.
- The UK regime covers consumer connectable products only. It asks for three things: no universal default passwords, a published way to report vulnerabilities and a published support period.
- The US has no single IoT security law. FCC certification covers the radio, the security duties come from federal procurement rules and state laws such as California’s, and the Cyber Trust Mark is voluntary.
- Some duties start after the product ships. EU vulnerability reporting under the Cyber Resilience Act has applied since September 11, 2026, including to products already on the market.
What counts as a connected product?
For regulatory purposes, a connected product is any physical product with a radio, a network port or an internet connection, whether it connects directly or through a hub or phone. That connection pulls it into radio rules if it transmits and security rules if it exchanges data, on top of its ordinary product safety rules.
Each regime uses a different trigger, so the same product can be in scope in one market and out in another. The EU’s radio cybersecurity act turns on a radio that can communicate over the internet, directly or through other equipment.[1] The Cyber Resilience Act turns on any data connection, wired or wireless.[2] The UK regime turns on a consumer product that can connect to the internet or a network,[3] and the FCC’s rules turn on the radio alone.[4]
Start from the product, not the regulation. List each radio module, wired port, companion app and cloud service, then attach each rule to the line it applies to. For the wider question of which regulations apply to your product, start with the general guide. A pre-certified Wi-Fi module does not carry your product’s security assessment with it: the passwords, the app and the update process are yours.
Which IoT rules apply in the EU?
Two layers apply in the EU, one after the other: the Radio Equipment Directive’s cybersecurity requirements for radio products now, and the Cyber Resilience Act for all connected products from December 11, 2027.
Radio Equipment Directive: Directive 2014/53/EU, the Radio Equipment Directive (RED), contains three security requirements: radio equipment must not harm the network, must protect personal data and privacy, and must protect against fraud.[5] They only apply once the Commission switches them on for specific equipment, and Delegated Regulation (EU) 2022/30 did that. The network requirement covers any radio equipment that can communicate over the internet. The privacy requirement covers internet-connected radio equipment, childcare equipment, toys and wearables that can process personal data. The fraud requirement covers internet-connected equipment that lets the user transfer money or virtual currency.[1]
Medical devices are excluded entirely, and vehicles, aviation and road toll equipment are excluded from the privacy and fraud requirements.[1] The requirements have applied since August 1, 2025.[6]
Harmonized standards: EN 18031-1, -2 and -3:2024 were cited in January 2025 with restrictions. For example, they give no presumption of conformity where the user may choose not to set a password.[7] That has a cost. Under the RED, you can only self-assess against these requirements if you applied the cited standards in full. Otherwise, a notified body (an independent assessment body appointed by an EU country) has to be involved.[5]
Cyber Resilience Act: Regulation (EU) 2024/2847, the Cyber Resilience Act (CRA), covers hardware and software “products with digital elements” that have a data connection, so wired and industrial products are included.[2] It excludes products covered by the EU medical device and vehicle type-approval regulations, certified civil aviation products, marine equipment, identical spare parts and products made only for national security or defense.[2] Its essential requirements include a secure-by-default configuration and the ability to fix vulnerabilities through security updates.[2]
Most products can self-assess. Products whose core function matches a category in Annex III are “important” (Class I or II). Class I includes routers, smart home products with security functions (door locks, cameras, baby monitors, alarms), smart home voice assistants and wearables that monitor health. Smart meter gateways and smartcards are “critical.”[2] Class I products can self-assess only if they apply harmonized standards or another specified route. Otherwise they need a notified body. Class II products need third-party assessment unless they qualify as free and open-source software with public technical documentation, and critical products need third-party assessment in every case.[2] Implementing Regulation (EU) 2025/2392, adopted November 28, 2025, describes each category technically.[8] Building an important component, such as a router module, into your product does not make your product important.[2] The EU Data Act is a separate EU law for makers of connected products and sits outside this article.
Which applies when: the RED cybersecurity act or the Cyber Resilience Act?
Until December 10, 2027, internet-connected radio products follow the RED cybersecurity act, and wired products have no dedicated EU product cybersecurity requirement, only the cybersecurity factor in the general product safety assessment for consumer products.[9] On December 11, 2027, the CRA applies in full and the RED cybersecurity act is repealed.[2, 6] From then on, radio products meet the CRA for cybersecurity and stay under the RED for safety, electromagnetic compatibility and spectrum use.[5]
The cutover attaches to each unit placed on the market, not to the design. Units placed on the market before December 11, 2027 stay outside the CRA’s product requirements unless they are substantially modified afterwards.[2] Every unit placed on the market from that date needs CRA conformity, even if the model was assessed years earlier.
Reporting is the exception. CRA vulnerability and incident reporting has applied since September 11, 2026, and it covers in-scope products already on the market.[2] Teams that read December 2027 as the start date miss this one.
Which IoT rules apply in the UK?
Great Britain splits connected products into two regimes: the Radio Equipment Regulations 2017 for the radio, and the Product Security and Telecommunications Infrastructure (PSTI) regime for the security of consumer connectable products.
Radio: The GB radio rules cover safety, electromagnetic compatibility and spectrum use, with duties on manufacturers, importers and distributors. Since October 1, 2024, GB has accepted either the UKCA (UK Conformity Assessed) marking or the CE marking, with no end date. Northern Ireland follows EU rules.[10]
Product security: The PSTI regime has applied since April 29, 2024.[11] Passwords must be unique per product or set by the user. The manufacturer must publish a contact point for reporting security issues and say when reporters will hear back. It must also publish the minimum period it will provide security updates, and it cannot shorten that period later.[11] Meeting named provisions of ETSI EN 303 645, a European standard for consumer IoT security, counts as compliance. So does ISO/IEC 29147, the vulnerability disclosure standard, for the reporting requirement.[11]
Each product must come with a statement of compliance, which can be digital. It names the product, the manufacturer and the support period.[11, 12] Several kinds of product are excepted: medical devices, smart meters, electric vehicle charge points, and desktops, laptops and non-cellular tablets unless they are designed only for children under 14. Vehicles within the type-approval rules are also excepted.[11] Importers and distributors have their own duties, and none may sell a product without its statement of compliance.[3]
Which IoT rules apply in the US?
There is no single federal IoT security law. The US rules come in separate pieces: mandatory FCC radio authorization, federal procurement rules, state laws and a voluntary label.
FCC equipment authorization: A product with Wi-Fi, Bluetooth or cellular is an intentional radiator. It must be certified by a Telecommunication Certification Body (TCB) before it is marketed.[4] The party that holds the grant is responsible for compliance.[13] FCC authorization covers radio emissions, not security.
Federal procurement: The IoT Cybersecurity Improvement Act of 2020 (Public Law 116-207) has barred federal agencies since December 4, 2022 from buying or using IoT devices that prevent compliance with NIST (National Institute of Standards and Technology) standards and vulnerability disclosure guidelines.[14] It binds agencies, not manufacturers, but it reaches you if you sell to the federal government. NIST’s baseline for manufacturers is NIST IR 8259 Rev. 1, published in April 2026.
State laws: California requires connected devices to have reasonable security features. For a device that can be logged into from outside a local network, the law treats a unique preprogrammed password per device, or a forced credential change before first use, as reasonable.[15]
Cyber Trust Mark: On March 14, 2024, the FCC adopted a voluntary label for consumer wireless IoT products, excluding medical devices, motor vehicles and enterprise and industrial products.[16] The FCC named a new lead administrator on April 13, 2026.[17] On October 27, 2026, it sought comment on label design, a three-year renewal cycle and post-market testing, and the security requirements themselves are still to come.[17] Treat the label as a market choice, not a legal requirement. How the US Cyber Trust Mark works is covered in its own guide.
What do manufacturers have to do in each market?
In every market, someone has to assess the product, keep the evidence, mark it and sign for it. This table shows how that works for a consumer product with Wi-Fi.
| Step | EU | UK (Great Britain) | US |
|---|---|---|---|
| Conformity route | RED: self-assessment if cited EN 18031 standards are applied in full, notified body otherwise. CRA from December 11, 2027: self-assessment for most products, third party for many important and all critical products | Radio: UKCA or CE route. PSTI: manufacturer’s own assessment against the three requirements | FCC certification by a TCB; state law requirements self-assessed |
| Technical documentation | Technical file; under the CRA, a cybersecurity risk assessment | Radio technical file; PSTI compliance records | Test reports filed for the grant |
| Marking | CE | UKCA or CE | FCC ID; Cyber Trust Mark optional |
| Declaration | EU declaration of conformity | UK or EU declaration of conformity, plus PSTI statement of compliance | Grant of certification |
| Who is responsible | Manufacturer; importer and distributor checks | Manufacturer, importer, distributor | Grantee |
In the EU, importers must check the conformity assessment, documentation and CE marking before selling, and distributors must act with due care.[2, 5] In all three markets, an importer that skips those checks takes on part of the manufacturer’s risk.
How do you tell which rules apply to a connected product?
Work through the product in a fixed order: connections, exclusions, category and then standards.
- List the connections: each radio, wired port, app and cloud service, per market.
- Check the exclusions: medical devices are excluded from the RED cybersecurity act, the CRA and the UK regime, and type-approved vehicles from the CRA and the UK regime. Exclusions are narrow. A dashcam sold on its own is not a type-approved vehicle, so assess it on its own terms.
- Place the product in a category: the categories decide who does the assessment.
- Check the standards: use the cited edition, check its restrictions, and remember that a test report against an uncited standard gives no presumption of conformity.
Categories change the answer most for these product types:
- Consumer products: every layer applies in every market.
- Industrial equipment: the UK regime and the Cyber Trust Mark cover consumer products only, but the RED cybersecurity act and the CRA make no consumer distinction.
- Wearables: the RED privacy requirement covers any wearable that processes personal data, and health-monitoring wearables are CRA Class I.
- Smart home: locks, cameras, alarms, baby monitors and voice assistants are CRA Class I. A smart plug or bulb with no security function is usually a default product.
Doing this by hand for every product and market is where teams lose track, and Daptic works out which requirements apply to a product in each market and flags the regulatory changes that affect it.
What happens after the product ships?
Several duties start when the product leaves the factory rather than ending there.
- Support period: under the CRA, the support period must be at least five years unless the product is expected to be in use for less time.[2] In the UK, the published period cannot be shortened.[11]
- Vulnerability reporting: under the CRA, an actively exploited vulnerability needs an early warning within 24 hours of the manufacturer becoming aware of it and a notification within 72 hours. A final report is due within 14 days after a fix is available.[2] Reports go through ENISA’s (the EU cybersecurity agency’s) Single Reporting Platform, which opened on September 11, 2026.
- Vulnerability intake: the UK contact point and its response times must stay live for as long as the product is on the market.[11]
When do the obligations start?
This table lists the dates that change what a manufacturer has to do, in order.
| Date | Milestone | Status |
|---|---|---|
| December 4, 2022 | US federal procurement prohibition takes effect (Public Law 116-207, section 7) | In force |
| March 14, 2024 | FCC adopts the Cyber Trust Mark program | Adopted, voluntary |
| April 29, 2024 | UK PSTI regime applies | In force |
| October 1, 2024 | GB recognizes CE marking with no end date | In force |
| December 10, 2024 | CRA enters into force | In force |
| August 1, 2025 | RED cybersecurity requirements apply | In force |
| September 11, 2026 | CRA vulnerability and incident reporting applies (Art. 71(2)) | In force |
| October 27, 2026 | FCC seeks comment on label, renewal and surveillance rules | Proposed |
| December 11, 2027 | CRA applies in full; RED cybersecurity act repealed | Adopted |
| June 11, 2028 | Cybersecurity type-examination certificates under other EU laws expire (CRA Art. 69(1)) | Adopted |
To keep this current, track citations of CRA harmonized standards, any changes to Annex III, revisions of EN 18031 and the FCC’s next public notice on security requirements.
Example: a Wi-Fi smart plug sold in the EU, UK and US
Here is how the article applies to one product: a Wi-Fi smart plug with a companion app and a cloud account, sold in all three markets.
EU, now: the plug communicates over the internet, so the RED network requirement applies. The app account processes personal data, so the privacy requirement applies too. Fraud does not apply, because the plug moves no money. If the setup flow lets users skip a password, EN 18031 gives no presumption for that part, and a notified body has to be involved. The plug carries the CE marking and an EU declaration of conformity. If a vulnerability in the plug is being actively exploited, the 24-hour CRA reporting clock already applies, even for units sold in 2025.
EU, from December 11, 2027: each new unit needs CRA conformity. A plug with no security function is a default product, so self-assessment is available, but the support period must be at least five years unless the plug is expected to be in use for less time.
UK: the plug needs a unique or user-set password, a published contact point, a published support period and a statement of compliance, plus UKCA or CE marking for the radio.
US: the plug needs FCC certification through a TCB. Under California law, a unique password or a forced credential change counts as a reasonable security feature. The Cyber Trust Mark is optional, and the program is not finished yet.
Frequently asked questions
Does the Cyber Resilience Act replace the Radio Equipment Directive?
Only for cybersecurity. From December 11, 2027, the RED cybersecurity act is repealed and radio products meet the CRA instead, while the RED still covers safety, electromagnetic compatibility and spectrum use.
Is there a federal IoT security law in the US?
No. FCC authorization covers the radio, the IoT Cybersecurity Improvement Act governs what federal agencies buy, and security duties for consumer devices come from state laws such as California’s.
Is the Cyber Trust Mark mandatory?
No. It is voluntary, and in October 2026 the FCC was still taking comments on label design, renewal and post-market testing.
Does the UK PSTI regime apply to industrial products?
No. It covers consumer connectable products. Industrial connected equipment sold in Great Britain still needs to meet the radio rules.
Do I have to report vulnerabilities in products already on the EU market?
Yes. CRA reporting has applied since September 11, 2026, and it covers in-scope products placed on the market before December 11, 2027.
Are universal default passwords still allowed?
No, not in the UK, and they fall outside the password options California’s law treats as reasonable. The UK requires a password that is unique per device or set by the user, California treats either as a reasonable security feature, and EN 18031 gives no presumption in the EU if users can skip setting one.
Notes and sources
- Delegated Regulation (EU) 2022/30, particularly Articles 1 and 2.
- Regulation (EU) 2024/2847 (Cyber Resilience Act), particularly Articles 2(1), 3(1), 7(1), 8, 13(8), 19, 20, 69 and 71(2); Article 2(2) to (4), (6) and (7); Annex I, Part I, point (2)(b) and (c); Article 32(1) to (5); Article 14(1) to (3).
- Product Security and Telecommunications Infrastructure Act 2022, Part 1, particularly Part 1.
- 47 CFR 15.201, particularly § 15.201(b).
- Directive 2014/53/EU (Radio Equipment Directive), particularly Articles 3, 12 and 17; Article 3(3)(d) to (f).
- Delegated Regulation (EU) 2026/339, particularly Article 1; recital 5.
- Implementing Decision (EU) 2025/138, particularly Annex, entries 164 to 166.
- Implementing Regulation (EU) 2025/2392, particularly Annexes I and II.
- Regulation (EU) 2023/988 (General Product Safety Regulation), particularly Article 6(1).
- GOV.UK, Radio Equipment Regulations 2017: Great Britain (guidance on the Radio Equipment Regulations 2017, SI 2017/1206).
- PSTI Regulations 2023 (SI 2023/1007)
- GOV.UK, Regulations for consumer connectable product security
- 47 CFR 2.909, particularly § 2.909(a).
- Public Law 116-207 (IoT Cybersecurity Improvement Act of 2020), particularly sections 4, 5 and 7.
- California Civil Code section 1798.91.04
- FCC 24-26, Report and Order, PS Docket No. 23-239, particularly paragraphs 11, 29 and 32.
- FCC DA 26-354, Public Notice, PS Docket No. 23-239
Additional sources:
- European Commission, Cyber Resilience Act reporting obligations
- SI 2025/211
- GOV.UK, Radio Equipment Regulations 2017: Great Britain
- NIST IR 8259 Rev. 1
- FCC DA 26-1162, Public Notice, PS Docket No. 23-239
This article reflects Marc Haddad’s independent opinions, not necessarily those of Daptic.



