Topic: Foreign Policy and National Security

Was the Iraq War Worth It?

That’s the question posed by US News and World Report’s “Debate Club” today.

Here’s the opening to my response.

Tragically, the Iraq War was not worth the costs. The leading advocates for war understated the costs and exaggerated the benefits. They claimed that the war would be cheap, perhaps even profitable, thanks to lower oil prices. They suggested that it would be easy, a “cakewalk,” not requiring a long-term U.S presence to stabilize the country after Saddam Hussein’s ouster. They blithely dismissed concerns about the tensions between Arabs and Kurds, and between Sunnis and Shiites.

We now know how wrong they were. A new report from the Watson Institute for International Studies at BrownUniversity tallies up the costs: nearly 4,500 U.S. troop fatalities, more than $1.7 trillion spent, and another $490 billion owed. Estimates of the number of Iraqis killed in the sectarian bloodletting that occurred after the collapse of Saddam’s regime exceed 130,000. Millions were displaced, many still have not returned to their homes. The Iraqi Christian community has been decimated.

You can read the rest here and vote for the best argument.

Who Failed to Stop the Iraq War?

With thanks to Mark Thompson at Time’s Battleland for calling this to my attention, the discussion yesterday on CNN’s “Reliable Sources” concerning the decision to invade Iraq was more interesting than the others that I’ve seen or read. 

Host Howard Kurtz noted that editors at the New York Times had admitted to having “printed too many credulous claims about Saddam and Iraq.” Kurtz explained that Len Downie, then the editor of the Washington Post, had admitted “he had made a mistake of not putting more skeptical stories on the front page. Even the people who ran the news organizations seem to acknowledge that they had fallen short.” Given all this, Kurtz asked the panelists, “Didn’t most of the media…get rolled by the Bush administration during this run-up to war?”

The panel, which included Thompson, and Fred Francis, formerly with NBC, explained why the press got the story wrong: Saddam fooled a lot of people, including his own people and his neighbors. He fooled many people in the U.S. government, too.

But the Washington Post’s Rajiv Chandrasekaran properly looked past the distractions of phony Iraqi connections to 9/11 and Iraq’s nonexistent nuclear weapons. Chandrasekaran agreed with Kurtz that “there was far more that we all could have done. You could go to Iraq. I was in Iraq for the bulk of the six months leading up to the war. What you couldn’t really do is get an independent assessment of what Saddam really had.”

But, he continued:

it wasn’t just the issue of weapons of mass destruction. It was the broader questions. What is the political transition plan? Truth squadding the White House’s claims that Iraq could pay for it, the reconstruction of its country, the questions of the long simmering tensions between the principal religious and ethnic groups in the country. These were questions that were all easily reportable. They should have had more coverage. We didn’t do enough in really aggressively looking at all of that.

Chandrasekaran (who will be speaking at Cato in a few weeks) is right. The greatest argument against launching a war to overthrow Saddam Hussein was what would come after him. The advocates for the war hyped the threat of Saddam’s weapons, and what he would do with them, to build a case for the benefits that would obtain from the war. We now know that they exaggerated these benefits because Saddam didn’t have nuclear weapons. But the claim that Saddam would use the weapons, or give them to terrorists, was also dubious, and was noted as such at the time (and well before) by some of the leading opponents of the war.

But the war hawks also downplayed the costs of invading Iraq by claiming that there would be no need for a long-term U.S. troop presence, and certainly not as large as Army leaders had estimated. They dismissed the overwhelming evidence that Iraq was beset by ethnic and sectarian divisions. Bill Kristol famously dismissed the notion that “somehow the Shia can’t get along with the Sunni” as so much “pop sociology.” I suspect that they were aware of these divisions, because it would have been far harder to convince the American people to support a conflict if they knew that it was going to be long and costly, instead of the “cakewalk” that the war’s supporters claimed.

I cannot prove the war hawks knew the truth about Iraq and concealed it. I’m certain that they should have known. But they weren’t trying to stop a war; they were trying to start one.

