A private security firm holds a State Department protective services contract. It also runs a separate detail guarding an oil company's facility in the same country. One officer covers both assignments in the same week. He gets hurt on the commercial detail. Is that injury covered under the Defense Base Act, or does it fall to a foreign workers' compensation policy that may not exist?
This is the question that strands more private military contractor (PMC) claims than almost any other. The Defense Base Act was built around federal nexus. When a security contractor's client is not the Department of Defense, that nexus gets blurry fast. Attorneys assume the badge, the rifle, and the war zone are enough. They are not.
DBA coverage for a private security contractor on a non-DOD client turns on the contract, not the uniform. A guard force can be doing identical work for two different clients on the same day, with only one of those engagements pulling them under the Act. Getting this wrong means filing the wrong claim, naming the wrong carrier, and watching the statute of limitations run while you argue jurisdiction.
The security niche makes this harder than any other DBA sector. PMCs hold layered contracts across multiple agencies, run commercial work alongside federal work, and rebrand through mergers that scramble the paper trail. ClaimTrove's records show how tangled this gets. This guide explains where coverage attaches, where it breaks, and why the carrier answer almost never sits on the surface.
Does the Defense Base Act Cover Security Contractors Working for Non-DOD Clients?
The DBA does not require a Department of Defense client. That surprises attorneys who equate the Act with the Pentagon. The statute reaches several distinct categories of overseas work, and DOD is only one of them.
Coverage attaches when the work falls under a public-work contract with any U.S. government agency, a contract approved and financed by the United States, or work on a military base or related facility outside the continental United States. A security contractor guarding a USAID compound or a State Department embassy annex is covered, even though no DOD contract exists anywhere in the chain.
The trap is the purely commercial engagement. When a PMC contracts directly with a private oil company, a mining operation, or a foreign corporation, and no U.S. government funding or approval sits behind it, the DBA generally does not reach that work. The officer is overseas, armed, and in danger, but the federal nexus is missing.
Here is what makes the security sector uniquely treacherous. The same firm frequently runs both. A PMC can hold a federal protective services contract and a commercial facility-security contract in the same theater. The DBA question is decided assignment by assignment, not company by company.
Three quick tests help frame the analysis:
- Who is the ultimate client? A U.S. agency, a U.S.-funded entity, or a purely private buyer.
- Where does the money originate? Federal appropriations, foreign aid funding, or private commercial revenue.
- What does the contract say about insurance? A DBA insurance clause is strong evidence the parties expected coverage.
None of these tests is conclusive on its own. Funding can flow through intermediaries. A grant-funded NGO might subcontract security to a PMC, which pulls the work back under the Act through the approved-and-financed prong. Understanding which agencies trigger coverage is the starting point, and the range of OCONUS contract types that require DBA insurance is wider than most practitioners expect.
What Counts as Federal Nexus for a Private Security Contractor?
Federal nexus is the hinge of every non-DOD security claim. The DBA extends the Longshore Act to contractors, and the extension provisions define the reach. Three of those provisions matter most for PMC work.
The first is the public-work prong. Any contract with a U.S. agency for public work performed outside the United States qualifies. State Department, USAID, the Department of Justice, and the Department of Energy all let security contracts that carry DBA obligations. Most attorneys check for DOD and stop. They miss the civilian agencies entirely.
The second is the approved-and-financed prong. This is the prong that captures commercial-looking work funded by Washington. If a U.S.-financed and U.S.-approved reconstruction project hires a security firm, the contract can pull that firm under the Act even where the immediate client is a private contractor or a foreign government. Both approval and financing by the United States are required under § 1651(a)(5). USAID work is the classic example, and the mandatory carrier history behind USAID security coverage shows how deliberate that financing nexus can be.
The third is the military-base prong. Work performed on or near a U.S. military base abroad is covered regardless of who signs the paycheck. A PMC guarding the perimeter of a base under a sub-tier arrangement is reached even if its direct contract is with a foreign facility operator.
The DOJ category is the one almost nobody investigates. ClaimTrove records identify roughly 900 overseas DOJ contracts, many of them protective or investigative in nature. The blind spot is enormous, and we have written separately about DOJ overseas contractor coverage for exactly this reason.
Nexus also survives subcontracting. A second- or third-tier security sub on a federal protective services contract is still covered, because the DBA obligation flows down the tier chain. Identifying which tier the injured worker actually sat on is its own investigation, and it determines which carrier ultimately answers.
Why Is the Carrier So Hard to Identify for Security Contractors?
Even when coverage clearly attaches, naming the carrier is a separate problem. The security sector produces the most tangled carrier records in the entire DBA universe. Three forces drive that complexity.
The first is corporate identity churn. PMCs merge, rebrand, and absorb each other constantly. ClaimTrove records show one well-known Iraq security contractor appearing under 14 distinct name variations across federal databases, and another security firm carrying nine name variations tied to 25 separate carrier records. A name search alone will never surface the full picture.
The second is temporal carrier shifting. DBA carriers do not stay constant. Our data shows most contractors change carriers every three to five years, often at contract renewal or rebid. A security firm covered by one carrier in 2014 may sit with an entirely different carrier by 2018, with no public announcement of the switch. The temporal shift problem in DBA coverage is acute in the security sector because PMC contracts rebid so frequently.
The third is the multi-client structure that started this article. A PMC running federal and commercial details simultaneously may carry a DBA policy for the federal work and a separate, non-DBA policy for the commercial work. The injured officer's assignment that day determines which policy responds. Matching the worker to the right contract, the right period, and the right carrier requires cross-referencing several federal data sources at once.
This is precisely what the ClaimTrove investigation engine was built to solve. Instead of guessing from a single award record, it cross-references prime and subcontract awards, FOIA database results, OALJ decisions, and SME-confirmed carrier mappings across more than a million records. The output is a carrier answer tied to a specific employer, contract, and period, with the alias resolution already done. Run a free investigation on your security-contractor employer and see how many name variations and carrier records surface before you ever file.
How Do Mergers and Aliases Break the Carrier Trail?
Security contractor consolidation is relentless, and every merger fractures the carrier trail a little more. The firm that held a contract in 2010 may have been acquired twice by 2020, with the surviving entity bearing a name that appears nowhere in the original DBA filing.
Consider how this plays out in records. A protective-services prime files DBA coverage under its operating name. The parent holding company appears on the federal award. A regional subsidiary appears on the OALJ decision when a claim is litigated. Three names, one company, and an attorney searching any single name finds only a fragment. This is the heart of why tracing subcontractor insurance is so hard in the PMC space.
Aliases are not limited to mergers. They come from transliteration of foreign entity names, abbreviations on government forms, DBA-name registrations, and simple clerical variation. ClaimTrove maintains hundreds of employer alias mappings precisely because no two federal databases spell a security contractor's name the same way.
The merger problem also shifts liability. When a contractor is acquired, the carrier obligation for an old claim may stay with the original insurer, transfer to the successor, or land in dispute between them. Broader patterns of defense contractor consolidation reshaping DBA coverage show how often these transitions leave injured workers caught between entities that each point at the other.
For a non-DOD security claim, the alias problem compounds the nexus problem. You first have to establish the work was federal-nexus, then trace the right corporate entity, then find the carrier that covered that entity during that period. Each step depends on the one before it. Miss the alias and you never reach the carrier.
What Should Attorneys Verify Before Filing a Non-DOD Security Claim?
Before you file, work through a structured checklist. The security niche punishes assumptions, and the cost of a wrong filing is the claim itself.
- Confirm the assignment, not just the employer. Establish exactly which contract the worker served under on the date of injury. For a multi-client PMC, this single fact decides everything.
- Establish federal nexus on that assignment. Identify the agency, the funding source, and whether the work sat on or near a U.S. base abroad. Document the prong you are relying on.
- Resolve the corporate identity. Map the operating name, parent, and any successor entities. Account for mergers that occurred between the injury date and the filing date.
- Trace the carrier for that period. Carriers shift every few years. The carrier on a recent award may not be the carrier on the injury date.
- Check the tier. If the worker was a subcontractor employee, determine whether the prime's carrier, the sub's carrier, or both are in play.
The commercial-versus-federal distinction deserves special caution. If the work was purely commercial with no U.S. nexus, the DBA may not apply at all, and the claim belongs in a foreign compensation system or under a different policy. Filing a DBA claim on non-covered commercial work wastes the limitations period and can forfeit the real remedy.
Documentation beats inference at every step. Secure the contract, the task order, the funding citation, and any insurance clause before you commit to a theory of coverage. A DBA insurance clause in the contract is strong evidence the parties expected the Act to apply, even on work that looks commercial on its face.
None of this is something to do from memory or from a single award lookup. The data lives across prime contract awards, subcontract awards, FOIA database results, and litigated decisions, and the pieces only make sense when joined. Start a ClaimTrove investigation on your PMC employer to confirm nexus, resolve aliases, and pull the period-correct carrier before the clock runs.