Engineer working on a laptop connected to a device test rig, surrounded by wiring harnesses and test hardware

Firmware vulnerabilities & fixes

The ioXt Alliance Security Pledge and certification programme, explained

Last updated:

The ioXt Alliance is an industry-led, non-profit certification body for consumer and commercial IoT product security, built around an 8-principle Security Pledge and a set of product-category security profiles that manufacturers test against — either by self-certifying or through an Authorized Lab. Its own mission statement describes the goal as building "confidence in Internet of Things products through multi-stakeholder, international, harmonized, and standardized security and privacy requirements, product compliance programs, and public transparency of those requirements and programs." The organization's profile has risen sharply in 2026: on 13 April 2026, the FCC named ioXt the new Lead Administrator of the U.S. Cyber Trust Mark programme, after the prior administrator withdrew amid a national-security review.

Key takeaways

  • No Universal Passwords — unique credentials required for operation.
  • ioXt's certification pages describe a continuous, subscription-style model rather than a one-time test.
  • Per the Pledge document, every profile has three parts: a definition of which devices it covers, a threat analysis for those devices, and a test plan built from a shared ioXt Test Case Library.
  • Two items are easy to underestimate.

What are the 8 Security Pledge principles?

A product certified against ioXt's Security Pledge commits its manufacturer to eight baseline practices:

  1. No Universal Passwords— unique credentials required for operation.
  2. Secured Interfaces— all product interfaces appropriately secured.
  3. Proven Cryptography— strong, updatable methods using open, peer-reviewed designs.
  4. Security by Default— security appropriately enabled without extra user action.
  5. Verified Software— only signed software updates are supported.
  6. Automatic Security Updates— the manufacturer applies timely updates.
  7. Vulnerability Reporting Program— a channel exists with a timely manufacturer response.
  8. Security Expiration Date— transparent disclosure of how long the product will receive updates.

These eight read as a condensed version of the same baseline ideas underlying ETSI EN 303 645 and the UK PSTI regime — unique passwords, a vulnerability disclosure channel, and a disclosed update-support window all appear on every one of those baselines, which is part of why a Pledge-compliant product tends to clear a large share of each scheme's requirements in parallel.

The ioXt Pledge document gives two acceptable ways to meet the eighth principle: print an explicit minimum support date, or publish an end-of-life notification policy, for example "supported for two years from the date of purchase" or "at least two years notice before discontinuing support".

Self-certification or an Authorized Lab: how does ioXt certification actually work?

ioXt's certification pages describe a continuous, subscription-style model rather than a one-time test. A manufacturer submits product information through the ioXt SmartCert portal and measures the product against a published security profile, with an independent researcher validating the submission. From there, two paths diverge:

Path How it works
Self-certification The manufacturer measures its own product against the profile, with independent-researcher validation of the submission
ioXt Authorized Lab "IoT manufacturers and developers seeking more sophisticated testing and the validation of a third-party expert can have an ioXt Authorized Lab perform the test plan and certify the results"

Either path leads to an annual ioXt SmartCert, and ioXt states that "certification status is reevaluated as new device or app versions are released" — certification is not a one-time badge.

ioXt's certification walkthrough breaks the process into five steps:

  1. Jointhe Alliance and register for the certification programme.
  2. Testthe product against the chosen profile, by self-certification or an Authorized Lab.
  3. Submitproduct information and test results in the certification portal and review the profile score.
  4. Certify: ioXt reviews the submission and, if the device or app meets the criteria, grants the SmartCert.
  5. Verify: independent researchers keep reviewing certified products, and the manufacturer receives ongoing status and regulatory updates.

What do the security profiles add on top of the pledge?

ioXt's certification pages list six published profiles, each layering product-category-specific requirements on top of the 8-principle pledge: Base Profile, Android Profile, Mobile Application Profile, Smart Speaker Profile, Residential Camera Profile, and Network Lighting Controller Profile. A manufacturer selects the profile matching its product category rather than certifying against the generic Base Profile alone whenever a more specific profile exists.

Per the Pledge document, every profile has three parts: a definition of which devices it covers, a threat analysis for those devices, and a test plan built from a shared ioXt Test Case Library. Each pledge item has numbered security levels; level 1 is the minimum for certification, and higher levels show stronger protection. The Base Profile is the exception: it covers "all devices which are not covered under another profile" and, because that population is so broad, ships without a threat model.

What does the Base Profile actually test?

The ioXt 2021 Base Profile, version 2.0 (25 March 2021, tied to Test Case Library version 5.0) lists the test cases behind each pledge item:

