DHS Orders DeepSeek Purged From All Civilian Federal IT Systems
DHS Exclusion and Removal Order #2026-01, signed July 24 and filed publicly October 19, orders all U.S. civilian agencies to immediately remove DeepSeek products and any third-party software built on DeepSeek implementations from their IT systems.
The Department of Homeland Security banned DeepSeek and any software built on its models from civilian federal IT, citing PRC data transfer risk and possible malware embedded in the models.
Key takeaways
- DHS Exclusion and Removal Order #2026-01, signed July 24, 2026, orders immediate removal of DeepSeek products and any third-party software built on DeepSeek implementations from all U.S. civilian executive branch IT systems.
- The order invokes the Federal Acquisition Supply Chain Security Act of 2018 and cites three threat vectors: sensitive data transfer to PRC servers, intelligence collection on U.S. persons and federal agencies, and potential malware inside the models themselves.
- The order carries an exception process requiring agencies to submit requests 60 days in advance with a compelling justification; that window had elapsed before the public Federal Register filing appeared on October 19, meaning agencies seeking exceptions were already past the submission point before the notice was publicly posted.
The Department of Homeland Security filed a public notice on October 19, 2026 confirming it had issued Exclusion and Removal Order #2026-01 on July 24, directing all U.S. civilian executive branch agencies to immediately halt procurement of DeepSeek products and remove any existing DeepSeek software, including third-party products built on DeepSeek implementations, from their IT systems. The order names Hangzhou DeepSeek Artificial Intelligence Co., Ltd. and states that DeepSeek's models "present multiple threat vectors," including the risk that use "may result in the transfer of sensitive data to the PRC if used by U.S. government employees or vendors" and could "produce actionable intelligence on US persons and/or government agencies."
The Federal Register public inspection filing (docket DHS-2026-0628) is the primary document. The order is scheduled for formal Federal Register publication at federalregister.gov/d/2026-21447. Legal authority comes from the Federal Acquisition Supply Chain Security Act of 2018, via a Federal Acquisition Security Council review. The order is explicitly limited to civilian executive branch agencies and does not cover the Department of Defense. The order does not invoke export controls into the private sector.
What the Order Actually Covers
The headline ban on DeepSeek is the obvious part. The more significant element is scope: the order targets not just DeepSeek-branded products but any third-party product or service built on DeepSeek implementations. A vendor who white-labeled or embedded DeepSeek under a different name is also out. Federal agencies must now audit the model lineage inside their software stack, not just the front-end vendor name.
That posture is structurally identical to what the U.S. applied to Huawei telecom hardware, where federal restrictions eventually created procurement pressure across the private sector as well. Prior enforcement actions on China-linked AI server export controls and restricted data center financing show this enforcement posture is not isolated.
The order also carries an exception process: agencies seeking to retain DeepSeek products must submit a request 60 days in advance with a compelling justification, such as an inability to fulfill a mission-critical function. The public Federal Register filing appeared October 19, meaning agencies were already past that submission window before the notice was publicly posted.
The Governance Model Is the Tell
The substance of the security concerns, PRC server exposure, potential intelligence collection, possible malware in model weights, is plausible and worth taking seriously. But the process is worth equal attention. Rules with retroactive teeth, published after the deadline, are the governance model.
The order's breadth also sets a template. If federal procurement now requires auditing model lineage inside third-party software products, the logical extension is a regime where any AI model touching federal systems must be certified against a growing exclusion list. The threat framing behind the order is real. But the regulatory infrastructure being built to address it is one that any future administration can apply to any model, from any jurisdiction, for any reason.
For builders and operators in the freedom-tech space, the downstream question is direct: what happens when Washington decides that an open-weight model you're running locally once used a training dataset, a distillation process, or an RLHF pipeline that touched a sanctioned entity? The logic of model-lineage auditing doesn't stop at Chinese AI companies. AI infrastructure that runs locally with no external dependencies is structurally less exposed to that risk than cloud-hosted or API-dependent alternatives, and that calculus only sharpens as orders like this one multiply.
The falsifiable version of that thesis: if the U.S. government codifies a permissionless, vendor-neutral AI infrastructure standard for federal use and issues a companion order making self-hosted open-weight models a preferred procurement path rather than a compliance exception, this is supply-chain hygiene. Until then, it's a gatekeeping template being assembled in public.
What to Watch
The FASCSA mechanism has not previously been used against a named AI software vendor at this scale. Whether DHS issues follow-on orders targeting other Chinese AI firms, and whether federal procurement pressure migrates into private-sector contracting requirements as it did with Huawei hardware, are the two variables that determine whether this order is a one-off or the opening move of a broader AI supply-chain control regime.
Sources
Frequently Asked Questions
Does the DHS DeepSeek ban apply to private companies?
Not under this specific order. Exclusion and Removal Order #2026-01 applies only to U.S. civilian executive branch agencies. Private companies are not directly covered. However, the Huawei hardware precedent shows that federal supply-chain restrictions routinely create downstream pressure on private-sector procurement, particularly for vendors that sell into government or work as federal contractors.
What is the Federal Acquisition Supply Chain Security Act and why does it matter for AI?
The FASCSA of 2018 was designed to give the federal government authority to exclude vendors from procurement on supply-chain security grounds. It was originally built for hardware. This order represents a significant application of that authority to AI software, specifically to model implementations, not just hardware or network equipment. The mechanism can now be used against any AI vendor the Federal Acquisition Security Council flags.
Can federal agencies still use self-hosted open-weight AI models?
This order targets DeepSeek specifically and any third-party products built on DeepSeek implementations. Self-hosted open-weight models from other vendors are not covered by this order. The concern flagged in the dossier is longer-term: if model-lineage auditing becomes standard practice, the criteria for what gets flagged could expand. Models that run locally with no external dependencies are structurally less exposed to that risk than cloud-hosted or API-dependent alternatives.
