While responding to a security advisory may not be a daily occurrence in a VMware vSphere environment, the occasion still arises when a prompt response is needed. This will depend on a number of different things, like how critical the threat is, and what processes your organization may already have in place. If you don’t have a security advisory response plan for your VMware vSphere environment, now is the time to create one. For some reason, many are hesitant to reach out to their organization’s information security team. Many see them as the enemy since a conversation with them usually results in more work for an administrator. The fact is your information security team is there to help you protect your environment and your data. Here are a couple things to think about as a VMware vSphere administrator when a threat arises.
Ready to reach out to them and have a conversation about your VMware vSphere environment? Are you just starting to think about security and how it relates to VMware vSphere? Here are some things to help get you in a more secure mindset.
Pay Attention Key Advisories
In the event of a security advisory, you will be notified by VMware. You can also follow VMware Security Advisory and Response on Twitter for the latest advisories. Is this your first time looking at a security advisory? Let’s take a look at a recent one, and see if we can make sense of it together. This advisory is named VMSA-2018-0002, which means it is the second VMware Security Advisory of 2018.
(NOTE: This is a screen shot taken from VMware’s Security Advisory site for illustrative purposes. Always check the security advisory for the latest information, in this case, the link is here: VMSA-2018-0002. Do not save security advisories to your computer for later use, always check the active link for the latest information.)
First, let’s look at the severity. In this case it is important, which means we need to read and understand it, and start thinking about how we can address it in our environments. If this advisory was critical, like VMSA-2018-0001, it means we need to act on it as soon as possible if our environment can be compromised by it.
Next, you will see information on the dates that the advisory was announced, and when it may have been updated.
Then, you will see the CVE number of the advisory. CVE stands for Common Vulnerabilities and Exposures, and it is a way to consistently track a vulnerability. While each vendor will release their own security advisories, they will all reference the common CVE number. You can find out more about CVEs here.
Next, you can read on to learn more about the specific threat, and what VMware products are impacted by it. Now that we understand more about what an advisory is and what information it gives us, what do we do now?
Plan Your Response
Your response will depend on a number of things, such as how many of your hosts are impacted, the business applications they run, and the severity of the treat. This is where you should be talking to your information security team to understand the wider impact of the security advisory. In some cases, the decision may be made to wait before taking any action. In other cases, the decision may be to patch immediately. Whatever the case is, it is important to have processes in place.
For example, if the decision is to wait before acting, part of your process may be to monitor the security advisory for changes, and re-assess after any updates. If the decision is to patch, you may decide to patch in your regular maintenance window, or you may need to request an emergency maintenance window.
A Word On Patching
When there is a critical advisory, you may tend to err on the side of caution and patch your environment as soon as possible. While this is great from a security perspective, it is important to ensure the rest of your environment is not broken as the result of a patch. This includes checking compatibility between the new version of ESXi you may be patching to if you are going to a new release and the things that interact with your vSphere environment such as your hardware, storage, and backup software. Don’t forget, when it comes to patching your environment, Update Manager is built into VCSA, and easy to use.
Even in the event of a critical patch it is important to maintain standard operating procedures, which usually involve testing the patch in development or test environments before moving it to production. This can of course be done on an accelerated schedule provided you have the buy in from your management team. In this case, the information security team may be able to help you communicate to management in the event a critical vulnerability requires immediate action.
But What About My VMs?
Usually, you virtual machines will be covered by their respective operating system operations team. For example, in the event of a Windows vulnerability, the windows operations team will often be the ones remediating the threat. As a VMware administrator, it is also important to have an understanding who is responsible for the workload being hosted in your environment. You should confirm what teams have operational responsibility for the virtual machines in your environment, and ask them to review their information security procedures with you. If they do not have any, this is another opportunity to reach out to your friendly neighborhood information security team. They won’t bite, I promise.
These are just a few things to think about as a VMware vSphere administrator in today’s world. Becoming familiar with security processes and procedures now will help you act swiftly and confidently in the event action is required to protect your VMware vSphere environment against a threat.