Stumbling Towards Bush 4.0 Territory

Looking back, president Bush went through three distinct iterations during his two terms in the White House.

Bush 1.0 (1998-September 10th, 2001) During this phase Bush was the "compassionate conservative", successful and popular governor of Texas and a man who knew that there were republican solutions to traditionally Democratic issues such as education.

Bush 2.0 (9/11 2001 - April 2004) This is the version that got up on pile of ruble in the days following 9/11 and promised a group of workers at ground zero that "the people who knocked these buildings down will hear all of us soon." It was this notion of Bush as the warrior, the protector, that led directly to his reelection in November in 2004. However, by November of '04 the creation of the third version of Bush had already begun.

Bush 3.0 (April of 2004-1/09) In April of 2004 Rumsfeld offered Bush his resignation because of gross abuses of Iraqi POWs. Bush refused to accept the resignation. This is the president Bush that is most remembered today; the man who let events get the better of him. The high - or low - point of Bush 3.0 was his "heckuva job Brownie" moment in the days following Hurricane Katrina.

And so it came to pass in November of 2008 then senator Barack Obama was elected to bring change. Throughout his campaign, Obama promised repair the damage done by the Bush administration and restore transparency and accountability to government.

But that was Obama .07, the public beta released for testing before all the bugs had been ironed out.

The first official release of Obama 1.0 has thus far proved buggy and has often been corrupted by errant files left over from the previous software (Bush 3.0). And on Christmas day, 2009, the Obama OS suffered its first full-scale kernel panic requiring a complete reboot. So far, the administration has decided to release a patch, which is designed to correct the security flaw in Obama 1.0 and update the system to Obama 1.01. Unfortunately, this may not be enough to really correct the security flaws:

Everyone who read the name "Umar Farouk Abdulmutallab" prior to December 25, 2009 should be reprimanded and fired.

The White House findings state that, "Mr. Abdulmutallab possessed a U.S. visa, but this fact was not correlated with the concerns of Mr. Abdulmutallab's father about Mr. Abdulmutallab's potential radicalization." It's an embarrassing sentence of bureaucratese in its own right, but more so when considered in context. The State Department didn't revoke Abdulmutallab's visa because an office clerk misspelled his name in a database.

Has no one in the intelligence community ever used Google? When "Abdulmutalab" was typed in, did the computer not ask, "Did you mean 'Abdulmutallab'?"

Another admission that crosses the threshold of bewildering into the realm of criminally negligent: the National Counterterrorism Center has a database of all known and suspected international terrorists. Umar Farouk Abdulmutallab was added to that database.

But that database does not feed directly into the TSA No-Fly List.

Who more than known terrorists belong on the No-Fly List? There should be no human involvement required here. One line of SQL database code could have averted disaster.

According to the White House, when the CIA and NCTC got the name of a radicalized militant from the militant's own father, and a warning that he was planning an attack, they did not search "all available databases to uncover additional derogatory information." How many databases are there? And how many terrorist databases must one appear in before he or she is considered a threat to U.S. national security?

This wasn't a ticking time bomb situation involving a lone wolf under the radar. Such a terrorist will succeed, and there's nothing we can do about it, aside from remaining vigilant. But the United States already knew about Abdulmutallab, and learned of his intentions on November 18th -- a month before he struck.

Most grating in the White House report is the repeated notion that Abdulmutallab's plot failed. It didn't. Nine years after 9/11, and after billions of spent dollars in needless security, confiscated fingernail clippers, and dumped breast milk, he succeeded in smuggling explosives onto an airliner destined for American soil. He succeeded in igniting the explosive. If not for dumb luck involving bad chemistry and a brave Dutch film director, there might today be a smoldering crater in Detroit.

Worse, there are a number of indications that the Bush 3.0 software, which was supposedly deleted, may be coming back:

After the attack, President Obama remained in Hawaii and enjoyed a Christmas vacation on the golf course. After the attack, National Counterterrorism Center director Michael Leiter took a six-day skiing holiday. After the attack, CIA director Leon Panetta remained in beautiful Monterey, California. The nation, the administration claims, can be governed from afar, and that's probably true. But when terrorists attempt a major strike on U.S. soil, isn't it a good idea to have someone in the White House situation room above the rank of janitor?

