Daptic announces $22M funding to bring compliance into product development. Learn More
Request Demo
Expert Authored

US Cyber Trust Mark: how the FCC’s IoT security label works

The US Cyber Trust Mark explained: what the FCC's voluntary IoT security label covers, what manufacturers commit to and where the program stands.
A checklist card with a shield icon titled US Cyber Trust Mark, listing six manufacturer commitments, on indigo gradient columns.
November 20, 2026

Michelle NgMichelle NgSenior Regulatory Analyst

 

The US Cyber Trust Mark is a voluntary cybersecurity label for wireless consumer smart products, run by the Federal Communications Commission (FCC). A product that meets a federal security baseline can carry a shield logo and a QR code linking to its security details. As of November 2026, the FCC was still finishing the rules, and no product could be certified yet.

 

Key points

 

  • Voluntary to join, binding once joined: No US law requires the mark, but a manufacturer that uses it signs declarations under penalty of perjury and can face FCC enforcement if it breaks them.
  • It covers wireless consumer smart products: Computers, smartphones, routers, wired-only devices, FDA-regulated medical devices, vehicles and enterprise products are outside it.
  • The test covers the company as well as the device: Four of the ten security criteria concern the manufacturer’s own processes, such as answering vulnerability reports and publishing a support period.
  • A chain of bodies grants it: An accredited lab tests the product, a Cybersecurity Label Administrator authorizes the label, and the product’s details go into a public registry.
  • The rules are not finished: The technical standards, renewal period and label design were still open in November 2026, and the FCC expects the first labeled products within about a year.

What is the US Cyber Trust Mark?

 

The US Cyber Trust Mark is the FCC’s label for consumer Internet of Things (IoT) products, meaning everyday devices that connect to the internet and sense or act on the physical world. A qualifying product shows a shield logo and a QR code that leads to a public registry entry about its security.

 

The FCC created the program in a Report and Order adopted on March 14, 2024, and the rules took effect on August 29, 2024.[1, 2] They sit in Part 8 of the FCC’s rules in Title 47 of the Code of Federal Regulations (CFR), where the label is formally called the FCC IoT Label.[3]

 

The label is binary: a product either meets the requirements or it doesn’t, with no grades or star ratings.[1] The QR code must appear wherever the mark does, and the registry behind it tells a buyer how long the product will get security updates, how to change the default password and whether updates install automatically.[1, 3]

Is the Cyber Trust Mark mandatory?

 

No. A connected product can be sold in the US without the mark, and the FCC rejected arguments that participation should be mandatory.[1] The mark is also separate from FCC equipment authorization, the radio approval that wireless devices need whether or not they join the program.[1]

 

The obligations start when a manufacturer opts in. Its application includes declarations made under penalty of perjury, and a company that misuses the mark or breaks its commitments can face FCC fines (called forfeitures), cease-and-desist orders, loss of the right to use the label, and claims of trademark infringement or breach of contract.[1, 3] Using the mark in a deceptive or misleading way in advertising is prohibited.[3]

 

The reason to join is commercial. Retailers and institutional buyers may come to use the mark as a quick check of baseline security, the way many already look for ENERGY STAR on appliances. The binding security rules for connected products sit elsewhere, in laws such as the EU’s Cyber Resilience Act and the UK’s Product Security and Telecommunications Infrastructure (PSTI) Act.

Which products does the Cyber Trust Mark cover?

 

It covers consumer IoT products: devices meant mainly for consumers that connect to the internet, intentionally emit radio energy, and have at least one sensor or actuator and one network interface.[1, 3] The “product” also includes the parts needed to use the device beyond its basic functions, such as a hub, a companion app and the cloud backend.[1, 3]

 

That second point shapes the work. A device can be secure on its own and the product can still fall short if the app or the cloud service behind it doesn’t meet the criteria.

 

The table below shows how common product groups fall under the 2024 rules.

 

