Still running a Windows Server 2003?
You’ll want to read this.
As you may or may not have heard, the end of life for Windows Server 2003 is now set for July 14th, 2015 – meaning after that date, it will no longer be supported by Microsoft.
So, what does this mean for you? It means that, along with other support, Microsoft will no longer be providing any security updates to Windows 2003 servers, leaving them exposed to malware and open for attack.
Security pros and IT specialists around the globe have already begun preparing as there are still 23.8 million Windows 2003 Servers out there. Some are even going as far to call the end of life for this product the “biggest security threat of 2015.”
You can bet that most hackers have this date marked on their calendars and are eagerly awaiting its arrival.
Lucky for you, with this blog (the first of a series of five intended to outline your options and solutions) we’ll help you to ensure you’re adequately protected when the date rolls around. Right now, there are three paths you can choose to go down in order to prepare:
- Upgrade to a newer version of Windows such as Windows 2012 R2
- Migrate Windows 2003 workloads to the public cloud
- Stay on Windows 2003 for now
However, each of these three paths comes with their own associated challenges, namely:
- How to secure a hybrid compute environment and protect virtualized servers.
- How to secure virtual servers in the public cloud.
- How to secure Windows 2003 servers after July 14th, 2015.
Ultimately, the “do nothing” model is not an option as customers run the risk of no longer being compliant and leaving themselves vulnerable to malware.
At Intel Security we’re preparing materials to help you transition as seamlessly as possible, and overcome these challenges by securing your server environment no matter which of the three paths you decide to take.
Stay tuned for our next blog where we will outline in more depth each of the three migration options available to you and how you can overcome the challenges inherent with each. And, be sure to follow @IntelSec_Biz on Twitter for the latest security updates.