DHS has published an order that excludes DeepSeek products from federal civilian procurement and directs their removal from civilian agency IT
Exclusion and Removal Order #2026-01 is addressed to federal civilian agencies, not to vendors. Its text sets immediate exclusion and removal duties for agencies, with a written exception route, so contractors feel it through agency buying and agency system inventories.
Bottom line: The order is binding on the federal civilian executive branch agencies it covers. It directs them to exclude DeepSeek, its affiliated entities and their products from procurement, and to remove DeepSeek products, and third-party products built on DeepSeek implementations, from their IT systems.
Who this affects: Federal civilian agencies first. Contractors, subcontractors and software vendors whose products or services use DeepSeek implementations are affected through those agencies' procurement and system reviews.
Issue date: The order text gives an original release date of 24 July 2026. The Federal Register notice publishing it appeared on 20 October 2026.
What changed: DHS published a notice (91 FR 66346, FR Doc. 2026-21447, Docket DHS-2026-0628) carrying the signed order under the Federal Acquisition Supply Chain Security Act.
Analysis: In our reading, the order reaches vendors indirectly. A vendor with a federal civilian customer would want to know whether any DeepSeek model sits inside its product, because that is what the removal duty names.
- Instrument (English)
- Notice of Order Regarding Exclusion and Removal of DeepSeek Products From Federal Civilian Executive Branch Information Technology Systems and Procurements, carrying Exclusion and Removal Order #2026-01
- Authority
- U.S. Department of Homeland Security. The order is signed by the Secretary of Homeland Security; the notice is signed by the DHS General Counsel. CISA handles exception requests
- Jurisdiction
- United States (federal). Applies to federal civilian executive branch agencies, except their national security systems and secure compartmented information systems
- Status
- Published order. The Federal Register notice of 20 October 2026 publishes the signed order
- Bindingness
- Binding on covered civilian agencies. The order cites the FASCSA final rule as stating that executive agencies "shall comply with exclusion and removal orders". It is not a rule addressed to private vendors
- Issue date
- Original release date 24 July 2026 (order text); published in the Federal Register on 20 October 2026
- Effective date
- Exclusion "effective immediately after issuance of this Order"; removal "immediately after the issuance of the Order, or seek an Exception". The order does not state a separate calendar date for either
- What changed
- DHS excluded DeepSeek, its affiliated entities and their products from civilian agency procurement and directed removal of DeepSeek products, and third-party products and services developed using DeepSeek implementations, from civilian agency IT systems
- Who this affects
- Federal civilian agencies; contractors, subcontractors and vendors that sell to them or embed DeepSeek implementations in what they sell
- Primary source
- Federal Register, Vol. 91, No. 201, 20 October 2026, pp. 66346-66350, FR Doc. 2026-21447
- Workflow impact
- The order directs agencies to exclude and remove DeepSeek products, which in practice means checking procurement channels and system inventories. Vendors may receive agency questions about DeepSeek content; the order does not itself set a vendor certification step
- Operational next step
- Inventory any DeepSeek model, API or derivative in products sold to federal civilian customers, and prepare an accurate written answer before an agency asks
- Last verified
- 2026-10-25
Primary source: Federal Register, 20 October 2026, FR Doc. 2026-21447
Key takeaways
- The order directs agencies to "Exclude" DeepSeek, its affiliated entities and their products from civilian agency procurements, including approved product lists and e-commerce markets.
- It also directs removal of products provided by DeepSeek and of third-party products and services developed using DeepSeek implementations.
- Agencies may ask the DHS Issuing Official for an exception in writing within 60 days of issuance of the order.
- The Secretary of Homeland Security will review the order within one year and annually thereafter, according to the order.
What does the DHS order require federal civilian agencies to do?
Two things, under the heading "Required Actions". First, agencies are to exclude DeepSeek, DeepSeek-affiliated entities and their products from civilian agency procurements, "effective immediately after issuance of this Order", and the order says this includes agency-approved products lists, service provider equipment lists, e-commerce markets and similar functions that facilitate buying IT hardware, software and services. Second, agencies are to remove products provided by DeepSeek, affiliated entities, and third-party products and services developed using DeepSeek implementations from their IT systems, "immediately after the issuance of the Order, or seek an Exception".
The Federal Register notice states the legal basis: the Federal Acquisition Supply Chain Security Act of 2018 (41 U.S.C. 1321-1328) and its implementing regulations at 41 CFR 201-1, following review of a Federal Acquisition Security Council recommendation and affiliated evidence. The order text adds that the Secretary may issue exclusion and removal orders on the Council's recommendations to the extent they are not covered by the Department of Defense (named in the order as the Department of War) or the intelligence community.
Who does the order cover, and does it reach contractors directly?
The order says it applies to "Federal Civilian Executive Branch Agencies except for their national security systems and secure compartmented information systems". The order treats an individual or business as an affiliated entity if, directly or indirectly, either one controls or can control the other, or a third party controls or can control both, with a reference to the definition of affiliates in 48 CFR 2.101. The company named in the Federal Register notice is Hangzhou DeepSeek Artificial Intelligence Co., Ltd; the order's own text names Hangzhou DeepSeek Artificial Intelligence Basic Technology Research Co., Ltd.
The duties in the order fall on agencies. The text we read does not impose a certification or reporting step on contractors. Its reach to vendors comes through two phrases: procurement exclusion covers "third party implementations of DeepSeek used to provide products and services" to civilian agencies, and removal covers third-party products and services "developed using DeepSeek implementations". A product that wraps or embeds a DeepSeek model is therefore within the wording, though the order does not define "implementations" further.
What exceptions, timing and follow-up does the order set?
Executive agencies may request an exception from the DHS Issuing Official under 41 CFR 201-1.304(b), including a request that the order not apply to the agency, to certain actions, or that compliance be delayed. The order says requests must be "submitted in writing within 60 days of the issuance of this order". The order lists what a request must contain: the order identified, the exception sought, the covered product or service, "compelling justification", and any alternative mitigations. CISA reviews requests and gives written approval or disapproval.
In the interim, the order says agencies are "encouraged" to take steps such as monitoring traffic, enhanced logging and controls on data exfiltration, and detecting anomalous activity. It says CISA may provide technical assistance to agencies without internal capability to comply. The Secretary will review the order within one year and annually after that. Questions go to FASCSA.Orders@cisa.dhs.gov.
Why does the order say DeepSeek products are a risk?
The order's "Summary of Risks from Source" describes DeepSeek as a foreign, privately owned company in the People's Republic of China. These are the order's statements, not our findings. It says DeepSeek servers are located in the PRC and that the PRC legal system permits extensive government access to private company infrastructure. It says DeepSeek-hosted instances collect personally identifiable information and may track users, that use of DeepSeek applications by U.S. government employees or vendors may result in sensitive data reaching the PRC, and that the models themselves may contain malware or other vulnerabilities. It cites open-source research reporting critical vulnerabilities in the DeepSeek iOS app. Earlier regulators have acted on DeepSeek for data protection reasons, including Italy's Garante and South Korea's PIPC; those are separate instruments.
What should federal contractors and AI vendors check now?
The order addresses agencies, so the practical questions are about what your customers will ask. The steps below are our suggestions, not requirements of the order.
- List every DeepSeek model, API, hosted service or fine-tuned derivative inside products or services you sell to federal civilian agencies, including components supplied by your own subcontractors.
- Check whether any product reaches agencies through a schedule, approved product list or e-commerce market, since the order names those channels for exclusion.
- Decide who answers an agency inquiry about DeepSeek content, and keep the answer in writing and consistent across contracts.
- Watch your contract clauses and agency notices for flow-down language. Our piece on the GSA AI clause and OMB flow-downs covers a separate contractor-facing instrument, and the D.C. Circuit supply-chain exclusion ruling concerns a different exclusion.
What are the key dates and deadlines in the order?
| Item | Detail |
|---|---|
| Original release date (order text) | 24 July 2026 |
| Federal Register notice publishing the order | 20 October 2026 (91 FR 66346, FR Doc. 2026-21447) |
| Exclusion from procurement | "effective immediately after issuance of this Order"; no separate calendar date stated |
| Removal from IT systems | "immediately after the issuance of the Order, or seek an Exception"; no separate calendar date stated |
| Exception requests | In writing "within 60 days of the issuance of this order"; the order does not say whether "issuance" means the July release or the October publication, so the end date is unresolved |
| Order review | Within one year and annually thereafter, per the order |
FAQ
Is the DHS DeepSeek order binding?
Yes for the civilian executive branch agencies it covers. The order cites the FASCSA final rule as stating that executive agencies shall comply with exclusion and removal orders. It is addressed to agencies, not private vendors.
Does the order apply to national security systems?
No. The order says it applies to federal civilian executive branch agencies except for their national security systems and secure compartmented information systems.
Does the order cover products built on DeepSeek models?
Its wording does. Removal covers third-party products and services developed using DeepSeek implementations, and the procurement exclusion includes third party implementations of DeepSeek used to provide products and services to civilian agencies.
Can an agency get an exception?
Yes. An agency may ask the DHS Issuing Official for an exception under 41 CFR 201-1.304(b), in writing within 60 days of the issuance of the order, and CISA reviews requests.
When did the order take effect?
The order says exclusion is effective immediately after issuance and removal is due immediately after issuance unless an exception is sought. It gives an original release date of 24 July 2026, and the notice was published on 20 October 2026.
What we did not verify
What we opened: all five pages of the Federal Register notice (91 FR 66346-66350, FR Doc. 2026-21447) as published on govinfo.gov, including the signed order in the appendix, which is printed as page images, on 24 October 2026.
What we did not open: the docket on regulations.gov (DHS-2026-0628), the Federal Acquisition Security Council recommendation, the evidence behind the order's risk statements, the FASCSA statute and 41 CFR 201-1 themselves, and any agency or CISA implementation guidance. We could not confirm whether the 60-day exception window runs from the 24 July 2026 release date or from Federal Register publication, because the order says only "issuance".
What we refuse to claim: that the order binds private contractors directly, that it sets a vendor certification or reporting duty, that any agency has completed removal, or that the order's risk statements about DeepSeek have been independently confirmed.
DHS Order #2026-01 directs civilian agencies to exclude DeepSeek and affiliates from procurement and to remove DeepSeek-based products from their IT. If you sell to those agencies, find out now whether any DeepSeek implementation sits in your product, and record the answer.
Related briefings
Source File
Primary: https://www.govinfo.gov/content/pkg/FR-2026-10-20/pdf/2026-21447.pdf
Secondary: None relied on for the facts above.
Last checked: 2026-10-25 (UTC)
Status: Published order, binding on covered civilian agencies.
Editorial note: Informational analysis for working professionals, not legal advice. Confirm how any rule applies to your situation with qualified counsel.
Informational analysis for working professionals, not legal advice. Confirm how any rule applies to your situation with qualified counsel.
Sponsored Training
Practical AI training for regulated professionals, built around verification, documentation and a defensible process. See the courses.