White House unveils Cyber Trust Mark program for consumer devices
The White House launched the Cyber Trust Mark program to enhance consumer awareness of IoT device cybersecurity standards, with products expected to feature the mark by 2025 and federal procurement by 2027.
Read original articleThe White House has introduced the Cyber Trust Mark program aimed at enhancing consumer awareness regarding the cybersecurity standards of Internet of Things (IoT) devices. This labeling initiative, similar to the Energy Star program, will help consumers identify products that meet government-vetted cybersecurity criteria. Developed in collaboration with the National Institute of Standards and Technology (NIST) and the Federal Communications Commission (FCC), the program will be administered by UL Solutions and ten other firms. The Cyber Trust Mark is expected to appear on products by 2025, with major retailers like Amazon and Best Buy assisting in consumer education about the label's significance. The mark will feature a shield symbol and will vary in color based on product design, indicating compliance with NIST standards for safer home integration. Additionally, a forthcoming executive order will mandate that the federal government procure devices bearing the Cyber Trust Mark by 2027, signaling a push towards a more secure IoT market. Deputy National Security Director for Cybersecurity and Emerging Technology, Anne Neuberger, emphasized the importance of this initiative in promoting cybersecurity in consumer products.
- The Cyber Trust Mark program aims to inform consumers about the cybersecurity standards of IoT devices.
- The initiative is developed in collaboration with NIST and FCC and will be administered by UL Solutions.
- Major retailers will help educate consumers about the Cyber Trust Mark.
- The mark is expected to appear on products by 2025, with federal procurement mandated by 2027.
- The program is part of a broader effort to enhance cybersecurity in consumer technology.
Related
Summary of the USA federal government's zero-trust memo
The U.S. government's Zero Trust Cybersecurity Memo promotes enhanced federal cybersecurity by advocating dynamic authentication methods, eliminating long-lived credentials, mandating encryption, and encouraging bug bounty programs for vulnerabilities.
FTC Pushed to Crack Down on Companies That Ruin Hardware via Software Updates
A coalition of 17 consumer groups is urging the FTC to regulate smart device manufacturers over practices like "software tethering" and subscription fees, which threaten consumer rights and product functionality.
Securing Hardware and Firmware Supply Chains
Microsoft is enhancing hardware and firmware supply chain security in cloud data centers through initiatives like Caliptra for device identity, the OCP SAFE program for security reviews, and the SCITT for transparency.
CISA proposes new security requirements to protect govt, personal data
CISA proposed new security requirements to protect sensitive U.S. data from adversarial states, targeting key sectors and recommending measures like vulnerability remediation and encryption, while seeking public feedback.
America's Phone Networks Could Soon Face Penalties for Insecure
The FCC is proposing new regulations to enhance telecommunications cybersecurity, including financial penalties and annual certifications for compliance, in response to increasing threats and past incidents like the Colonial Pipeline attack.
We propose to focus the scope of our program on intentional radiators that generate and emit RF energy by radiation or induction.31 Such devices – if exploited by a vulnerability – could be manipulated to generate and emit RF energy to cause harmful interference. While we observe that any IoT device may emit RF energy (whether intentionally, incidentally, or unintentionally), in the case of incidental and unintentional radiators, the RF energy emitted because of exploitation may not be enough to be likely to cause harmful interference to radio transmissions.
I guess it is the FCC so this makes sense from their point of view. From my perspective, I'd like to see marks indicating:* If the devices can be pointed to an alternate API provider if the company stops supporting
* If firmware has been escrowed / will be made available if the company stops supporting
* If device data is stored by the company
* If that data is certified as end to end encrypted
* Some marks for who / how the data is used
The scary bit is that this label is going to be found to be ineffective, and then consumers may lose trust in government-issued safety stamps.
I'd still put my faith in other indicators like a company's track record, third party audits, robustness of open source library choices where applicable, my own analysis of their stack and engineering choices based on signs I can observe about their product / interface / etc (there are usually several present), my own testing and so forth.
I'd argue the generally accepted pace of consumer product development these days is reckless, and not sustainable if you want truly robust results.
I would have been glad to see this step in the right direction if I weren't convinced all it will likely amount to in practice is security theatre. Here's hoping my skepticism is unwarranted.
1) What are the requirements for the mark? E.g. no passwords stored in plaintext on servers, no blank/default passwords on devices for SSH or anything else, a process for security updates, etc.?
2) Who is inspecting the code, both server-side and device-side?
3) What are the processes for inspecting the code? How do we know it's actually being done and not just being rubber-stamped? After all, discovering that there's an accidental open port with a default password isn't easy.
What the government probably _should_ do is begin establishing a record of manufacturers/vendors which indicates how secure their products have been over a long period of time with an indication of how secure and consumer-friendly their products should be considered in the future. This would take the form of something like the existing travel advisories Homeland Security provides.
Should you go to the Bahamas? Well, there's a level 2 travel advisory stating that jet ski operators there get kinda rapey sometimes.
Should you buy Cisco products? Well, they have a track record of deciding to EOL stuff instead of fixing it when it's expensive or inconvenient to do the right thing.
Should you buy Lenovo products? Well, they're built in a country that regularly tries and succeeds in hacking our infrastructure and has a history of including rootkits in their laptops.
- Must the Cyber Truck (Musk) bear the Cyber Trust Mark?
there is no regulation in tech. they own the fed.
No matter how good everyone in this trust mark program is, you're only one confused deputy[1] away from disaster.
User upgradability if the Company Folds or Sunsets the product. When that happens, the user will need to buy a new device or live with comprised devices. Most will live with the comprised device.
So, IMO, the product should be fully open source and easily upgraded in order to get the Cyber Trust Mark.
https://abcnews.go.com/International/us-diplomats-cuba-suffe...
Verdict: nope.
This is something that an independent, international cybersecurity nonprofit should be in-charge of, not a standards org that shills for what we think may have been the NSA (BULLRUN).
Cybersecurity best practices are a point in time snapshot, the label will be dependent on at purchase time, how will that help people who have purchased second hand, or had products where items on shelves suddenly had a vulnerability discovered? You really think they are going to go through the cost of sending those back?
All software bugs can potentially be security bugs. This follows classic shock doctrine.
We need a blue ribbon commission on transparency, honesty, and good governance desperately. Let's reduce any federal agencies that make any sort of direct-to-citizen recommendations by 100% and instead spend that on rooting out bad incentives, misinformation, etc.
Same thinking afflicts consumer devices. New IoT device? Which known-good security validated and battle tested software stack is the vendor reusing? Oh, your own homebrew stack that phones home? How novel! You mean you slapped on whatever it took to ship? Terrific! There is a bug in ROM with no way to securely remediate? Shocking! /s
Related
Summary of the USA federal government's zero-trust memo
The U.S. government's Zero Trust Cybersecurity Memo promotes enhanced federal cybersecurity by advocating dynamic authentication methods, eliminating long-lived credentials, mandating encryption, and encouraging bug bounty programs for vulnerabilities.
FTC Pushed to Crack Down on Companies That Ruin Hardware via Software Updates
A coalition of 17 consumer groups is urging the FTC to regulate smart device manufacturers over practices like "software tethering" and subscription fees, which threaten consumer rights and product functionality.
Securing Hardware and Firmware Supply Chains
Microsoft is enhancing hardware and firmware supply chain security in cloud data centers through initiatives like Caliptra for device identity, the OCP SAFE program for security reviews, and the SCITT for transparency.
CISA proposes new security requirements to protect govt, personal data
CISA proposed new security requirements to protect sensitive U.S. data from adversarial states, targeting key sectors and recommending measures like vulnerability remediation and encryption, while seeking public feedback.
America's Phone Networks Could Soon Face Penalties for Insecure
The FCC is proposing new regulations to enhance telecommunications cybersecurity, including financial penalties and annual certifications for compliance, in response to increasing threats and past incidents like the Colonial Pipeline attack.