No, the content/web filtering policy you applied to your LAN network will not be effective on the IP address 192.168.22.10 if it's added to the Sangfor global whitelist.

Here's how Sangfor NGAF prioritizes rules:

    Global Whitelist: Entries in the global whitelist take precedence over most other rules, including content/web filtering policies applied to specific networks.
    Network-Specific Policies: Rules applied to specific networks (like your LAN policy) are evaluated next.
    Default Policies: If no network-specific policies match, default policies are applied.

In your scenario:

    When traffic from 192.168.22.10 reaches the NGAF, it first checks the global whitelist.
    Since 192.168.22.10 is whitelisted, it's allowed to pass through without being subject to the LAN-specific content/web filtering policy.

No, the content/web filtering policy you applied to your LAN network will not be effective on the IP address 192.168.22.10 if it's added to the Sangfor global whitelist.

Here's how Sangfor NGAF prioritizes rules:

    Global Whitelist: Entries in the global whitelist take precedence over most other rules, including content/web filtering policies applied to specific networks.
    Network-Specific Policies: Rules applied to specific networks (like your LAN policy) are evaluated next.
    Default Policies: If no network-specific policies match, default policies are applied.

In your scenario:

    When traffic from 192.168.22.10 reaches the NGAF, it first checks the global whitelist.
    Since 192.168.22.10 is whitelisted, it's allowed to pass through without being subject to the LAN-specific content/web filtering policy.