Washington bans DeepSeek in federal civilian agencies

The US Department of Homeland Security has ordered federal civilian agencies to stop using DeepSeek and its derivatives. The broad wording raises practical difficulties for vendors and IT teams.

The US Department of Homeland Security on Monday ordered federal civilian agencies to stop using DeepSeek and to remove existing deployments. The measure also targets third-party products developed with DeepSeek implementations, a rather vague phrase that seriously complicates compliance. Washington is targeting a Chinese AI service considered sensitive for data security and privacy.

Un bannissement large, pas seulement l’application DeepSeek

The text requires excluding “all DeepSeek and DeepSeek-affiliate products, and third-party products and services developed using DeepSeek implementations.” This wording goes beyond simply blocking the DeepSeek application or API. It may also concern tools routed through AI gateways like OpenRouter or Vercel AI Gateway, which automatically select a model provider. In other words, a public service might end up using DeepSeek without explicitly deciding to do so.

This ambiguity is not just a legal detail. Katie Moussouris, founder and CEO of Luta Security, believes that banning the application and API is feasible, but not the services “developed using DeepSeek implementations.” She points out that “An AI software bill of materials doesn't record which tools developers used, so it would be no real help. Every vendor would have to attest that nothing it relies on ever touched DeepSeek. There's no practical way to verify that.”

Des inquiétudes déjà anciennes à Washington

US authorities have been considering a DeepSeek ban since the release of DeepSeek-R1 in early 2025. On February 6, 2025, Representatives Darin LaHood and Josh Gottheimer introduced the No DeepSeek on Government Devices Act, citing national security risks. The bill did not advance in Congress, but several agencies took preemptive action.

In the same move, the Defense Information Systems Agency began blocking DeepSeek on Pentagon networks in January 2025. The Navy, NASA, and the House of Representatives followed, as did several US states. DHS is thus generalizing a policy already applied by part of the federal apparatus, but on a larger scale and with a more difficult scope to define.

Le vrai sujet : qui contrôle les données et où elles passent

The reasons cited by US authorities mainly concern data flows to DeepSeek's servers in China, data collection, and risks related to the mobile app. A December 2025 report on the Android and iOS versions cited cleartext information leaks, connections to servers operated by Chinese companies, and the absence of SSL pinning, a technique that locks communication to an expected server. These weaknesses mainly relate to mobile security, not the AI's operation itself.

On this point, Moussouris believes the order goes too far. She recalls that the cited risks mainly concern “data flowing to DeepSeek's servers in China, its data collection, and its app.” According to her, US-hosted versions would already limit most of the problem. She adds that NIST's remarks on DeepSeek's vulnerability to prompt injection and ease of jailbreak also apply, to varying degrees, to other models. Prompt injection involves pushing a model to follow malicious instructions hidden in the data it processes.

Une décision utile pour la sécurité, mais coûteuse pour les usages

Substantively, the US administration seeks to cut off access deemed too risky. Formally, it requires agencies to verify sometimes opaque software supply chains, which can become a headache for public IT directors and their providers. And while lawyers debate the exact meaning of “developed using,” technical teams will have to sort through dependencies that no inventory necessarily documents. The devil, as often in cybersecurity, is in the API.

Key points

  • DHS: order published Monday for federal civilian agencies.
  • DeepSeek-R1 revived the issue in early 2025.
  • DISA began blocking in January 2025.
  • LaHood and Gottheimer introduced a bill on February 6, 2025.
  • Moussouris considers the phrase “developed using” impractical.

By the numbers

  • February 6, 2025 — introduction of the No DeepSeek on Government Devices Act in the US Congress.
  • January 2025 — start of DeepSeek blocking by DISA on Pentagon networks.
  • December 2025 — report on the DeepSeek mobile app for Android and iOS.
  • 2 representatives — Darin LaHood and Josh Gottheimer behind the bill.

To read