Pledge item Level 1 (required for certification) Higher levels
Proven Cryptography PC1 standard cryptography L2: PC2 independently reviewed protocol, implementation or open standard
No Universal Password UP1 credentials not common or predictable, or changed at first use L2: UP2.1 / UP2.2 two-factor authentication at initialization and management
Verified Software VS1 update patch policy; VS2 signed and verified images, including plug-ins and apps; VS3 proven cryptography L2: VS4 limit downgrade attacks; L3: VS5 images verified at boot; L4: VS6 secure boot on a hardware root of trust, VS7 anti-rollback
Security by Default No test cases in this profile —
Secured Interfaces SI1.1–SI1.4 remote attack surface: certifiable protocols certified, unused services disabled, authentication, secured communications L2: SI2.1–SI2.3 the same for proximity interfaces; L3: local debug ports disabled
Automatic Security Updates AA1 updates supported; AA2 software maintained and updated; AA3 updates made available to impacted parties L2: AA4 security updates applied automatically when product usage allows
Vulnerability Reporting Program VDP1 programme in place; VDP2 accepts external submissions L2: VDP3 monitoring of security-relevant components; L3: VDP4 disclosure to impacted parties; L4: VDP5 public researcher rewards
Security Expiration Date SE1.1 end-of-life notification policy published, or SE1.2 expiration date published —

Two items are easy to underestimate. Level 4 of Verified Software asks for secure boot anchored in a hardware root of trust plus anti-rollback, which is a silicon and bootloader decision, not a late firmware change. And level 2 of the Vulnerability Reporting Program, monitoring security-relevant components, assumes you know which components ship in each image, which in practice means a firmware SBOM.

ioXt also cross-recognises PSA Certified Level 1, 2 or 3 credentials, stating that PSA Certified silicon "automatically satisfies specific ioXt test cases", which shortens the hardware-related part of the test plan.

How do the eight principles map to ETSI EN 303 645, UK PSTI and NIST IR 8425?

The table below is SoftWSP's reading of the four documents, not an official crosswalk. Sources: ETSI EN 303 645 V3.1.3 provisions 5.1–5.13, PSTI Regulations 2023 Schedule 1, and NIST IR 8425 (September 2022), the baseline behind the US Cyber Trust Mark.

ioXt principle ETSI EN 303 645 UK PSTI Schedule 1 NIST IR 8425 outcome
No Universal Passwords 5.1 No universal default passwords Para 1, passwords Interface Access Control
Secured Interfaces 5.5 Communicate securely; 5.6 Minimize exposed attack surfaces — Interface Access Control; Data Protection
Proven Cryptography 5.4 Securely store sensitive security parameters; 5.5 — Data Protection
Security by Default 5.6; 5.12 Make installation and maintenance of devices easy — Product Configuration
Verified Software 5.7 Ensure software integrity; 5.3 Keep software updated — Software Update
Automatic Security Updates 5.3 Keep software updated — Software Update
Vulnerability Reporting Program 5.2 Implement a means to manage reports of vulnerabilities Para 2, how to report security issues Information and Query Reception
Security Expiration Date 5.3-13 (publish the defined support period) Para 3, minimum security update period Documentation; Information Dissemination

PSTI is a legal minimum covering only three of the eight; ETSI EN 303 645 and NIST IR 8425 go wider than the pledge (data protection, telemetry, resilience). An ioXt certificate is useful evidence for the other schemes, but each still has its own assessment route.

Worked example: what evidence would a small camera maker prepare?

Synthetic example. The company, product and documents are invented for illustration; the profile facts come from ioXt's published profile documents.

A ten-person company sells "ExampleCam C200", a Wi-Fi home camera with cloud video upload. It has an image sensor, an IP interface and remote access to media, so it falls inside the Residential Camera Profile rather than the Base Profile. That profile's threat model adds camera-specific scenarios, including provisioning QR codes visible on the product, NTP attacks, SD-card theft, man-in-the-middle attacks on video upload and camera control, and firmware updates or reboots interrupting monitoring. The team prepares:

Pledge item Evidence prepared
No Universal Passwords Per-device setup code printed inside the box; factory test log showing no shared credentials
Secured Interfaces Port scan of the shipped image; TLS configuration for video upload and control; debug UART disabled in production
Verified Software Signing procedure for OTA images; bootloader check of image signatures; downgrade policy
Automatic Security Updates Update channel description and default-on setting
Vulnerability Reporting Program Public reporting page, triage owner, and per-release SBOM matched against known CVEs
Security Expiration Date "Security updates until at least 31 December 2030" on the product page and box

The SBOM line does double duty: it supports the component-monitoring level of the reporting programme and gives the PSIRT a fast answer when a library CVE lands.

What changed in April 2026 with the US Cyber Trust Mark?

