Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Endpoint

6/1/2010
02:20 PM
Connect Directly
Google+
Twitter
RSS
E-Mail
50%
50%

Report: Google Dropping Windows For Security Reasons

'Aurora' attacks out of China reportedly helped prompt OS changes at Google

Google reportedly has been moving away from the internal use of Windows in the wake of the Operation Aurora attacks, according to a report by The Financial Times. New employees can choose either Mac or Linux systems, the report said.

The targeted attacks out of China that hit Google, Adobe, Intel, and other U.S. firms in several cases exploited a zero-day flaw in the Internet Explorer 6 browser; Google was among the firms that fell victim to that exploit.

Google would neither confirm nor deny whether it was phasing out Windows, as was reported by the FT, which quoted unnamed Google employees. "We're always working to improve the efficiency of our business, but we don't comment on specific operational matters," a Google spokesperson said in response to the report.

One employee quoted in the article said if a Google employee prefers to stick with Windows, he or she must get clearance from senior officials. In addition, purchasing a new Windows machine "requires CIO approval," another unnamed Google employee is quoted as saying.

The move is security-driven, as concerns have intensified within the company since the Aurora attacks, which Google revealed earlier this year. Google employees said the transition away from Windows was also prompted by Google's plan to run on its own products, including its upcoming Chrome operating system, the report said. "Before the security, there was a directive by the company to try to run things on Google products," a Google employee told the FT. "It was a long time coming."

Have a comment on this story? Please click "Discuss" below. If you'd like to contact Dark Reading's editors directly, send us a message.

Kelly Jackson Higgins is the Executive Editor of Dark Reading. She is an award-winning veteran technology and business journalist with more than two decades of experience in reporting and editing for various publications, including Network Computing, Secure Enterprise ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
6 Emerging Cyber Threats That Enterprises Face in 2020
This Tech Digest gives an in-depth look at six emerging cyber threats that enterprises could face in 2020. Download your copy today!
Flash Poll
State of Cybersecurity Incident Response
State of Cybersecurity Incident Response
Data breaches and regulations have forced organizations to pay closer attention to the security incident response function. However, security leaders may be overestimating their ability to detect and respond to security incidents. Read this report to find out more.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-11494
PUBLISHED: 2020-04-02
An issue was discovered in slc_bump in drivers/net/can/slcan.c in the Linux kernel through 5.6.2. It allows attackers to read uninitialized can_frame data, potentially containing sensitive information from kernel stack memory, if the configuration lacks CONFIG_INIT_STACK_ALL, aka CID-b9258a2cece4.
CVE-2020-7619
PUBLISHED: 2020-04-02
get-git-data through 1.3.1 is vulnerable to Command Injection. It is possible to inject arbitrary commands as part of the arguments provided to get-git-data.
CVE-2020-7620
PUBLISHED: 2020-04-02
pomelo-monitor through 0.3.7 is vulnerable to Command Injection.It allows injection of arbitrary commands as part of 'pomelo-monitor' params.
CVE-2020-7621
PUBLISHED: 2020-04-02
strong-nginx-controller through 1.0.2 is vulnerable to Command Injection. It allows execution of arbitrary command as part of the '_nginxCmd()' function.
CVE-2020-7623
PUBLISHED: 2020-04-02
jscover through 1.0.0 is vulnerable to Command Injection. It allows execution of arbitrary command via the source argument.