SOLVED

Configure Windows 10 Firewall Rule for MS Teams In- & Outgoing

Brass Contributor
Hi guys
i need to configure in Endpoint security panel the Windows 10 Firewall. We would like to block all in- and outbound traffic. Also we will configure a rule for each app which will be allowed to communicate. For MS Teams i have issues to configure as it is installed in the userprofile.

Does anybody know how to configure that without using a Script outside the Endpoint security section?

Many thanks for your feedback
Marc
4 Replies

@marckuhn 

 

So far I am aware, you can't user uservariables such as %localappdata% or %username%... If you don't want to go down the scripting option..

 

Maybe opening the port necessary ?

TCP, Allow Ports 50000-50059
UDP, Allow Ports 3479-3481, 50000-50059

 

Maybe that would help 

Hi Rudy

thanks for your response. I'm not sure if that is what we want. I'm wondering if configure to block outbound traffic in Windows Firewall is not a configuration which is used a lot.

Do you configure it or not?

Best regards
Marc
best response confirmed by marckuhn (Brass Contributor)
Solution
We are using it to block some well known reverse shell ports and as example we also block port 21 (ftp) outgoing.

In a blog I have written you can see for yourself the results when blocking the port 21
So I guess its worth a try to test out on a test device? to see for yourself if it what you want?

https://call4cloud.nl/2020/07/the-windows-firewall-rises/
Hi Rudy

thanks a lot for your article, sounds great. I will check that and see if that is everything we need.

Best regards
Marc
1 best response

Accepted Solutions
best response confirmed by marckuhn (Brass Contributor)
Solution
We are using it to block some well known reverse shell ports and as example we also block port 21 (ftp) outgoing.

In a blog I have written you can see for yourself the results when blocking the port 21
So I guess its worth a try to test out on a test device? to see for yourself if it what you want?

https://call4cloud.nl/2020/07/the-windows-firewall-rises/

View solution in original post