For TCBs & test labs
The ban's due-diligence burden lands on you on 6 September, with no tooling behind it. We're piloting a verification API that screens BOM lines against producer attestations and a machine-readable Covered List.
In validation · Supply-chain evidence · US FCC
From 6 September 2026, no device gets FCC equipment authorization if any logic-bearing hardware component — SoC, module, transceiver — was produced by a Covered List entity. Proposed next: a signed HBOM and SBOM with every application.
PolkaSpots is building the attestation layer that makes this provable once per component, instead of once per applicant.
BOOK A 30-MINUTE PILOT CALLFCC adopts the Third Report & Order: no authorization for devices containing logic-bearing hardware components produced by Covered List entities.
The component ban takes effect, thirty days after Federal Register publication on 7 August.
Comments and replies close on the proposal to require a signed HBOM and SBOM with every certification application, term-limited authorizations, and SDoC registration.
The first ISP supply-chain annual report in which foreign-produced routers count.
The first Conditional Approval renewal wave.
Around 43,000 certifications are granted each year through 18 Telecommunication Certification Bodies. The facts that now decide eligibility — who produced each processing component, and who owns that producer — are facts about the component, not about the applicant.
Yet every applicant is expected to research them independently, for every filing, under penalty of revocation. The same chipset gets re-documented hundreds of times. Nobody gets better information. Everybody pays.
One signed attestation per component, made by its producer: producing legal entity, ownership screened against the Covered List and its subsidiaries and affiliates, production sites. Versioned, append-only, cryptographically signed.
Applicants resolve their BOM against these attestations and roll up an HBOM/SBOM a TCB can actually verify — and every applicant using that component reuses the same record.
We filed this architecture as comments with the FCC in ET Docket 21-232.
For TCBs & test labs
The ban's due-diligence burden lands on you on 6 September, with no tooling behind it. We're piloting a verification API that screens BOM lines against producer attestations and a machine-readable Covered List.
For device makers & ODMs
If you file more than a handful of grants a year, you are about to document the same components again and again — and sign for it every time. Attest against the record instead.
Entities, subsidiaries, and affiliates in one structured brief, updated as the list changes. Free.
One brief, no sequence. We email you when the list changes.
Three pilot slots. Same rule as ForgeCRA: design partners shape the schema. Everyone else waits.
Already collecting supplier evidence for the EU Cyber Resilience Act? It is the same attestation problem with a different regulator, and the same record answers both.
Writing on the Covered List, logic-bearing components and HBOM →
The FCC's definition covers essentially any hardware capable of digital processing — devices, modules, and integrated circuits, including modular transmitters, IoT modules, semiconductors, and optical transceivers.
Existing authorizations stand, and applications pending on the effective date are exempt unless amended to change a logic-bearing component. Separately, the FCC has proposed limiting importation and marketing of some previously authorized covered equipment — that proceeding is open.
In force: the component ban and the marketplace FCC-ID display rule. Proposed: signed HBOM/SBOM with every application, term-limited authorizations, SDoC registration, and a US-based liable party.
Named entities including Huawei, ZTE, Hytera, Hikvision, and Dahua — including their subsidiaries and affiliates — plus categorical entries for foreign-produced routers, drones, power inverters, and advanced robotic devices.
No. We build screening data and attestation infrastructure. For legal determinations about your products, use FCC counsel.