Carbon Black Cloud: Host-Based Firewall rules not applying because Windows network policy doesn't update when connecting to VPN

[#1]

Environment

• Carbon Black Cloud Sensor: All Supported Versions
• Carbon Black Cloud Host-Based Firewall
• Windows OS: All Supported Verisons
• Global Protect VPN

Symptoms

When connecting to Global Connect VPN, the Windows OS firewall policy is not updating to show connected to the "DOMAIN" policy, and instead shows "PUBLIC" policy is still connected.

Cause

This is a known Windows OS issue and not related to the Carbon Black Cloud sensor.

Resolution

This behavior is documented by Microsoft: Firewall profile doesn't switch to Domain when you use a third-party VPN - Windows Client