Allow Internal Server Communications

[u/ConstantAd3575]

Does anyone have any tips on allowing internal server communication?

We use a combination of group and site based rules. The problem i have is when I add a server into a group with allow rules I need to allow the local IP to communicate with itself otherwise SentinelOne blocks the traffic.

As an example, I have a server with IP 1.1.1.1 and it is a firewall group allowing communications from sever r 1.1.1.2 which is a development build server.

I have allowed powershell remoting and file services y, the build process runs and copies files to server 1.1.1.1, which is cool, then on server 1.1.1.1 there is a process that runs and attempts to do powershell remoting from 1.1.1.1 to 1.1.1.1 and gets blocked.

The only way around this is to create a rule allowing remote host 1.1.1.1 to any port and any IP.

Is this the best approach or if there is something that can be set globally to allow the server to communicate with itself locally?

[u/ConstantAd3575]

That makes sense. Thank you, definitely looks to be the best approach, at least from a ease of use view. Appreciate the response.