Why the U.S. Router Ban Makes Sense from a Cybersecurity Perspective

The U.S. government has taken a stronger position against foreign-made consumer routers, and from a cybersecurity perspective, I understand why.

According to Reuters, the FCC announced in March 2026 that it was banning the import of new foreign-made consumer routers, citing national security and cybersecurity concerns. The FCC’s public notice added routers produced in foreign countries to the FCC Covered List unless a specific router or class of routers receives conditional approval from the Department of War or the Department of Homeland Security. The FCC notice says the concern is that compromised routers can enable espionage, network disruption, intellectual property theft, and attacks against critical infrastructure. :contentReference[oaicite:0]{index=0}

That may sound extreme at first, but routers are not normal consumer gadgets. They sit at the edge of homes, businesses, schools, clinics, farms, local governments, and critical infrastructure. They see traffic. They route traffic. They often provide Wi-Fi, DNS, firewalling, VPN access, port forwarding, and remote administration.

When those devices are poorly secured, unsupported, or controlled through opaque supply chains, they become more than a household inconvenience. They become infrastructure.

This is not just about one brand

A lot of the public conversation focuses on China, and there are real reasons for that. Reuters reported that China is estimated to control at least 60% of the U.S. home router market. The FCC also cited foreign-made routers being implicated in major cyber campaigns, including Volt Typhoon and Salt Typhoon. :contentReference[oaicite:1]{index=1}

But the broader issue is not simply “foreign-made equals bad.”

The real issue is this:

  • Who designs the firmware?
  • Who controls the software update process?
  • Where is the hardware manufactured?
  • Who can influence the vendor?
  • How long does the vendor support the device?
  • Does the device ship securely by default?
  • Can the device be patched quickly when a critical vulnerability is found?
  • Is there a realistic way for customers to know when the device is no longer safe?

For most consumers and small businesses, the answer is usually: “I have no idea.”

That is the problem.

Routers are perfect targets

Attackers love routers for a few reasons.

First, they are usually always on. Second, they often sit directly on the internet. Third, many people never update them. Fourth, older devices may continue running for years after the vendor stops supporting them. Fifth, compromised routers are useful because they let attackers hide inside normal residential and business internet traffic.

That last point matters. If an attacker uses a compromised router in a normal neighborhood or small business, the traffic may look less suspicious than traffic coming from a known malicious server overseas. This makes compromised routers useful for proxy networks, botnets, reconnaissance, credential attacks, spam, denial-of-service attacks, and espionage.

This is where I personally agree with the U.S. stance. Over time, we could unintentionally build a giant sleeper network of vulnerable devices. They may look harmless while sitting in homes and small offices, but if enough of them are compromised or designed with weak controls, they could become a “waiting on a signal” network that can be used for large-scale internet attacks.

That is not science fiction. We have already seen botnets made out of cameras, routers, DVRs, and other IoT devices.

Security issues seen across common IoT and network devices

The concern is not theoretical. There is a long history of severe vulnerabilities in routers, cameras, DVRs, NVRs, NAS devices, and other internet-connected equipment.

Here are some of the major vendors and device categories I would watch closely.

VendorCountry / RegionDevice typesExample security issueWhy it matters
HikvisionChinaIP cameras, NVRs, DVRsCVE-2021-36260, a command injection vulnerability in Hikvision productsCameras and recorders are often placed on trusted networks and may be reachable remotely.
DahuaChinaIP cameras, DVRs, NVRs, intercomsCVE-2021-33044 and CVE-2021-33045, authentication bypass flaws added to CISA’s Known Exploited Vulnerabilities catalogAuthentication bypass on cameras can allow attackers to access devices without valid credentials.
TP-LinkChina / global operationsConsumer routers, Wi-Fi devices, mesh systemsCVE-2023-1389 in the TP-Link Archer AX21 allowed unauthenticated command injection as root. Fortinet reported botnets exploiting this vulnerability for wide-scale spread.Cheap, widely deployed routers create a large attack surface.
D-LinkTaiwanRouters, cameras, NAS devicesMultiple D-Link router flaws have been added to CISA’s Known Exploited Vulnerabilities catalog, including command injection issues.Older home and small-business routers often remain online after support ends.
QNAPTaiwanNAS devicesCVE-2022-27593 affected QNAP Photo Station on internet-exposed NAS devices and was tied to DeadBolt ransomware activity.NAS devices often contain backups and sensitive business data.
ZyxelTaiwanRouters, firewalls, gateways, access pointsZyxel has had router and firewall vulnerabilities appear in exploitation tracking over time, including CISA KEV-listed issues.Edge firewalls and gateways are high-value because compromise gives attackers a network foothold.
ASUSTaiwanRouters and network gearASUS routers and update mechanisms have had serious security issues over time.Consumer routers often blend home and business use, especially in very small businesses.
Unknown white-label brandsVariousCameras, smart plugs, bulbs, doorbells, baby monitors, DVRsWeak default passwords, poor update support, hardcoded credentials, exposed services, and unclear firmware originsCheap IoT devices can be difficult to assess, patch, or trust.

