Layer 8

Security is fundamentally about people, and everything we know about people is relevant to security. -- B. Schneier

The Problem With Pundits, Part II.

Ira Winkler, who is normally a smart guy, completely blows it with this article on why ethics should stay out of computer security awareness programs.

Clearly, a good computer security program should help to identify illicit activities, but it is not what it exists to do, and it’s counterproductive to accomplishing the program’s true goals. In too many organizations, computer security has a negative connotation, and its rules (and personnel) seem to exist mainly to mete out punishments for rule infractions.

Well then, Ira, I’d suggest that you’re not doing it right.  Users who are not technically sophisticated also need to be taught why certain behaviors on the computer ARE unethical.  Too many people don’t understand that copying software to multiple computers can be wrong and even illegal.  They don’t see anything wrong with sharing passwords.  They don’t understand that if they’re blogging about confidential information, it’s findable by the whole world, including their employers. 

Underlying practically all security awareness instruction is plain old IT instruction.  It’s needed both within IT and in other parts of the organization.  You simply cannot assume that a developer understands that he shouldn’t build a back door into an application; he may not even realize that it IS a back door until you explain it to him. 

Not only that, but computer security is data security.  You have to explain to people what they are allowed to do with data and why.  A security awareness program is very closely married to confidentiality and legal issues.  Most of the policies created in those areas end up being funneled through my awareness program because it makes sense to do so, and often I’m the one who raises the issues because I end up having to investigate them and deal with their fallout.

My awareness program isn’t all “meting out punishments for rule infractions.“  It’s also education for the users on how to keep themselves secure at home, and how to keep themselves out of trouble in general.  I think it’s better for me to warn them that everything on the network is potentially logged, and that they shouldn’t write anything that they don’t want their co-workers to know about, just in case a legal discovery request forces me to go through their mailbox.  I warn them that they shouldn’t publish anything under their own name on the Internet unless they want it to be searchable by their bosses or employees for the next 20 years.  (One of my guys is STILL giving me grief about a college photo of mine that he found.  It was a Coca-Cola bottle in my hand, I swear!)

And you should never pass up an opportunity to educate users about IT policies that you may be using later as grounds for disciplinary action, termination and/or prosecution.  The Legal, HR and Audit folks will all thank you for it.  You shouldn’t have to say “Don’t impersonate a co-worker,“ but you may well have to say, “Don’t send email from someone else’s account; that’s the same as impersonation.“  You may have to explain why stealing bandwidth IS stealing.  Our justice system isn’t THAT robust yet when it comes to dealing with ethical violations involving information technology. 

If you do it right, a security awareness program can open the door for all sorts of IT-related education, some of which is sorely necessary.  If you’re only concentrating on telling users How Not To Break The Computers, you’re missing a huge part of the big picture, and therefore you’re not doing your job.

 

Posted by shrdlu on Friday, October 27, 2006
(3) CommentsPermalink blogmarks Favicon del.icio.us Favicon Digg Favicon Fark Favicon Furl Favicon Google Bookmarks Favicon StumbleUpon Favicon Technorati Favicon TailRank Favicon

Next entry: Intel Igence.

Previous entry: Everything You Know Is Wrong.

Comments

LonerVamp United States on 10/30  at  02:40 PM:

Ira’s article is rather bipolar. He makes a lot of odd arguments, but near the Enron illustration (which feels like just a thrown-in recent example just to be journalistic even though it has nothing to do with the topic) seems to accept the opposite of what he had been saying.

Maybe Ira just didn’t communicate his position clear enough. Perhaps he was intending to say that *initial* ethical *decisions* shouldn’t be done by IT. In that case, he would be correct, those decisions should be made by C-levels, HR, and Legal. IT can still take an infraction and say, “hey, this went against current policy which I am reading here in front of me.“

However, there are still two problems. First, like you mention, people don’t know what is proper when it comes to the convergence of ethics and computer systems and information. It takes IT to offer some insightm, technical knowledge, and sometimes just to plain breach the subject at all. Second, so many ethical things end up tracked and/or audited via the exact same technologies and processes that IT is performing anyway. You wouldn’t necessarily want one email gateway to check for unethical email use, while another one is set up just to check or AV. Granted, yes, you can do that, but why not put both on one box rather than scan email twice? (Yes, that is further attackable as an argument, but the illustration still counts.)

I also find it annoying to compare physical security with IT security. I think if the local IT security folks came by regularly with a hub and laptop and sniffed traffic in person for a bit, they might make some additional personal friendships in that fashion. It is obvious that people find it easier to be angry at an object or something anonymous, as opposed to scowling at a security guard in person and up close.

And I find the argument about education getting muddled due to trying to make too many points to end users who can only remember a few at a time to be misleading. If that is the case, then you adjust the education to give smaller tidbits.

shrdlu United States on 10/30  at  07:54 PM:

You make a good point, LonerVamp.  IT Security has to be careful not to be the decision-maker when it comes to questions of access or legal policies.  People often see the security group as the ones who approve access, when that shouldn’t be the case.  It’s the business managers who decide who gets access to what resources; the security group is just there to carry out those decisions on the technical level.

Likewise, it’s a very fine line between monitoring traffic for security breaches and monitoring for what are more properly audit, legal or HR offenses (such as viewing porn).  I would rather not be the “good taste police,“ and I have always fought being put in charge of monitoring web surfing, for example.  It’s not my place as a security manager to decide how much personal use of company resources is too much, and it’s not my place to decide whether having a woman in a bathing suit as a desktop background constitutes an infraction of anti-harassment policies. 

Having said that, though, my management consistently looks to me to be able to collect information on how the technical resources are being used or misused.  If they ask me to conduct a business analysis of how much web surfing is work-related and how much isn’t, I’ll take my best shot and just give them the data and let them make the final decision.  I get asked to provide a lot of analysis and recommendations on things that are always IT-related but not necessarily related to security.  But because security crosses all IT areas, we’re often the only group that works with all of the others. 

When it comes down to implementing any kind of organizational policy at the IT level, the natural reaction is to go to security to do it.  But I try always to stay on the implementation side and leave the policy-making where it belongs, in its originating department.

LonerVamp United States on 10/31  at  03:27 PM:

An excellent approach which I would take as well, if I were put in the position. smile

I have been spearheading our own data access processes lately (from non-existent to existent), and I definitely dislike being put in the middle of the discussion on authorizing access. Too often asking me to give someone access to data is mistaken to be them asking me to authorize their use of that data. I don’t authorize use, their manager and the data owner do that. I just push the buttons when the right people ask for them to be pushed. I also tend to act like the bumpers around the obstables of the amusement park bumper car tracks. People bounce around trying to get something done, and I keep them on course or from going way out in left field.

Perhaps they ask you all those IT-related things because you tend to know what you’re talking about! smile

Page 1 of 1 pages

Add a comment

Name:

Email:

Location:

URL:

Smileys

Remember my personal information

Notify me of follow-up comments?

Submit the word you see below: