To the Public Cloud – and Beyond! Migrating from Windows Server 2003

Windows 2003 Blog 3.jpgAs you may remember from the last blog in this series, End of Support (EOS) for Windows Server 2003 goes into effect on July 15th, 2015. The clock is winding down, and we’re highlighting migration options available to those still running Windows Server 2003 in an effort to beat the buzzer.

Last week, we highlighted the first of three migration options available: upgrading to a newer version of Windows Server. Now, we will discuss the second migration path: moving to the public cloud.

Moving workloads to the public cloud has brought with it some real advantages in that it can help to reduce costs, provide greater agility, and enhance scalability. These benefits will most likely be realized as you move Windows Server 2003 based workloads into a public cloud environment.

However, a top concern when workloads are moved into a public cloud environment is security. As protection from a traditional network perimeter is not always available, a very common question is: what are the security controls that are in place for workloads that have moved into public cloud environments?

To answer this question, let’s take a look at the importance of security for your public cloud deployments starting with Infrastructure as a Service (IaaS).

Many enterprises mistakenly assume that public cloud providers for IaaS will protect their operating systems, applications, and data running on the server instances. While public cloud providers will secure the underlying infrastructure – it’s up to you to secure the virtual servers that run in that infrastructure. In other words, security is a shared responsibility in the cloud.

Luckily, we’ve come up with a solution that will help you break through the haze and gain complete control over workloads running within an IaaS environment: McAfee Public Cloud Server Security Suite.

This suite of security solutions is ideal for the public cloud, and uses hourly pricing so you only pay for security for the hours that your virtual servers are running in the cloud. The protection provided in McAfee Public Cloud Server Security Suite includes:

  • Comprehensive cloud security to extend and manage security policies for virtual servers in Microsoft Azure, Amazon AWS, and other public clouds such as those based on OpenStack.
  • Broader visibility into server instances in the public cloud via a powerful combination of blacklisting and whitelisting technologies.
  • Dynamic management of cloud environments in concert with on-premise endpoints and physical servers with McAfee ePolicy Orchestrator (ePO) software.

What about moving Windows Server 2003 applications such as email and collaboration into a Software as a Service (SaaS) public cloud environment?

If you’re planning on migrating to an environment such as Microsoft Office 365, McAfee Email Protection has you covered. This solution provides enterprise-grade security against targeted phishing threats, includes integrated data loss prevention technology, and protects Office 365 Exchange Online, Microsoft’s public cloud email solution.

Want to learn more about the security questions you need to ask about protecting email servers? Find all the information you need, here.

If moving to the public cloud doesn’t suit you or your business needs, fear not! Next week, we’ll take a deep dive into the third option available to those running Windows Server 2003: implementing additional protection for servers that cannot immediately be migrated by the EOS date.

In the meantime, follow @IntelSec_Biz on Twitter for the latest security updates. We’ll see you next week!

Windows Server 2003 EOS

This blog post is episode #3 of 5 in the Tech Innovation Blog Series

View all episodes  >