A paralegal opens a new file. The LS-203 names the employer as Aegis Defence Services. The injury site is a checkpoint outside Baghdad. The date is sometime in 2007. The claimant remembers a British security firm and a chaotic convoy run. He does not remember a carrier, a policy number, or a broker. The file is thin, and the clock is already running.
This is a common starting point for DBA claims tied to private security contractors. The employer name feels solid. Everything behind it is not. Aegis was a real company with real contracts, but its corporate identity shifted over time. A name that was accurate in 2007 may point nowhere by the time the claim lands on your desk.
Aegis matters because it sat at the center of the private security boom in Iraq. It carried thousands of workers across the most dangerous corridors of the war. Those workers were covered by the Defense Base Act under 42 U.S.C. 1651. Yet the carrier that actually wrote that coverage is buried under contract vehicles, corporate ownership changes, and a stack of near-identical names.
This profile walks through what Aegis actually did, how the GardaWorld acquisition reshaped the paper trail, and why identifying the carrier by injury period takes real investigation. It does not hand you a single carrier name. That answer depends on the exact date and contract, and it has to be traced, not assumed.
Who was Aegis Defence Services and what did it actually do?
Aegis Defence Services was a British private security company founded in 2002. Its early reputation was built on high-risk work in Iraq. The firm provided armed protection, convoy security, and intelligence coordination for reconstruction efforts. That mission put its people directly in the path of the war's most dangerous routes.
In 2004, Aegis won a large contract tied to the US-led reconstruction effort in Iraq. Reporting at the time valued it at roughly 293 million dollars over three years. The work centered on Reconstruction Operations Centers that tracked contractor movement across the country. This was among the largest private security awards of the Iraq war.
That scale is the first reason the carrier trail runs deep. A contract of this size carries thousands of workers over several years. It generates a long stream of injuries, claims, and coverage endorsements. Each renewal or task order can shift the underwriting behind the scenes, even when the employer name never changes.
The company later expanded beyond Iraq into other conflict and post-conflict zones. Its workforce mixed expatriate operators, third-country nationals, and local staff. Each of those categories carries a different DBA analysis. That mix alone makes a clean carrier trace harder than most attorneys expect.
For DBA purposes, the mission matters as much as the name. Protective-services work spreads across many task orders and funding streams. That structure mirrors the way protective-services contracts scatter carrier evidence across the federal record. A single employer can sit under a dozen contract vehicles at once.
How did the GardaWorld acquisition change the DBA paper trail?
In 2015, the Canadian security group GardaWorld acquired Aegis Defence Services. The deal folded a well-known British security firm into a much larger global platform. For a claimant hurt years earlier, that corporate change creates a real problem. The employer on the injury notice may no longer operate under the same ownership.
Acquisitions do not erase the original insurance obligation. A carrier that wrote coverage for Aegis in 2007 still owes on a 2007 injury. But the records that prove that coverage now sit behind a new corporate parent. Finding them means searching both the old identity and the new one.
We cover how GardaWorld absorbed Aegis into a global security platform in a companion profile. That larger story explains the parent structure. This profile stays focused on what the change means for a single injured worker and the carrier that must pay.
The timing of the injury controls everything. A pre-2015 injury points toward Aegis-era coverage. A later injury may involve arrangements made under GardaWorld ownership. Blending the two produces a wrong carrier and a wasted demand letter. Period discipline is the difference between a fast answer and months of dead ends.
Why does Aegis show up under so many names in federal records?
Aegis is not one clean string in the data. ClaimTrove tracks 31 name variations grouped under the Aegis and GardaWorld family. Some are spelling differences. Some are registered legal entities in different jurisdictions. Some reflect the parent name applied to older work. Search one variation and you miss the rest.
This is the alias problem that defeats most manual searches. An attorney types the name from the LS-203 into a federal contract site and gets a handful of results. The real footprint is spread across every spelling the government ever used. Miss a variation and you miss the contract that names the carrier.
Alias resolution is a discipline, not a lucky guess. It means mapping every corporate name, subsidiary, and jurisdiction-specific entity to one canonical employer. Our guide to resolving a single employer's many federal names walks through how that mapping works in practice. For a firm like Aegis, that step is not optional.
The stakes are concrete. Federal contract systems hold 865,232 entity registrations and 43,298 overseas prime awards in the ClaimTrove index. A security firm's true carrier evidence may sit under a name you never thought to search. The alias map is what connects the name the claimant gave you to the records that actually matter.
What makes a security contractor like Aegis harder to insure than a logistics prime?
Private security is a distinct risk class. The core job is to stand between a threat and a protected asset. That means armed movement, static protection at high-value sites, and exposure to direct attack. The injury profile looks nothing like a food-service or base-support prime.
Carriers price that risk carefully, and they do not all write it the same way. A security firm may carry different coverage for different theaters, clients, or contract types. That fragmentation is why a single Aegis policy answer rarely exists. The correct carrier depends on which slice of the business the worker fell under.
The pattern is visible across the sector. What DBA records reveal about the highest-risk security employers is that claim volume and severity cluster around exactly this kind of work. Security primes generate dense, contested claim histories. Those histories leave a trail, but only if you know where to look.
Mergers compound the problem. Security firms buy and sell each other constantly, and each deal reshuffles the corporate tree. The tangled family trees behind private security mergers show how quickly a clean name becomes a maze. Aegis sits inside one of those trees, and the GardaWorld deal added another branch.
If you handle security-contractor claims, you can run this exact analysis inside ClaimTrove. The tool resolves aliases, maps the corporate family, and surfaces the contract vehicles that point toward the carrier by period. It turns a thin LS-203 into a documented starting point in minutes.
How does Aegis's mixed workforce complicate DBA coverage?
Aegis did not staff its contracts with one kind of worker. A single site could hold British and American operators, third-country nationals recruited from Africa or Asia, and local Iraqi guards. The Defense Base Act can reach all three groups, but the analysis differs for each. That variation shapes which claims get filed and which get contested.
Expatriate operators are the clearest case. They are US or allied nationals working a US-funded contract overseas. Coverage under 42 U.S.C. 1651 is usually straightforward. Their claims tend to carry the cleanest paper trail.
Third-country nationals are harder. They may be recruited through layered subcontractors, which pushes the carrier question down the chain. The prime's carrier and the sub's carrier can differ. Tracing that chain is where many security-contractor investigations stall.
Local national guards add another layer. Their coverage can turn on the specific contract terms and any DOL waiver in effect for that country. War-zone work also raises the War Hazards Compensation Act, 42 U.S.C. 1701 et seq., whose reimbursement provision at 42 U.S.C. 1704 can reimburse a carrier for combat-related losses. Each wrinkle changes who ultimately pays.
What federal records confirm Aegis's contract footprint?
Carrier identification starts with proving where the employer actually worked. Federal contract data does that job. The ClaimTrove index holds 43,298 overseas prime awards and 4,315 subaward records. Those records place a contractor at a country, a period, and a funding agency.
For Iraq and Afghanistan security work, contractor presence is verifiable. FOIA database results tracking Afghanistan contractors cover 29,902 records of companies that operated there. That data confirms whether a firm was present, under what contract number, and as a prime or a sub. Presence is the foundation every carrier trace stands on.
Contract clauses matter too. FAR 52.228-3 requires DBA coverage on covered federal contracts performed overseas. When that clause appears, it tells you a carrier existed and coverage was mandatory. The clause does not name the carrier, but it proves one is out there to be found.
Legal records fill the last gap. The ClaimTrove index includes 5,022 administrative decisions and hundreds of federal court opinions. Security contractors appear across that body of case law. A single decision naming the employer and carrier can settle a question that months of contract review could not.
The value of these records is that they cross-check each other. A contract award places the firm at a site, a coverage filing confirms a policy, and a decision names the carrier. When two or three sources agree, the answer holds up under a carrier's challenge. That is the standard an Aegis claim should be built to meet.
What should you gather before investigating an Aegis claim?
A strong Aegis investigation starts with four facts. Get the exact injury date, not just the year. Get the specific country and site. Get the job role, which hints at the contract type. Get any contract number the claimant or the file references.
The injury date anchors the period split at the 2015 acquisition. The country and site narrow the contract vehicles. The role separates security operations from support work, which can sit under different coverage. The contract number, when it exists, is the fastest path to the carrier.
Do not stop at the name on the LS-203. Ask the claimant which entity signed the paychecks and which appeared on any insurance card. Security firms often paid workers through a subsidiary or a local entity. That detail can point to a different carrier than the parent name suggests.
Finally, note whether the work was for the US government or a private client. Non-governmental security work can change the DBA analysis entirely. Confirming the client is a quick way to avoid chasing a carrier that never carried the obligation.
How do you trace Aegis's DBA carrier by injury period?
The right method is disciplined and sequential. First, fix the injury date and location with precision. Second, resolve every name variation for the employer. Third, pull the contract vehicles active on that date in that country. Fourth, match those vehicles to carrier evidence.
No single free tool does all four steps. Contract sites show awards but not carriers. Carrier lists confirm authorization but not the employer link. FOIA database results and coverage filing records fill parts of the gap, but only after you know which names and periods to search. The work is real, and shortcuts produce wrong answers.
This is where the corporate history becomes practical. Because Aegis was acquired in 2015, the carrier question splits cleanly at that line. A 2007 checkpoint injury and a 2018 injury are two different investigations. Treating them as one is the most common mistake in security-contractor claims.
ClaimTrove runs the full sequence in one investigation. Enter the employer and the injury details, and the engine resolves the Aegis and GardaWorld alias family, checks agency mandates under 42 U.S.C. 1651, pulls the contract footprint, and ranks carrier candidates by temporal proximity to the injury date. You get a defensible, source-cited starting point instead of a guess. Run Aegis Defence Services through ClaimTrove and let the engine resolve the aliases, the corporate family, and the carrier-by-period trail for you.