FCC weighs covered-list hardware ban as NIST convenes AI data center workshop
The useful signal is provenance: certification filings and AI facilities now share a supply-chain security problem.
TL;DR
Inside Cybersecurity reports that the Federal Communications Commission will consider a Wednesday order barring authorization for devices with logic-bearing hardware components made by entities on the FCC’s covered list. An attached notice would propose requiring Software Bill of Materials or Hardware Bill of Materials filings at certification. NIST also holds a two-day AI data center workshop on architecture, training, security posture, supply-chain issues and emerging standards. The common demand is evidence about what is inside the stack before anyone calls it secure.
The FCC item is the immediate gate. Inside Cybersecurity reports that commissioners will consider a third report and order Wednesday that would prohibit equipment authorization for devices containing logic-bearing hardware components produced by entities on the FCC’s covered list of equipment and services that pose national security risks. The attached further notice would propose requiring certification applicants to submit a Software Bill of Materials or Hardware Bill of Materials. If adopted, component provenance moves out of the supplier questionnaire and into the authorization file.
NIST’s workshop is less immediate but just as telling. NIST says the July 22-23 virtual workshop is part of an effort to develop secure AI data center standards and will cover architecture, hardware, software, data storage, access control, system management, AI training and inference, Operational Technology, facility construction, power, physical and personnel security, supply chain and regulatory challenges (https://www.nist.gov/news-events/events/2026/07/securing-ai-data-center-architecture-security-posture-and-emerging). That list is sprawling because the object is sprawling. AI data center security spans chips, racks, buildings, energy systems, admin access, workers and workloads.
Read together, the week’s compliance signal is practical. Device makers and importers should watch whether restricted hardware content becomes evidence submitted at the point of certification. AI infrastructure teams are still in standards-shaping mode, so their Monday work is to track the scope and feed real technical constraints into NIST’s process. The government is asking for less faith in the stack and more proof of what is in it.
Published ·Deep Fathom