DNS allow list / cloud RMM and AV access for isolated endpoints
R
Robert Dana
Huntress now supports an IP address allow list for isolated hosts, but this doesn't work with Cloud RMM, AV, or other tooling which typically uses dynamic IP addresses for agent connectivity. Vote here if you'd like to see this capability added.
Even better, it would be great to hear what specific tools you'd want to use it with; the list of DNS names that need allowing for typical cloud tooling is long, and we could potentially preconfigure them (just check a box) for common-needed tools.
Matthiew Morin (Huntress)
Merged in a post:
Tooling Allowlist: Allow FQDN/DNS Names/Dynamic IPs/Load-Balanced IPs
J
Jason Pool
For cloud-hosted RMMs, only being able to allow by static IP limits our ability to use the RMM during host isolation. Allowing FQDN allowlisting would let cloud-based RMMs connect to an isolated agent to remediate issues.
Photo Viewer
View photos in a modal
T
Thomas ONeal
This feature would significantly improve ability to remotely perform remediation/hunting on an endpoint without being forced to put hands on the endpoint or release it from isolation in order to remote in.
Many RMM tools do not publish IP ranges, or use load balancing, etc and provide FQDNs for users to establish tool connectivity.
J
Jack Hebden
FQDN capability please !
E
Ethan Dakin
How many more upvotes/comments do you need before this Feature Request is addressed? We are new to Huntress and we absolutely need this for N-Able Take Control and N-Central. N-Able only publishes FQDNs which is what should be used anyway since IPs can change. This feature is needed ASAP if we are going to move forward with Huntress. The other acceptable option would be to allow us to give File Paths to our RMM on the local device that Huntress could exclude from Isolation and allow to phone home. This is the approach we currently have with SentinelOne and it works well.
B
Benjamin Scribner
Need Level RMM added.
P
Peter Kardel
yes please. How much longer before the cyber liability underwriters refuse to write policies for MSP with self-hosted RMM's?
J
Jeffrey Hunt
Reminder, this needs to be bumped up in priority by a lot. Incidents are happening more frequently, and not being able to whitelist an RMM via an FQDN is very outdated. WE NEED THIS CAPABILITY
Y
Yossi Leitner
We urgently need the option to add IP blocks.
Already had lot of headaches because of the absence of this.
G
Gary Herbstman
Most tooling these days does not use static IPs. When we need to allow something like Splashtop or our RMM tool during the remediation process, we need to allow FQDN, not an IP address.
J
Jordy Minnebo
I was very annoyed that this was not implemented straight away... :)
Load More
→