On 13 April 2026, the FCC announced it had selected ioXt as the new Lead Administrator of the U.S. Cyber Trust Mark Program — the voluntary cybersecurity label for consumer wireless IoT products built on the NIST IR 8425 baseline, covered in full in our UK PSTI and US Cyber Trust Mark guide. The FCC's press release describes ioXt as "an independent, U.S.-based non-profit organization, whose focus is on improving the security, privacy, and transparency of IoT products," noting that "ioXt describes itself as the United States' preeminent certification body dedicated to the security of IoT products." The prior Lead Administrator, UL Solutions, had "filed a notice of withdrawal" in December 2025 after FCC Chairman Brendan Carr opened a national-security review into UL's testing locations operating inside China. FCC Chairman Carr's statement framed the selection around that national-security concern: "With today's decision, the FCC is ensuring that the Lead Administrator will implement the program in a way that is consistent with that vision, while advancing national and cyber security."

As Lead Administrator, ioXt's duties — per the FCC's own release — are to collaborate "with stakeholders to develop a consumer outreach campaign and recommend[] to the Commission additional cybersecurity standards, testing procedures, and label design." This is a distinct, government-facing role layered on top of ioXt's pre-existing industry Pledge and profile certification programme described above; the two run in parallel rather than one replacing the other. Further Cyber Trust Mark rollout milestones, such as accredited Cybersecurity Label Administrators and testing labs, are not covered by this April 2026 announcement; the FCC's current programme page tracks them as they are confirmed.

The programme's rules sit in 47 CFR Part 8, Subpart B, "Cybersecurity Labeling Program for IoT Products". Its sections separate the roles: § 8.209 covers the grant of authorization to use the FCC IoT Label, § 8.217 the accredited test labs (CyberLABs), § 8.219 and § 8.220 the Cybersecurity Label Administrators, § 8.221 the Lead Administrator and § 8.222 the IoT Registry. In other words, an ioXt SmartCert is an industry certificate; the FCC label is a separate authorization under these rules, even though ioXt now also holds the Lead Administrator role.

What are the common pitfalls?

  • Certifying against the Base Profile when a specific profile exists. A camera, smart speaker, lighting controller, Android device or mobile app has its own profile with its own threat model.
  • A support period nobody can find. The expiration date or end-of-life policy has to be published where buyers see it, not only in a contract.
  • A reporting page with no component monitoring behind it. Accepting reports meets level 1; monitoring security-relevant components is the next level, and it needs an inventory per release.
  • Leaving secure boot to the end. Boot-time verification and a hardware root of trust are fixed by silicon and bootloader choices made early in design.
  • Treating the SmartCert as permanent. Status is re-evaluated as new device or app versions ship; build the portal update into each release.
  • Assuming ioXt certification equals the FCC label. They are separate authorizations under separate rules.

Where should a manufacturer start?

  1. Map your existing EN 303 645/PSTI work to the 8 principles firstUnique passwords, a disclosed vulnerability-reporting channel, and a published update-support window are shared requirements — don't re-derive evidence you already have for another scheme.
  2. Pick the most specific profile that fits your product, not the generic Base Profile, if a camera, speaker, lighting controller, Android, or mobile-app profile applies.
  3. Decide self-certification vs. Authorized Lab by audienceSelf-certification with independent-researcher validation is faster; an Authorized Lab's third-party test and certification buys more credibility with enterprise, retail, or export buyers.
  4. Plan for annual re-evaluation, not a one-time badgeCertification status is revisited as new device or app versions ship, so build the SmartCert portal update into your release process rather than treating certification as a closed task.
  5. Track ioXt's Cyber Trust Mark role separately from its Pledge programme, since the FCC's own administrator rollout (accredited labs, additional standards recommendations) is still being finalized as of this guide's last-updated date.

For a broader test plan beyond the pledge, the OWASP Firmware Security Testing Methodology covers the firmware side in depth. SoftWSP covers one part of the evidence: it extracts an SBOM from each firmware image, writes it as CycloneDX 1.6 JSON, and matches the components against NVD, CISA KEV, FIRST EPSS and CISA's CSAF ICS advisories, with an AI-drafted report that cites the record behind each finding for an engineer to check; watchlist alerts fire on a CVE ID or vendor/product you follow. It does not test credentials, interfaces, boot chains or cryptography, and it is not an ioXt Authorized Lab. See Device & Firmware Security.

This guide summarises ioXt Alliance's own published pages and the FCC's 13 April 2026 press release; it is not a substitute for ioXt's current certification rules or the FCC's current programme page, and does not constitute compliance or legal advice.

Put this guide to work

Frequently asked questions

What is the ioXt Alliance?

