Managed EDR

Since Huntress Potentially Unsecured Credentials have a 30 day cool-down between Incident Reports this can leave partners unaware if the machine has detections for multiple files. This data is normally only exposed to partners via Investigated Signals or Incident Reports, both of which do not populate with new PUC data inside the 30 day cool-down. If we had a central place partners could view these detectors partners could tackle all of these files at once rather than wait for reports to trickle in over time. * Request from ticket 115283

I know Huntress is GDPR compliant. But I think it would be way better for europeans to be able to choose the data to be stored in a Europe based amazon data center.

Currently, the notifications (enrollment and reminders) for the Managed Learning are not looking at the account level settings and do not allow for editing on the individual assignments. It would be nice if the Managed Learning pulls the notification settings from the Account Settings for Assignments, this way it helps to maintain an automated/hands off management of the system but allows clients to request customization to their notifications.

We would love for Huntress to also feature a command shell option that we could hit. This would help investigation when a device is isolated as well as another way to start or stop processes.

Show installed software and any CVEs attached to that version of software. This is handy when checking machines which require updates for things like Cyber Essentials.

Add the ability to restrict access to the web control panel (Huntress and Curricula) to only a specified, registered IP address or address range.

Please can Huntress look at incorporating Microsoft Smartscreen DNS filtering into the Huntress Managed Anti Virus offering as per: https://petri.com/microsoft-defender-endpoint-network-web-protection-macos-linux/ Thanks

A column in the incidents table that indicated which users marked an incident as resolved.

As an MSP we have some accounts that we co-manage with IT at their organization. We resell Huntress as a service. It would be great to be able to set admins at an account level to be able to manually isolate and deisolate hosts. This can be current admin or something like adding a checkbox that adds the permissions or a separate "super" admin that has the permissions. There are users that we trust to remediate issues at their organization. With remediation, the ability to remove isolation should be an immediate option at their discretion.

An app for huntress to enable direct notifications rather than via email for example and give quick access to see what the issue is or be able to manage remediation steps