Product group Status in the program
Wireless smart home and personal devices: locks, thermostats, lighting, cameras, smart watches, fitness trackers In scope
Connected toys, baby monitors and other children’s products In scope if they meet the same device definition
Wired-only devices Excluded for now
Personal computers, smartphones and routers Excluded
Medical devices regulated by the Food and Drug Administration (FDA) Excluded
Motor vehicles and motor vehicle equipment Excluded
Enterprise and industrial products Excluded
Products tied to entities on US government restricted lists Barred

 

The product category alone doesn’t decide it. A connected toy and a smart lock face the same test, while a wired-only appliance is left out however smart it is.[1] Routers are out because the FCC followed the National Institute of Standards and Technology (NIST) definition of an IoT device, which excludes them. NIST published separate router requirements, NIST IR 8425A, in September 2024, but the 2024 rules still leave routers out.[1, 4]

 

Products made by companies on the FCC’s Covered List, the Commerce Department’s Entity List or the Defense Department’s list of Chinese military companies, or containing components from them, cannot get the label, and neither can products tied to suspended or debarred parties.[3]

Who runs the Cyber Trust Mark program?

 

The FCC owns the mark and sets the rules, but private bodies do most of the day-to-day work.[1] Each has a defined role.

 

  • FCC Public Safety and Homeland Security Bureau: approves the standards, test procedures and label design. Commissioner Olivia Trusty supervises the program, an assignment from Chairman Carr that she announced on October 28, 2026.[5]
  • Lead Administrator: develops and recommends technical standards and test procedures, runs consumer outreach and links the FCC with the label administrators. The ioXt Alliance has held the role since April 13, 2026.[6]
  • Cybersecurity Label Administrators (CLAs): review applications, grant permission to use the label and run post-market checks. They must be accredited to ISO/IEC 17065, the international standard for product certification bodies.[1, 3]
  • CyberLABs: test products against the approved standards. They must be accredited to ISO/IEC 17025, the standard for testing labs, and a manufacturer’s own lab can qualify if it is accredited and recognized by the Lead Administrator.[1, 3]
  • Manufacturer: applies, makes the declarations, publishes registry data and stays responsible for the product’s continued compliance.[3]

 

Administrators and labs owned or controlled by a foreign adversary government, such as China or Russia, cannot take part.[1]

What security requirements does a product have to meet?

 

The baseline is NIST IR 8425, NIST’s 2022 profile of security outcomes for consumer IoT products, which the FCC adopted as the program’s criteria.[1, 7] It has ten outcomes: six for the product and four for the manufacturer.

 

The table lists all ten.

 

NIST IR 8425 outcome What it asks for
Asset identification The product can be uniquely identified and keeps an inventory of its components
Product configuration Settings can be changed only by authorized users, and a secure default can be restored
Data protection Stored and transmitted data is protected from unauthorized access and changes
Interface access control Access to interfaces, protocols and services is limited to authorized parties
Software update Software can be updated only through a secure, configurable mechanism
Cybersecurity state awareness The product helps detect security incidents
Documentation The manufacturer records security information across the product’s life
Information and query reception The manufacturer can receive and respond to security reports and questions
Information dissemination The manufacturer tells customers and the public about security matters, such as updates
Product education and awareness The manufacturer helps customers use the product securely

 

These outcomes are not test specifications. The FCC said they must be developed into requirements with testing procedures, which the Lead Administrator drafts and the Bureau approves after public comment, and labs cannot be recognized until that happens.[1] As of November 2026, that step was still open: the first Lead Administrator filed recommendations in June 2025, ioXt filed more on October 26, 2026, and the Bureau said it would seek comment on both in a later notice.[8]

 

The last four rows are where companies most often underestimate the work. A device can pass every lab test and the application still fail if the company has no working channel for vulnerability reports or no published support period.

What does a manufacturer commit to beyond testing?

 

