Read-only keys are desired at both at the organization level, and at the partner level. It feels odd to use a read-write key to fetch the installer, and we are likely to develop reports at the partner level that will only read data, not write it.

Just like all the other column headers have a filter function. This will greatly help in drilling down to unknown / new assets when using tags to document already-analyzed findings.

Having a formal documentation repository for functionality within the system would be fantastic. Being able to have staff and customers self train/learn/lookup FAQ's in the system saves time for us as an MSP to perform formal trainings on every on...

Add search option under vulnerability parameters to search/filter on Severity on endpoint vulnerability grid

Several customers have commented on confusion in the UI and reports with the difference between Endpoint vulnerability and Remote vulnerability data sets. For ease of clarity to customers the Remote vulnerability naming should updated to network v...

Add functionality to enable triggers in the policy engine for software. Primary request would be to notify on new unapproved software detected. Additionally, I could see the potential for alerts on specific software found.

Add ability to remove organization after offboarding. Would be great if the agents could uninstall if the organization was removed

Would it be possible to have a progress bar or a file counter to show the progress of the scan?

Review potential for adding cloud connector for Drop Box as a source for PII scans

Currently we can only schedule vulnerability reports for agents. We also need to be able to schedule reports for vulnerabilities on the remote scans (network scans).