Mar. 05, 2015

The Problem With Computer Surveillance

by Bruce Schneier

Click to enlarge images
The following is an excerpt from Bruce Schneier's Data and Goliath. Listen to SciFri on Friday, March 6, to hear Schneier talk more about data and privacy.
One of the common defenses of mass surveillance is that it’s being done by algorithms and not people, so it doesn’t compromise our privacy. That’s just plain wrong.
The distinction between human and computer surveillance is politically important. Ever since [Edward] Snowden provided reporters with a trove of top-secret documents, we’ve learned about all sorts of NSA word games. The word “collect” has a very special definition, according to the Department of Defense. It doesn’t mean collect; it means that a person looks at, or analyzes, the data. In 2013, Director of National Intelligence James Clapper likened the NSA’s trove of accumulated data to a library. All those books are stored on the shelves, but very few are actually read. “So the task for us in the interest of preserving security and preserving civil liberties and privacy is to be as precise as we possibly can be when we go in that library and look for the books that we need to open up and actually read.”
Think of that friend of yours who has thousands of books in his house. According to this ridiculous definition, the only books he can claim to have collected are the ones he’s read.
This is why Clapper asserts he didn’t lie in a Senate hearing when he replied “no” to the question “Does the NSA collect any type of data at all on millions or hundreds of millions of Americans?” From the military’s perspective, it’s not surveillance until a human being looks at the data, even if algorithms developed and implemented by defense personnel or contractors have analyzed it many times over.
This isn’t the first time we’ve heard this argument. It was central to Google’s defense of its context-sensitive advertising in the early days of Gmail. Google’s computers examine each individual e-mail and insert a content-related advertisement in the footer. But no human reads those Gmail messages, only a computer. As one Google executive told me privately in the early days of Gmail, “Worrying about a computer reading your e-mail is like worrying about your dog seeing you naked.”
But it’s not, and the dog example demonstrates why. When you’re watched by a dog, you’re not overly concerned, for three reasons. The dog can’t understand or process what he’s seeing in the same way another person can. The dog won’t remember or base future decisions on what he’s seeing in the same way another person can. And the dog isn’t able to tell anyone—not a person or another dog—what he’s seeing.
When you’re watched by a computer, none of that dog analogy applies. The computer is processing what it sees, and basing actions on it. You might be told that the computer isn’t saving the data, but you have no assurance that that’s true. You might be told that the computer won’t alert a person if it perceives something of interest, but you can’t know whether that’s true. You have no way of confirming that no person will perceive whatever decision the computer makes, and that you won’t be judged or discriminated against on the basis of what the computer sees.
Moreover, when a computer stores your data, there’s always a risk of exposure. Privacy policies could change tomorrow, permitting new use of old data without your express consent. Some hacker or criminal could break in and steal your data. The organization that has your data could use it in some new and public way, or sell it to another organization. The FBI could serve a National Security Letter on the data owner. On the other hand, there isn’t a court in the world that can get a description of you naked from your dog.
The primary difference between a computer and a dog is that the computer communicates with other people and the dog does not—at least, not well enough to matter. Computer algorithms are written by people, and their output is used by people. And when we think of computer algorithms surveilling us or analyzing our personal data, we need to think about the people behind those algorithms. Whether or not anyone actually looks at our data, the very facts that (1) they could, and (2) they guide the algorithms that do, make it surveillance.
You know this is true. If you believed what Clapper said, then you wouldn’t object to a camera in your bedroom—as long as there were rules governing when the police could look at the footage. You wouldn’t object to being compelled to wear a government-issued listening device 24/7, as long as your bureaucratic monitors followed those same rules. If you do object, it’s because you realize that the privacy harm comes from the automatic collection and algorithmic analysis, regardless of whether or not a person is directly involved in the process.

Excerpted from Data and Goliath: The Hidden Battles to Collect Your Data and Control Your World by Bruce Schneier. Copyright © 2015 by Bruce Schneier. With permission of the publisher, W. W. Norton & Company, Inc. All rights reserved.

Author photo © Geoff Stone
About Bruce Schneier

