Modernizing Authentication — What It Takes to Transform Secure Access
To know the future, you must understand the past and this has never beenmore the case in IT than it is today. The future will carry many thingsthat have foundations in the threats and exploits of the past year ortwo. Without a clear understanding of those things, the threats andvulnerabilities of the new year will seem overwhelming.
Here are my Top Five things to look for in the new year -- and why you'vealready seen forshadowings of them and should be prepared to deal withthem.
One way to really simplify the matter is to ask two questions: When wasthe last time you had an analog phone compromised and a keystroke loggerinstalled? Oh, yeah. Never. When was the last time any one of yourworkstations was compromised with any form of rootkit? A lot morefrequently than you'd like to admit to probably.
So, let's hook the phones up to the computer so any traffic sniffer willnot only have access to all your data, but all your strategic andtactical discussions on how to build your company successfully. Warningbells should be going off for even the most inexperienced IT manager atthis point.
To be practical about this, you are effectively setting your company upfor a single point of failure. And it's one that is known to occur on aconsistent, if not regular, basis, and one that can cause considerabledamage before identified and remediated. By adding your phone lines tothis matrix, you increase the amount of damage possible prior todiscovery.
I am not saying that you cannot implement VoIP securely. Setting up yourVoIP implementation should mean taking the necessary precautions tosecure the implementation appropriately. Securing the server that will behandling your phone calls, setting traffic on a protected subnet andother precautions specific to your environment are paramount. I've heardhow some are excited to be able to push phone calls over to wirelessaccess points for greater convenience. This indicates to me that they arereally missing the key point to security.
As with any technology, proper security implementation has to be includedfrom the outset. Attempts to add security as a secondary considerationare going to cause difficulties in the implementation. If you come to apoint where VoIP is no longer a discussion but a directive, it's time toswitch to arguing for appropriate security levels and valid descriptionsof the threats to corporate assets.
The .WMF vulnerability and exploit was reported late in December, andpublished in Microsoft Security Advisor 912840. It has shown thatMicrosoft is not in the clear for future events of this nature. Exploitswill continue to become more esoteric, as well as virulent in the sensethat they will affect a wider spectrum of the Windows operating systems.
In the case of the .WMF vulnerability, every version of Windows isvulnerable (even those Microsoft no longer supports security patches for)regardless of patch level.
Second, it's not just one portion of the operating system that isaffected but multiple major portions. The Windows Fax and Image Viewerlibrary (shimgvw.dll) is used to render images in Windows Explorer,Internet Explorer and other applications such as Lotus Notes. Anythingthat gives a view (whether thumbnail image or full view) of an image isat risk of processing malicious code in an image that's been downloadedfrom the Internet, or transmitted by email or instant messenger service.
System administrators will have to decide whether to use thrid-partypatches or wait for the official patch from the House of Gates. This willbe the case, as well, in future incidences.
This is the future -- more spam, more phishing, more really cooltechnology gone awry, and Microsoft making your life dificult, becauseyou can't live with them and you can't live without the operating system.