|Google Hiring a Rapid Response Privacy Team|
| 1:51 pm on Aug 27, 2012 (gmt 0)|
Google has opened a Red Team tasked with discovering privacy issues, ostensibly to curb a string of costly bungles.
The small team is named after the label given to units established to test an organisations’ security posture such as military outfits and physical and IT penetration testers.
Engineers within the team would examine all Google products including its Chrome web browser to sniff out privacy gaffes before they become bad headlines.
News of the group followed a recent $US22.5 million ($21.3 million) fine imposed by the US Federal Trade Commission on Google to settle charges that the company bypassed user privacy settings in the mobile Safari browser.
Google was seeking highly skilled engineers to build the team.
In a job advertisement first reported by Kaspersky’s Threat Post, Google sought a data privacy engineer for its US office who would “have an intimate knowledge of the inner workings of modern web browsers and computer networks, enjoy analysing software designs and implementations from both a privacy and security perspective, and will be recognised experts at discovering and prioritising subtle, unusual, and emergent security flaws.
Google has begun hiring for a crack team of data experts to help resolve privacy complaints, following the $22.5 million fine it had to pay the Federal Trade Commission (FTC) after issues relating to the Safari browser.
News that the search giant is recruiting a new privacy division codenamed "red team" broke last week when Google posted a job post looking for data engineers.
"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," read the job post. "Specifically, you will work as a 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."
| 2:34 pm on Aug 27, 2012 (gmt 0)|
Perhaps they should just instruct their existing staff not to bypass people's security? Or is there a reason why they cannot do so?
| 2:50 pm on Aug 27, 2012 (gmt 0)|
Self-policing is always a first line defense against regulatory intervention, of course it's typically more of a spin factor than a genuine attempt to comply with laws.
I'm sorry officer, in the future I'll police myself, no need of you.
| 2:52 pm on Aug 27, 2012 (gmt 0)|
Ok but why are they looking outside of Google for a crack team of engineers? Why don't they just promote the people from within who designed and programmed all these exploits into their various platforms in the first place? Who would have better knowledge of the situation? Or have they all been fired already, as sc(r)apegoats probably.
| 3:02 pm on Aug 27, 2012 (gmt 0)|
|Ok but why are they looking outside of Google for a crack team of engineers? |
It makes for better theatre.
| 3:55 pm on Aug 27, 2012 (gmt 0)|
Will they have a theme tune,and a logo, like Thunderbirds ..
Will we have a hot-line to call them on in case of privacy breaches..or a G sign to shine at the "cloud" like in batman..
Will they protect us from "rogue engineers working unsupervised"..