VMware vCenter PAM Support

Summary

We are proud to announce to Tenable customers the latest enhancement with the introduction of the VMware vCenter API credential featuring Privilege Access Manager (PAM) Integration support. This functionality enables customers to authenticate to the vCenter API using either manual entry credentials or by leveraging one of our PAM integrations to retrieve the vCenter API credential from the specified PAM. 

The newly introduced credential serves the same purpose as our existing "VMware vCenter SOAP API" credential. However, it eliminates confusion by removing the term "SOAP" from the credential, emphasizing its compatibility with both REST and SOAP API versions. This update streamlines privileged access for customers, facilitating the use of PAM integration features.

With this addition, customers can now benefit from a more comprehensive understanding of their cyber exposure through credentialed vulnerability scans. Please note that the old credential will not be removed at this time to avoid any disruption to customer experience. Nevertheless, we strongly recommend that customers migrate to the new "VMware vCenter API" credential. This will be fully available in Nessus Manager and TVM on Wednesday May 15th, 2024. The release date for Security Center support is yet to be determined.

Supported PAM Integrations:

• Arcon
• BeyondTrust Password Safe
• CyberArk
• CyberArk (Legacy)
• Delinea Secret Server
• Hashicorp Vault
• QiAnXin
• Senhasegura
• WALLIX Bastion

Plugin Impacts

When using a PAM to authenticate to vCenter API in this new credential, please refer to our new plugin ID (186662) “vmware_vsphere_vcenter_settings.nasl” in the debug logs for any PAM related logs.

Example, if using VMware vCenter API with CyberArk support, the file will display as “vmware_vsphere_vcenter_settings.nbin~CyberArk”.

Release Date

May 15th, 2024 - TVM, Nessus; TBD for Security Center.