And that is why those who should have known better and did not speak up, or who lent their credibility as experts to the side making the case for war, deserve special scorn on the 10-year anniversary of the start of the Iraq war. They failed to stop the war. The news media’s coverage was inadequate and lazy. In retrospect they should have paid more attention to the vocal few who raised serious objections. But reporters cannot be blamed for not finding experts who did not speak publicly. Or at all.

That is where Colin Powell comes in. He is likely to be remembered for his crucial role in making the case for war at the United Nations on February 5, 2003. But Powell should also be remembered for his words of caution six months earlier, in August 2002.

It is known today as the Pottery Barn principle–“If you break it, you own it.” But what Powell actually said reflects a deep appreciation for the folly of regime change and preventive war: “You are going to be the proud owner of twenty-five million people,” Powell warned the president. “You will own all their hopes, aspirations, problems… . It’s going to suck the oxygen out of everything.”

We know about this exchange from Bob Woodward, and Powell was probably the veteran reporter’s source, so the words could be dismissed as self-serving, or simply invented after the fact. But they shouldn’t be. Because what Powell allegedly said to Bush then could just as easily have been said by Condoleezza Rice in 2007 with respect to war with Iran, or by Hillary Clinton in 2011 regarding Bashar al-Assad in Syria, or by John Kerry in response to North Korea’s latest antics today. And even if Powell never said them, the sentiment is spot on. I only wish he had said them in public.

Whenever reporters, scholars, academics–or anyone in the public at large, for that matter–hears someone making the case for preventive war, the Pottery Barn principle, Powell’s unspoken warning from a war that never should have happened, should be burned in their brain. I think that it is. And that explains why Bill Kristol’s modern-day Project for a New American Century has proved far less effective than its predecessor.

I sincerely wish that we didn’t have to suffer the loss of blood and treasure, the thousands of American dead, and tens of thousands wounded, to learn these lessons. But I especially hope that we’re not already forgetting them.

Making Sense of Drug Violence in Mexico with Big Data, New Media, and Technology

Yesterday we hosted a very interesting event with Google Ideas about the use of new media and technology information in Mexico’s war on drugs. You can watch the whole thing in the video below.

Unfortunately, one of the biggest casualties from the bloodshed that besets Mexico is freedom of the press. Drug cartels have targeted traditional media outlets such as TV stations and newspapers for their coverage of the violence. Mexico is now the most dangerous country to be a journalist. However, a blackout of information about the extent of violence has been avoided because of activity on Facebook pages, blogs, Twitter accounts, and YouTube channels.

Our event highlighted the work of two Mexican researchers on this topic. Andrés Monroy-Hernández from Microsoft Research presented the findings of his paper “The New War Correspondents: The Rise of Civic Media Curation in Urban Warfare” which shows how Twitter has replaced traditional media in several Mexican cities as the primary source of information about drug violence. Also, we had Javier Osorio, a Ph.D. candidate from Notre Dame University, who has built original software that tracks the patterns of drug violence in Mexico using computerized textual annotation and geospatial analysis.

Our third panelist was Karla Zabludovsky, a reporter from the New York Times’ Mexico City Bureau, who talked about the increasing dangers faced by journalists in Mexico and the challenges that new media represent in covering the war on drugs in that country.

Even though Enrique Peña Nieto, Mexico’s new president, has focused the narrative of his presidency on economic reform, the war on drugs continues to wreak havoc in Mexico. Just in the first two months of the year over 2,000 people have been killed by organized crime. 

At the Cato Institute we closely keep track of developments in Mexico and we have published plenty of material on the issue, including:

Watch the full event:

And for those who speak the language of Cervantes, here’s a ten minute interview that Karla Zabludovsky and I did on CNN en Español about the Cato event.

Karzai’s Latest Outrageous Comment

Yesterday, Afghan President Hamid Karzai alleged that the United States and the Taliban are “working in concert to convince Afghans that violence will worsen if most foreign troops leave.” His accusation exposes a strange irony. Karzai not only supports U.S. forces in Afghanistan after 2014, but also disparages that presence to evade his own failings. 

