U.S. Bans DeepSeek at Federal Agencies: The AI Supply-Chain Lesson for Your Business | inicIA
Direct answer
On October 19, 2026, the U.S. Department of Homeland Security (DHS) ordered federal civilian agencies to remove DeepSeek products — and third-party services built on its models — from their IT systems, and to stop acquiring them (Reuters, TechCrunch, Wall Street Journal). The order, under the Federal Acquisition Supply Chain Security Act of 2018, cites "multiple threat vectors": using DeepSeek "may result in the transfer of sensitive data to the PRC" and could produce actionable intelligence on U.S. persons or agencies. What matters is the scope: it covers not just the DeepSeek app, but any third-party product or service developed using DeepSeek implementations — including models served through APIs and intermediaries.
The Details Every Business Should Understand
- The invisible third-party problem: as The Register noted, services like OpenRouter or the Vercel AI Gateway route requests to different model providers. An agency (or your company) could be using DeepSeek without knowing it, because the intermediary routes it silently.
- Restrictions already existed: a December 2025 law had already limited DeepSeek's use in intelligence and national security systems. This order extends the ban to civilian agencies and to already-deployed systems.
- China pushed back: foreign ministry spokesperson Mao Ning accused the U.S. of "overstretching the concept of national security" and said it would defend its companies' rights (TechCrunch). Bloomberg reported China is considering export restrictions on 23 AI technologies, including chip designs.
- AI is now regulated infrastructure: the order treats AI models for what they are — a supply-chain component — not just software. That's the mindset your business needs to adopt.
The AI Supply-Chain Checklist for Your Business
- Ask what models your vendors use: your CRM with "included AI," your transcription tool, your chatbot — what models power them? Where is your data processed? If your vendor doesn't know or won't say, you have unmeasured risk.
- Map the intermediaries: if you use gateways or platforms that route between models, lock in which providers are allowed and which aren't. Automatic routing is convenient and dangerous at the same time.
- Separate sensitive data from unverified tools: the DHS logic applies to any company — customer information, finances or strategy doesn't go into tools whose origin and data handling you can't audit.
- Put the clause in your contracts: when buying software with AI, demand model transparency, processing jurisdiction and audit rights. What's a recommendation for SMBs today may be a regulatory requirement tomorrow (for government, it already is).
Related links
- Privacy and data: what happens to your customers' information
- Microsoft: your AI agents are the new insider threat — Guardian Agents and living permissions
- How to choose an AI vendor: 7 questions before signing
Frequently asked questions
What exactly did DHS order?
Federal civilian agencies: remove DeepSeek and affiliate products from their systems, including third-party products and services developed using DeepSeek implementations, and don't acquire them in the future. The order was published October 19, 2026.
Does this ban me from using DeepSeek in my business?
No: the order applies to U.S. federal civilian agencies. But the security logic applies to any company — and governments tend to anticipate what later becomes industry standard.
How could I be using DeepSeek without knowing it?
Through intermediaries (AI gateways) that route requests to the "best available provider," or tools that use rebranded Chinese open-weight models under another name. That's why vendor mapping matters.
What should I ask my software vendors?
Which AI models they use, where data is processed, whether they use subprocessors or gateways that switch models, and whether they accept transparency and audit clauses. If they don't answer clearly, reconsider the relationship.
