Google's Chrome OS Will Attempt to Reinvent the Security Model

by Sam Dean - Nov. 24, 2009Comments (1)

ZDNet's Dana Blankenhorn has an interesting post up called "Crome OS will rise or fall on the safety dance." In it, he notes that there are a number of security initiatives in Google's upcoming operating system for netbooks, including "system hardening, process isolation, secure auto-update, verified boot, intuitive account management, defenses in depth, and devices secure by default." Indeed, one of the most ambitious aspects of Chrome OS is the tough stance that it will take on the security front. Here are some details on that tough stance.

Chrome OS is built to behave quite different from other operating systems, bypassing a number of types of boot processes and others in order to optimize performance. Additionally, however, the OS will actually reimage itself if malware is detected. If Google does this properly, Chrome OS systems may be free of the guaranteed performance decay that Windows systems tend to have over time. Every Windows user is used to how that decay creeps in as a system continues to be used.

However, Google is going to be banking on the idea that that users will like the idea of having a system reimage the instant malware shows up. Additionally, Blankenhorn notes that Chrome OS "has to develop  an ecosystem of applications around itself that are themselves secure." That's true, if Google's end-to-end secure intentions are to be realized.

I've seen some posts going around on Chrome OS that characterize it as an easy OS to do, since it's only aimed at netbooks, and will work only with cloud applications, not the intricate workings of local apps. I don't think Google has an easy job ahead, though. Security is one of the primary areas where what Google wants to do will be difficult.

 


Browse Blog

Mark Hinkle uses OStatic to support Open Source, ask and answer questions and stay informed. What about you?



1 Comments
 

It depends on how big the disk image is.


On a 4GB SSD, the Asus eeePC700 would take around 5 minutes to reimage the OS for use. Yes it's slow and the user really doesn't want to wait around that long. SSDs have grown a lot faster since then, but the onus will be on Google to keep that system partition as small as possible so that reimaging is done as quickly as possible.


0 Votes
Share Your Comments

If you are a member, to have your comment attributed to you. If you are not yet a member, Join OStatic and help the Open Source community by sharing your thoughts, answering user questions and providing reviews and alternatives for projects.