If Nexpose and your target vCenter or virtual asset host are in different subnetworks that are separated by a device such as a firewall, you will need to make arrangements with your network administrator to enable communication, so that the application can perform Dynamic Discovery.
To perform Dynamic Discovery, the Security Console initiates connections to the vSphere application program interface (API) via HTTPS. You must configure your VMware vSphere deployment to communicate through HTTPS. The application supports direct connections to the following ESX(i) versions: To determine if the application supports a connection to an ESX(i) host that is managed by vCenter, consult VMware’s interoperability matrix at. To perform dynamic discovery in VMware environments, Nexpose can connect to either a vCenter server or directly to standalone ESX(i) hosts. Preparing the target VMware environment for Dynamic Discovery
Once you initiate Dynamic Discovery it continues automatically as long as the discovery connection is active. In response to these challenges the application supports dynamic discovery of virtual assets managed by VMware vCenter or ESX/ESXi. If you know what scan targets you have at any given time, you know what and how to scan. To manage their security effectively you need to keep track of important details: For example, which virtual machines have Windows operating systems? Which ones belong to a particular resource pool? Which ones are currently running? Having this information available keeps you in synch with the continual changes in your virtual asset environment, which also helps you to manage scanning resources more efficiently. Merely keeping track of virtual assets and their various states and classifications is a challenge in itself. Discovering Virtual Machines Managed by VMware vCenter or ESX/ESXiĪn increasing number of high-severity vulnerabilities affect virtual targets and devices that support them, such as the following:
0 kommentar(er)
