U.S. Restrictions on Surveillance Technology: What Is Banned, What Is Limited and What Changed in 2026
New FCC action reaches surveillance chips inside other brands’ devices. But equipment authorization, federal contracting and commercial spyware controls remain different rules—and none amounts to a ban on all surveillance.
A security camera can arrive in an American warehouse with an unfamiliar brand on the box and a far more consequential name hidden inside it. That gap between the finished product and its components is now a central issue in U.S. surveillance policy.
On October 22, 2026, the Federal Communications Commission announced that its Office of Engineering and Technology had prevented a dashboard camera and a wireless video transmitter from being marketed or sold in the United States. The agency said both contained a chip made by HiSilicon, a Huawei subsidiary. It described the action as its first enforcement of new component rules that had taken effect the preceding week. The announcement is the primary source; reporting by The Record independently covered the action the following day.
The practical message is not that every camera has suddenly become illegal. It is that checking the brand on a box is no longer enough to understand whether a device can enter the U.S. market. For importers, retailers, security installers and corporate buyers, the question increasingly reaches into the hardware supply chain.
For everyone else, there is a second important distinction. Washington’s restrictions on surveillance technology are not one law. They are overlapping measures governing equipment approvals, importation and marketing, federal procurement, exports, government use of commercial spyware and, in some cases, the people involved in abusive surveillance. Understanding the boundary between them matters as much as understanding the headline.
WHAT CHANGED: THE FCC NOW LOOKS INSIDE THE DEVICE
The FCC’s Third Report and Order, adopted July 22 and released July 23, 2026, addresses what the agency calls a component-part loophole. Its core rule prohibits authorization of devices incorporating logic-bearing hardware components when the device would itself be prohibited from receiving authorization if it had been produced by the relevant Covered List entity.
That last condition is important. The rule is not simply a prohibition on every part associated with every foreign manufacturer. It follows the scope of the underlying Covered List determination. The order distinguishes producer- or provider-based restrictions from those based on where equipment is produced, and explains that use-based entries retain relevant scope conditions.
A logic-bearing component is a physical part that performs digital functions—not an ordinary screw, enclosure or passive cable. The order gives examples distinguishing a plain battery cell from a battery-management system containing control logic, and a bare motor from a motor-controller board. A manufacturer cannot necessarily solve a restricted-chip problem by changing the label on the finished device.
In its October announcement, the FCC said HiSilicon advertised the relevant chip as designed for the surveillance market, with built-in human-face detection algorithms. That is the agency’s description of the manufacturer’s marketing. It does not establish that the two blocked devices were observed stealing Americans’ data. The FCC action rests on its national-security authorization framework, not on a published forensic demonstration that each device had conducted an espionage operation.
The release identified device categories but did not provide consumer-facing model names. Readers should therefore resist social-media lists claiming to identify those exact products without separate evidence. The sound conclusion is narrower: the FCC has begun using its component rules to stop particular devices from obtaining the approvals necessary for U.S. marketing and sale.
OLDER APPROVALS ARE NO LONGER THE WHOLE ANSWER
The October action sits on top of another important 2026 development. In a June 26 public notice, the FCC’s Public Safety and Homeland Security Bureau and Office of Engineering and Technology prohibited continued importation and marketing of certain previously authorized covered communications equipment added to the Covered List in 2024 or earlier.
That notice explicitly says the prohibition does not affect continued use or operation of already-purchased communications equipment. It also says its action does not extend to equipment added to the Covered List in 2025 or 2026, giving certain foreign-produced drones, drone components and routers as examples. Different categories can have different rules; the June notice should not be stretched to cover everything on the list.
For a homeowner, that distinction is reassuring but not a security guarantee. A camera can remain lawful to operate while still being obsolete, unsupported or inappropriate for a sensitive setting. Conversely, a prohibition on importing or marketing a covered model does not, by itself, tell an existing owner to remove it immediately.
For a distributor, the lesson is less comfortable. An old FCC authorization is no longer sufficient evidence that every previously approved covered product may continue to be imported and marketed. The current list, later agency orders, product scope and applicable exceptions all need checking.
THE COVERED LIST IS SPECIFIC, NOT A LABEL FOR ALL CHINESE TECHNOLOGY
The FCC Covered List is a statutory national-security instrument identifying specified equipment and services. It includes Huawei and ZTE telecommunications equipment, as well as specified surveillance and telecommunications equipment from Hytera, Hikvision and Dahua.
The entries are not interchangeable. For the latter manufacturers, the descriptions include particular public-safety, government-facility security, critical-infrastructure surveillance and other national-security purposes. The exact wording, applicable definitions and any approved compliance arrangements matter. A summary saying that every product from every named company is prohibited in every setting is too broad.
Nor should a reader assume that a product absent from the Covered List is secure. The list answers a particular regulatory question. It is not a comprehensive inventory of vulnerabilities, poor password practices, excessive data collection or unreliable software updates across the consumer-electronics market.
SECTION 889: WHY FEDERAL CONTRACTORS FACE A DIFFERENT TEST
Another frequently confused measure is Section 889 of the National Defense Authorization Act for fiscal year 2019, implemented through the Federal Acquisition Regulation.
Broadly, Part A restricts federal agencies from procuring or obtaining systems using covered telecommunications equipment or services as a substantial or essential component, or as critical technology. Part B restricts federal contracting with entities that use covered equipment or services, subject to the law’s definitions, exceptions and waiver provisions. Its reach can extend beyond the equipment used directly to perform a particular federal contract.
Consider an illustrative example, not a finding about any company: a regional consulting firm seeks a federal contract while its office uses a covered security system. A sales representative’s assurance that the system is not connected to the project does not necessarily answer the Part B question. The firm needs a documented assessment under the contracting rules.
This is why an installer’s broad claim of “NDAA compliance” should invite follow-up questions. Which provision? Which equipment and services? Which components? Which actual use? What records support the representation? A short slogan is not a substitute for a product- and organization-specific review.
Section 889 is a federal contracting restriction, not a universal ban on private consumers owning all products from the manufacturers it names. The FCC’s market-access rules and contracting requirements may overlap in practice, but compliance with one does not automatically establish compliance with the other.
COMMERCIAL SPYWARE IS A DIFFERENT PROBLEM
A network camera and spyware installed on a phone both involve surveillance, but they create different risks. A camera may collect footage where it is installed. Commercial spyware can, depending on the product and exploit, covertly compromise a device and access communications or other sensitive information. The important distinction is capability and use, not whether both can be described as monitoring tools.
In November 2021, the Commerce Department added NSO Group and Candiru to the Entity List. Commerce said the companies developed and supplied spyware to foreign governments that used it to target officials, journalists, activists, academics and others. That is the department’s stated basis for its action; this article does not independently reconstruct each alleged deployment.
Entity List designations impose requirements on exports, reexports and transfers of items subject to the Export Administration Regulations to listed entities, according to the relevant entries. They should not be casually described as a blanket consumer-ownership ban or treated as identical to a Treasury sanctions designation.
Commerce also established controls for specified cybersecurity items through its 2021 rule and subsequent implementation in 2022. These include defined intrusion-software-related and network-surveillance items. The rules have technical boundaries and exceptions; they do not make every legitimate penetration-testing tool an unlawful export.
License Exception ACE provides a route for certain eligible cybersecurity transactions without an individual license, but it has conditions and limitations. Product classification, destination, end user and intended use can all matter. A vendor’s claim that a tool is “for security research” does not eliminate the need to examine the applicable rules.
FEDERAL SPYWARE USE AND VISA RESTRICTIONS
Executive Order 14093, signed March 27, 2023, established restrictions on U.S. government operational use of commercial spyware determined to pose significant counterintelligence or security risks to the United States, or significant risks of improper use by foreign governments or persons, including human-rights abuses and suppression of civil liberties.
Its scope is federal-government operational use and the assessment process the order establishes. It is not a general federal ban on all private-sector surveillance software, and it is not a promise that all surveillance conducted by a government is lawful or proportionate.
In February 2024, the State Department announced a visa-restriction policy aimed at people believed responsible for or complicit in misuse of commercial spyware, with specified coverage extending to certain beneficiaries and immediate family members. A visa policy addresses entry to the United States. It does not itself prohibit every product associated with the affected person from being sold domestically.
These older measures explain the architecture of U.S. policy. They are not presented here as announcements made this week, and this report does not establish a complete, up-to-date inventory of all classified federal use determinations, export-license decisions or individual visa restrictions.
DOMESTIC PRIVACY DOES NOT DISAPPEAR WHEN A DEVICE IS AUTHORIZED
FCC authorization is not permission to monitor anyone, anywhere, for any purpose. Recording audio, collecting biometric identifiers, tracking workers or exposing private camera feeds can raise separate legal questions depending on the jurisdiction, setting, notice, consent and applicable law.
The Federal Trade Commission’s enforcement against SpyFone illustrates another tool: action against allegedly unfair or deceptive conduct by a stalkerware provider. It is a specific enforcement matter, not proof of a comprehensive federal ban on monitoring software.
A company buying a camera system should therefore ask two different questions. Can this product lawfully be imported, marketed and procured for our setting? And can we lawfully collect, retain, analyze and share the information it produces? Passing the first test does not answer the second.
WHAT AMERICAN BUYERS SHOULD DO NOW
For households, start with the actual device and its support status rather than a frightening generic headline. Record the model, manufacturer and FCC ID where applicable. Check for updates, change default credentials, disable unnecessary remote access and review who can view recordings. If equipment is already installed, do not infer a removal mandate from the June FCC notice; equally, do not interpret continued lawful operation as a recommendation to keep vulnerable hardware indefinitely.
For businesses and installers, ask suppliers for written, model-specific representations and component provenance. Examine original-equipment and rebranding relationships rather than only the retail name. Keep purchasing records and clarify responsibility for replacements if regulatory status or software support changes. A sticker or marketplace listing is weak evidence of compliance.
For federal contractors, involve the people responsible for procurement and legal compliance before signing representations. Inventory relevant organizational uses, not merely the hardware attached to the proposed contract. For exporters of cyber tools, obtain an appropriate classification and end-use assessment rather than treating the word “cybersecurity” as an exemption.
For journalists, advocates and other people at elevated risk of targeted phone compromise, camera-import restrictions are not the main defense against spyware. Device updates, account security and specialist incident-response advice remain relevant. Our related explainer examines the separate technical problem: https://thenewsrupt.com/article/zero-click-spyware-devices-compromised-without-a-click
WHAT WE DO NOT KNOW YET
The October FCC release does not name the two blocked consumer models or disclose a complete technical investigation. This article does not identify them, measure the security of their chips or claim independent evidence of data exfiltration. Future enforcement may clarify how suppliers document components and how the agency applies scope conditions in disputed cases.
We have also not established a comprehensive account of pending litigation, every waiver, individual export-license decision or post-2024 implementation of the commercial-spyware executive order and visa policy. The July FCC document contains both adopted rules and further proposals; proposed bill-of-materials and other transparency measures must not be mistaken for already-final universal obligations.
The strongest conclusion is practical rather than rhetorical. U.S. restrictions increasingly reach the supply chain behind a surveillance product, not just its brand. But market access, federal procurement, export controls and the legality of surveillance itself remain separate questions. Anyone making a purchasing or compliance decision needs the rule that actually applies—not simply the word “ban.”
EDITORIAL NOTE AND SOURCES
This is a document-based news explainer and analysis, not a hardware test, forensic investigation or legal opinion. AI assisted research and drafting. Regulatory descriptions are attributed to the relevant agencies; practical recommendations are editorial analysis. Sources were checked for this publication on October 26, 2026. Readers should consult current agency materials and qualified counsel for transaction-specific advice.
FCC, October 22, 2026 announcement of the two-device action: https://docs.fcc.gov/public/attachments/DOC-426130A1.pdf
FCC, Third Report and Order and Third Further Notice of Proposed Rulemaking, July 2026: https://docs.fcc.gov/public/attachments/FCC-26-50A1.pdf
FCC, June 26, 2026 public notice on previously authorized covered equipment: https://docs.fcc.gov/public/attachments/DA-26-635A1.pdf
FCC, current Covered List: https://www.fcc.gov/supplychain/coveredlist
The Record, October 23, 2026 reporting on the FCC action: https://therecord.media/fcc-bans-devices-huawei-surveillance-chips
Federal Acquisition Regulation, Section 4.2102 and Subpart 4.21: https://www.acquisition.gov/far/4.2102 and https://www.acquisition.gov/far/subpart-4.21
Commerce Department, November 2021 Entity List announcement: https://www.bis.gov/press-release/commerce-adds-nso-group-other-foreign-companies-entity-list-malicious-cyber-activities
Commerce Department, October 2021 cybersecurity export-control announcement: https://www.bis.gov/press-release/commerce-tightens-export-controls-items-used-surveillance-private-citizens-other-malicious-cyber
Executive Order 14093, published March 30, 2023: https://www.federalregister.gov/documents/2023/03/30/2023-06730/prohibition-on-use-by-the-united-states-government-of-commercial-spyware-that-poses-risks-to
State Department, February 2024 commercial-spyware visa policy: https://2021-2025.state.gov/announcement-of-a-visa-restriction-policy-to-promote-accountability-for-the-misuse-of-commercial-spyware/
FTC, SpyFone case materials: https://www.ftc.gov/legal-library/browse/cases-proceedings/192-3003-support-king-llc-spyfonecom-matter
Every claim above is sourced to a document, a named person, or a record we hold. Where we could not verify a claim, we say so. Read our standards and corrections policy →
