DHS DeepSeek Ban: What the Federal Order Covers

The Department of Homeland Security has ordered every civilian federal agency to stop buying DeepSeek products and to rip out the ones already running. The notice appeared in the Federal Register on October 20, but the order itself isn’t new. Here are the questions I’d ask first.

Who does this apply to?

Civilian executive branch agencies, so think EPA or the FCC rather than the Pentagon. Cyberpress, which read the order closely, says national security systems are carved out. Private companies and ordinary users aren’t covered, and nothing here stops you downloading the open model yourself.

The legal hook is the Federal Acquisition Supply Chain Security Act of 2018. It lets DHS act on a recommendation from the Federal Acquisition Security Council, and that’s what the notice says happened.

What exactly has to go?

The notice lists two things. DeepSeek’s parent company, Hangzhou DeepSeek Artificial Intelligence, and its affiliates are excluded from federal buying. And agencies must remove “all DeepSeek and DeepSeek-affiliate products, and third-party products and services developed using DeepSeek implementations.”

That last clause is the one to read twice. A vendor that built a feature on top of a DeepSeek model, and sold it to an agency under its own brand, could fall under the order. Cyberpress reads it the same way: broader than a ban on the chatbot app. How an agency finds out what’s inside the software it bought is a different problem, and the notice doesn’t solve it.

Why did DHS do it?

The reasons come from a letter by Secretary Markwayne Mullin that’s attached to the notice. CyberScoop’s summary: DeepSeek’s models store data on servers in China, where national security laws give the government wide room to demand it. DeepSeek’s own hosted service collects personal information and tracks users’ “digital fingerprints.” And the normal prompt-and-response process “may result in the transfer of sensitive data.”

Mullin also wrote that the data, alone or combined with public information, “could produce actionable intelligence on U.S. persons and/or government programs.” Engadget adds that DHS said the models could contain malware or other security vulnerabilities. I haven’t seen any evidence for that claim in the notice. It reads as a risk statement, not a finding.

Notice that most of this concerns DeepSeek’s hosted service. An agency running the open weights on its own hardware wouldn’t send anything to China. The order’s reach into “implementations” suggests DHS wants those gone too, but the notice text I could read doesn’t spell out the self-hosted case.

When was it signed?

Depends who you read. CyberScoop and Particle say the Mullin letter is dated June 26, so the ban has been in effect for months. Cyberpress says the order was “originally released July 24” and calls it Exclusion and Removal Order 2026-01. I couldn’t open the full signed appendix, so I can’t tell you which is right. Either way, agencies have been under it far longer than the notice date suggests.

Can an agency get out of it?

Yes, narrowly. Exception requests need a “compelling justification,” such as a mission-critical function that can’t be done another way. The timing is reported two ways. CyberScoop says requests must come 60 days in advance. Cyberpress says within 60 days of issuance, and that the clock started at signing, not at Federal Register publication. If it’s the second, some of that window may already be closed.

Until the software is gone, agencies are “encouraged” to watch traffic in and out, add logging and flag odd activity.

What I think

This is less about DeepSeek than the precedent. Until now agencies set their own rules. The Commerce Department confirmed to FedScoop last year that it blocked such models by its own choice. A single government-wide order under a supply-chain law is a different tool, and nothing about it is specific to one company. CyberScoop points out that Moonshot’s Kimi and Alibaba’s Qwen worry officials too, and the same law could reach them.

The practical pain lands on contractors. If you sell software to a civilian agency and one of your features calls a DeepSeek model, check your stack now. We covered DeepSeek’s October 17 model update and how China wants to license its model exports, and the pull in both directions is the same: cheap Chinese models keep getting better, and Washington keeps adding rules about who can touch them.

I’d also watch whether DHS publishes any list of affected products. Without one, “developed using DeepSeek implementations” is a phrase every vendor will read differently.

Sources

I read the notice’s summary text and the full CyberScoop article. The signed order appendix wasn’t readable to me, so details from it (the July 24 date, the national security carve-out) come from Cyberpress and are unconfirmed.