This does not mean every device from these vendors is compromised. It also does not mean U.S.-based vendors are automatically secure. Country of origin is not a replacement for security testing.

But country of origin, supply chain control, vendor transparency, update practices, and legal jurisdiction all matter when the device sits at the edge of the network.

The real risk is concentration

One vulnerable router is a problem for one household or one business.

Millions of vulnerable routers are a national security problem.

That is the part that often gets missed. The concern is not just that a single small business might get hacked. The concern is that entire product lines can become mass-exploitation targets. If a vendor has a huge share of the market and the devices are difficult to patch, attackers can scale very quickly.

This is how a consumer device becomes a national infrastructure issue.

Routers connect everything behind them. If they are compromised, they can potentially be used to:

  • spy on traffic patterns
  • redirect users to malicious sites
  • intercept DNS requests
  • attack other targets
  • participate in botnets
  • hide attacker traffic
  • create persistence inside homes and businesses
  • disrupt connectivity during a crisis

When these devices are foreign-produced and the supply chain is not trusted, the risk is not only vulnerability management. It becomes a strategic risk.

What small businesses should take from this

Most small businesses are not going to do firmware reverse engineering. They are not going to review supply chains. They are not going to analyze bootloaders or validate the integrity of embedded operating systems.

That is fine. They do not need to.

But they should have basic purchasing and lifecycle rules for network-connected devices.

For example:

  1. Do not buy the cheapest router, camera, DVR, or smart device just because it works.
  2. Avoid unsupported or end-of-life devices.
  3. Do not expose router, camera, NAS, or DVR management interfaces directly to the internet.
  4. Replace devices that no longer receive firmware updates.
  5. Put IoT devices on a separate network whenever possible.
  6. Require unique passwords and disable default accounts.
  7. Turn off UPnP unless there is a specific business need.
  8. Keep a simple inventory of routers, cameras, access points, NAS devices, and firewalls.
  9. Check whether critical vulnerabilities exist before buying or deploying a device.
  10. Prefer vendors with clear security advisories, update history, and vulnerability disclosure processes.

The goal is not perfection. The goal is to stop casually adding unknown, unmanaged, internet-connected hardware to business networks.

This is bigger than home Wi-Fi

For a home user, a bad router may mean poor privacy, malware risk, or participation in a botnet.

For a business, it can be worse. A compromised router or IoT device can become the first step toward ransomware, data theft, credential harvesting, or business email compromise. It can also create liability if the business unknowingly becomes part of attacks against others.

This matters even more for organizations that handle regulated data, provide critical services, or support local infrastructure.

A router is not just a box with blinking lights. It is a trust boundary.

My view

I support the U.S. taking a harder stance on foreign-made routers where there is a credible national security concern.

Not because every foreign-made device is malicious. Not because domestic devices are magically secure. But because routers are too important to treat like disposable electronics.

If we keep filling homes, businesses, and critical infrastructure with cheap devices that have poor patching, unclear ownership, weak firmware security, and questionable supply chains, we are building risk at scale.

That risk may sit quietly for years.

Then, during a conflict, crisis, or major cyber campaign, those devices can become useful to an adversary. That is the “sleeper network” concern. A large population of vulnerable routers and IoT devices does not need to be activated all at once to cause damage. It only needs to be available, distributed, and hard to clean up.

That should concern everyone.

Practical policy language for businesses

If you are a small business, school, city, clinic, manufacturer, or nonprofit, you do not need a complicated policy to start improving this area.

Here is a simple version:

Network-connected devices, including routers, firewalls, cameras, DVRs, NVRs, NAS devices, wireless access points, and IoT equipment, must be purchased from vendors with a documented security update process, supported firmware, unique credentials, and a clear vulnerability disclosure process. Unsupported devices, devices with known exploited vulnerabilities, and devices with internet-exposed management interfaces must be replaced, isolated, or remediated.

That one paragraph is better than having no standard at all.

Final Thought

Cybersecurity is not just about laptops, antivirus, and passwords. It is also about the devices we forget are even there.

Routers, cameras, DVRs, smart devices, and other IoT equipment are often treated as low-risk purchases. They are not. They are network infrastructure.

The U.S. router restriction is a reminder that supply chain security is no longer just an enterprise or government issue. It affects homes, small businesses, and the basic trust we place in the devices that connect us to the internet.

I understand the concerns raised by groups like the Electronic Frontier Foundation. A broad restriction on foreign-made routers will likely create short-term challenges, especially since the United States does not currently manufacture these devices at the scale consumers and businesses rely on.

But from a national security perspective, I think the concern is valid. If the choice is between short-term market disruption and continuing to build a massive population of vulnerable, foreign-controlled, or poorly supported edge devices, I think the long-term security benefit is worth taking seriously.

This does not mean every foreign-made device is malicious. It means routers are too important to treat like disposable consumer electronics. They are part of the trust layer of the internet, and we should be much more careful about who builds them, who updates them, and who can influence them.

PPS

Anyone remember the Bloomberg story about Supermicro? That one still keeps me up at night.