Migrating to a New Application
Choosing to migrate to an entirely new application is perhaps the most difficult route to
take for any number of reasons. Lack of alternatives for a given operating system, data
migration, and impact on users are a few of the bigger challenges to be faced. In some
cases, choosing to migrate to a new application may also require a change in host operating
systems. Of course the new application must provide sufficient functionality to
replace the existing vulnerable application, but additional factors to consider before
migrating include the security track record of the new application and the responsiveness
of its vendor where security problems are concerned. For some organizations, the
ability to audit and patch application source code may be desirable. Other organizations
may be locked into a particular operating system or application because of mandatory
corporate policies. The bottom line is that migrating in response to a newly
discovered vulnerability should be done because a risk analysis determines that it is the
best course of action. In this instance, security is the primary factor to be looked at, not a
bunch of bells and whistles that happen to be tacked onto the new application.
Pages:
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845