America's Mercenary Army

When years from now historians and government officials reexamine precedents set by the U.S. experience in Iraq, many "firsts" are likely to pop up.

One still playing out is the extraordinarily wide use of private contractors. A Congressional Research Service report published last month titled "Private Security Contractors in Iraq: Background, Legal Status, and Other Issues," puts it this way: "Iraq appears to be the first case where the U.S. government has used private contractors extensively for protecting persons and property in potentially hostile or hostile situations where host country security forces are absent or deficient."

Only estimates are available for the total employment by contractors in Iraq that perform "functions once carried by the U.S. military," according to the study. Testimony at an April 2007 congressional hearing gave the impressive figure of 127,000 as the number working in Iraq under Defense Department contracts. Breakdowns don't exist, but one Pentagon official said less than 20 percent were American.

[...]

But the expanded contractor use has evoked new attention to a 1995 criticism of the practice. According to the study, a Defense Department Commission on Roles and Missions found then that depending on contractors was detrimental and that it kept the Pentagon "from building and maintaining capacity needed for strategic or other important missions."

An advertisement last week on IntelligenceCareers.com illustrates part of the problem. It seeks an "Intelligence Analyst" to work in Iraq for a Dayton, Ohio-based outfit called MacAulay-Brown, or MacB, which in turn is a subcontractor to the giant Lockheed Martin information technology group. The client is Counterintelligence Field Activity, the Defense Department's newest intelligence arm, which is responsible for coordinating force protection for the military services inside the United States and abroad.

[...]