Since 2001, senior U.S. officials have tethered our military might to the sick man of Central Asia. In 2004, President George W. Bush pledged America’s “ironclad commitment” to help Karzai’s country succeed. In 2010, President Obama made clear that the U.S. role in Afghanistan “is a long-term partnership.” 

President Karzai codified those pledges last May by concluding the Enduring Strategic Partnership Agreement between the Islamic Republic of Afghanistan and the United States of America. Despite his history of hindering U.S.-backed anti-corruption investigations, denouncing the international community, and claiming the U.S. ferried Taliban to the north in order to spread violence, he eagerly signed an Agreement that commits the U.S. government to Afghanistan’s future. It provided for the possibility of a U.S. troop presence until 2024, and a long-term framework for training Afghan security forces and targeting al Qaeda. 

Washington’s devotion to nation building still holds fast despite Karzai’s inability to fulfill its lofty expectations. As former U.S. ambassador to Kabul Karl W. Eikenberry bluntly warned his superiors in November 2009, Karzai “is not an adequate strategic partner.” 

Certainly, the United States is not blameless for Afghanistan’s downward spiral—it took responsibility back in 2001 to rebuild the war-ravaged country and then shifted its attention and resources in 2003 to invade and occupy Iraq. Yet, the endemically corrupt Karzai regime and its band of thugs and cronies are also culpable. 

Ample reporting on Afghan corruption need not be repeated here. More to the point, Karzai fails to appreciate the way in which his poor governance vindicates insurgent propaganda and drives many Afghans to fight. A widespread perception of the central government’s massive corruption delegitimizes the state and inspires the sense of injustice that makes the Taliban appear as an effective alternative. Apart from Karzai himself, Afghan police are notorious for perpetrating crimes they are supposed to be stopping, such as corruption, theft, kidnapping, murder, and child abuse. Meanwhile, the Afghan army, long hailed as the mission’s shining success story, is rife with factionalism and patronage networks that could splinter the institution along political and ethnic lines. Foreign policy planners in Washington overlooked the second- and third-order consequences of their attempts to build a strong central government that wields a monopoly on the legitimate use of force. 

As the Democratic majority staff of the Senate Foreign Relations Committee admitted two years ago, “Foreign aid, when misspent, can fuel corruption, distort labor and goods markets, undermine the host government’s ability to exert control over resources, and contribute to insecurity.” (Emphasis mine.] 

Perversely, the corruption of the Afghan central government and the failures of the foreign-led nation-building project feed off one another in disturbing symbiosis. The Washington Post hasreported that foreign military and development spending provide roughly 97 percent of Afghanistan’s gross domestic product, fomenting fears that withdrawal will push the Afghan economy into depression. The alternative to popping that foreign aid bubble, some argue, would be to commit several hundred thousand troops and decades of attention, resources, and patience to transform Afghanistan’s deeply divided society into a stable, non-corrupt, electoral democracy. Of course, such success would hardly be guaranteed and assumes we possess the local knowledge as well as the cultural and religious legitimacy to operate indefinitely in a country notoriously suspicious of outsiders and largely devoid of central authority. 

Over twelve years of nation-building has had little success in creating an economically viable Afghan state, much less a self-sustaining Afghan security force. Indeed, nation building has propped up an erratic and unreliable regime whose behavior feeds the insurgency’s momentum. 

Policymakers must reject the flawed premise on which their policies rest. They must overcome their tendency to overestimate the strategic importance of a small, underdeveloped country to the narrower and more achievable goals of disrupting terrorist networks and preserving U.S. national security.

Rand Paul and Jim Webb on Congress’s Abdication of Foreign Policy Power

John Brennan’s confirmation as CIA director displayed Congress’s disinterest in checking the president’s runaway security powers. Two months ago, when I wrote an article with the unwieldy title, “Will Obama’s Brennan Pick Shed Some Much Needed Light on Drones?” I wouldn’t have guessed that the answer would be yes; it will bestir Congress to finally force the administration to say clearly that it does not reserve the right to kill Americans at home with drone strikes, insofar as they are not engaged in combat. That statement came only thanks to whomever leaked the Justice Department’s summary memo on the topic, Brennan and Attorney General Eric Holder’s impolitic reluctance to articulate limits on the president’s power to kill Americans by calling them terrorists, and, of course, Sen. Rand Paul’s (R-Ky.) resulting filibuster. The Senate predictably left Brennan’s other sins against civil liberties mostly unexamined. 

