This week in the Special Outside the Box, good friend George Friedman addresses the lax governance and control of Blackwater, a private security firm recently embroiled in the accusation of firing upon Iraqi civilians without provocation. George shows us that private security contractors' working beside the military is not a recent mode of operation but rather one that has long been employed by the US military.
Furthermore, that private security firms serve a necessary role in US military operations and will continue to be a tool utilized in military operations throughout the world. Elsewhere, Stratfor notes that it is the Diplomatic Security Service that is usually responsible for the protection of diplomats. But there are only 1,400 of the officers world wide. You need more than that just for Iraq. We simply do not have the manpower to protect all the diplomats in Iraq and elsewhere without private contractors. It is just a fact of life. But as George notes, they are not in the chain of command. Resolving this is very important, as you will read.
Stratfor continues to provide insightful and pertinent research on economic and geopolitical events and their respective ramifications. I depend on Stratfor to keep me abreast of such events and strongly recommend it to all wanting knowledgeable, reputable, analytical commentary discerning through the complexity of world affairs. Strafor continues to generously provide significant savings to readers of Outside the Box, for further information please click here.
John Mauldin, Editor
Outside the Box
The Geopolitical Foundations of Blackwater
For the past three weeks, Blackwater, a private security firm under contract to the U.S. State Department, has been under intense scrutiny over its operations in Iraq. The Blackwater controversy has highlighted the use of civilians for what appears to be combat or near-combat missions in Iraq. Moreover, it has raised two important questions: Who controls these private forces and to whom are they accountable?
The issue is neither unique to Blackwater nor to matters of combat. There have long been questions about the role of Halliburton and its former subsidiary, KBR, in providing support services to the military. The Iraq war has been fought with fewer active-duty troops than might have been expected, and a larger number of contractors relative to the number of troops. But how was the decision made in the first place to use U.S. nongovernmental personnel in a war zone? More important, how has that decision been implemented?
The United States has a long tradition of using private contractors in times of war. For example, it augmented its naval power in the early 19th century by contracting with privateers -- nongovernmental ships -- to carry out missions at sea. During the battle for Wake Island in 1941, U.S. contractors building an airstrip there were trapped by the Japanese fleet, and many fought alongside Marines and naval personnel. During the Civil War, civilians who accompanied the Union and Confederate armies carried out many of the supply functions. So, on one level, there is absolutely nothing new here. This has always been how the United States fights war.
Nevertheless, since before the fall of the Soviet Union, a systematic shift has been taking place in the way the U.S. force structure is designed. This shift, which is rooted both in military policy and in the geopolitical perception that future wars will be fought on a number of levels, made private security contractors such as KBR and Blackwater inevitable. The current situation is the result of three unique processes: the introduction of the professional volunteer military, the change in force structure after the Cold War, and finally the rethinking and redefinition of the term "noncombatant" following the decision to include women in the military, but bar them from direct combat roles.
The introduction of the professional volunteer military caused a rethinking of the role of the soldier, sailor, airman or Marine in the armed forces. Volunteers were part of the military because they chose to be. Unlike draftees, they had other options. During World War II and the first half of the Cold War, the military was built around draftees who were going to serve their required hitch and return to civilian life. Although many were not highly trained, they were quite suited for support roles, from KP to policing the grounds. After all, they already were on the payroll, and new hires were always possible.
The second impetus was the end of the Cold War and a review carried out by then-Secretary of Defense Les Aspin under then-President Bill Clinton. The core argument was that it was irrational to maintain a standing military as large as had existed during the Cold War. Aspin argued for a more intensely technological military, one that would be less dependent on ground troops. The Air Force was key to this, while the Navy was downsized. The main consideration, however, was the structure of the standing Army -- especially when large-scale, high-intensity, long-term warfare no longer seemed a likely scenario.
The U.S. Army's active-duty component, in particular, was reduced. It was assumed that in time of war, components of the Reserves and National Guard would be mobilized, not so much to augment the standing military, but to carry out a range of specialized roles. For example, Civil Affairs, which has proven to be a critical specialization in Iraq and Afghanistan, was made a primary responsibility of the Reserves and National Guard, as were many engineering, military-intelligence and other specializations.
This plan was built around certain geopolitical assumptions. The first was that the United States would not be fighting peer powers. The second was that it had learned from Vietnam not to get involved in open-ended counterinsurgency operations, but to focus, as it did in Kuwait, on missions that were clearly defined and executable with a main force. The last was that wars would be short, use relatively few troops and be carried out in conjunction with allies. From this it followed that regular forces, augmented by Reserve/National Guard specialists called up for short terms, could carry out national strategic requirements.
The third impetus was the struggle to define military combat and noncombat roles. Given the nature of the volunteer force, women were badly needed, yet they were included in the armed forces under the assumption that they could carry out any function apart from direct combat assignments. This caused a forced -- and strained -- redefinition of these two roles. Intelligence officers called to interrogate a prisoner on the battlefield were thought not to be in a combat position. The same bomb, mortar or rocket fire that killed a soldier might hit them too, but since they technically were not charged with shooting back, they were not combat arms. Ironically, in Iraq, one of the most dangerous tasks is traveling on the roads, though moving supplies is not considered a combat mission.
Under the privatization concept, civilians could be hired to carry out noncombat functions. Under the redefinition of noncombat, the area open to contractors covered a lot of territory. Moreover, under the redefinition of the military in the 1990s, the size and structure of the Army in particular was changed so dramatically that it could not carry out most of its functions without the Reserve/Guard component -- and even with that component, the Army was not large enough. Contractors were needed.
Let us now add a fourth push: the CIA. During Vietnam, and again in Afghanistan and Iraq, a good part of the war was prosecuted by CIA personnel not in uniform and not answerable to the military chain of command. There are arguments on both sides for this, but the fact is that U.S. wars -- particularly highly politicized wars such as counterinsurgencies -- are fought with parallel armies, some reporting to the Defense Department, others to the CIA and other intelligence agencies. The battlefield is, if not flooded, at least full of civilians operating outside of the chain of command, and these civilian government employees are encouraged to hire Iraqi or other nationals, as well as to augment their own capabilities with private U.S. contractors.
Blackwater works for the State Department in a capacity defined as noncombat, protecting diplomats and other high-value personnel from assassination. The Army, bogged down in its own operations, lacks the manpower to perform this obviously valuable work. That means that Blackwater and other contract workers are charged with carrying weapons and moving around the battlefield, which is everywhere. They are heavily armed private soldiers carrying out missions that are combat in all but name -- and they are completely outside of the chain of command.
Moreover, in order to be effective, they have to engage in protective intelligence, looking for surveillance by enemy combatants and trying to foresee potential threats. We suspect the CIA could be helpful in this regard, but it would want information in return. In order to perform its job, then, Blackwater entered the economy of intelligence -- information as a commodity to be exchanged. It had to gather some intelligence in order to trade some. As a result, the distinction between combat and support completely broke down.
The important point is that the U.S. military went to war with the Army the country gave it. We recall no great objections to the downsizing of the military in the 1990s, and no criticisms of the concepts that lay behind the new force structure. The volunteer force, downsized because long-term conflicts were not going to occur, supported by the Reserve/Guard and backfilled by civilian contractors, was not a controversial issue. Only tiresome cranks made waves, challenging the idea that wars would be sparse and short. They objected to the redefinition of noncombat roles and said the downsized force would be insufficient for the 21st century.
Blackwater, KBR and all the rest are the direct result of the faulty geopolitical assumptions and the force structure decisions that followed. The primary responsibility rests with the American public, which made best-case assumptions in a worst-case world. Even without Iraq, civilian contractors would have proliferated on the battlefield. With Iraq, they became an enormous force. Perhaps the single greatest strategic error of the Bush administration was not fundamentally re-examining the assumptions about the U.S. Army on Sept. 12, 2001. Clearly Donald Rumsfeld was of the view that the Army was the problem, not the solution. He was not going to push for a larger force and, therefore, as the war expanded, for fewer civilian contractors.
The central problem regarding private security contractors on the battlefield is that their place in the chain of command is not defined. They report to the State Department, not to the Army and Marines that own the battlefield. But who do they take orders from and who defines their mission? Do they operate under the Uniform Code of Military Justice or under some other rule? They are warriors -- it is foolish to think otherwise -- but they do not wear the uniform. The problem with Blackwater stems from having multiple forces fighting for the same side on the same battlefield, with completely different chains of command. Indeed, it is not clear the extent to which the State Department has created a command structure for its contractors, whether it is capable of doing so, or whether the contractors have created their own chain of command.
Blackwater is the logical outcome of a set of erroneous geopolitical conclusions that predate these wars by more than a decade. The United States will be fighting multidivisional, open-ended wars in multiple theaters, and there will be counterinsurgencies. The force created in the 1990s is insufficient, and thus the definition of noncombat specialty has become meaningless. The Reserve/Guard component cannot fill the gap created by strategic errors. The hiring of contractors makes sense and has precedence. But the use of CIA personnel outside the military chain of command creates enough stress. To have private contractors reporting outside the chain of command to government entities not able to command them is the real problem.
A failure that is rooted in the national consensus of the 1990s was compounded by the Bush administration's failure to reshape the military for the realities of the wars it wished to fight. But the final failure was to follow the logic of the civilian contractors through to its end, but not include them in the unified chain of command. In war, the key question must be this: Who gives orders and who takes them? The battlefield is dangerous enough without that question left hanging.