The application binds the company to ongoing duties. Under penalty of perjury, the applicant declares that the product meets the requirements, has no ties to restricted entities, and that the company will identify critical vulnerabilities and fix them until the support period end date it discloses.[3]

 

  • Support period: The manufacturer decides how long the product will get security updates and must publish the end date in the registry, or state that the product is unsupported.
  • Registry data: product and manufacturer names, authorization date and status, the CLA and test lab, default password instructions, secure setup guidance, whether updates are automatic, the support end date, and whether the company keeps a software or hardware bill of materials (SBOM or HBOM), meaning a list of the components inside.[1, 3]
  • US agent: an applicant names a US agent to receive legal papers and keeps it for at least a year after it stops marketing the product, and a US-based company can name itself.[3]
  • Records: design specifications, production testing procedures and test results, kept for two years after the product stops being marketed.[3]
  • Corrections: if the FCC finds a noncompliance complaint justified, the manufacturer has 20 days to report how it will fix future production and units already sold, and an inadequate response leads to termination.[3]

How do you get the Cyber Trust Mark?

 

The route runs through a lab, a CLA and the registry. Product applications had not opened as of November 2026, so the steps describe how the rules set the process up.

 

  1. Check scope: Confirm the product meets the device definition, falls outside the exclusions and has no restricted-list ties in its supply chain.
  2. Set up the processes: Decide the support period and put vulnerability intake and update processes in place, since the declarations depend on them.
  3. Test: Have a recognized CyberLAB test the whole product, app and backend included, against the approved standards.
  4. Apply to a CLA: Submit the test report, declarations and US agent details. The CLA issues a written grant, and the label can’t be used before its date.[3]
  5. Publish registry data: Make the required information available through the registry’s common interface so the QR code resolves to it.[1, 3]
  6. Apply the label: Show the mark and QR code where buyers will see them, usually on the packaging, with flexibility for online sales and products bought unboxed.[1] An October 2026 proposal would adopt the Lead Administrator’s recommended minimum label size of 1 by 2 inches, with smaller options for small products still open for comment, and would also require the label in product documentation.[8]
  7. Maintain and renew: Respond to post-market sampling and complaints, and renew before the authorization lapses. The Bureau proposed a three-year renewal cycle, renewal applications at least 90 days before expiry, and CLAs sampling at least 3% of the products they certified each year.[8]

What is the status of the Cyber Trust Mark program?

 

The program exists in the FCC’s rules but was not open to products in November 2026. Its administrators were still being put in place and its technical standards were not approved.

 

On December 11, 2024, the Bureau conditionally approved 11 CLAs, and that month it approved UL Solutions as the first Lead Administrator.[9] Conditional approval does not let a CLA certify products.[9]

 

In June 2025, the first Lead Administrator filed recommendations on technical requirements, label design, renewal and surveillance.[8] On August 15, 2025, CTIA Certification withdrew as a CLA, and UL Solutions withdrew as Lead Administrator effective December 19, 2025.[9]

 

In January 2026, the Bureau opened new application windows for a Lead Administrator and for more CLAs.[9] On April 13, 2026, it selected the ioXt Alliance as the new Lead Administrator.[6]

 

On October 27, 2026, the Bureau proposed rules on label design, renewal, post-market surveillance and complaints, with comments due 30 days after Federal Register publication.[8] On October 28, 2026, Commissioner Trusty said consumers should begin to see labeled products within the next year and that a notice on technical requirements and testing would follow in the coming months.[5]

 

Each of those notices can change what a manufacturer has to prepare, from label size to renewal timing, while the mandatory rules for the same device keep moving in other markets. Daptic tracks regulatory changes like these across jurisdictions, flags the ones that affect a company’s products and works out which requirements apply to each product in each market. The 2024 order also lets FCC staff pursue mutual recognition with other countries’ labels, but none of the FCC notices above announces an agreement, so a label earned abroad doesn’t carry over.[1]

Example: preparing a connected camera for the Cyber Trust Mark

 

Consider, as an example of applying this article to a product, a composite manufacturer of a Wi-Fi home security camera sold with a phone app and a cloud video service, built by a contract factory overseas.

 

