There Is No Department of War, and That Should Worry You

The headline landed in my feed this morning: The Department of War Releases Updated List of Foreign Institutions Engaging in Problemati… The truncation felt apt. The department doesn’t exist. The United States has a Department of Defense, a State Department, a Treasury Department that administers sanctions, and a Commerce Department that runs export controls. It does not have a Department of War. If you see that phrase on a .gov domain, you’re either reading a very old document from 1947 or you’re looking at something that isn’t what it claims to be.

The Real Architecture of Designation

When the U.S. government wants to flag a foreign entity, it uses specific legal authorities. The Treasury’s Office of Foreign Assets Control (OFAC) maintains the Specially Designated Nationals and Blocked Persons List (SDN). The Commerce Department’s Bureau of Industry and Security (BIS) runs the Entity List and the Military End-User (MEU) list. The State Department designates state sponsors of terrorism and applies sanctions under various executive orders. The Pentagon produces an annual report on military and security developments involving the People’s Republic of China, mandated by the FY2000 NDAA. None of these live under a “Department of War” masthead.

Conflating them into a single “list of problematic institutions” is analytically lazy. Each list has different evidentiary standards, different appeal processes, and different practical consequences. An SDN designation freezes assets and prohibits U.S. persons from transacting. An Entity List entry requires a license for exports, reexports, and transfers (in-country). A MEU listing restricts items with military end use in China, Russia, or Venezuela. Mixing them obscures what a business or research institution actually needs to do.

Why the Branding Matters

Language shapes policy perception. “Department of War” evokes a pre-1947 world where conflict was the organizing principle of foreign policy. The 1947 National Security Act renamed it the Department of Defense for a reason: the architecture shifted from declared war to continuous deterrence, alliances, and gray-zone competition. Using the old name — even ironically — reinforces a binary mindset that ill-fits an era where the most consequential designations involve dual-use semiconductor equipment, quantum research collaborations, and data governance standards.

I’ve watched compliance teams waste weeks because a senior leader saw a headline, assumed a single “banned entities” list existed, and directed the team to “screen against the DoD list.” There is no such list. The screening stack must query OFAC SDN, BIS Entity List, BIS MEU, State Department terrorism designations, and the non-SDN sanctions programs (Sectoral Sanctions, Correspondent Account, etc.) separately. Each has its own update cadence. OFAC updates daily. BIS updates when it publishes a Federal Register notice. The PRC military report is annual. Treating them as one feed guarantees false negatives.

The Google News Vector

The URL in the feed is a Google News RSS redirect — a long, encoded string that resolves to who-knows-where. That’s not a primary source. Primary sources are Federal Register notices, Treasury press releases, BIS final rules, State Department Federal Register determinations. If you’re building a compliance process on an RSS redirect, you’re building on sand. The .gov domain in the snippet is a red herring; Google News caches content from many domains, and the display URL doesn’t guarantee provenance.

This matters because designation data is high-stakes. A false positive on an SDN match can freeze a legitimate transaction, trigger a voluntary self-disclosure, and cost a company months of legal fees. A false negative lets a prohibited transaction proceed, exposing the company to enforcement. The source fidelity is not academic.

What a Serious Update Looks Like

When OFAC adds entities, it publishes a notice with the legal authority (e.g., E.O. 14024, 13848, 13660), the identifiers (aliases, addresses, ID numbers, vessel IMOs), and a compliance advisory. When BIS adds to the Entity List, it publishes a final rule with the specific license requirements (License Exception GOV, License Exception ENC, etc.) and the end-use concerns. The State Department’s terrorism designations come with a statutory citation (e.g., Section 6(j) of the Export Administration Act, though that’s the old statute; now it’s IEEPA and specific E.O.s).

A credible “updated list” announcement would cite the specific authorities, the Federal Register citation, the effective date, and the scope of the change. It would not lead with a department that hasn’t existed in 77 years.

The Takeaway

If you’re a compliance officer, general counsel, or export control attorney, ignore the branding. Map your screening to the actual lists: OFAC SDN, OFAC Non-SDN (Sectoral, Correspondent Account, etc.), BIS Entity List, BIS MEU List, BIS Unverified List, State Department State Sponsors of Terrorism, State Department Non-Proliferation Sanctions, and the various EU/UK/UN lists if you operate multilaterally. Automate the pulls from the official XML/JSON feeds each agency publishes. Log the timestamp of each pull. Document the authority for every match.

And if a vendor tries to sell you a “Department of War consolidated list,” walk away. They don’t understand the regulatory architecture, and they’ll sell you a product that misses designations or hallucinates them. Both are expensive.

Source: original report