The ENS Firewall has built-in rules (Core Networking) that allow network traffic for our signed executables. But, these processes must be signed with a specific certificate so that the ENS Firewall doesn't block network communication for our products.

The built-in Core Networking rules don't account for the certificate change. So, it's possible for ENS Firewall to block ENS ATP network communications when you use a non-default firewall rule set. For example, when you don't have a firewall rule that allows traffic through other rules, such as Allow all outgoing traffic.