Comprehensive data protection for all workloads
Post Reply
cosmik
Enthusiast
Posts: 74
Liked: 10 times
Joined: Jan 23, 2021 10:14 am
Full Name: Michael Pappas
Contact:

Securing console access

Post by cosmik »

I'd like to limit access to the B&R console (hosted on our BR server VM). Would firewalling port 9392 to allow only localhost access do the job?

Would allowing access to 10003/tcp and 9396/tcp only from localhost be a solid idea here?

I'm asking since I'm certain that some advice regarding hardening the BR server included removing the console from the main server altogether. Although feasible in my installation, it would lead to a worse setup security-wise, hence for my questions here...
PetrM
Veeam Software
Posts: 3626
Liked: 608 times
Joined: Aug 28, 2013 8:23 am
Full Name: Petr Makarov
Location: Prague, Czech Republic
Contact:

Re: Securing console access

Post by PetrM »

Hi Michael,

Please have a look at this table for the full list of used ports.

Thanks!
cosmik
Enthusiast
Posts: 74
Liked: 10 times
Joined: Jan 23, 2021 10:14 am
Full Name: Michael Pappas
Contact:

Re: Securing console access

Post by cosmik »

Hello PetrM,

I've seen the table, in fact that's how I came up with 9392, 10003 and 9396. What I am asking here is:
1) whether B&R will work just fine if the console is firewalled to allow access for these 3 ports only from localhost (that is, someone could not install a console in my network and be able to access the BR server)
2) whether other ports should be included, always with regard to console access
PetrM
Veeam Software
Posts: 3626
Liked: 608 times
Joined: Aug 28, 2013 8:23 am
Full Name: Petr Makarov
Location: Prague, Czech Republic
Contact:

Re: Securing console access

Post by PetrM »

1) I don't see a reason for any issues with Veeam B&R if firewall rules are correctly set.
2) You should include only those ports that are listed in the table.

Thanks!
Post Reply

Who is online

Users browsing this forum: No registered users and 59 guests