What Office 2010 is Teaching About Security

Terry Olaes

I Used to be the [H] News Guy
2FA
Joined
Nov 27, 2006
Messages
4,646
PCWorld has an article about the security practices in the Microsoft Office 2010 beta and how developers can learn from them. Instead of removing or disabling features in the name of security, they are taking a new approach based on five principles. Seems simple enough but we’ll see how it translates in the real world.

As long as security procedures create a tug of war between users and software, users will always find ways to "win" -- thus, subverting the very security measures designed to protect them. By offering a gradual, multilayered security model, Office 2010 tries to make security a partnership with the user -- and that's a lesson that any application developer can take to heart.
 
4. Don't rely on users to enforce security
Too many desktop applications use a security model that boils down to asking the user: "The action you are about to take poses a security risk. Do you want to go ahead anyway (Y/N)?"

This approach is not only lazy but dangerous.

Sounds a lot like UAC in Vista and Win7. Guess the Windows developers also have a lot to learn from the Office developers :p
 
Sounds a lot like UAC in Vista and Win7. Guess the Windows developers also have a lot to learn from the Office developers :p

Problem is, what else can you do with regards to that? For a home system, the user is the administrator, that's just how it works. That means that they can do whatever they want, including mess up the system. With great power comes great responsibility and all that.

If there's a way to design an OS that can protect people from themselves, I'd love to hear it. However remember that it has to do so while still offering them the features they need. For example you can solve a whole lot of problems by not letting users install software. Many work environments do just that, only their IT staff can do installs. Well that isn't feasible at home, there is no IT staff.

What you want to do is block bad software. Well the problem is that there's noevil bit to indicate software is bad. So software access is all or nothing. Either the administrator can install software or they cannot. At home, obviously, it has to be that they can install it. The ability to install good software also means they have the ability to install bad software. Just how it works.
 
Back
Top