Bruce Schneier is an internationally renowned security technologist and the author of twelve books. He is a fellow at Harvard University’s Berkman Center and serves on the Board of Directors for the Electronic Frontier Foundation.

The views expressed are those of the author and are not necessarily those of Science Friday.
EVAL ERROR: Entity: line 1: parser error : Space required after the Public Identifier

Entity: line 1: parser error : SystemLiteral " or ' expected

Entity: line 1: parser error : SYSTEM or PUBLIC, the URI is missing


line 1: package tmpevalpackage;
line 2: sub doEval { 
line 3: 	my($parent);
line 4: 	
line 5: 	if($LayoutManager::url_resolved_values{'SEGMENT.nickname'}) {
line 6: 		$parent = $LayoutManager::url_resolved_values{'SEGMENT.nickname'};
line 7: 	}
line 8: 	elsif($LayoutManager::url_resolved_values{'VIDEO.nickname'}) {
line 9: 		$parent = $LayoutManager::url_resolved_values{'VIDEO.nickname'};
line 10: 	}
line 11: 	elsif($LayoutManager::url_resolved_values{'DOCUMENT.nickname'}) {
line 12: 		$parent = $LayoutManager::url_resolved_values{'DOCUMENT.nickname'}
line 13: 	}
line 14: 	
line 15: 	if($parent) {
line 16: 		my(@books) = &Database::SelectClause('BOOK',"parent = $parent");
line 17: 		if(!@books) {
line 18: 			$parent = '';
line 19: 		}
line 20: 	}
line 21: 	
line 22: 	if(!$parent) {
line 23: 		my(@sel) = &Database::SelectClause('GLOBAL','record all ""');
line 24: 		if(@sel) {
line 25: 			$parent = 'GLOBAL.' . $sel[0];
line 26: 		}
line 27: 			$main::ENV{'reading_header'} = "FEATURED READING";
line 28: 	}
line 29: 	
line 30: 	 = '';
line 31: 	
line 32: 	if($parent) {
line 33: 		my(@books) = &Database::SelectClause('BOOK',"parent = $parent");
line 34: 		0 = 0;
line 35: 		my $dots;
line 36: 		foreach(@books) {
line 37: 			my(%data);
line 38: 			&Database::GetRow($_,'BOOK',\%data);
line 39: 			my($status,$title,$author,$url,$image,$width,$height) = &SciFri::Schema::getAmazonItem($data{'isbn'});
line 40: 			if($data{'title'}) {
line 41: 				$title = $data{'title'};
line 42: 			}
line 43: 			if($data{'author'}) {
line 44: 				$author = $data{'author'};
line 45: 			}
line 46: 			if($status eq 'ok') {
line 47: 				 .= "<div class=\"box-2x1-item box-slide\" data-href=\"$url\">";
line 48: 				 .= "	<div class=\"box-2x1-item-photo\">";
line 49: 				 .= "		<div class=\"image-wrapper\" data-jsclass=\"imageWrapper\" data-align=\"right\">";
line 50: 				 .= "			<img src=\"$image\" data-width=\"$width\" data-height=\"$height\">";
line 51: 				 .= "		</div>";
line 52: 				 .= "	</div>";
line 53: 				 .= "	<h4>$title</h4>";
line 54: 				if($author) {
line 55: 					 .= "	<p>by $author</p>";
line 56: 				}
line 57: 				 .= "	<div class=\"box-2x1-more-button\"><a href=\"$url\"><img src=\"/images/v1/icon_text_more_white.png\" width=47 height=15 border=0></a></div>";
line 58: 				 .= "</div>";
line 59: 				++0;
line 60: 			}
line 61: 		}
line 62: 	}
line 63: 	if($parent eq "GLOBAL.1") { $main::ENV{'reading_header'} = "FEATURED READING"; }
line 64: 	else { $main::ENV{'reading_header'} = "RELATED READING"; }
line 65:  };
line 66: &doEval();
line 67: 1;

Science Friday® is produced by the Science Friday Initiative, a 501(c)(3) nonprofit organization.

Science Friday® and SciFri® are registered service marks of Science Friday, Inc. Site design by Pentagram; engineering by Mediapolis.