Paul’s hard-won “toehold of constitutionality” isn’t much to cheer about, even if we add to the spoils the administration’s vague agreement to be more open about its legal rationale for placing people on kill lists. This minimal defense of civil liberties and congressional privilege is what got Republican senators like Marco Rubio of Florida and Ted Cruz, Jr. of Texas, who seem to support unfettered executive discretion to kill in the name of counterterrorism outside the United States, to support the filibuster. 

Even that was too much restraint for the neoconservative right. Sen. John McCain (R-Ariz.) read on the Senate floor a Wall Street Journal editorial calling Paul’s effort a stunt meant to “fire up impressionable libertarian kids” and assuring us that those targeted by drones here or abroad will be “enemy combatants.” McCain and the Journal spectacularly miss Paul’s point: the issue is whether the president should make that designation, chucking due process rights, without being checked by another branch of government. 

As McCain amigo Sen. Lindsay Graham (R-S.C.) noted, the Republican caucus’ flirtation with civil libertarianism seems a situational consequence of partisanship. The same goes for Democrats. Were it President McCain doing what Obama is, far more than two Democratic senators (Jeff Merkley of Oregon and Pat Leahy of Vermont) would have voted against Brennan. During his filibuster, Paul asked what happened to the Senator Obama of 2007, who opposed torture and war by executive fiat. Paul suggests that those views were products of Obama’s then circumstance: not being president. Even that may be too generous. As I wrote in a recent book review concerning Obama’s counterterrorism record, “even when he took office, there was ample evidence that his dovish positions would not outlast their political convenience.” 

We can hope, I suppose, that Paul’s stance will increase Congress’s willingness to assert its constitutional war powers. Although he did not, as far as I know, propose specific restrictions on the use of military force outside of the United States, Paul did complain that the 2001 Authorization of Military Force against the perpetrators of the September 11 attacks and those that harbored them has become a permanent warrant for almost limitless executive war powers, a kind of escape hatch from the Constitution opened by presidential utterance of the word “terrorist.”

Parsing AG Holder on Domestic Targeted Killing

As I wrote on Thursday, I’m not really losing sleep over the prospect of domestic targeted killing, mostly because it seems as though it would be so manifestly politically radioactive even within the intelligence community that I doubt it could be done secretly, and would almost certainly provoke a constitutional crisis if it became public. That said, as Marcy Wheeler notes, if we look closely at the precise wording of Attorney General Eric Holder’s response to Sen. Rand Paul disavowing any such presidential prerogative, it’s actually phrased in a way that seems calculated to preserve a fair amount of wiggle room:

It has come to my attention that you have now asked an additional question. “Does the President have the authority to use a weaponized drone to kill an American not engaged in combat on American soil?” The answer to that question is no.

Now, it’s true that Senator Paul often recurred to the example of a drone “dropping a Hellfire missile on your cafe experience” during his Wednesday filibuster, but it seems weirdly specific to give an answer that is, read strictly, confined to weaponized drones, as opposed to snipers or poison or what have you. More importantly, it’s not entirely clear what Holder considers to be the parameters of “engaged in combat.” During Paul’s filibuster, the senator often agreed that it would clearly be permissible to use defensive lethal force against someone “actively engaged in combat”—shooting down a plane on a heading to crash into a target, or killing a terrorist in the middle of a shooting spree. There’s nothing particularly controversial about those cases: in the latter instance, we’d expect police to do as much without any presidential orders.

