1) In the asset-page, there is a cpe:o value, possibly from nmap - it would be great to get this returned by the api in the status (/api/scan/status) request
2) reverse-resolve the IP, and return "name" or fqdn or something along with the results from the /api/scan/status request.
in a "continuous" setting, the owner typically uses tools like this to discover NEW assets as well as vulnerabilities in old and new assets. Then it could be useful with OS-type and a reverse-resolv if found.
Just an idea...
1) In the asset-page, there is a cpe:o value, possibly from nmap - it would be great to get this returned by the api in the status (/api/scan/status) request 2) reverse-resolve the IP, and return "name" or fqdn or something along with the results from the /api/scan/status request.
in a "continuous" setting, the owner typically uses tools like this to discover NEW assets as well as vulnerabilities in old and new assets. Then it could be useful with OS-type and a reverse-resolv if found.
great work!