Agent Support for WFP
When enforcement is configured to use WFP, Secure Workload filters override Windows Firewall rules.
In WFP mode, the agent configures the following WFP objects:
-
Provider has a GUID and name, is used for filter management, and does not affect packet filtering
-
Sublayer has a GUID, name, and weight. The Secure Workload sublayer is configured with higher weight than the Windows Advanced Firewall sublayer.
-
Filter has name, GUID, ID, weight, layer ID, sublayer key, action (PERMIT/ BLOCK), and conditions. WFP filters are configured for Golder rules, Self Rules, and Policy Rules. The agent also configures the port scanning prevention filters. Secure Workload filters are configured with the FWPM_FILTER_FLAG_CLEAR_ACTION_RIGHT flag. This flag ensures that Secure Workload filters are not overridden by Microsoft Firewall rules. For each Secure Workload Network policy rule, one or more WFP filters are configured based on the direction (inbound or outbound) and protocol.
When port scan probes are sent to the host, the status of the corresponding flows is displayed as PERMITTED:REJECTED on the Policy Analysis page. Note that this is applicable to all agent versions up to 3.10.2.11.
For TCP inbound policy,
id: 14 , TCP Allow 10.195.210.184 Dir=In localport=3389
The WFP filters configured are:
Filter Name: Secure Workload Rule 14
------------------------------------------------------
EffectiveWeight: 18446744073709551589
LayerKey: FWPM_LAYER_ALE_AUTH_LISTEN_V4
Action: Permit
Local Port: 3389
Filter Name: Secure Workload Rule 14
------------------------------------------------------
EffectiveWeight: 18446744073709551589
LayerKey: FWPM_LAYER_ALE_AUTH_RECV_ACCEPT_V4
Action: Permit
RemoteIP: 10.195.210.184-10.195.210.184
Secure Workload agent configures Secure Workload Default Inbound and Secure Workload Default Outbound filters for inbound and outbound CATCH-ALL policy respectively.