But since Holder conspicuously omitted the word “actively,” it isn’t clear that this is what he means. The public hasn’t seen the detailed legal memoranda underlying the CIA’s overseas drone program, and so we can’t really know what to make of Holder’s statement without knowing what the government thinks it means to be “engaged in combat” in this non-traditional conflict. Though the Obama administration has (symbolically) abandoned the use of the phrase “enemy combatant,” the Bush Justice Department argued in 2004 that a “little old lady in Switzerland” who “gave money to a charity for an Afghan orphanage, and the money was passed to al Qaeda” might meet their definition of an “enemy combatant.” Could a citizen suspected of being involved in the planning stages of some future attack, then, be considered to be “engaged in combat” (perhaps even “actively”)?  Against the backdrop of the sort of examples Senator Paul was discussing, it’s presumably not what we’d intuitively think of, but then neither have the targets of our overseas drone attacks necessarily been “combatants” in the colloquial sense of one directly personally engaged in bearing arms. Again, until we see the memos and have a fuller understanding of the administration’s broader reasoning, isolated statements like Holder’s are difficult to interpret with much confidence.

Such definitional game-playing would not exactly be a novelty for this administration, which has apparently expanded the definition of “imminent threat” to cover people believed to be senior leaders of hostile groups, whether or not there is any evidence that they are actively engaged in planning some impending attack. And recall how another recent attorney general, Alberto Gonzales, managed to mislead Congress about President Bush’s warrantless wiretap program by silently redefining “the program the president has acknowledged” to mean “only the specific components he has already acknowledged,” even though these components had never been previously regarded as a separate surveillance program. So if this kind of hyperliteral close parsing of a few sentences seems like paranoid hairsplitting, it’s only because such word games appear to be par for the course when it comes to classified counterterrorism programs.

Do I think this means there’s some domestic assassination plan in the works? Certainly not. But I would not exactly be shocked if the attorney general had used a bit of careful lawyerly language to placate Senator Paul while leaving an opening for a future administration to claim that technically his disavowal of authority had been far narrower than it seemed.

Sequestration Is a Small Victory for Budget Hawks

The budget battles in Washington, D.C., are far from over. President Obama’s attempt to break the stalemate by reaching across the aisle and dining with GOP members two days in a row seems more about show than substance. 

The apparent lack of urgency to undo the cuts underscores what we knew all along: the world did not end under sequestration. Most of the cuts will be phased in over the next few months. The defense cuts amount to just 6.5 percent of total spending on national security (Pentagon base budget plus war costs). This is a pittance, and spending will still dwarf what we spent before 9/11. Those who claim that the cuts will undermine American security should explain how we managed to win the Cold War while spending much less, on average. (To learn more about proposals that would maintain a highly capable, but less costly, military, attend our event on March 14th.) 

There is still the possibility that most of this year’s cuts, or the caps on planned spending over the next decade, may not materialize. Congress could reverse the cuts in the future as part of a grand bargain. Or they could simply punt without one. Meanwhile, legislation is moving along that would allow the Pentagon and other agencies to implement the cuts with greater discretion across department programs. This is a good thing, potentially. Smarter cuts are desirable, but we should be on the lookout to ensure that Congress doesn’t simply legislate away any cuts, dumb or otherwise. 

Nonetheless, the fact that military spending actually declined is a small victory. But how will future battles play out? Are the neocons and their supporters in retreat? In a piece running today at Foreign Policy, I offer a cautionary note. Just because the fiscal hawks won this time doesn’t mean that they’ll win the next one, or the one after that: 

The defense contractors and special interests still have enormous firepower in Washington, and they’ve turned their attention to the “continuing resolution” that will fund the government for the remainder of the year. Meanwhile, the neoconservatives are single-minded and relentless. Their tenacity paid off in their bid to launch a war in Iraq and depose Saddam Hussein, but failed to stop Chuck Hagel’s nomination and eventual confirmation as secretary of defense.

The budget fight matters even more. A $470 billion military is more than sufficient to fight the wars the United States truly needs to fight, but not the wars that the neocons want to fight. The next phase in the fight over the Pentagon’s budget should focus less on how much the United States spends on defense, but rather why it spends so much. If we are going to give our military less than it expected to have three or four years ago, we need to think about asking it to do less.

Read the full article here.