The Quiet Clause in the Federal DeepSeek Ban

On October 19, 2026, the Federal Register published a Department of Homeland Security order, FASCSA Exclusion and Removal Order #2026-01. DHS Secretary Markwayne Mullin signed it on July 24, 2026. The order does two things. It excludes Hangzhou DeepSeek Artificial Intelligence Basic Technology Research Co., Ltd. and its affiliates from federal civilian procurement. It also requires agencies to remove DeepSeek and affiliate products from their information systems, including third-party products and services developed using DeepSeek implementations.

The second obligation does more work. If a U.S. company sells an AI tool under its own brand to a federal agency, that tool is in scope when it calls DeepSeek models or implementations underneath. A supplier cannot clear compliance by saying “my brand is not DeepSeek.” It has to trace the product stack: model weights, API calls, fine-tuned versions, deployment infrastructure. Model provenance becomes a variable that procurement reviewers can ask about and use to exclude a product.

The legal basis is the Federal Acquisition Supply Chain Security Act of 2018, FASCSA, 41 U.S.C. 1321-1328. DHS issued the order after reviewing recommendations and evidence from the Federal Acquisition Security Council. FASCSA’s exclusion and removal tools were built for hardware and software supply chains, where components can be counted, disassembled, and replaced. Applied to AI models, the review changes object. It no longer looks at one server or one software package. It looks at model ownership, training-data provenance, and the jurisdiction that governs deployment infrastructure. The order does not ask agencies to test model quality or model behavior. It asks where the model comes from.

The 60-day window and the three-month delay

The order was signed July 24 and published October 19. The text gives affected agencies 60 days to apply for exceptions or delays. CISA reviews the applications. Counted from the signing date, the window had closed by the time the order became public. Between July and October, federal contractors and civilian agencies faced a compliance clock that had started but had not been announced. The DHS notice does not explain the delay. It does not say whether any agency completed removal or applied for an exemption in that period. The public text gives the rationale: DeepSeek servers sit in China; Chinese law gives the government broad access to corporate infrastructure; use may send sensitive data to China; the model may produce inaccurate or biased content. The notice does not lay out the evidence. CISA oversees implementation.

What the federal bill actually shows

DeepSeek’s revenue exposure in U.S. federal civilian procurement is small. It is a privately held startup with no meaningful contract base on the federal side. The broader paid enterprise market is thin. Ramp, a corporate spend management platform, tracks payment data from about 50,000 U.S. businesses. For most of 2026, DeepSeek’s paid adoption rate was around 0.1%. In June 2026, when its low-priced model drew attention, adoption briefly reached 0.3% and then fell back. Over the same period, Anthropic and OpenAI each held more than 30% of U.S. enterprise AI spending. Much of DeepSeek’s use happens through open-weight downloads, individual trials, and unpaid API calls. FASCSA procurement controls do not reach those channels. The order will not change the high-usage, low-payment pattern.

The direct financial weight is limited. The compliance signal travels further. DHS’s exclusion decision gives risk-averse buyers an official risk finding. Contractors with federal contracts, regulated industries, and state and local governments now have to ask whether a model’s provenance touches a federal exclusion list. Before the DHS order became public, New York, Tennessee, and Virginia had imposed similar state-level bans. The Commerce Department and the Navy had restricted DeepSeek on government devices. The federal order consolidated those scattered measures into one baseline for the federal civilian executive branch. For suppliers, compliance costs do not stop at the federal contract. If the same product serves federal contractors and commercial customers, model-provenance documentation gets reused, and the review chain gets longer.

Scope and exemptions

The order covers federal civilian executive branch agencies. The Department of Defense, the intelligence community, and national security systems follow other rules and are not directly covered. U.S. private companies and ordinary consumers are not directly constrained. The text includes an exemption channel. Agencies may apply in writing for non-application, partial application, or delayed compliance, and must propose alternative mitigation measures. CISA reviews the applications. The text does not list criteria for granting exemptions. It does not disclose how many applications have been filed.

A template other exclusions can reuse

The review framework behind the order is not limited to DeepSeek. OMB Memorandum M-26-04, effective in March 2026, requires federal agencies to run ongoing supply-chain assessments and model-behavior monitoring when they buy large language models. NSA guidance issued the same year treats AI systems as full supply chains and asks for data provenance and model lineage. The FASCSA order names DeepSeek. The questions it formalizes, who owns the model, where training data comes from, which jurisdiction governs deployment infrastructure, can be applied to other models deemed linked to foreign adversaries. The order leaves behind a reusable exclusion template. It invokes FASCSA, lists entities and affiliates, adds a third-party use clause, sets removal obligations, assigns CISA oversight, and keeps an exemption channel. A later action can swap in new entity names and keep the structure.

China’s Ministry of Foreign Affairs responded on the day the order became public. It said China “has consistently opposed overstretching the concept of national security and politicizing science, technology, and economic and trade issues.” It said China “will resolutely safeguard the lawful rights and interests of Chinese companies.” The response continued the position China had stated in the months before the FASCSA order, when the Commerce Department postponed adding DeepSeek to the Entity List and the U.S. alleged that Chinese AI companies engaged in “industrial-scale distillation.”

When the order became public, the 60-day exception window counted from the signing date had closed. CISA had not disclosed any exemption review records. No public text yet covers removal progress in federal civilian systems, provenance criteria for third-party products, or how contractors can prove they did not use DeepSeek implementations.