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.

Risk

7/8/2009
03:53 PM
Connect Directly
Google+
Twitter
RSS
E-Mail
50%
50%

Google Discloses Plans For New Malware-Resistant OS

Chrome OS aimed at eradicating malware issues for desktops with lightweight platform and cloud-based application model

Google is building its own operating system aimed at eliminating malware problems at the consumer's desktop.

The company late yesterday announced its work on the new Google Chrome OS, a lightweight OS that sits atop a Linux kernel and will run on X86 and ARM chips.

"We are going back to the basics and completely redesigning the underlying security architecture of the OS so that users don't have to deal with viruses, malware," blogged Google's Sundar Pichai, vice president for product management, and Linus Upson, engineering director. "Most of the user experience takes place on the Web."

Chrome OS code will be available as open source later this year, and Google says it plans to make it available on netbooks by the second half of 2010.

Google wouldn't provide specifics on the OS or its security features beyond the blog post, but security experts say while this Web application-focused OS should eliminate the usual desktop threats, it still will be subject to Web-borne threats. Web application vulnerabilities today are some of the most prevalent, with cross-site scripting (XSS) and SQL injection attacks increasing on Websites.

"[Google Chrome OS] should be immune to most existing PC viruses, but will face Web-based risks and attacks much like any other browser model would," says Rob Enderle, principal analyst with the Enderle Group. "User authentication is probably [the] biggest problem -- even more than a PC -- as this will become a natural key to a lot of large databases and services."

Enderle says the Chrome OS will likely also focus on phishing and Web-borne attacks versus traditional desktop viruses. "It effectively changes the security model for the desktop into something much more similar to a thin client/cell phone model," he says.

Rich Mogull, founder of Securosis, says smart handsets already have paved the way to this type of user model. But the Chrome OS model doesn't necessarily mean safer computing for consumers. "It just shifts the risk," he says. "It's just going to be a shift in attacks [to Web applications]...and we've already seen of lot of that [occurring]. If anything, [Chrome OS is] going to highlight Web application security issues."

Paul Henry, security and forensics expert for Lumension, says Google thus far hasn't provided enough information on the security elements of Google Chrome OS. "There have been claims that it is virus-free or virus-proof -- however, there really is no specific security capability mentioned on the product beyond, perhaps, the reduced threat envelope you would get in using any application-specific OS," he says.

Meanwhile, Google said in its announcement that the Web is the platform for application developers writing for Chrome OS. "All Web-based applications will automatically work and new applications can be written using your favorite web technologies. And of course, these apps will run not only on Google Chrome OS, but on any standards-based browser on Windows, Mac and Linux thereby giving developers the largest user base of any platform," the blog said.

Enderle says Chrome OS is basically a scaled-up Android based on the Linux kernel. "An app store model will limit most of what runs, and an increasing amount of content will be online and not run locally at all," he says.

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
Threaded  |  Newest First  |  Oldest First
COVID-19: Latest Security News & Commentary
Dark Reading Staff 5/22/2020
How an Industry Consortium Can Reinvent Security Solution Testing
Henry Harrison, Co-founder & Chief Technology Officer, Garrison,  5/21/2020
Is Zero Trust the Best Answer to the COVID-19 Lockdown?
Dan Blum, Cybersecurity & Risk Management Strategist,  5/20/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: This comment is waiting for review by our moderators.
Current Issue
How Cybersecurity Incident Response Programs Work (and Why Some Don't)
This Tech Digest takes a look at the vital role cybersecurity incident response (IR) plays in managing cyber-risk within organizations. Download the Tech Digest today to find out how well-planned IR programs can detect intrusions, contain breaches, and help an organization restore normal operations.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-13485
PUBLISHED: 2020-05-25
The Knock Knock plugin before 1.2.8 for Craft CMS allows IP Whitelist bypass via an X-Forwarded-For HTTP header.
CVE-2020-13486
PUBLISHED: 2020-05-25
The Knock Knock plugin before 1.2.8 for Craft CMS allows malicious redirection.
CVE-2020-13482
PUBLISHED: 2020-05-25
EM-HTTP-Request 1.1.5 uses the library eventmachine in an insecure way that allows an attacker to perform a man-in-the-middle attack against users of the library. The hostname in a TLS server certificate is not verified.
CVE-2020-13458
PUBLISHED: 2020-05-25
An issue was discovered in the Image Resizer plugin before 2.0.9 for Craft CMS. There are CSRF issues with the log-clear controller action.
CVE-2020-13459
PUBLISHED: 2020-05-25
An issue was discovered in the Image Resizer plugin before 2.0.9 for Craft CMS. There is stored XSS in the Bulk Resize action.