The U.S. Cyber Trust Mark is a voluntary cybersecurity labeling program run by the Federal Communications Commission (FCC) for wireless consumer Internet of Things products, such as cameras, smart locks, baby monitors, voice assistants and connected appliances. A product that carries the shield-shaped mark has been tested by an accredited laboratory against baseline security criteria derived from NIST guidance, and its label includes a QR code linking to a public registry with details about support and updates.
In smart home privacy, the Cyber Trust Mark addresses a long-standing problem: buyers cannot see from the box whether a device uses unique credentials, encrypted communication or security updates. The label turns those hidden properties into a visible purchasing signal, similar in spirit to energy efficiency labels, while leaving participation optional for manufacturers.
How the Cyber Trust Mark program works
The program works through a chain of testing, review and authorization rather than self-declaration alone. A manufacturer submits a product to an FCC-recognized CyberLAB, a testing laboratory accredited to ISO/IEC 17025, which evaluates the device against the applicable criteria. The results then go to a Cybersecurity Label Administrator (CLA), which reviews the application and authorizes use of the mark.
The FCC adopted the framework in March 2024 and the first products could carry the label from early 2025. The Commission oversees the program, recognizes the administrators and laboratories, and can remove the mark from products that no longer comply. Product eligibility, criteria and administration details have continued to evolve since launch, so the current program rules should be checked before relying on any specific procedure.
The table below summarizes the roles of the parties involved.
| Participant | Role | Responsibility |
|---|---|---|
| FCC | Program owner and regulator | Sets rules, recognizes bodies, enforces label use |
| Cybersecurity Label Administrator | Application reviewer | Authorizes labels and manages the process |
| CyberLAB | Accredited testing laboratory | Tests products against the criteria |
| Manufacturer | Applicant | Submits products, maintains support, updates registry data |
| NIST | Technical reference | Provides the baseline security outcomes |
Security criteria behind the label
The criteria are based on the NIST IR 8425 consumer IoT baseline, which describes outcomes a secure product should achieve rather than prescribing particular technologies. This outcome-based approach lets a thermostat and a security camera meet the same principles with different implementations.
The following table lists the main technical and non-technical outcomes and what each means in a household device.
| Outcome | Requirement in practice | Privacy relevance |
|---|---|---|
| Asset identification | Product and components are uniquely identifiable | Enables tracking of vulnerable models |
| Product configuration | Secure defaults; settings can be restored | Removes weak factory settings |
| Data protection | Data protected in storage and in transit | Shields audio, video and usage data |
| Interface access control | Only authorized users reach interfaces | Blocks default password takeover |
| Software update | Updates are secure and can be applied | Fixes vulnerabilities over time |
| Cybersecurity state awareness | Product can detect security incidents | Supports response to compromise |
| Documentation and disclosure | Support period and policies are published | Informs buyers before purchase |
In practice, these outcomes rule out the most common weaknesses exploited by IoT botnets, such as shared default passwords, unencrypted local services and firmware that never receives patches.
What the label and registry tell a buyer
The label tells a buyer that the product met the criteria at the time of certification, and the linked registry supplies the details needed to judge long-term risk. Scanning the QR code opens an entry with information about the manufacturer and the product’s security commitments.
- Support period: the minimum date until which the manufacturer commits to provide security updates.
- Update policy: whether patches are applied automatically or require user action.
- Contact for vulnerabilities: how researchers and users can report security problems.
- Configuration guidance: instructions for changing defaults and securing the device.
- Product identification: model and version information that ties the label to the specific product.
The registry is the more valuable half of the scheme. A shield logo alone cannot convey that support ends next year, whereas the registry entry can, which helps buyers avoid devices that will soon reach end of support.
Comparison with other IoT security schemes
The Cyber Trust Mark is voluntary and market-driven, while several other jurisdictions impose mandatory baseline requirements. The schemes share many principles, notably the ban on universal default passwords and the need for vulnerability reporting and published support periods.
| Scheme | Jurisdiction | Legal status | Technical basis |
|---|---|---|---|
| U.S. Cyber Trust Mark | United States | Voluntary label | NIST IR 8425 baseline |
| UK PSTI regime | United Kingdom | Mandatory since April 2024 | Three core security requirements |
| ETSI EN 303 645 | Europe and global use | Voluntary standard | Thirteen provisions plus data protection |
| EU Cyber Resilience Act | European Union | Mandatory, phased in | Essential requirements and CE marking |
| Singapore CLS | Singapore | Voluntary, tiered levels | Builds on ETSI EN 303 645 |
Because the criteria overlap substantially, a manufacturer that designs to ETSI EN 303 645 is usually well positioned for the Cyber Trust Mark and the UK PSTI regime, although each scheme still requires its own testing or conformity documentation.
Scope, limitations and common misconceptions
The program covers wireless consumer IoT products and excludes categories regulated elsewhere, such as medical devices and motor vehicles. Products from companies on the FCC Covered List, and certain entities connected to it, cannot obtain the label. Wired-only devices, computers and smartphones fall outside the initial scope.
| Misconception | Reality | Practical consequence |
|---|---|---|
| The device cannot be hacked | It meets a baseline, not perfect security | Owners must still update and configure it |
| The label is mandatory | Participation is voluntary | Unlabeled products are not necessarily insecure |
| It certifies data practices | It focuses on security, not data use policy | Privacy policies still need separate review |
| Certification lasts forever | Compliance depends on ongoing support | Check the registry support date |
The most important limitation is that security is not the same as privacy. A labeled camera may encrypt its video perfectly while the manufacturer still collects and shares usage data under its privacy policy, so the mark should be one input among several when evaluating smart device data collection.
The idea in brief
The U.S. Cyber Trust Mark is a security badge on the box of a smart home gadget. It shows that an independent lab checked the device for basic protections. These include no shared default password, encrypted data and a way to get security fixes.
Scanning the QR code on the label tells you how long the maker promises updates. The badge does not mean the device is perfect or that your data is never shared. It simply means the product cleared a minimum security bar that many cheap devices miss.
A practical scenario
A homeowner is choosing between two indoor security cameras with similar prices and image quality. One box carries the Cyber Trust Mark; the other has no label. Scanning the QR code on the first box opens a registry entry showing security updates guaranteed for at least five years, automatic patching and a published address for reporting vulnerabilities.
The unlabeled camera’s documentation mentions a factory login printed on a sticker and gives no support date. The homeowner buys the labeled model, sets up a unique account during pairing and places it on a separate guest network as an extra precaution. Two years later, a vulnerability is disclosed in a common video streaming library, and the labeled camera receives a firmware fix automatically within weeks. The outcome is a device that stays protected for its expected lifetime, with the buyer making the choice in minutes rather than researching security practices from scratch.