Security vs. Usability - A Good Fight
Oh boy, a good old slugging match, and from two writers for the same magazine, no less. Bob Lewis writes on Information Security, Off the Deep End in response to Roger Grimes' Unauthorized Applications (still) a bad idea.I find myself in agreement with both points of view. I have great sympathy for Roger's (as well as most IT managers') dilemma in trying to keep the place secure in the face of increasing pressures. At the same time, though, Bob correctly observes that people do unsecure things because they are trying to do their jobs.
So how do I reconcile the two? Actually, I think Bob has most of it right, as he observes that a good IT department will be listening to its users and have appropriate tools in place. If someone wants to work from home and get data from the office there should be some type of VPN connection and either access to files or Citrix in place to make that possible in a secure manner. Need a laptop because you need the applications as well and either don't have the bandwidth or some other restriction? That should be thought out and machines should be available as well.
Where Roger is correct, however, is that user's shouldn't be allowed to use applications that haven't been through the acceptance process. The word "process" isn't meant to imply some long, drawn-out affair. It is meant to see that IT supports only the number of applications it really needs to, and that it has a decent handle on the security implications of those it supports. Otherwise, you could easily have half a dozen (or more) IM solutions running around, with significant support and security implications. As Bob says, implement a secure corporate-wide IM solution.
Security needs are valid, and with the ever-increasing number of security violations that are in the news, no organization can afford to ignore them. What the IT department needs to do, in conjunction (hopefully) with top management, is strike an effective balance between the security needs and efficiency / productivity needs of its internal customers. This implies, of course, an IT department that is "on the ball" and listens to what its users need to be effective. Easier said than done, of course, but after all, IT is (typically) in the internal customer service business. If you're not delivering what users need and what the organization needs, why are you around?