Managed EDR

I spoke to support on this. We have surveyed our user base and been sending them the free link to the SAT for password storing. The feedback is grim, none of them login to watch it. I am willing to bet that the same applies for the majority of people that send that out. This is a missed opportunity. We would like it, and I am sure Huntress would like it, as a way to give them training video quickly, but to ALSO promote SAT. Surely there is a way to publish that link as a public link, and then slap advertising around it for Huntress and us, the partner?

I manage my exclusions by group policy and MDM, and I'd like them to not be flagged as non-compliant. It would be good to have a way to provide account and organization exclusion lists to huntress that wouldn't actually apply the exclusions, just check the host exclusions against the list and consider them compliant.

Currently there is no control from Huntress to manage syslog sources, no ability to mark a source as illegitimate, or delete inerrant logs from an undesired source. I understand this can be managed by firewalls, but since it is not secured by TLS and SIEM ingestion has data and cost implications from within Huntress, managing this from Huntress grants control within same department/interface.

We are starting to see a lot of unwanted access escalations. Maybe this is not such a big issue in the US, but for europeans who travel a lot between our tiny countries, this is like americans receiving an Unwated Access escalation every time one of their users travel to a different US state, or even a different city. One way to greatly reduce the amount of notifications would be to cross-check the MDR locations with those seen in the EDR, or even on devices pulled through the Microsoft Graph API. Because if an account AND a PC is in use on the same IP / same strange country, then it's highly likely that it's just the user who's out travelling, and not actually unwanted access.

Would like to be able to add notes to the exceptions for credential documents found. We often have to move people to a password manager, but need the exception there temporarily and it would be nice to be able to add a note for one of my fellow techs to remember to remove them.

We want to have organisation level users, with sufficient privileges (Admin/security engineer), to act on escalations within their own organisations. These are capable people who know what to do and it reduces the workload for us as an MSP.

Hi, there are a few requests, one completed, for Halo PSA sync. Its there for tickets but its one way. Seems to me that a quick code improvement could give us two way sync. Far more importantly, we need billing sync please! We are moving to Halo from CW after 15 years in CW and the accounts team need this badly. Please push up the list!

It would be fantastic to see when our own agents are erroring and what errors they are experiencing for streamlined troubleshooting and documentation. If we're seeing the same error across 10 devices in a client tenant, it would be a lot faster to submit one ticket with the issue already narrowed down than 10 investigation tickets across the devices.

We would like to be able to change the hostname on the Huntress platform without having to change it in the Windows hostname or add a customisable field to better identify computers. Currently you can only change the huntress hostname if you change it in the Windows hostname.