vps
You can use the tool in another application, once you copy the executable and rename it to vps , simply launch it, and it will do the testing on that particular application. When testing your applications for vulnerabilities and other issues you can set it up on a virtual machine (VPS) on a cloud provider, and all the VPS applications installed on that account will automatically be scanned, while running them in a cloud provider to keep the CPU usage low.
Although the tool itself is based on the original OpenVAS tool, the code is very similar and it still uses the OpenVAS API. As a result it uses the OpenVAS cloud architecture to communicate with the cloud provider. Also, the actual time and CPU consumption of the processes running in the cloud provider is cached in a separate thread. However, at the moment there is no API or framework to communicate with other VPSs using this method.
The current version is based on an older version of OpenVAS, however it uses the Cloud-vPS framework. It also allows to use other cloud providers by using the VPS property to pass the IP address of a virtual machine hosting the tool. The currently supported cloud providers are Amazon, DigitalOcean, VirtualBox, Varnish, Rivet Networks, OpenShift, AWS, CloudClient, Serversquid, and PCPap.
All the API functions and properties can be accessed with the FING command (codice_1), available in PowerShell or Open PowerShell as well as in the PowerShell Modules, called Hyper-V XML Scripts, that you can find on the MSDN.
From this point, the framework can work in your virtual machine, sending and receiving the different API calls, performing the checks, and using the tools in different virtual machines.
You can see more information about the framework on MSDN.
You can find the vps.exe on the Hyper-V PSC. For more information about how to use it with VirtualBox, Microsoft Virtual PC, and Hyper-V, please refer to the documentation available on GitHub.
