The Challenge
The Department of Homeland Security's recent order against DeepSeek has put federal civilian agencies in a tough spot. This order doesn't just prevent future contracts with Hangzhou DeepSeek Artificial Intelligence Co.; it requires agencies to remove DeepSeek's products from their systems entirely. It also affects third-party tools built on DeepSeek's models.
This isn't just about finding a chatbot. Your team must identify every tool that might be running on DeepSeek implementations, including those embedded in vendor products without clear disclosure.
The order warns that DeepSeek's models "may contain malware or other security vulnerabilities" and could expose sensitive data to Chinese intelligence services. This means government employees or contractors using these tools might unknowingly transfer sensitive data to China.
The Environment and Constraints
Federal civilian agencies operate under the Federal Acquisition Supply Chain Security Act of 2018, which allows the DHS secretary to exclude risky technology from civilian systems. The defense secretary and the director of national intelligence have similar powers for military and intelligence networks. This framework enables agencies to act quickly when supply chain threats arise.
The implementing rule for the Federal Acquisition Security Council extends exclusion and removal orders to prime contractors and subcontractors. A 2023 Federal Acquisition Regulation update mandates that contractors comply with these orders. If you're a contractor, this is a compliance obligation affecting your federal work eligibility.
Agencies have 60 days to request exceptions, which the Cybersecurity and Infrastructure Security Agency (CISA) will approve or deny in writing. DeepSeek has 60 days to challenge the order in the U.S. Court of Appeals for the District of Columbia Circuit.
The Approach Federal Agencies Are Taking
Agencies are conducting multi-layer discovery efforts. Initially, they're scanning for obvious DeepSeek installations, such as chatbots and API integrations. The real challenge is identifying third-party tools that use DeepSeek models. Many vendors built products on DeepSeek's open-weight releases without making this clear in their documentation.
DHS has urged agencies to monitor network traffic for data leaving their environments and to enhance logging. This isn't just about detecting DeepSeek connections; it's about understanding what your AI tools are doing with your data. If you can't track where a tool sends information, you can't enforce a removal order effectively.
Agencies are also reviewing contractor relationships. Under the 2023 FAR update, contractors must comply with exclusion and removal orders. Your prime contractors need to audit their subcontractors' toolchains, and you need contract language that makes supply chain compliance a material term.
Results and What's Still Uncertain
The order has taken immediate effect: DeepSeek is now excluded from federal civilian procurement, and agencies must remove its products. Texas banned DeepSeek from state-issued devices in January 2025, with New York and Virginia following suit. Australia, South Korea, and Taiwan have also banned it from government systems.
However, operational compliance is ongoing. Agencies are discovering DeepSeek dependencies they weren't aware of. The 60-day exception window allows agencies to document cases where removal poses unacceptable operational risks and seek CISA approval to maintain specific implementations under controlled conditions.
The order's reach into third-party tools built on DeepSeek models presents measurement challenges. There's no central registry of which products use which AI models, and vendors aren't always transparent about their dependencies. Agencies rely on vendor attestations, contract reviews, and traffic analysis to get a complete picture.
What Agencies Would Do Differently
If agencies could start over, most would have built AI model inventories before the ban. Knowing which tools run on which models is essential for responding to exclusion orders and understanding exposure to model vulnerabilities, license changes, and geopolitical risks.
Stronger contract terms would have been beneficial. Standard IT service agreements don't typically require vendors to disclose their AI model dependencies or notify customers of changes. Agencies are now adding these requirements to renewals, but it's a reactive measure.
Early traffic monitoring would have provided a baseline. Without knowing normal AI tool behavior, it's hard to spot unusual data movement when a ban forces scrutiny.
Takeaways for Your Team
Build an AI model inventory now. Don't wait for the next exclusion order. Document which tools use which models, where they're hosted, and what data they process. This isn't just about Chinese AI developers; it's about managing a new class of supply chain risk.
Update your contractor terms. Make AI model disclosure a contract requirement. Require vendors to notify you within 30 days of changes to underlying models. Include language that makes compliance with federal exclusion and removal orders a material contract term, with clear remediation timelines.
Implement continuous monitoring for AI tool traffic. You need visibility into where your AI tools send data. Log API calls, monitor egress traffic, and set alerts for unexpected destinations. The order urged agencies to watch for "signs of data leaving their environments." This requires ongoing monitoring.
Test your removal process. Can you remove a tool from your environment in 60 days? Do you have alternative solutions ready? The Federal Acquisition Supply Chain Security Act won't stop with DeepSeek. The Department of Defense has already blacklisted Anthropic. Your removal process needs to be a documented, tested capability.
Document your risk decisions. If you're requesting an exception under the 60-day window, build a clear risk case. CISA needs to see that you understand the threat, have evaluated alternatives, and are implementing compensating controls. "We don't have time to replace it" isn't a justification. "We've isolated it to a specific enclave, implemented enhanced monitoring, and have a replacement timeline" is.
The DeepSeek ban is a preview of how supply chain security will work in the AI era. Models are dependencies now, and dependencies are attack surfaces. Your compliance program needs to account for that reality before the next order drops.
