;) |
;) |
;) |
| May 01, 2002 | a newsletter from TechTarget |
;) |
;) |
Windows 2000 in the Enterprise: Technology strategies in action
|
;) |
;) |
;) |
;) |
;) |
Instant messaging insecurity gains momentum
by Meredith B. Derby, assistant news editor
Using consumer-based instant messengers in the workplace may be cause for some serious security troubles, according to IM expert Jeremy Dies. Yet, many businesses today are relying on them to handle commercial/enterprise jobs.
| S P O N S O R E D B Y : NetIQ |
|
|
Need solid advice on securing Microsoft Windows .NET Server? Register now for the FREE eBook, "The Tips and Tricks Guide to Securing .NET Server." You'll gain best practices and technical advice that will open your eyes to Microsoft Windows .NET security. Get the inside scoop on legacy systems, .NET group policy, secure remote access, and emerging .NET enhancements.
FREE Security eBook from NetIQ - HOT off the Press!
|
|
A March 2002 Osterman Research study found that 84% of 164 businesses surveyed use instant messaging. The five main IM products organizations are using include AOL Instant Messenger, MSN Messenger, Yahoo! Messenger, Lotus Sametime and Microsoft Windows Messenger. AOL Instant Messenger was used by 68% of the companies, either officially or unofficially, according to the survey results. The survey also found that 24% of the companies have standardized on one IM system, with 65% of these companies using Lotus Sametime.
Standardizing on one IM service is ideal, said Dies. But, standardizing on an enterprise IM system is better. Enterprise IM installations can alleviate security issues more effectively than a consumer-based system, he said. Dies, offerings manager for advanced collaboration at Cambridge, Mass.-based Lotus Software from IBM, Corp., spoke with SearchWindowsManageability recently about the current issues with enterprise IM systems.
What are the benefits of using enterprise IM systems, as opposed to consumer-based ones?
When you bring an IM service in-house and manage it from an IT perspective, there are benefits on two levels: the corporate IT benefits and the end user benefits. From the corporate IT standpoint, the fact that it's secure is the most important. Then there's the fact that it's more manageable and controllable. The IT manager needs to have total control over who can access the IM environment, and he does with enterprise IM services. That could be only people in your company. Or, that could be only people in the company and some subset of your extended enterprise: customers, suppliers or partners.
>From the end user standpoint, they have the ability to integrate with the directory so they can pull groups they're already familiar with from the directory. So, they don't have to worry about obscure screen handles. It's also a network affect. If you have a bunch of people using all different IM systems, you might as well not have IM.
Why are consumer IM services more insecure than enterprise ones?
Frankly, IM is a security nightmare right now. People are using public (consumer) IM services for business purposes. That means they are sending unsecured, confidential information all over the Internet, over an AOL server or an MSN server, for example. The IT department has no control over this. So, not only is it unsecure because there's no guarantee that I'm talking to who I think I'm talking to, or I am who I say I am, but it's also not encrypted.
What are some of the specific capabilities enterprise IM systems have over consumer IM products?
One capability is the ability to embed presence information in business applications, which boosts efficiency and improves customer satisfaction. Embedding presence information means that users don't have a separate buddy list they have to launch every time that it's running separate on their machine. What users can do is have their presence, if you will, follow them around if they're on a corporate Web site. For example, in our Lotus intranet, there's a little window that shows the other people that are viewing that intranet page. As you go from application to application, it shows the other people that are there. So, there's kind of an instant community associated with that.
Why is it important for businesses to consider standardizing on one IM platform?
This is an end user driven technology. So from that perspective, when a company standardizes on an IM platform, it makes it simpler. If I have a colleague whom I need to communicate with and that person is using MSN and I'm using AOL, we might as well not be on IM. If we standardize from a corporate standpoint, then we're all using the same platform.
Why don't corporations take more strides to block users from running the less secure IM products, such as AOL or MSN?
A lot of companies have, actually. They block the ports that go through and prevent the users from using them.
Can you describe a new IM feature called Chat Logging?
This is increasingly important now, especially for financial services. All the trends are indicating that people are using IM for business purposes. That raises a lot of issues because those interactions need to be logged and managed. For example, in financial services, any interaction you have with a client needs to be logged for a period of seven years due to federal regulations. So, people that are using IM for these purposes are all of the sudden not in compliance with regulations. In addition to not being secure and being vulnerable, it's a regulatory compliance issue. Lotus, for example, adds the ability to log chats to comply with those regulatory bodies.
You also might want to log chats for a knowledge management system, to make them discoverable. You can actually capture that knowledge like it's done with e-mail so those chats can become permanent as well.
What's in the future for instant messaging?
I think we'll see a transition over time, as people become more comfortable with this technology, from having a separate, stand alone buddy list to integrating the concept of presence awareness inside of e-mail or a CRM application, for example. Rather than have a product just be an instant messaging server, it's going to a real-time engine where any other vertical application can be able to call someone's presence as a part of it. It's this concept of contextual collaboration, where if you're working in an e-mail, why should you have to jump out of that e-mail to launch a buddy list to instant message that person?
|
***********************************************************************
Do you find this email useful? Forward it along to a colleague.
***********************************************************************
|