Yale and the Google zeitgeist – Breach put Yalies’ SSNs in Google searches – and Yale outsou rces email to Google

Very interesting story by Joe Gorman from the Yale Daily News on the June 30th ‘breach’ that exposed 43,000 Yale affiliates. What I find most interesting about this fantastic piece of journalism by Mr. Gorman is the revelation that Yale will begin outsourcings its email to Google in September of this year. I am curious at the terms and conditions of that agreement and what it could mean for the research structures, results and summarized findings from Yale. Output that could perchance find its way into Yale email.

Is it possible that the T’s & C’s could provide contractual permission to allow a direct, searchable, pipeline of all Yale information to flow directly into the ‘Carnivore-like’ Intellectual Property machine that is the private Google zeitgeist?

-The Breachpool

Original Story by Joe Gorman here:

On June 30, staff at the University’s Information Technology Services office got an unwelcome surprise when they found that the names and Social Security numbers of 43,000 Yale affiliates showed up in Google searches for the past 10 months.

The breach occurred when Google altered its search in September 2010 to find and index special file transfer protocol (FTP) servers, such as the one that stored the Yalies’ private information. ITS has taken steps to protect the information compromised in the breach, which Yale publicly announced Aug. 12, and set about notifying the affected students, faculty, staff and alumni — all of whom were linked to the University in 1999 — via postal mail.

Though ITS Director Len Peters said there is no indication that the information has been exploited, Yale has established a response center for affected individuals and is offering them two years of free credit monitoring and identity theft insurance.

“I wasn’t thrilled about it but I’m not terribly concerned,” said Heather Jones ’99, whose Social Security number was one of those included in the file. “Honestly, I’m going to take my chances and not do anything about it.”

While Google representatives told the University that the file is no longer available in searches, they would not say whether any Google users had actually accessed the file.

“We immediately blocked that server from the Internet, removed the file, and did a complete scan of the server to make sure there were no additional at-risk files,” Peters said.

The information was stored on an FTP server used primarily for open source materials. Peters said the file containing the names and Social Security numbers, mostly of people who worked for the University in 1999, was the only sensitive file to be made public. The file did not include addresses, birth dates or financial information.

Since Google modified its search to include FTP servers, hackers have developed a process for finding and exploiting weaknesses via the search called “Google dorking.”

Peters said ITS was not aware that Google instituted the advanced FTP search last September. He added that since discovering that the file was accessible, ITS has confirmed that other search engines, such as Yahoo!, do not index FTP servers.

Peters said that both file and the directory in which it was contained had innocuous names. A user who encountered the file in a Google search would not be able to determine what information the file held unless he or she opened it, he said.

“It was pretty well hidden, with a very inconspicuous file name,” Peters said.

Google would not release information on how many times files have been accessed from its search engine, he added.

Peters, who came to ITS from Columbia Business School at the end of last year, said he will take steps to improve information security during his first year as Yale’s Chief Information Officer. These measures will include better communication with Google, he said.

Starting in September, Yale will outsource University email to Google.

By Zoe Gorman
Staff Reporter
Friday, August 26, 2011

Advertisements

Leave a comment

Filed under Uncategorized

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s