The devil is in the details with VMware audits

It is said that in this world nothing is certain, except for death and taxes. But, as license management experts, we can tell you that software audits are a certainty as well. You might hope and keep your fingers crossed for the publishers to skip your organization, but that’s not how it works and if there is something to worry about, this will definitely not help. Properly managing your software licenses, on the other hand, is the action you would want to take.

Even though Oracle, IBM, SAP and Microsoft are usually the most feared publishers in terms of audits, VMware should not be ignored either. This since audits have been on the rise as virtualization software faces increasing competition, becomes more commoditized in the industry, and VMware is looking for opportunities to boost their sales.

As the best defense starts always with a strong preparation, it’s useful to know what a VMware audit entails and what the auditors look for, as well as what are the most common issues around license compliance.

With VMware, an audit will consist of three major phases: notification, self-declaration and validation, and closure. When performing an audit, VMware is (like any other publisher) usually looking for evidence that your company has installed more licenses than it has purchased. VMware, however, is more concerned with the interpretation of documents. They are looking for any indication that the licenses are not being used in the way they are intended or where they are intended to be used.

In our “The devil is in the details with VMware audits” whitepaper we cover in detail the audit phases, the specific aspects you need to pay attention to and the risk control strategies that will help you ensure you are compliant.

This article was published on 24-05-2018