Java is currently the leading exploit vector for Windows machines, and Java vulnerabilities are packaged into many of the “exploit kits” available in the darker corners of the Internet (see http://krebsonsecurity.com/2010/10/java-a-gift-to-exploit-pack-makers/). Internet Explorer, Flash Player, and even the Windows operating system itself have done a good job of either improving the security of their products or improving their patching processes. Java, however, still lags noticeably behind in both user/media awareness and quality of code. According to some statistics, Java vulnerabilities account for up to 70% of successful exploits, making it a veritable nightmare from a security perspective.
The browser is a gateway to the Internet, to applications, to data, to the corporate intranet. Outside of the office, its not uncommon to switch between browser versions between devices: or even have different browsers on the same device. My Google App world is ably accessed from a Chrome experience synchronised between devices, but I have Internet Explorer on-hand, and Firefox still gets a run out all be it increasingly less so.
Indeed, for many corporations such care-free browser relationships are equally common. This might be because different browser versions are required to maintain access to legacy applications; to give users more choice; an effort to reduce the impact of a browser security issue. Alternatively, because control of different browser environments has been complex in the past, it is deemed less cumbersome and risky to mandate a single browser environment.
With the release of Catalyst, can care-free relationships be afforded a level of sensible protection? Can restrictive single-browser choices be relaxed and more business user friendly? Browsium intend Catalyst to reduce helpdesk calls and improve IT security allowing more granular control of all browsers in the enterprise and how does it do that?
A browser is a gateway to the Internet, to applications, to data. Many home users have multiple browsers; increasingly many corporations do, too. This might be because different browser versions are needed to maintain access to legacy applications while offering modern access to the Internet. Maybe it is to give users more choice. Maybe it is in an effort to reduce the possibility of a security breach. Maybe it is because users have just installed a second browser because they can. Regardless, managing user use of multiple browsers—so they are working productively and not bogging down the help-desk—is a complex undertaking.
Browsium, which has developed Browsium Ion to allow management of Internet Explorer, is looking to solve this multi-browser problem with Catalyst.
Reports on IE6’s death are often greatly exaggerated. A number of sites do offer statistics for consumer Internet browser share, but enterprise users are another breed and have a different browser use profile: IE6 is still there alive and well in a large swathe of enterprise desktops. This puts a risk on projects that look to move an organisation beyond Windows XP.
To address this, Browsium have built on their experience in providing a solution to IE6 compatibility to launch Browsium Ion. Browsium have designed Ion to enable IE6 and IE7-dependent web applications to run unmodified in an IE8 or IE9 tab.
The end of life for IE6 is tied to Microsoft XP/Server 2003.. the clock ticks to 2014. Can Ion address the compatibility problems for corporates and still stay on the right side of Redmond? Will Browsium Ion get migration projects shackled by a reliance on IE6 going?
With a little over 28 months left until Microsoft ends all support for Windows XP and with Internet Explorer 6, the time to consider their replacements is long overdue. While Microsoft and others have acted to deliver tools to assist with Windows 7 migration activities little effort has been made to address the challenge of IE 6. One of the others, Quest, has released an IE 6 rescue package. However, if anything, Microsoft’s only visible response has been to act stymie the actions of those withing to offer a solution. Continue reading Quest delivers IE 6 rescue package
Application Virtualization allows users to use potentially conflicting software in the same workspace. Towards the end of 2010 there was a great deal of discussion about the complexity of using application virtualization to finally let corporations end their dealings with the recalcitrant Internet Explorer 6. Continue reading Browsium Release Candidate available: time to put Internet Explorer Virtualization issues to bed?