Shadow Force: Private Security Contractors in Iraq

Let’s start with why I wrote this book. My rationale was simple. I wrote it to fill a void. It is a sad fact that much of the debate over private military and security contractors is, to borrow from Shakespeare, a tale told by idiots, full of sound and fury; signifying nothing. The tale is made worse by the fact that much of those doing the telling have highly partisan axes to grind.

I have been following the industry since the early 1990s, long before most contemporary writers even realized there was a PMC sector. As time passed, it became clear that an interesting, indeed, fairly important subject‐​the role and impact of outsourcing traditional military and other national security functions‐​was degenerating into a politicized debate.

This book is simply a modest attempt to bring some facts into view and let the chips fall where they may. Although I do have opinions on the pros and cons of governmental use of private military contractors, I am neither a diehard supporter nor fervent opponent of their use. I have no dog in the fight over outsourcing things that used to be considered governmental functions. As Mr. Spock used to tell Captain Kirk on the original Star Trek series, I consider it a fascinating phenomenon, worthy of continuing study.

In general there has been far too much sensationalistic, sometimes misleading coverage of how and why tasks formerly done in‐​house by the U.S. military have been outsourced, especially in regard to Iraq. Now that PMCs are becoming embedded in popular culture via film, popular books, cartoons, and television, the time is long overdue for a factual, dispassionate accounting of both the good and bad of the subject.

Let’s be honest about this. The fact that we are dealing with an industry that has really only been in the public eye for a bit over a decade, depending on who and where you count, makes drawing conclusions difficult. Quite simply it is, despite notable consolidations in recent years, an industry in flux. Ten years ago, most public commentary focused on just three companies, Executive Outcomes and Sandline of Great Britain (both of which no longer exist) and U.S.-based MPRI (now a subsidiary of L‑3).

A quick note on terminology is in order. In this book I write about private security contractors (PSCs). These are firms that employ people who carry weapons to protect their clients and use them when necessary. Such firms are often labeled “private military contractors,” although that more accurately refers to firms doing unarmed logistics work, such as KBR.

PSCs are generally considered a subset of PMCs. Academics have spent years arguing over the appropriate terminology. I largely consider it an academic distinction that doesn’t have much relevance to real‐​world discussion of the subject. But for the sake of convenience‐​because the acronym is already firmly embedded in popular culture and discourse‑I generally use PMC, although I am writing specifically about PSCs, an acronym I use as well.

There is no consensus on what constitute a PMC, but three main categories of their activities stand out:

• Military combatant companies-Firms that actually provide military forces capable of combat are fairly rare and only constitute a minority of PMCs, even though such firms tend to receive the most publicity. Examples include the now disbanded PMCs Executive Outcomes of South Africa and Sandline of the United Kingdom; none are currently operating in Iraq.
• Military consulting firms-These traditionally provide training and advisory services, though some have expanded into personal security and bodyguard services. Examples include Blackwater, MPRI, DynCorp, and SAIC of the United States.
• Military support firms-These provide nonlethal aid and assistance, such as weapons maintenance, technical support, explosive ordnance disposal, and intelligence collection and analysis. Examples include Halo Group, Vinnell, and Ronco of the United States.

Put aside for a moment the reality that as nations have frayed, private security contractors are far from the only type of group that has taken a bite out of the monopoly of violence traditionally assumed by states: think gangs in urban ghettos or factions in failed states, for example. The truth is that defining a mercenary is a bit like defining pornography; it is frequently in the eye and mind of the beholder. From the viewpoints of accountability or regulation, words that have been cited innumerable times over the past few years in regard to private security contractors, the only definition that counts is the legal one.

The most widely if not universally accepted definition is that in the 1977 Protocol I to the Geneva Conventions. Article 47 puts forward six criteria, all of which must be met for a combatant to be considered a mercenary. Accordingly, a mercenary is any person who:

((a) is specially recruited locally or abroad in order to fight in an armed conflict;

(b) does, in fact, take a direct part in the hostilities;

(c) is motivated to take part in the hostilities essentially by the desire for private gain and, in fact, is promised, by or on behalf of a Party to the conflict, material compensation substantially in excess of that promised or paid to combatants of similar ranks and functions in the armed forces of that Party;

(d) is neither a national of a Party to the conflict nor a resident of territory controlled by a Party to the conflict;

(e) is not a member of the armed forces of a Party to the conflict; and

(f) has not been sent by a State that is not a Party to the conflict on official duty as a member of its armed forces.

So why wouldn’t someone working for a private security contractor in Iraq‐​for example‐​meet that definition? Well, for starters, a majority of those working for private security contractors are Iraqi, and as such are nationals of a party to the conflict, so they don’t qualify. Second, not all private security workers take a direct part in the hostilities.

There are at least 200 foreign and domestic private security companies in Iraq, ranging from major firms such as Aegis Defence Services, ArmorGroup, Blackwater USA Group, DynCorp, and Triple Canopy to far smaller ones. Not all their employees are out there toting guns. Some of their consultancy services are extremely white‐​collar, involving work such as sitting in front of computer consoles at Regional Operations Centres and monitoring convoy movements. Some people consider PMCs (or PSCs) simply patriotic Americans willing to do their part in supporting America, just like regular military forces. But others consider them thinly veiled mercenaries. Typical is this view by Yale English professor David Bromwich:

Putting aside the fact that, historically speaking, mercenary hasn’t always been a dirty word, the truth is more complex. There are both good and bad aspects to private military contracting, and I’ve mentioned both in past writings. Admittedly, the line between the two is often hard to discern. One British commentator noted:

When I asked an official at the Foreign Office a question about mercenaries last week, he replied “they’re not mercenaries, they’re private security companies.” “What’s the difference?” “The difference is that a private security company is a properly registered company, not an individual getting a few friends together.” In other words, you cease to be a mercenary by sending £20 to Companies House.

And it is true that there are connections between the worlds of classic mercenaries and security contractors.

For example, consider Simon Mann, a former British Army officer, a South African citizen, and a mercenary. In 2004 he was accused of planning to overthrow the government of oil‐​rich Equatorial Guinea. His coup attempt was viewed as a real‐​life version of the 1974 novel The Dogs of War by Fredrick Forsyth, which chronicled the efforts of a company of European mercenary soldiers hired by a British industrialist to depose the government of a fictional African country.

Interestingly, in recent years, after the release of once‐​secret British government documents, Forsyth was forced to admit his own role in financing a similar, and similarly failed, coup against Equatorial Guinea in 1973. Mann is a former associate of Lieutenant Colonel Tim Spicer, the chief executive of the British private military contractor Aegis Defence‐​one of the biggest security firms currently in Iraq‐​having worked with him in another private security firm, Sandline International. Forsyth was an investor when Spicer first set up Aegis, and he reportedly made quite a bit of money from his investment.

But Mann also helped establish Executive Outcomes. That firm was the mother of all private security contractors and the missing link between the “Wild Geese”-style mercenaries of old and the new generation of PMCs. Executive Outcomes was renowned around the world in the 1990s for fighting against rebel leader Jonas Savimbi in Angola and against the murderous Revolutionary United Front rebel group in Sierra Leone.

Nowadays, people tend to label anyone who carries a gun while not a member of a regular military establishment a mercenary. Such people are supposedly uncontrollable rogues who commit unspeakable atrocities and wreak havoc. As a member of an industry trade group put it, “The term ‘mercenary’ is commonly used to describe the private peace and stability operations industry by opponents and those who lack a fundamental understanding of exactly what it is that the industry does. Regardless, it is a popular pejorative term among those who don’t particularly care for the private sector’s role in peace and stability operations.”

Well, war is war and violence is an inextricable part of it. But even the worst of classical mercenaries from ancient times or the Middle Ages would have a hard time rivaling the record of human and physical destruction achieved by regular military forces.

For example, mercenaries did not invent concentration camps, firebomb cities from the air, use chemical or biological weapons, or use nuclear weapons on civilian cities. In fact, the bloodiest century in recorded human history was the twentieth, courtesy of regular military forces. Not even the most bloodthirsty mercenaries of centuries past could have imagined committing the kind of carnage for which that contemporary regular military forces routinely plan and train.

And, just to confuse things a little more one might note that there are tens of thousands of people serving in the American military who aren’t even American, at least not yet. The number increased from 28,000 to 39,000 from 2000 to 2005 alone.

Many of them applied under a fast‐​track process approved by President Bush in 2003 and enacted in October 2004. Under the new rules, people in the military can become citizens without paying the customary $320 application fee or having to be in the United States for an interview with immigration officials and naturalization proceedings.

The President also made thousands of service members immediately eligible for citizenship by not requiring them to meet a minimum residency threshold, as civilians applying to be citizens must do, although they must still be legal residents of the United States.

In late 2006 it was reported that the U.S. military, struggling to meet recruiting goals, was considering opening up recruiting stations overseas and putting more immigrants on a faster track to U.S. citizenship if they volunteered.

Such proposals have been catching on among parts of the establishment. Michael O’Hanlon, a senior fellow at the Brookings Institution in Washington, and Max Boot, a senior fellow at the Council on Foreign Relations in New York, have proposed allowing thousands of immigrants into the United States to serve for four years in the military in exchange for citizenship.

In any event, such immigrants are fighting‐​and in some cases dying‐​for a country of which they are not a part, but we don’t call them mercenaries. As of March 2008, more than 100 foreign‐​born members of the U.S. military had earned American citizenship by dying in Iraq.

In fact, in the current age, in which modern state militaries are staffed by volunteer recruits largely joining in peacetime‐​many for the pay and benefits‐​the difference between the private and public soldiers appears to revolve largely around the form of employment contract

As a U.S. military veteran, I believe there is another side to the use of private security and military contractors that few people care to talk about publicly.

The reality is that private contractors did not crawl out from under a rock somewhere. They are on America’s battlefields because the government, reflecting the will of the people, wants them there.

The reason we have such reliance on private contractors is simple enough.

Even though the Cold War is over and the Soviet Union is a historical memory, the United States still reserves the right to militarily intervene everywhere. This, however, despite the so‐​called Revolution in Military Affairs that Defense Secretary Donald Rumsfeld championed, is a highly people‐​powered endeavor. And most people have decided that their children, much like Dick Cheney during the Vietnam War, have “better things to do.”

Looking at it historically, however, it wasn’t supposed to be this way. As one scholar noted,

But, given the downsizing the U.S. armed forces had undergone since the fall of the Berlin Wall, the military turned to the private sector for help.

My own view of the world is that the international order will continue to be roiled and disrupted for some time to come. Thus, there will be a void in international politics. And, just as in nature, which abhors a vacuum, private contractors will step in to fill it. Personally, I think the outsourcing of military capabilities left the station decades ago. It has taken this long for public perception to catch up‐​and people still only see the caboose.

If people don’t want to use private contractors, the choices are simple. Either scale back U.S. geopolitical commitments or enlarge the military, something that will entail more gargantuan expenditures and even, some argue, a return to the draft down the road.

Personally, I prefer the former. But most people prefer substituting contractors for draftees. As former Marine colonel Jack Holly said, “We’re never going to war without the private security industry again in a non‐​draft environment.”

Still, what I would really like to see is a national debate on this. Instead, we bury our heads in the sand and bemoan the presence of private contractors. That is a waste of time. Private security contractors, after all, are just doing the job we outsourced to them. And, like them or hate them, they are going to be around for a long time.

As Paul Lombardi, CEO of DynCorp, said in 2003, “You could fight without us, but it would be difficult. Because we’re so involved, it’s difficult to extricate us from the process.” And as Professor Debra Avant noted, “A lot of the companies in the 1990s were small, service‐​based companies. Now they’re small services‐​based wings of large companies. Defense contractors have been buying up these companies like mad. This is where they think the future is.”

Permit a brief overview. As Shakespeare wrote, “Cry “Havoc!” and let slip the dogs of war. But the question is whose dogs exactly?

Traditionally, the ultimate symbol of the sovereignty of a nation is its ability to monopolize the means of violence‐​in other words, raising, maintaining, and using military forces. Although there have always been exceptions, such as partisans and guerrilla forces, the evolution of the international system over the centuries has been such that military conflict has been conducted using state‐​raised forces. Of course, even during that evolution private actors played significant roles. Some of the same criticisms made against private contractors today were made against the East India Company back in the 17th to 19th centuries. Indeed, it was the East India Company that pioneered the shareholder model of corporate ownership.

In modern times these forces have been motivated by issues of nationalism and ideology, in opposition to earlier traditions of fighting for whoever could pay. The evolution of national military establishments has also been accompanied by changes in international law that, though often belatedly and imperfectly, seek to regulate the means by which military force is used, including the types of military units considered legitimate.

According to estimates from the International Peace Operations Association, the total industry value of the global “Peace and Stability Operations Industry” is $20 billion for all companies providing services in the field. Of that number, private security contractors (PSCs) make up only about 5 to 10 percent of the total (approximately $2 billion annually of total industry value). Although the normal peacetime number would be closer to 5 percent for PSCs, events in Iraq have driven the number up.

But the industry is seen as a growth sector. In September 2005 the Stockholm International Peace Research Institute said that the industry is likely to double in size over the next five years, confirming predictions that industry revenues will hit $200 billion in 2010.

The military’s growing reliance on contractors is part of a government‐​wide shift toward outsourcing that goes back decades. During the Clinton administration, it was promoted as “Reinventing Government” by former Vice President Al Gore, an initiative that promised that cutting government payrolls and shifting work to contractors would improve productivity while cutting costs. In early 2005, the federal government was spending about $100 billion more annually for outside contracts than on employee salaries. Many federal departments and offices‐​NASA and the Department of Energy, to name just two‐​have become de facto contract management agencies, devoting upward of 80 percent of their budgets to contractors.

Not to be outdone, in 2000, presidential candidate George W. Bush promised to let private companies compete with government workers for 450,000 jobs. As recently as 2003, Defense Secretary Donald Rumsfeld said that as many as 320,000 jobs filled by military personnel could be turned over to civilians. By even the narrowest interpretation, the PMC sector dates back at least 15 years, to when the then‐​little‐​known South African firm, Executive Outcomes, started gaining world attention for its operations against Jonas Savimbi’s UNITA in Angola. But there has certainly been a recent expansion.

In the United States one can trace the push for outsourcing of military activities back to the 1966 release of the revised Office of Management and Budget (OMB) Circular A‑76.51 Private contractors were prominent in the “nation‐​building” effort in South Vietnam and grew significantly over the decades that followed.

Certainly, the use of private contractors by the U.S. military has been an increasing trend.

In the United States the PMC industry was fueled by the same zeal for market‐​based approaches that drove the deregulation of the electricity, airline, and telephone‐​service industries. The military was considered to be particularly well‐​suited to public‐​private partnerships, because the need for its services fluctuates so radically and abruptly. In light of such sharp spikes in demand, it was thought, it would be more efficient for the military to call on a group of temporary, highly trained experts in times of war‐​even if that meant paying them a premium‐​rather than to rely on a permanent standing army that drained resources (with pension plans, health insurance, and so forth) in times of peace.

Now it should be noted that the jury is still out, in terms of hard evidence, whether the facts support the ideology.

One article noted:

In the past Blackwater itself, the 800 pound gorilla of private security contractors, acknowledged that the cost‐​benefit claim is still undecided. This was seen in the October 2, 2007, hearing of the U.S. House Oversight and Government Reform Committee at which Erik Prince, the founder and head of Blackwater, testified. Mr. Prince was asked about the cost‐​benefit of using private contractors:

An economic professor wrote that “[e]xcessive use of private contractors erodes checks and balances, and it substitutes market transactions, controlled by the executive branch, for traditional political mechanisms of accountability. When it comes to Iraq, we’ve yet to see the evidence of a large practical gain in return; instead, use of contractors may have helped to make an ill‐​advised venture possible.”

Many academics who examine the issue of the relative cost of private versus public point to the politics behind the various ways one can measure cost. What you include or exclude in your study can be a complicated political exercise. Economists disagree on how to answer this question, at least in part because they use different variables when measuring cost. When you measure the savings of using retired special operations forces personnel, do you factor in the hundreds of thousands of tax dollars used to train these ex‐​soldiers? This is a valid economic variable worth including, but no study yet published seems to have done so. Even more difficult can be attaching a dollar value to in‐​house military ‘services.’ Because military establishments often have a ‘monopoly’ of service delivery and information regarding cost, getting accurate comparative information is not easy.

Privatization has been touted as one way to actually allow a government the ability to see cost comparisons between, say, what the army will charge and what a private provider would charge. It is not a bad idea, but problems arise when cost reductions are assumed, or when statistics measuring savings from outsourcing are based on hypothetical projections.

Furthermore, ‘cost’ is not the only way to measure value. Logistics officers often talk about value in terms of cost/​speed of delivery/​quality of service. If you need it tomorrow in a war zone, you can’t expect Federal Express to get it there for you. That affects quality and price. The private and public sectors might‐​and do‐​behave differently because of inherent differences between these two sectors.

What little cost‐​benefit analysis there has been to date has focused on narrow economic cost comparisons and has generally avoided addressing equally important political factors, such as avoiding tough political choices concerning military needs, reserve call‐​ups, and the human consequences of war.

Nevertheless, the fact that outsourcing of military functions from the public to the private sector has not been proven to be more cost effective has not stopped people from claiming that it is so. Typical of this is the statement by Doug Brooks, president of the International Peace Operations Association, that “[c]ontractors are cost effective. Although the popular perception is of huge salaries for cushy jobs, the reality is that contractors live along side military personnel and generally cost the government far less in the long run.”

In truth recent events in Iraq are far from the first time the U.S. government has turned to the private sector for help. Before the 1990s privatization push, private firms had periodically been used in lieu of U.S. forces to enforce covert military policies outside the view of Congress and the public. Examples range from Civil Air Transport and Air America, the CIA’s secret paramilitary air arm from 1946 through 1976‐​prominently used during the Vietnam War‐​to the use of Southern Air Transport to run guns to Nicaragua in the Iran‐​Contra scandal.

Historically speaking, in fact, the story goes back even farther. Privateers, or private ships licensed to carry out warfare, helped win the American Revolution and the War of 1812. In World War II, the Flying Tigers, American fighter pilots hired by the government of Chiang Kai‐​shek, helped defeat the Japanese.

The only point I try to make with these figures is that the use of civilians in American military operations goes back to the founding of the country. Beyond that, any comparisons are problematic because of differences caused by the changes in military control.

For example, none of the eras cited used volunteer armies. Civilian workers in the Revolutionary War were sutlers. These were merchants traveling behind the columns who each night would sell the troops extra items not supplied by the military (jam for the hardtack, liquor, better shoes, and so on). They were not part of the war effort in the way we talk about today, and they certainly did not provide a personal security detail for General George Washington.

Thus we can say that private military industry is neither as new nor as big as is frequently claimed. Also, it is evident that civilians have always been instrumental to military operations and have often been in harm’s way in support of the military.

So what is new? Specifically, the past two to three decades have seen increased prominence given to the reemergence of an old phenomenon: the existence of organizations working solely for profit. The modern twist, however, is that rather than being ragtag bands of adventurers, paramilitary forces, or individuals recruited clandestinely by governments to work in specific covert operations, the modern firm is solidly corporate. Instead of organizing clandestinely, such firms now operate out of office suites, have public affairs staffs and Web sites, and offer marketing literature.

But although they like to call themselves private security firms, such organizations are clearly quite different from the traditional private security industry that provides watchmen and building security.

Some questions, despite being increasingly asked over the past few years, are still unanswered: How many private security firms work in Iraq? How many contractors do they employ? How many contractors have been wounded or killed? What cost is incurred in such operations?

For the first three years of Operation Iraqi Freedom, the U.S. government had no accurate count of its contractors. As recently as December 2006, the Iraq Study Group estimated that only 5,000 civilian contractors worked in Iraq. The same month, however, Central Command issued the results of its own internal review: about 100,000 government contractors, not counting subcontractors, were operating in Iraq. Then, in February 2007, the Associated Press reported 120,000 contractors working in Iraq.

A Government Accountability Office report released in July 2005 noted that neither the Department of State, the Department of Defense, nor the U.S. Agency for International Development has complete data available on the costs of using PSCs.

In December 2006 the Washington Post reported that about 100,000 government contractors were operating in Iraq, not counting subcontractors‑a total approaching the size of the U.S. military force there. That finding, which includes Americans, Iraqis, and third‐​party nationals hired by companies operating under U.S. government contracts, was significantly higher and wider in scope than the Pentagon’s only previous estimate, which claimed that 25,000 security contractors were in the country. It is also 10 times the estimated number of contractors that were deployed during the Persian Gulf War in 1991.

Reporting a major milestone, the Los Angeles Times wrote in July 2007 that the number of U.S.-paid private contractors in Iraq exceeded that of American combat troops. More than 180,000 civilians, including Americans, foreigners, and Iraqis, were working in Iraq under U.S. contracts, according to State and Defense Department figures. The numbers include at least 21,000 Americans, 43,000 foreign contractors, and about 118,000 Iraqis. That number, by the way, is still bigger than U.S. military forces, even after the United States increased the number of forces during its 2007 “surge.” Furthermore, private security contractors were not fully counted in the survey‐​so the total contractor number was even larger.

The truth is, for most of the time since the United States went to war in both Afghanistan and Iraq, the Pentagon simply didn’t know how many contractors worked in the U.S. Central Command’s area of responsibility, which includes both countries.

Some questions, despite being increasingly asked over the past few years, are still unanswered: How many private security firms work in Iraq? How many contractors do they employ? How many contractors have been wounded or killed? What cost is incurred in such operations?

We may be getting closer to answers though. For example, back in February 2007, a relatively unknown senator named Barack Obama introduced the Transparency and Accountability in Military and Security Contracting Act, which required federal agencies to report to Congress numbers of security contractors, types of military and security equipment used, numbers of contractors killed and wounded, and disciplinary actions taken against contractors.

What kind of casualties do contractors suffer? In February 2006 it was reported that 505 civilian contractors had died in Iraq since the beginning of the war. Another 4,744 contractors have been injured, according to insurance claims on file at the U.S. Department of Labor.

As of December 2006, at least 770 contractors had been killed in Iraq and at least 7,700 wounded. According to U.S. Labor Department statistics, the first three months of 2007 brought the highest number of contract worker deaths for any quarter since the beginning of the Iraq war. At least 146 contract workers were killed, topping the previous quarterly record of 112 killed at the end of 2004. From August 2004 to the beginning of June 2007, 138 private security workers were killed, and 451 were wounded.

In May 2007 the New York Times reported the total number of contractors killed in Iraq to be at least 917, along with more than 12,000 wounded in battle or injured on the job. Those statistics suggested that for every four American soldiers who die in Iraq, a contractor is killed.

By the end of June 2007, the number of contractors killed in Iraq reached 1,001. But these numbers were likely understated, for the data only showed the number of cases reported to the Labor Department, not the total number of injuries or deaths that occurred. The Department broke down 776 contractor deaths by company, leaving out almost a fourth for unspecified reasons, and did not include all companies whose employees or contractors have died in the war.

A report by the U.S. Government Accounting Office in April 2005 found that monitoring of civilian contractors in Iraq was so poor that there was no way to determine how many contractors are working on U.S.-related security and reconstruction projects in Iraq or how many had been killed.

At the end of January 2005, a quarterly report sent to Congress by the inspector general appointed to audit U.S.-funded work in Iraq found that at least 232 civilians had been killed while working on U.S.-funded contracts in Iraq, and the death toll was rising rapidly. It cited U.S. Labor Department statistics showing that companies had filed 232 compensation claims under the Defense Base Act for workers killed there, an increase of 93 percent in the fourth quarter of 2004.

In this sense outsourcing is advantageous for the administration. For example, it allows the administration to push costs that would otherwise be incurred by Veterans Affairs not just off the books but out of government altogether, at least for now. Although those costs may be hidden in the short term and deferred in the middle term, they will have to be borne eventually. But instead of being addressed in a comprehensive, cost‐​effective way, the problems will be diffused and the burdens carried by individual families and communities. Think of the long‐​term social costs associated with the veterans returning from Vietnam, but without the government and social service available to veterans. Those services have rarely been as generous as Vietnam veterans deserve, but at least we had a framework and means for providing such services.

Some say that contractors, motivated perhaps by profit, deserve less than the troops. But had it not been for contractors, we would have needed more troops. So we would have had to pay the price one way or the other. However, part of the reason for using contract workers in Iraq was to avoid the political ramifications of calling up and paying for the number of troops that were actually needed.

At most, contractors who are killed get an obituary buried in the back pages of their hometown newspaper, based on a press release by their employer, or perhaps a brief mention by a government spokesman if the contractor’s client was a U.S. government agency.

Numbers like these tend to confirm the view long held by many observers of the industry that one reason government likes to turn to contractors is that it lowers their political costs. Bluntly put: if you are not on active duty in the U.S. military‐​even if you were for 10 to 20 years previously‐​and even if you are contributing to the war effort, nobody beyond your immediately family cares if you get killed.

Who works for these firms? PMCs are employing personnel from numerous countries around the world, not only the United States. Contractors come from Bosnia, Britain, Nepal, Chile, Ukraine, Israel, South Africa, New Zealand, Australia, and Fiji, not to mention those who served in the French Foreign Legion, to name just some countries. It is globalization in action. Though they are doing a wide variety of tasks in Iraq, the common link is helping, in one way or another, to provide security. Personnel from one country who are recruited by a company in another country to work in yet another country are called third‐​country nationals (TCNs). The Pentagon says that 30 percent of contract personnel in Iraq are so‐​called TCNs.

Let’s turn to oversight for a moment. It is simply inarguable that proper monitoring of contracts was woefully deficient in the first few years of the U.S. occupation of Iraq. And it still leaves much to be desired. A Government Accountability Office report released in March 2008 said that the Pentagon relies too much on contractors who often work alongside their government counterparts, cost more, and sometimes take on responsibilities they are not supposed to. The report said that as the government’s workforce has shrunk, its demand for services has mushroomed and procurement deals have become more complex and hard to manage. That has forced agencies to hire more contractors. In 2007 the Defense Department spent $158.3 billion on services, a 76 percent increase over the past decade and more than what it spends on supplies, equipment, and major weapons systems.

The GAO looked at the Army Contracting Agency’s Contracting Center of Excellence (CCE), which does procurement for 125 divisions at the Pentagon. It found that 42 percent of the Army’s CCE procurement specialists are contractors, up from 24 percent in fiscal 2005. The report said that relying so much on contractors creates “the risk of loss of government control over and accountability” for government programs.

Some companies early on argued that greater care should be taken in vetting the qualifications of their employees. Back in September 2004, ArmorGroup, the London‐​based company, published a white paper arguing that companies offering armed guards abroad should be vetted under the 2001 Private Security Industry Act. At that time only companies offering services within the United Kingdom were covered by the law.

Christopher Beese, director of ArmorGroup International, said, “It seems extraordinary that the doorman for a nightclub, catering for a particular clientele in a particular part of town may have to be vetted and licensed, when the same man can be equipped with a rifle and an armoured vehicle and be engaged to protect diamond concessions for a foreign regime in clear breach of public interest and perhaps even in contravention of human rights, but needs no such regulation.”

About six months later a spokesman for ArmorGroup said: “We are demanding regulation. It is extraordinary that door supervisors have to be licensed but any Joe Public can get a Kalashnikov and work with a security company abroad. This is an issue of accountability, as these companies can be set up so quickly.”

Of course, what constitutes proper vetting is debatable. In March 2006, five years after Mr. Beese’s statement, British Foreign Secretary Jack Straw said that armed U.K. security guards working in Iraq could be checked by the Security Industry Authority, the same body that vets British pub bouncers.

ArmorGroup was hardly the only company concerned about weeding out gunslingers. At a conference at Oxford University in December 2004, Colonel Tim Spicer, chairman of Aegis Defence, and Harry Legge‐​Bourke, who runs Olive Security, argued that the security industry should be tightly regulated and new restrictions placed on their operations.

Of course, the big companies also had a self‐​interested motive in doing this, namely, eliminating the competition. The smaller security companies took away huge chunks of the pie. When an industry becomes highly regulated, it drives the smaller firms out because of administrative and compliance costs.

The need for better supervision of contractors has been apparent for years. It is not just a matter of law. There are, actually, quite a few laws and regulations governing the use of contractors. The problem is that there are not enough auditors to monitor contracts.

For example, back in late 2004 the Defense Contract Management Agency went on a hiring spree. It needed 200 civilian employees experienced in overseeing contracts and producing items needed by the military services. The agency wanted people experienced in contract management so they could be deployed to various hot spots, including Iraq, 90 days after they were hired.

Although there were not many contractors involved in Abu Ghraib I devoted a chapter to it just because it was so notorious.

What does Abu Ghraib tell us about control over and accountability of PMCs? Though much of the most relevant material is still classified, the bulk of the evidence to date suggests that most of the abuses were carried out by regular military forces. Though several PMC contractors seem guilty of criminal behavior and merit prosecution, it does not appear that the use of translators and interrogators from private firms like Titan and CACI were part of any effort to deliberately avoid oversight. If anything, such efforts came from government agencies like the CIA, which requested the Army to keep certain prisoners off the books, that is, the so‐​called ghost detainees.

Abu Ghraib, like the overall slipshod, ill‐​planned way the United States prepared for post‐​major combat operations, is a reflection of broader policy failings. In short, the Bush administration has tried to fight a war and build a nation on the cheap. It failed to commit the necessary number of trained and qualified personnel and failed to supply the necessary resources required for an occupation force under international law. In such a scenario, failure and criminal behavior by both private and public actors were virtually inevitable.

The CIA and civilian leadership higher up the chain of command in the U.S. Department of Defense (DoD) created and encouraged the culture in which such offenses occurred. In short, Iraq has shown that higher standards of accountability are required in both the public and private sector.

In addition, while Abu Ghraib has shown that certain tasks, such as prisoner interrogation, are too sensitive to be outsourced to the private sector without proper government oversight (because of the potential for human rights violations), it is a sad, current reality that the U.S. military plans to continue using PMC personnel for that task because it lacks sufficient qualified personnel of its own.

In the past some of the primary U.S. laws used to regulate contractors were inadequate. For example, the Arms Export Control Act (AECA) is a key statute in this area, although it is better known for regulating arms sales. The act gives the president full authority to promulgate regulations for this purpose and to designate items as defense articles and defense services by placing them on the United States Munitions List. Any person or organization that manufactures, exports, or imports the goods or services on the list must register with the U.S. government and receive a license for each contract. Criminal penalties can result from a failure to register properly.

But the AECA fails to effectively regulate PMC activities for three basic reasons.

First, it does not provide a mechanism to force presidential compliance. Second, the AECA’s reporting requirements provide inadequate information for Congress to assess private military service contracts. However, if legislation passed in 2007 makes it into law that may begin to change. Finally, the AECA provides only limited public information regarding unclassified contracts that may commit the nation to acts of war.

Because the AECA was drafted primarily to regulate one‐​time arms sales contracts, it does not provide adequate mechanisms for ongoing review of a service contract that may last for months or years.

Moreover, the regulations under the AECA provide no ongoing oversight after an export license has been granted. This lack of public information makes it virtually impossible for the public to assess the practice of private military contracting. Such lack of public accountability would be less bothersome if the regulatory

framework guaranteed adequate executive supervision and congressional oversight. But the level of review and inquiry that either branch gives to licensing decisions under the AECA is unclear.

The scarce public information that is available suggests that the current regulatory scheme, while constitutional, does not provide the same safeguards of ongoing executive review, in‐​depth congressional oversight, and public accountability that are applied to ventures undertaken by the U.S. military. Yet many of the same dangers to American interests are involved when private contractors do the work. The lack of public accountability is perhaps the most important issue because without it there is no way for voters to evaluate the adequacy of congressional enforcement provisions or oversight.

It is extremely difficult to generalize about private military and security firms. As an industry, or at least, business sector, PMCs have been around for less than 20 years. And although they have attracted growing attention from analysts, scholars, governments, and the general public in the past decade, there are still no agreements on how to define them, let alone categorize them.

Much of the public image of PMCs is based on perceptions that are woefully out of date, such as the activities of now‐​defunct groups like Executive Outcomes and Sandline. Specifically, many people still think that companies undertake direct offensive combat operations such as Executive Outcomes did in Angola and Sierra Leone, which is simply not the case. They also think that the various PMCs operating in Iraq constitute a cohesive army, second only in size to the American forces there.

What is worth remembering about PMCs in Iraq is that most of what you think you know is wrong. The private security sector there is very diverse. Yes, there are thousands of Westerners carrying arms, but there are also more host nationals, such as Iraqis and third‐​country nationals, doing the same. Some PMCs are more low key than others in using force, but, in general, they are more disciplined and experienced than their active‐​duty counterparts. And their function varies depending on what the contract calls for. While the common theme for a security contractor is providing security and protection, it can take many different forms, ranging from static security for buildings and infrastructure to security details for officials and reconstruction workers.

The role and impact of private actors in providing security vary significantly according to context. Obviously, in the case of Iraq, the provision of personal security, primarily for people doing reconstruction work but also for protecting infrastructure, has been the top priority, especially given the dangers caused by the insurgency. This has put groups like DynCorp, Triple Canopy, Erinys, Hart Group, Control Risks, ArmorGroup, and Aegis Defence squarely in the public eye.

Though it is not popular to acknowledge it, accountability of and control over private military and security companies have, at least in a few countries, actually been a pressing concern for several years. In South Africa attempts to regulate have been largely legislative. The problem with South African legislation is that the government views PMC activity with suspicion. Since many South Africans working in this sector had their formative military experience in the apartheid era, the government often views them as potential troublemakers, both in other countries and at home.

The United States, in sharp contrast, increasingly views PMCs as part of the total force. Just like the old American Express credit card ad, nowadays the U.S. military can’t leave home without them. Its concerns, bolstered by its experience in Iraq to date, tend to be administrative: how to ensure coordination between theater commanders and PMCs, how to prosecute PMC personnel if they commit a crime, how to ensure common standards for issuing and implementing contracts.

Given this, what might be done to improve the situation? The following suggestions merit consideration.

1. Establish an Army‐​controlled Force Protection Command (FPC) for PSCs.

The U.S. Multi‐​National Force‐​Iraq (MNF‑I) should consolidate PSCs into a unified DoD‐​backed organization: security companies could be placed directly under the command of a field‐​grade officer assigned to MNF‑I, with appropriate liaison staff big enough to support the needs and operations of all PSCs. This provisional FPC would be assigned the job of organizing, supporting, and regulating all PSC personnel in Iraq and making them accountable under a commissioned military commander.

2. Standardize the entire FPC force. The FPC could transform the PSC world in Iraq into a unified entity instead of dozens of individual companies guarding their own interests and those of their clients. In fact, in Iraq, the principal client is the U.S. government. All security contracts would be managed and contracted by MNF‑I, including those of the State Department. Having these contract forces, MNF‑I would oversee and be responsible

for the protection of all U.S. activities in Iraq. Only companies willing to put their men under the FPC chain of command and meet the Army’s standards would be awarded contracts.

3. Dispel the mercenary myth. As long as PSCs operate as commercial entities for commercial reasons of the owners, they will be viewed as mercenaries‐​mistrusted by U.S. forces and vilified in the press. A strict military command watching over, directing, and integrated with them will help dispel that myth.

4. End the mass contracting of third‐​country nationals (TCNs). Over time most detractors came to regard PSCs as mercenaries, especially those bringing in large numbers of third‐​country nationals. TCNs were brought in largely because they would work for low wages and were ethnically distinct from the Iraqis. With the exception of a few companies that have used ex‐​British army Gurkhas and United Nations‐​trained Fijians for years, the recent trend is to strip third world armies of full battalions in order to be the lowest bidder. It lends a bit of truth to accusations that MNF‑I is paying foreign mercenaries.

5. Implement strict accountability. The immunity granted to PSCs by Ambassador Bremer’s CPA Order 17 should be revoked completely. It should not be expected or welcomed by the private security community. To be able to act with complete impunity encourages rogue individuals and unscrupulous entities to enter Iraq with the intent to “get some and get paid” rather than perform the mission professionally. There have been no prosecutions to date of PSCs involved in questionable shootings or even outright murder. A “What happens in Baghdad, stays in Baghdad” mentality blurs the line between the rogues and the professionals.

Finally, Make PSCs an integral part of the strategy, legally. Congress needs to introduce legislation that would essentially force professionalism and transparency on PSCs. This legislation would also place them in a legally binding framework and protect them under the Geneva Conventions. It should also serve as a reminder that they are being paid to represent the interests of the ultimate paying client, the American people. Of course, amending international law is not done easily, so the sooner this is started the better.