Steve Miller's Blog

A digital workshop for systems-minded tech commentary.

DHS Ordered DeepSeek Out of Federal Civilian IT and Barred New Purchases: How to Build an AI Model Allowlist Before Your Own Regulator Asks for One

Three professionals in an office sort index cards and policy pages across a conference table during a review

Written by

in

Banning one app is the easy headline. The hard part, for agencies and companies alike, is answering “where is it actually running?” when models hide inside browser extensions, developer tools, and SaaS features nobody reviewed. That is why the DeepSeek federal ban is worth reading closely, and why it makes a good template for an AI model allowlist of your own. The order is narrower in some ways than the headlines, and broader in one way most people missed.

What the Order Is, and Who Issued It

It is not an executive order, an OMB memo, or a new law. It is Exclusion and Removal Order #2026-01, issued by the Secretary of Homeland Security under the Federal Acquisition Supply Chain Security Act of 2018 (FASCSA). The order, published in the Federal Register on October 20, 2026 as DHS Docket No. DHS-2026-0628, is signed by Secretary Markwayne Mullin and copies OMB Director Russell Vought. The notice says the Secretary acted “following review of the Federal Acquisition Security Council Recommendation and affiliated evidence.”

Dates matter here. The order’s “Original Release Date” is July 24, 2026. Federal Register publication came almost three months later. So the order was already in force well before most people heard about it.

What It Removes, and From Where

The order “Applies To: Federal Civilian Executive Branch Agencies except for their national security systems and secure compartmented information systems.” Under FASCSA, the Defense Department and the intelligence community issue their own orders, so this one does not cover them. That is why I retitled the post. “Federal civilian IT” is accurate. “Federal systems,” with no qualifier, is not.

Within that scope, the “Required Actions” section tells all civilian agencies to:

  1. Exclude “DeepSeek, DeepSeek-affiliated entities, and their products from civilian agency procurements, effective immediately after issuance of this Order,” including “agency-approved products lists, service provider equipment lists, e-commerce markets.”
  2. Remove “products provided by DeepSeek, DeepSeek-affiliated entities, and third-party products and services developed using DeepSeek implementations, from civilian agency information technology systems immediately after the issuance of the Order, or seek an Exception.”

Two details stand out. First, the phrase “third-party products and services developed using DeepSeek implementations.” This goes beyond DeepSeek’s own app or hosted API. As the law firm Haynes and Boone notes in its analysis, the order “does not define ‘DeepSeek implementation,’” and its removal text “neither distinguishes DeepSeek-hosted from self-hosted deployments nor addresses fine-tuned versions.” In other words, it is unclear whether a vendor’s product that runs a downloaded DeepSeek open-weight model is covered. The text reads broadly enough that a cautious agency would assume it is.

Second, the stated risks. The order’s risk summary says DeepSeek’s servers are in China and that its account process “collects personally identifiable information and may also track and digitally fingerprint users.” It says prompts may result in “the transfer of sensitive data to the PRC,” and that “the models themselves may contain malware or other security vulnerabilities.” It cites research that found “multiple critical vulnerabilities” in DeepSeek’s iOS app.

Exceptions, and a Window That Already Closed

Agencies can ask for an exception, including asking that the order not apply to them, to certain actions, or for a delay. Requests “must be submitted in writing within 60 days of the issuance of this order,” with a “compelling justification” and “any alternative mitigations.” The order names no automatic carve-out for research. Its only categorical carve-out is national security and compartmented systems. Haynes and Boone calculates that, counted from July 24, the 60-day window “closed on Sept. 22, 28 days before publication.” It also notes the order is inconsistent about who reviews requests: one passage says CISA, another says DHS.

Contractors are reached indirectly. Haynes and Boone explains that the FAR clause 52.204-30 carries FASCSA orders into contracts, requires contractors to check SAM.gov for such orders, and requires a report to the contracting officer within three business days of finding a covered article. That is Haynes and Boone’s reading of the clause, not text from the order itself.

My Recommendations: Build an AI Model Allowlist

This section is my opinion and my own playbook, not federal guidance. The order’s structure, exclude from purchasing, remove from systems, document exceptions, is a decent model for any organization.

  1. Inventory first. List every AI app, browser extension, IDE plugin, SaaS “AI feature,” hosted API, and locally run model. Ask vendors in writing which underlying models their features call. Contract language, not marketing pages, is where you will get a real answer.
  2. Write approval criteria. For each model, record who developed it, where it is hosted, where data goes, what the data-retention terms are, and which data classes it may touch. Approve a model per use case, not in general.
  3. Track open-weight provenance. For downloaded models, record the source repository, the exact model ID and hash, and any fine-tunes built on it. The DeepSeek order shows why: “developed using” can reach derivatives, and you will want to answer that question quickly.
  4. Enforce at the network and SaaS layers. Block unapproved AI domains at the secure web gateway or DNS layer, use your CASB or SaaS management tool to disable unapproved AI features, and route sanctioned API traffic through a gateway that logs which model was called.
  5. Control endpoints and developer tools. Use browser and extension allowlists, and watch for local model runtimes and large model-weight downloads on managed devices.
  6. Run an exceptions process with an expiry date. Require a written justification, compensating controls, an owner, and a review date, just as the order asks agencies to do.

Picture this hypothetical. Your help-desk SaaS ships a new “smart summary” feature, and three months later you learn it runs a fine-tuned open-weight model nobody on your team reviewed. If your allowlist records models per vendor feature, that is a ticket. If it only lists apps, it is a surprise. That is my illustration, not a reported case.

The Bottom Line

DHS did not ban DeepSeek from all of government. It ordered federal civilian agencies, outside national security systems, to stop buying it and to remove it, including third-party products built with it, as of July 24, 2026. The open question of what counts as a “DeepSeek implementation” is exactly the question your own allowlist should be able to answer about every model you run.

Comments

Leave a Reply

Your email address will not be published. Required fields are marked *