How to securely use Windows XP after support ends

While support for Windows XP ends today (Tuesday, 8 April 2014), Gartner Fellow and vice president Neil MacDonald has said that organisations can reduce the risk of continued use of the venerable operating system.

In a statement issued on Tuesday, 8 April 2014, MacDonald said that any system, supported or not, carries risk.

“For the majority of use cases, XP can continue to be used with the risk managed to a tolerable level, without requiring the enterprise to pay Microsoft for expensive custom support while migrations are completed,” MacDonald said.

“While doing nothing is an option, we do not believe that most organisations (or their auditors) will find this level of risk acceptable,” he added.

Gartner recommended the following 10 best practices for using Windows XP beyond 8 April 2014:

  1. Restrict Network Connectivity to the Minimum Possible — Protecting XP systems is easier when other systems can’t communicate to them over the network, the primary vector for attacks.
  2. Implement an Application Control Solution and Memory Protection — This can be accomplished using a dedicated solution, a host-based intrusion prevention system (IPS), or Microsoft’s Group Policy object (GPO)-based software restriction policies to establish a “lockdown” posture for XP to prevent the execution of arbitrary code.
  3. Remove Administrative Rights — This should be mandatory for all remaining users on Windows XP.
  4. Address the Most Common Attack Vectors — Web Browsing and Email: Remove Web browsing and email software from XP systems, and provide these capabilities from a server-based system that is up to date.
  5. Keep the Rest of the Software Stack Updated Where Possible, Including Office — Vendors of other software solutions and versions running on these XP systems may continue support. This further minimizes the vulnerable surface area that can be attacked.
  6. Use a network or host-based IPS to Shield XP Systems from Attack — Confirm that your IPS vendor will continue to research vulnerabilities and attacks on XP and provide filters and rules to block these attacks where possible.
  7. Monitor Microsoft — Microsoft will not publicly disclose if new vulnerabilities against XP are discovered (unless you have paid for custom support). However, pay particular attention to critical vulnerabilities that affect Windows Server 2003 as these will likely impact XP.
  8. Monitor Community Chat Boards and Threat Intelligence Feeds — Third-party threat intelligence feeds are an independent source of information. Communities of interest are expected to emerge specifically for sharing information related to XP.
  9. Have a Predefined Process Ready If an XP Breach Occurs – Have a plan to isolate XP workstations in the event of an attack that gains a foothold by quarantining these systems from a network perspective until mitigating steps are understood.
  10. Perform a Cost/Benefit Analysis – The cost and resources to implement the steps above might be better spent in accelerating the migration of the remaining XP systems, or it might be simpler to pay Microsoft for custom support.

If organisations do not implement these best practices, MacDonald said that they could consider paying Microsoft for custom support if the enterprises’ risk tolerance is low, or if regulations require.

Microsoft recommended on its End of Windows XP support website that users either upgrade to Windows 8.1, or buy a new PC.

The software giant warned that users should consider the age of their computer before electing to upgrade to Windows 8 and ensure that their programs and devices are compatible with the new operating system.

Pirate software costs SA businesses millions in fines – BSA

Windows 8.1 Update 1 launch date

Apple App Store price increase for South Africa

Office for iPad launched

Office 365 Personal price, launch date for SA

Latest news

Partner Content

Show comments

Recommended

Share this article
How to securely use Windows XP after support ends