Search: Home Bugtraq Vulnerabilities Mailing Lists Jobs Tools Vista
Security Czar
Scott Granneman, 2006-03-23

In this column Scott Granneman takes the role of dictator of the security world and presents his ideas about mandatory reforms that would improve security for millions of people.

Comments Mode:
Security Czar 2006-03-23
Erik N
Security Czar 2006-03-23
Anonymous (1 replies)
Here here!!! 2006-03-24
Anonymous (1 replies)
Re: Here here!!! 2006-11-08
Anonymous
Security Czar 2006-03-23
Stonewall
Security Czar 2006-03-23
Wremes (1 replies)
Re: Security Czar 2006-03-31
Anonymous
Security Czar 2006-03-23
Mr. Negative (1 replies)
Re: Security Czar 2006-03-26
Anonymous
Let's go for it! 2006-03-23
assurbanipal (2 replies)
Re: Let's go for it! - Why? 2006-03-24
Anonymous
Re: Let's go for it! 2006-04-14
Anonymous
Security Czar 2006-03-23
Nekromancer (1 replies)
Re: Security Czar 2006-03-30
EasterNerd (1 replies)
Re: Re: Security Czar 2006-03-31
Mick
Security Czar 2006-03-23
infamous41md (1 replies)
Re: Security Czar 2006-03-23
Todd Knarr (1 replies)
Re: Re: Security Czar 2006-03-23
infamous41md
Security Czar 2006-03-23
Anonymous (1 replies)
Re: Security Czar 2006-04-14
The Finger
Security Czar 2006-03-24
Anonymous
Security Czar 2006-03-24
Anonymous
Security Czar 2006-03-24
Anonymous
Security Czar 2006-03-24
Craig S Wright
No mandatory training 2006-03-27
Michael Scovetta (3 replies)
Re: No mandatory training 2006-03-29
Anonymous
Re: No mandatory training 2006-03-29
Anonymous
Re: No mandatory training 2006-03-30
Anonymous
Yes! (except for one thing...) 2006-03-28
Penguinisto
Security Czar 2006-03-29
Anonymous
Security Czar 2006-03-30
Lunkwill
Security Czar 2006-03-31
Paul Stepowski
I'd like to comment on one of your points:

* Training and licensing for all new computer users

In my experience, user education is generally wasted effort. Educating users about security is equivalent to "patching" users. Every time a new type of vulnerability appears, you have to "patch" (educate) your users about the security risks and ways of mitigating these risks. The patching model of addressing security risks is not scalable. The end result sees many patches released but the underlying security problems remain.

Consider this contrived example. A newbie system administrator has root access to a *nix system, and unwittingly runs "rm -rf /" as root. To prevent this we could educate the user about the operating system and the "rm" command, but this still would not prevent them from actually running the command. A better way to prevent this is not to allow this user access to run this command at all by revoking their root access.
I realise this is a contrived example but I believe the point is valid. Wherever possible, do not educate users. Instead, enforce sensible security policy that will prevent inept or malicious users from negatively impacting IT resources. Where it is not possible to mandate security policy, education may help, but it's no substitute for a properly enforced security policy. Our goal as IT security professionals should to be find better security solutions that are secure by design, not to find "better" ways of patching fundamentally flawed designs.

Someone already made the comment, "security needs to become invisible. You, the end-user, shouldn't need to worry about patching your systems, upgrading your anti-virus, etc. This should all be part and parcel of the total cost of owning a computer, and should come pre-installed, invisible, and just plain working." I agree with this idea and I think it applies to both patching and user education.

[ reply ]

Link to this comment: http://www.securityfocus.com/comments/columns/394/33410#33410
Security Czar 2006-03-31
FortHEX
Security Czar 2006-04-02
Anil B







 

Privacy Statement
Copyright 2008, SecurityFocus