On October 20, the Department of Homeland Security published notice of an order whose signed appendix lists July 24, 2026, as its original release date. The order excludes information technology products and services developed by DeepSeek and its affiliates from federal civilian agency procurement and directs removal of covered products from civilian agency IT. Its reach extends further: the removal language also covers third-party products and services developed using DeepSeek implementations, and procurement footnotes include third-party implementations used to provide products and services to civilian agencies. The appendix makes exclusion effective immediately after issuance and requires removal immediately after issuance or an exception request.
That last category turns model provenance into a procurement fact. A product may carry another company's name while relying on a DeepSeek implementation somewhere in its development chain. The order gives federal civilian agencies a reason to ask vendors what models sit underneath a tool, where they entered the build process, and what records support the answer.
DHS issued the order under the Federal Acquisition Supply Chain Security Act of 2018 and its implementing regulations, after reviewing a Federal Acquisition Security Council recommendation and related evidence. The published notice establishes the two-part exclusion and removal scope. It does not supply a technical test for deciding when a third-party product was "developed using" a covered implementation.
What changed
The order covers two different moments in the technology lifecycle. The procurement exclusion applies when a federal civilian agency is considering a future purchase. The removal direction applies to covered products and services already present in civilian agency information technology. Because the third-party clause widens the review beyond the name on a contract or application, an agency may need to examine whether a vendor's product depends on a DeepSeek implementation even when DeepSeek is not the seller. A direct vendor list will not answer that question by itself.
The notice does not say that every tool trained with, tested against, or connected to DeepSeek falls within the order. It also does not decide whether any particular third-party product is covered. Those determinations require evidence about the product and an interpretation of the order's language.
Why it matters
AI products can hide their lineage behind an interface. A contractor may integrate a model through an API, fine-tune an open model, distill one model into another, or use several models during development. The Federal Register notice does not say which of those relationships satisfies "developed using DeepSeek implementations." It does make the underlying relationship relevant to federal review, which creates a practical documentation problem for agencies and vendors. An agency needs enough information to identify covered technology in its current systems and purchasing pipeline. A vendor needs records that can support a precise answer about the models, components, and development stages behind its product. Ordinary software inventories may identify packages and versions while saying little about model ancestry or the role a model played before release.
A useful provenance record would connect the finished product to the model components and services used to create it. It would preserve version information, the stage at which each model entered, whether the relationship remains in the deployed product, and who approved the final attestation. The order does not require this specific format. The need follows from the difficulty of applying a dependency-based rule without reliable dependency evidence.
Verification bottleneck
The phrase "developed using" carries the operational burden. A current product can be inspected for embedded components and network calls, but development history may sit in build logs, vendor records, model registries, or contractual representations that an agency cannot see directly. A clean runtime scan would not necessarily resolve how the product was built.
That visibility problem has a mirror-image risk. A broad keyword match could treat incidental testing or compatibility work as proof that a product falls inside the order. The public notice does not support that conclusion. A defensible review needs a documented chain from the order's scope to the specific product relationship, with uncertainty and unresolved evidence kept visible.
Scope supplies another boundary. The order applies to Federal Civilian Executive Branch agencies except for their national security systems and secure compartmented information systems. It does not create a general prohibition on consumer or private-sector use. Organizations outside that scope may still treat the order as a supply-chain signal, but that would be their own risk decision rather than a direct requirement created by this notice.
Watch next
Watch for implementation material that defines acceptable evidence for third-party dependencies. Agency inventory instructions, vendor attestation language, contracting clauses, and decisions about specific products could show how DHS and civilian agencies interpret "developed using." The signed appendix already provides an exception process requiring written requests within 60 days of issuance, permits CISA technical assistance for agencies without sufficient internal capabilities, and requires review within one year and annually thereafter. Exception decisions, technical assistance, and those reviews may clarify how agencies handle products that cannot be classified from existing records; the October 20 publication is not stated to restart the exception-request window.
The immediate signal is narrower and more useful than a sweeping story about an AI ban. Federal procurement review is moving below the visible application and into the product's development lineage. The order establishes the scope; the next accountability test is whether agencies and vendors can produce enough evidence to apply it consistently.
This card describes the scope stated in DHS's public notice. It does not determine whether a particular product is covered and does not provide legal, procurement, or cybersecurity advice.
Source
- Department of Homeland Security, "Notice of Order Regarding Exclusion and Removal of DeepSeek Products From Federal Civilian Executive Branch Information Technology Systems and Procurements," FR Doc. 2026-21447, 91 FR 66346-66350, published October 20, 2026: https://www.federalregister.gov/documents/2026/10/20/2026-21447/notice-of-order-regarding-exclusion-and-removal-of-deepseek-products-from-federal-civilian-executive
- Official Federal Register text via GovInfo: https://www.govinfo.gov/content/pkg/FR-2026-10-20/html/2026-21447.htm
