Comprehensive data protection for all workloads
Post Reply
ddasal
Influencer
Posts: 14
Liked: 2 times
Joined: Mar 27, 2018 3:19 pm
Full Name: Dustin Dasal
Contact:

ThreatHunter Service

Post by ddasal »

After upgrading to 12.3, our scan indicate the new ThreatHunter service is using tcp port 6175. There is no reflection of this in the documentation for ports required. I have a case open (07580196) where the engineer has informed us that this port will be used between various components for this new feature. If there is documentation on these new port(s), can someone point me to it, otherwise, when do we expect this to be added? Like all the other ports and port ranges used between infrastructure components, we need this change to also be reflected so we can make the proper changes and have justification for it.

Thanks!
Mildur
Product Manager
Posts: 10324
Liked: 2756 times
Joined: May 13, 2017 4:51 pm
Full Name: Fabian K.
Location: Switzerland
Contact:

Re: ThreatHunter Service

Post by Mildur » 2 people like this post

Hello Dustin

I'm checking with our RnD team the purpose of port 6175.
And we will update the port list in our help center when I got the answer.

Best,
Fabian
Product Management Analyst @ Veeam Software
ddasal
Influencer
Posts: 14
Liked: 2 times
Joined: Mar 27, 2018 3:19 pm
Full Name: Dustin Dasal
Contact:

Re: ThreatHunter Service

Post by ddasal »

Thank you!
Mildur
Product Manager
Posts: 10324
Liked: 2756 times
Joined: May 13, 2017 4:51 pm
Full Name: Fabian K.
Location: Switzerland
Contact:

Re: ThreatHunter Service

Post by Mildur » 3 people like this post

Hello Dustin,

We have added port 6175 to our help center documentation. This port is used locally by the Veeam Threat Hunter Service.
When you initiate a antivirus scan with Veeam Thread Hunter (Scan Backup, Secure Restore), we start a small executable that runs the scan of your backup content.
This executable will communicate with the Veeam Threat Hunter Service through port 6175.

Please note that this connection is entirely local on the mount server machine, and no remote machine will need to connect to port 6175.

Best regards,
Fabian
Product Management Analyst @ Veeam Software
jeremyrogers
Influencer
Posts: 11
Liked: 6 times
Joined: Jul 13, 2023 2:43 pm
Full Name: Jeremy Rogers
Contact:

Re: ThreatHunter Service

Post by jeremyrogers »

Thanks for the clarification. So if the mount server "trusts" the veeam components on a local scope (from a FW persective) there's no additional port rule requirement?
ddasal
Influencer
Posts: 14
Liked: 2 times
Joined: Mar 27, 2018 3:19 pm
Full Name: Dustin Dasal
Contact:

Re: ThreatHunter Service

Post by ddasal »

I appreciate the update and documentation!
Mildur
Product Manager
Posts: 10324
Liked: 2756 times
Joined: May 13, 2017 4:51 pm
Full Name: Fabian K.
Location: Switzerland
Contact:

Re: ThreatHunter Service

Post by Mildur »

there's no additional port rule requirement?
Correct. No external firewall ports to open. Traffic stays local on the mount server between two Veeam components.

Best,
Fabian
Product Management Analyst @ Veeam Software
Gostev
Chief Product Officer
Posts: 32237
Liked: 7598 times
Joined: Jan 01, 2006 1:01 am
Location: Baar, Switzerland
Contact:

Re: ThreatHunter Service

Post by Gostev » 2 people like this post

@Mildur in this case let's remove it from the documentation ASAP, as it is meant to document external ports that need to be open in firewalls. Otherwise customers will just open it along with all other ports, and every open port increases attack surface.
Mildur
Product Manager
Posts: 10324
Liked: 2756 times
Joined: May 13, 2017 4:51 pm
Full Name: Fabian K.
Location: Switzerland
Contact:

Re: ThreatHunter Service

Post by Mildur » 2 people like this post

Hi Anton

As discussed yesterday, we will review all "local-only ports" and remove them from the documentation.

Best,
Fabian
Product Management Analyst @ Veeam Software
Post Reply

Who is online

Users browsing this forum: Bing [Bot], madbana and 99 guests