Feature Requests

The data that the ESXI inspector pulls for VMs is fairly limited if the following information could be grabbed it would be a significant improvementHard Disks (datastore path \ file name, Thin\thick provisioned, size)Disk Drives\Mapped ISOsvNICs (IPs, Adapter type)VMware Tools status\version

It would be great if the purchase date and warranty expiration were captured.

We bill based on storage usage in S3 buckets and having a single report that would have all clients and buckets with usage would be extreamly time saving.

Please add support for Virtual sonicwall appliances

I'm looking to get the "DPI-SSL-CLIENT" information pulled, as documented here: https://sonicos-api.sonicwall.com/#/dpi-ssl-client/get_dpi_ssl_client_baseUse Case: While the zone on/off alerts for security services are helpful, the zone can have it enabled but the service itself can be disabled. This one will pull DPI-SSL information and configuration for metrics and actionable alerts.

I want to implement this client-wide--for example, make all low+ risk users MFA upon login (regardless of trusted device status)--but cannot unless it is scanned.

Currently, a domain that has private registration causes an inspector error. Instead, it should be identified as private and include pertinent information from whois. At a minimum, it usually lists the registrar and DNS servers, created, updated, etc.Additionally, if a name is not registered, instead of an error, identify this as an unregistered domain.

Current one in AD does not account for cloud only logins

I would like to see in Lionguard which Edition uses an environment (Duo MFA, Duo Beyond, Duo Access) so that we can read out by means of a Metric. Why is this important? Duo has different license types, each with its own price. I then want to create a metric per license type that I can use to map with the correct Duo license/service type for our billing integration with Autotask. Now as a workaround I have created a group with the license type in the name and based on that I have created a metric. Unfortunately, we also have customers for whom this does not work well because these customers also have Duo users who cannot be made members of these groups.This information can be read in via the API as follows: https://duo.com/docs/accountsapi#get-edition

This would allow us to see what model devices we have at each client.