This tells me that Obama 1.0 - now 1.01 - is treading dangerously close to becoming Bush 4.0. And all it takes in one successful attack inside the U.S. and I have no doubt that the house and senate will pursue there own method of deleting the corrupt software, which will be very divisive and dramatic for the whole country. 

A Step in the Right Direction

I applaud the president for taking responsibility for the Christmas Day Attack -aka The Boxer Rebellion (he he) - but I fear his proposed changes, absent the ending of a career or two, will simply create more paper shuffling and CYA mentality:

The government will strengthen criteria for putting people on no-fly lists barring them from U.S. aircraft. Authorities will comb databases of people suspected of ties to terrorist organizations and determine whether any of them have U.S. visas. The man accused in the Christmas airliner attack, Nigerian national Umar Farouk Abdulmutallab, had a visa, even though he had recently been added to a government watchlist.

What was the point of the terror watch list? I heard recently that there might be 500,000 names on the government's terror watch list. 500k isn't a "watch list", its like 50 divisions. If Al Qadea had 500k people they would attempt a conventional combined arms invasion of Egypt, not send some goon to blow up his pants on an airplane.

What I really want is a system to stop somebody from getting on a plane - not a scanner - not a series of questions, but a system whereby a CIA station chief receives a tip - say the name of a foreign national who is reasonably suspected of receiving training in martyrdom operations - and he can quickly - within maybe 1 or two minutes, tops, put out an APB to every entry point to not let someone with the following name, nationality, etc, cross. The technology required to do this is a very sophisticated and expensive piece of technology known as Gmail.

But the level of cooperation between the CIA, DOS and DHS is probably not possible, and the  devolution of authority into the hands of lowly CIA station chiefs (not really a lowly position, but in the mind of some deputy COS in D.C. they are) would cause fits back at both Langley and Foggy Bottom but I believe it is an aspirational goal.

Also, why is a person who is banned from England allowed to enter the U.S.? Anyone barred from entering either the U.K. or E.U. should undergo a extra layer of scrutiny before being allowed entry into the U.S.

Madame Secretary, resign pt. 2

Perhaps I was a bit hasty when I called for the resignation of the secretary of DHS.

Thinking back, I now wish I had called for the resignation of the director and all deputy directors of the CIA as well whomever is directly in charge of the foreign service.

And the secretary of DHS.

Here is why:

ABC ferreted out the truth behind news reports that Umar Abdulmutallab's father alerted the U.S. Embassy about his concern that his son had gotten involved with radicals. The way such reports were worded conveyed the idea that the CIA didn't have a smoking gun to work with. Actually, the CIA had a smoking cannon handed to them.

ABC learned that what really happened is that Umar phoned his father to say he was calling for the last time because the people he was with in Yemen were going to destroy his SIM card. That would make his phone unusable. And that was as much telling his father he was entering the final phase of training for a terrorist suicide mission.

His father immediately alerted Nigerian intelligence officials that he was afraid his son was preparing for a terrorist mission in Yemen. The officials then brought him directly into the presence of the CIA station chief in Abuja on November 19.

So it's not as if some worried father wandered in off the street to unburden himself to a clerk at a U.S. embassy. And note that the Nigerian intelligence officials didn't run the risk of getting trapped in voice mail hell or hearing, 'I'm sorry your email got lost in the shuffle.' They made Double Dutch sure the station chief heard the father's statement and understood its import and urgency.

What happened after the station chief took in the father's account? Report, file, and forget:

The next day the embassy sent out a thin report to U.S. embassies around the world warning Adbulmutallab may be associating with extremists in Yemen. The CIA official compiled two more robust reports following the meeting with the suspect's father. One was sent back to CIA's Langley, VA [headquarters]; the other remained in draft form in Nigeria and was not circulated until after the attempted attack on Christmas Day, according to a U.S. official.[...]

The White House better be on notice, because if something goes bump in the night in the near future a quick impeachment is sure to follow. I realize there will be a political cost - short term, in my opinion - for a major house cleaning in a mid-term election year, but the Dems are toast in November anyway, and I think the American people would give the president a lot of credit for - shock! - holding the people responsible for our safety responsible for this lapse.