Tag: border security

The House Wants to Defund DHS. Let’s Restructure It Instead.

DHS_alert

Media outlets and blogs are taking to the fainting couches because Very Evil House Republicans who Hate America are threatening to defund the much-mocked Department of Homeland Security.

Sadly, they’re not failing to fund it because, say, it’s a gargantuan bureaucratic waste of time that funnels billions of taxpayer dollars to security grifting companies, or because it hands out military equipment to police departments with all the brio and experience of a private just out of basic training, or because DHS funding suppresses legitimate dissent by communities of color across the United States.

No, what’s really got House Republicans in a lather about DHS is realizing that something “must-pass” like a DHS funding bill would be a great vehicle for a poison-pill amendment overturning the President’s executive actions on immigration. So they sent that bill up to the Senate, and Senate Republicans, needing five Democratic votes to push through a DHS funding bill, somehow can’t find any Democrats willing to commit electoral hara-kiri with their own base in order to please the Republicans’ base. Go figure!

As a result, in two weeks’ time the DHS will run out of money, and apologists for the security state are beginning to panic – but they’re having trouble getting their stories straight. Sen. Lindsey Graham (R-SC) warns us all, “We can’t go too far here because look what happened in Paris.” Sen. John McCain (R-AZ) fulminates, “We can’t shut down the DHS. Not with the threats the homeland is subjected to as a result of the rise of ISIS.” [Note: There is no threat to “the homeland” from ISIS.] For God’s sake, the TSA might run out of money! What an awful shame that would be!

The DHS is a failure. It was a bad idea to begin with, coming out of the incorrect notion that the 9/11 attacks could have been prevented by “joined-up intelligence.” It never made sense to yoke the Coast Guard, FEMA, and the customs/border/transportation security/immigration agencies awkwardly together. DHS has always been poorly managed. It just layers an extra frosting of highly remunerated officials on top of agencies that would do just as fine where they were before. So let’s take a closer look at what a sensible structure would look like.

Continue reading The House Wants to Defund DHS. Let’s Restructure It Instead.

Drowning in Data, Starved for Wisdom: The surveillance state cannot meaningfully assess terrorism risks

In this movie, we're Brad.
Pity the analysts.

The NSA has just vigorously denied that their new Utah Data Center, intended for storing and processing intelligence data, will be used to spy on US citizens. The center will have a capacity of at least one yottabyte, and will provide employment for 100-200 people. With the most generous assumptions [200 employees, all employed only on reviewing the data, only one yottabyte of data, ten years to collect the yottabyte, 5GB per movie], each employee would be responsible on average for reviewing 4500 billion terabytes, or approximately 23 million years’ worth of Blu-ray quality movies, every year.

 

Must...keep...watching...my...country...needs...me
Must…keep…watching…my…country…needs…me

This astounding and continually increasing mismatch shows that we are well beyond the point where law enforcement is able to have a human review a manageable amount of the data in its possession potentially relating to terrorist threats. Computer processing power doubles every two years, but law enforcement employment is rising at a rate of about 7% every ten years, and nobody’s going to pay for it to double every two years instead. Purely machine-based review inevitably carries with it a far higher probability that important things will be missed, even if we were to suppose that the data was entirely accurate to begin with – which it certainly is not.

So why is anybody surprised that Tamerlan Tsarnaev, the elder of the Boston Marathon bombing suspects and one of around 750,000 people in the TIDE database, was not stopped at the border? That facial recognition software wasn’t able to flag him as a match for a suspect? That the fusion centers, intended to synthesize data into actionable “suspicious activity reports”, flag things too late for them to be of any use? That the Air Force is panicking a little at not having enough people to process the data provided by our drone fleet?

It’s in this context, then, that we should understand the calls for more surveillance after the Boston Marathon attacks for what they are. More cameras, more surveillance drones and more wiretapping, without many more humans to process the data, will make this problem worse, not better. These calls are being driven not by a realistic assessment that surveillance will help prevent the next attack, but by the internal incentives of the players in this market. Neither the drone manufacturers, nor law enforcement, nor elected officials, have an interest in being the ones to call a halt. So instead they’re promoting automation – automated drones, automated surveillance, and email scanning software techniques.

They are missing something very simple. We don’t need a terrorism database with 750,000 names on it. There are not 750,000 people out there who pose any sort of realistic threat to America. If the “terrorism watch list” were limited by law to a thousand records, then law enforcement would have to focus only on the thousand most serious threats. Given the real and likely manpower of the federal government, and the rarity of actual terrorism, that’s more than enough. If law enforcement used the power of the Fourth Amendment, instead of trying to find ways round it, it could focus more on the highest-probability threats.

Yes, they would miss stuff. That’s inevitable under both a tight and a loose system. But a tight system has the added advantages that it protects more people’s liberties, and costs a lot less.

UPDATE: With the help of a New Yorker fact-checker, the figure of “400 billion terabytes” above has been corrected to “500 billion terabytes”.