DoD’s Anthropic ban fractures across agencies mid-enforcement
Contractors are getting materially different certification demands from different DoD offices—some hewing to the letter of the order, some demanding blanket non-use of Claude.
TL;DR
Five months after the Pentagon designated Anthropic a supply-chain risk, contractors are discovering that enforcement isn't uniform. Different DoD agencies—and even different offices within the same agency—are issuing conflicting certification requests. Some ask only what the active designation requires: no Claude on DoD contracts. Others demand contractors certify they aren't using Claude at all, including on commercial or civilian-agency work. Subcontractors face a compounding problem, with primes sometimes flowing down their own broader checklists rather than the government's actual request. The gap between what the order says and what contracting officers are demanding is now a live liability question.
The Pentagon's Anthropic designation has now entered the phase where the formal order and the field execution don't match. That's the operational problem contractors are living with as of August 2026, and it has no obvious fix.
Two supply-chain risk designations were issued in March, as Federal News Network has tracked. One was enjoined at the district court level. The other is active and being litigated at the D.C. Circuit. Because the active one carries legal force, agencies within the Department of Defense have begun reaching out to contractors for certifications.
What they're asking for, however, varies materially. Some contracting officers have stuck to what the designation actually requires: certify that Anthropic products aren't being used in performance of DoD contracts. Others have gone further, demanding certifications that contractors aren't using Claude at all—on commercial work, on civilian-agency contracts, anywhere.
The government itself has been clear in litigation that it isn't trying to prohibit Claude use outside DoD contracts, Ryan Frazee of Mayer Brown noted in the Federal News Network interview. So the broader certification requests don't have a legal anchor. But a contractor who receives one still has to answer it. And answering it wrong opens the door to False Claims Act exposure.
The subcontractor squeeze
The fragmentation doesn't stop at the prime level. Subcontractors receive certification demands from primes, and those primes don't always pass through the government's request cleanly. Some flow it down verbatim. Others send broader checklist certifications of their own design, attempting to shield themselves from liability by extracting commitments the government never asked for.
This creates a cascading problem: a sub might be asked to certify something the prime's own contracting officer didn't require. Refusing risks the relationship. Complying risks misrepresentation. The only sound approach Frazee identified is to respond honestly and push back politely where the request exceeds the legal scope—but that requires the sub to know what the legal scope is, and not every sub has counsel on speed dial.
Litigation isn't clarifying anything soon
The active designation is under review at the D.C. Circuit, and Frazee described the tea leaves as hard to read. Merits briefing has been supplemented multiple times. The other designation remains enjoined. Neither track offers contractors a clear signal about whether Claude will be back in the picture for government work or permanently out.
In the meantime, some contractors have Claude embedded in their systems in ways that are genuinely hard to unwind. Others are trying to decide whether to buy enterprise licenses for non-DoD use, a decision that's hard to make when they don't know whether a contracting officer down the hall will later demand they certify against it.
DoD hasn't issued guidance standardizing the certification language across its agencies. Until it does—or until the courts resolve the underlying designation—contractors are navigating a compliance landscape where what's required depends on who's asking.
Published ·Deep Fathom