Managed EDR

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.

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

-Batch add and remove exclusions At the very least do this in a table where the dashboard does not have to reload.

This happens all the time, customers pull systems off of maintenance, turn them off and put them in a closet. Then we delete all of our stuff and all is well. - we think - Then, something happens, they need that system and it's back online. Our RMM kicks in and sees that huntress is installed and moves on, when actually the system is out of compliance. Kind of a big operational gap in my opinion that should be easy for you guys to fix.

It would be great if the API would allow to do onboarding tasks like adding data sources to siem or add the defender for endpoint integration or the m365 integration. So we could use tools like Rewst to fully automate the onboarding of a new client.

I would like to see the following enhancements to External Recon: A way to create a printable report on a per tenant basis showing Recon results The ability to send a PSA alert to Autotask and others if a new port is opened or changed. The ability to pull Recon data via API for reporting to clients in monthly/quarterly reporting. The ability to annotate the results with notes or reasons why this port is open

Enable the control of Bitlocker from the huntress portal. Also Bitlocker Key storage.

When enforcing SSO it would be nice to be able to exclude an account as a breakglass that could be used in the rare circumstance a certificate every expired we could use that to navigate back into the console and renew it.

Currently the Filter applies to the first page when selecting the ScreenConnect module on the command center. Once you drill down on the hosts the filter is removed and entries over 30 days are shown. Could they get the option to clear out/filter out entries on that page that are older than 30 days.

A Canadian partner pointed out that some of our phishing scenarios are too easily identifiable because some of the content isn't relevant to Canadian citizens > Venmo or since the Canadian election has already passed, this scenario will not be relevant for several years. Ideally, more content with Canadian learners in mind. They want the ability to have the managed phishing & learning be scoped to country specific content and to be able to opt out of some campaigns/assignments if the content is not relevant to their customer base: i.e. - google auth to a M365 only shop. The want to be able to opt out of certain scenarios without unenrolling from Managed phishing on a month-to-month basis.