Scope: The camera is wireless, internet-connected and has a sensor, and it is sold to households, so it is in scope. The app and cloud service are part of the product, which puts the cloud team inside the project, not just the hardware engineers.

 

Supply chain: Procurement checks the factory and key parts, such as the Wi-Fi module, against the restricted lists, since one listed component would bar the label.

 

Criteria: Engineering owns the product outcomes: unique default credentials, encrypted video in transit and at rest, and signed updates. The company-side outcomes need a public vulnerability reporting channel, documented security information and customer guidance, which usually sit with security, support and marketing.

 

Support period: The team picks an end date it can keep across camera, app and cloud, because the vulnerability declaration runs until that date.

 

Timing: Applications are not open, so the useful work now is building that evidence and reserving packaging space for the label, then checking the technical requirements notice when it is published.

Frequently asked questions

Is the US Cyber Trust Mark mandatory?

No. It is a voluntary FCC program and a connected product can be sold in the US without it, but a manufacturer that joins is bound by its declarations and can face FCC enforcement.

Can products carry the Cyber Trust Mark yet?

Not as of November 2026. The technical standards were not approved and conditionally approved CLAs could not certify products, and the FCC expects labeled products within about a year.

Are routers covered by the Cyber Trust Mark?

No. The 2024 rules follow NIST’s definition of an IoT device, which leaves out routers, personal computers and smartphones, although NIST has since published separate router requirements.

How long does Cyber Trust Mark certification last?

That is not settled yet. In October 2026, the FCC’s Bureau proposed a three-year renewal cycle, shorter than the five years an industry committee recommended.

Does the Cyber Trust Mark replace FCC equipment authorization?

No. Wireless devices still need FCC equipment authorization whether or not they carry the mark.

Can a manufacturer test in its own lab?

Yes, if the lab is accredited to ISO/IEC 17025 and recognized by the Lead Administrator, and it meets the same requirements as an independent lab.

Notes and sources

 

  1. FCC Report and Order FCC 24-26, Cybersecurity Labeling for Internet of Things (released March 15, 2024), particularly paragraphs 106 to 108; paragraphs 109 and 111 to 113; paragraphs 11 and 12; paragraph 43; paragraph 131; paragraphs 15 and 16; paragraph 21; paragraphs 15, 29 and 39; paragraph 16; paragraphs 42 and 44; paragraphs 53 and 59; paragraphs 72 to 74; paragraphs 61 and 77; paragraphs 96 and 99; paragraphs 67, 102 and 104; paragraphs 109 and 110; paragraphs 44 and 136.
  2. Federal Register, 89 FR 61242 (July 30, 2024), Cybersecurity Labeling for Internet of Things
  3. 47 CFR Part 8, Subpart B (eCFR), particularly sections 8.201 to 8.222, including section 8.203(f); section 8.222(b); sections 8.208(c) and 8.216; section 8.213(b); section 8.203(b) and (i); section 8.203(j); section 8.204; section 8.220; section 8.217; section 8.207; section 8.208(c) and (f); section 8.208(i); section 8.215; sections 8.214 and 8.216(a); sections 8.208 and 8.209.
  4. NIST IR 8425A, Recommended Cybersecurity Requirements for Consumer-Grade Router Products (September 2024)
  5. Remarks of FCC Commissioner Olivia Trusty, U.S. Cyber Trust Mark event, October 28, 2026
  6. FCC Public Notice DA 26-354, April 13, 2026
  7. NIST IR 8425, Profile of the IoT Core Baseline for Consumer IoT Products (September 2022)
  8. FCC Public Notice DA 26-1162, October 27, 2026, particularly paragraph 6; paragraphs 7, 9, 12, 13, 16, 31, 37 and 44.
  9. FCC Public Notice DA 26-18, January 6, 2026

 

Additional sources:

 

 

This article reflects Michelle Ng’s independent opinions, not necessarily those of Daptic.

Resources

Related Articles

Request a Demo Today