Managed EDR

We're using 3/4 of the "Huntress Stack", it would be really appreciated if there is some kind of "loyality program" or reward system for customers commited to you as vendor :)

Currently when logging in the user is presented an email field, and a button that says sign in with SSO If the user fills in their email, then hits this SSO button, they are redirected to another email field where they have to fill this in again and hit another button. Allowing the email value from the previous box to carry over would be awesome and remove the additional button click(s). Ideally filling in your email and selecting SSO on the first screen should take you directly to your SSO provider!

Want to be able to set a start date for expected rules so that when a client gives us the start and end date of a trip we can add the schedule in when they tell us instead of having to schedule in to do it on the day they leave.

Partners could establish what RMM they use and if another RMM appears on a machine under their management, an alert/isolation could take place. This could prevent an attacker from leveraging what's typically viewed as trusted RMM software as a persistence mechanism other than an autorun.

Allow specific IP-ranges not only countries in whitelists. Both for organization and per user. Have certain applications in a country I don't want to allow.

I'd love it if Huntress could provide information or an alert if an organisation uses MDE across the board but only default Defender is running on a given agent.

Adding additional telemetry streams and views to be able to better identify lateral movement, increasing our overall efficacy and being able to better pinpoint specific attack types.

Add the capability to have the Service and Display Name of the huntress agent list our Company name and maybe even display in Add Remove Programs. If our customers are working on their systems I want them to know the application is part of our tool/product suite.

Hello, We are evaluating Huntress and found it very impressive. We noticed that there is no support for + 39 country code. We don't feel secure enough without this kind of support. We think that every country should be fully supported

Case: Exclude specific filenames regarding the stored passwords scan. Not all files with 'password' in the path- or filename hold actual credentials. Example: Some of our customers are working with 1Password. Every time documention on how to use 1Password or how to implement SSO is opened, we get an Alert because the filename "1Password SSO Configuration" has 'password' in the title. Solution: Please make it possible to exclude certain specific filenames or pathnames from the automated stored credential scan so we can filter out that particular filename over 1 tenant or account-wide.