Tooling Allowlisting for RMM by DNS Records/FDQNs
N
Noah Caldwell
We would like to be able to add tooling allowlistings for DattoRMM to Huntress so that when a device is isolated by Huntress, we can still provide support. The issue we are only able to specify allowlistings by individual IP addresses, and DattoRMM has many IP listings that are subject to frequent changes. Datto's solution is that they provide a FDQN that returns all current IPs that need to be allowed.
You find this in their documentation: https://rmm.datto.com/help/en/Content/1INTRODUCTION/Requirements/AllowListRequirements.htm#:~:text=Port%20usage.-,Allowing%20the%20Datto%20RMM%C2%A0Agent%20access%20to%20the%20internet,-FQDNs/DNS%20A
We would need to lookup all the IPs for concord-ips.centrastage.net and tunnel-ips.centrastage.net which total to be able 90 IPs and update them reguarlly to ensure we are able to remotely access isolated devices.
The settings that control this in Huntress are in the Settings > Managed Response > Tooling allowlist section at the bottom.
I am requesting to be able to add FDQNs which would ensure we are always allowing what is required and don't have addtional IPs from previous changes to the list for DattoRMM.
E
Ethan Dakin
Agreed, We need this functionality for N-Central as well.
M
Matthew Buehlmann
+1 this would be a big improvement for our IR capabilities!
A
Adam Brazie
Would love for this to be an option! As it is currently, we cannot make an exception for our NinjaOne platform as they only support FQDN for whitelisting.
P
Phill Hodgkinson
This also applies if you use SentinelOne (or other) as primary EDR. Support for FQDN, especially for some of the leading well established platforms would be very helpful.