No consumer IM. IMO that is just a date leak accident waiting to happen. Especially if you allow any and all.
We provide internal OCS, but no gateway to public. We do have a public LiveMeeting server tied to OCS. My wifes company, a large computer OEM, allows Yahoo. She works from home, which means I support her laptop most of the time and anytime she has a problem, it is often related to Yahoo IM. Her computer seems to run slower with it. On Thu, Feb 18, 2010 at 3:43 PM, Kurt Buff <[email protected]> wrote: > Anyone out there care to share their policy and (very) general > implementation info on IM and personal video conferencing usage? > > Does your company, for instance, allow users to install and use any of > the major consumer IM/video apps and communicate directly to the major > public IM/video providers such as MSN, AOL, Yahoo! and Google? > > If your company does allow it, what does the company consider to be > the cost/benefit tradeoff WRT security and not using a centralized > IM/video server with gateways to public IM/video services? > > Also, what security concerns were looked at before implementation and > what measures, if any, were taken to mitigate them? > > If direct access to public IM/video services isn't allowed, is an > IM/video service provided for business purposes, and if so, what are > you using - MSFT OCS, or Openfire, or something else? > > If you can't comment on-list, but don't mind doing so off-list, I'd > certainly appreciate it. > > Kurt > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ > ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
