Reporting & Dashboards

I noticed that ScreenConnect instances remain visible on the Command Center dashboard even after deleting related files. It would be beneficial to have a feature that allows us to delete or clear these instances from the dashboard, providing a cleaner and more accurate view of active connections.

Currently, the Agent page does not display firewall-specific issues, which can lead to confusion. It would be beneficial if the Agent page could reflect the same firewall issues flagged on the Overview page. This consistency would help users quickly identify and address potential issues across different views.

It would be advantageous to have a dedicated dashboard within Huntress for tracking cloud app logs. This feature would enhance the ability to monitor and analyze logs from various cloud applications in a more organized and efficient manner.

I find it inconvenient to navigate through multiple screens to access exclusions. It would be beneficial to have direct access to exclusions from the agent configuration screen, allowing me to test exclusions on a single host before applying them company-wide.

Navigating the dashboard can be confusing due to the similar appearance of global and organization settings. It would be helpful to have a clearer distinction between these tabs to improve user experience and prevent navigation errors.

I noticed that while a scan is running, I can't see the progress or the number of files scanned so far. It would be beneficial to have this information displayed in the Huntress interface to better monitor the scan's progress.

Currently, the dashboard only shows MFA as enabled if Microsoft Authenticator is used. It would be beneficial if the system could recognize and display the status for third-party MFA providers as well. This would provide a more accurate representation of the MFA status for users who rely on alternative MFA solutions.

Hi, I would like to see more information about the handling of incidents to determine if the threat has been removed or actions are pending on the device (eg a reboot). Case and point, whilst Huntress reported an incident was resolved, when a Huntress analyst checked on the backend, there was still a reboot pending on the device in question. If I see a green tick and resolve status, I want to be confident that all actions are complete and if a reboot is pending, then I can contact the end user to perform a quick reboot etc. I dont want to wait to see if the incident is going to come back the next time a Huntress scan kicks off.