Risk
8/23/2012
02:59 PM
Connect Directly
Google+
LinkedIn
Twitter
RSS
E-Mail
50%
50%

Google 'Red Team' To Test Product Privacy

Taking privacy seriously translates into new hires for Google.

Google for years has said that it takes privacy very seriously, but the company's recent $22.5 million settlement with the Federal Trade Commission for breaking privacy promises and its commitment last year to endure 20 years of FTC privacy audits following "deceptive privacy practices" is pushing the company to take privacy with new, improved seriousness.

After confessing to being "mortified" in 2010 over revelations that its Street View cars had been vacuuming data cast blithely into the air by people running open WiFi access points, Google appointed Alma Whitten to be its director of privacy, added an information security awareness program for employees, and began requiring engineering product managers to keep a privacy design document for every project.

Now, Google is formalizing internal processes to test product privacy with the formation of a "red team," a group that attempts to challenge an organization's defenses in order to make those defenses more effective. In the security world, this often takes the form of penetration testing. Financial institutions, for example, often hire hackers to try to break into their systems and then implement improvements as needed.

[ Read Tent Promises Open, Distributed Social Networking. ]

A Google job posting, first noted by Kaspersky Lab, calls for candidates to apply for the role of Data Privacy Engineer, Privacy Red Team.

"As a Data Privacy Engineer at Google you will help ensure that our products are designed to the highest standards and are operated in a manner that protects the privacy of our users," the job posting says. "Specifically, you will work as member of our Privacy Red Team to independently identify, research, and help resolve potential privacy risks across all of our products, services, and business processes in place today."

Google declined to comment beyond this statement: "We are always on the lookout for talented people in a variety of roles," a company spokeswoman said in an email.

In 2006, as it was developing and deploying its Web productivity apps, Google made its concern about security more visible with support for organizations like StopBadware.org. Google subsequently launched a security blog in May, 2007. The security process for Web apps at the time just wasn't as formalized as what Microsoft was doing for desktop app security.

But concern about privacy lagged. In 2008, Google was being chided by California State Assemblyman Joel Anderson for not having a link to its privacy policy on its home page, as required by state law. Google was more worried about speed than privacy: The company resisted adding a privacy link because the text would add a few extra bytes to the "weight" of its home page, slowing it by milliseconds and making it unnecessarily cluttered.

The existence of a "red team" inside Google is likely to be seen as a sign that the company is taking privacy seriously. But increasingly, what's going on outside Google is shaping the privacy debate.

Privacy has become a point of competitive differentiation. Google's chief rivals, Apple and Microsoft, have realized that Google can only take privacy so far before it starves itself of the personal data it needs to maximize revenue from the ads it serves. And Mozilla, caught off-guard by Google's introduction of Chrome in 2008, has had to reinvent itself, even as it continues to collect millions from Google every year for making Google the default search engine in Firefox.

So it is that all the major browser vendors except Google--Apple, Microsoft, Mozilla, and Opera--have implemented support for Do Not Track, a technical mechanism by which browser users can communicate the desire not to be tracked for targeted advertising.

The seriousness of Google's avowed concern about privacy gets called into question when competitors provide privacy protections that Google does not. Whether or not Google will eventually be shamed into abiding by Do Not Track, the company is looking to fill other positions that underscore its commitment to privacy. These include: Privacy Engineer, Product Manager, Privacy, or Technical Program Manager, Ads Privacy Policy.

Google emphasizes the significance of this last position because whoever fills it will influence the company's advertising business practices. "For many users, advertising is where the rubber hits the road, because misuse of user information for advertising purposes creates a strongly negative user experience," the job posting says.

The formation of a Privacy Red Team may be noteworthy, but Google's privacy pacesetter is likely to continue to be its ad team.

Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
Partner Perspectives
What's This?
In a digital world inundated with advanced security threats, Intel Security seeks to transform how we live and work to keep our information secure. Through hardware and software development, Intel Security delivers robust solutions that integrate security into every layer of every digital device. In combining the security expertise of McAfee with the innovation, performance, and trust of Intel, this vision becomes a reality.

As we rely on technology to enhance our everyday and business life, we must too consider the security of the intellectual property and confidential data that is housed on these devices. As we increase the number of devices we use, we increase the number of gateways and opportunity for security threats. Intel Security takes the “security connected” approach to ensure that every device is secure, and that all security solutions are seamlessly integrated.
Featured Writers
White Papers
Cartoon
Current Issue
Dark Reading's October Tech Digest
Fast data analysis can stymie attacks and strengthen enterprise security. Does your team have the data smarts?
Flash Poll
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2014-7298
Published: 2014-10-24
adsetgroups in Centrify Server Suite 2008 through 2014.1 and Centrify DirectControl 3.x through 4.2.0 on Linux and UNIX allows local users to read arbitrary files with root privileges by leveraging improperly protected setuid functionality.

CVE-2014-8346
Published: 2014-10-24
The Remote Controls feature on Samsung mobile devices does not validate the source of lock-code data received over a network, which makes it easier for remote attackers to cause a denial of service (screen locking with an arbitrary code) by triggering unexpected Find My Mobile network traffic.

CVE-2014-0619
Published: 2014-10-23
Untrusted search path vulnerability in Hamster Free ZIP Archiver 2.0.1.7 allows local users to execute arbitrary code and conduct DLL hijacking attacks via a Trojan horse dwmapi.dll that is located in the current working directory.

CVE-2014-2230
Published: 2014-10-23
Open redirect vulnerability in the header function in adclick.php in OpenX 2.8.10 and earlier allows remote attackers to redirect users to arbitrary web sites and conduct phishing attacks via a URL in the (1) dest parameter to adclick.php or (2) _maxdest parameter to ck.php.

CVE-2014-7281
Published: 2014-10-23
Cross-site request forgery (CSRF) vulnerability in Shenzhen Tenda Technology Tenda A32 Router with firmware 5.07.53_CN allows remote attackers to hijack the authentication of administrators for requests that reboot the device via a request to goform/SysToolReboot.

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
Follow Dark Reading editors into the field as they talk with noted experts from the security world.