ioXt Alliance describes its own mission as building "confidence in Internet of Things products through multi-stakeholder, international, harmonized, and standardized security and privacy requirements, product compliance programs, and public transparency of those requirements and programs." The FCC's own description, in its 13 April 2026 announcement naming ioXt the new Lead Administrator of the U.S. Cyber Trust Mark Program, calls it "an independent, U.S.-based non-profit organization, whose focus is on improving the security, privacy, and transparency of IoT products," adding that "ioXt describes itself as the United States' preeminent certification body dedicated to the security of IoT products." Secondary sources (e.g., IoT For All's company directory) list a 2019 founding and a Costa Mesa, California base; press coverage from early 2019 traces its first industry gatherings to late 2018 — treat the precise founding date as approximate pending a primary ioXt history page, since ioXt's current site does not publish one.

What are the 8 Security Pledge principles?

Per ioXt's own Pledge page, a certified product's manufacturer commits to: (1) **No Universal Passwords** — unique credentials required for operation; (2) **Secured Interfaces** — all product interfaces appropriately secured; (3) **Proven Cryptography** — strong, updatable methods using open, peer-reviewed designs; (4) **Security by Default** — security appropriately enabled without extra user action; (5) **Verified Software** — only signed software updates are supported; (6) **Automatic Security Updates** — the manufacturer applies timely updates; (7) **Vulnerability Reporting Program** — a channel exists with a timely manufacturer response; and (8) **Security Expiration Date** — transparent disclosure of how long the product will receive updates.

How does ioXt certification actually work — self-certification vs. an Authorized Lab?

ioXt runs what its certification pages describe as a continuous, subscription-style model rather than one-time testing. A manufacturer enters product information into the ioXt SmartCert portal and measures the product against one of ioXt's published security profiles; an independent researcher then validates the submission. Manufacturers choose between two paths: **self-certification**, where the manufacturer measures its own product with that independent-researcher validation step, or testing through an **ioXt Authorized Lab**, where "IoT manufacturers and developers seeking more sophisticated testing and the validation of a third-party expert can have an ioXt Authorized Lab perform the test plan and certify the results." Either path leads to an annual ioXt SmartCert, and "certification status is reevaluated as new device or app versions are released" rather than staying fixed indefinitely.

What are the ioXt security profiles, and how does ioXt relate to the US Cyber Trust Mark?

ioXt's certification pages list six published profiles that layer product-specific requirements on top of the 8-principle pledge: Base Profile, Android Profile, Mobile Application Profile, Smart Speaker Profile, Residential Camera Profile, and Network Lighting Controller Profile. Separately, on **13 April 2026** the FCC announced it had selected ioXt as the new **Lead Administrator** of the U.S. Cyber Trust Mark Program — a voluntary cybersecurity label for consumer wireless IoT products, built on the NIST IR 8425 baseline — after the prior administrator, UL Solutions, "filed a notice of withdrawal" in December 2025 amid an FCC national-security review of its China-based testing locations. As Lead Administrator, ioXt is responsible for "collaborating with stakeholders to develop a consumer outreach campaign and recommending to the Commission additional cybersecurity standards, testing procedures, and label design" — a government role distinct from, and run alongside, ioXt's own pre-existing industry certification programme. See our [UK PSTI and US Cyber Trust Mark guide](/guides/psti-cyber-trust-mark/) for the Cyber Trust Mark's own legal basis and rollout timeline.

Sources

  1. ioXt Alliance: The Pledge — 8 security principles
  2. ioXt Alliance: Get ioXt Certified — self-certification and Authorized Lab testing
  3. ioXt Alliance: Certifying Your Device — security profiles and the SmartCert portal
  4. ioXt Alliance: About ioXt — mission statement
  5. FCC: FCC Selects New Lead Administrator for U.S. Cyber Trust Mark Program (press release, 13 April 2026)
  6. IoT For All: ioXt Alliance company profile (founding year, location)
  7. ioXt Alliance: ioXt 2021 Base Profile, version 2.0 (25 March 2021, PDF)
  8. ioXt Alliance: ioXt 2020 Residential Camera Profile, version 1.0 (PDF)
  9. ioXt Alliance: ioXt Security Pledge (PDF)
  10. ioXt Alliance: ioXt and PSA Certified cross-recognition
  11. eCFR: 47 CFR Part 8, Subpart B, Cybersecurity Labeling Program for IoT Products
  12. ETSI EN 303 645 V3.1.3: Cyber Security for Consumer Internet of Things: Baseline Requirements (PDF)
  13. legislation.gov.uk: PSTI (Security Requirements for Relevant Connectable Products) Regulations 2023, Schedule 1
  14. NIST IR 8425: Profile of the IoT Core Baseline for Consumer IoT Products (September 2022)
Was this guide helpful?

In this cluster