When creating policy, configure the ProxySG or Edge SWG to allow or deny traffic based on criteria such as IP address, destination URL, category, or protocol. When denying traffic, choose between Deny or Force Deny. This article explains the evaluation logic for each, specifically how they interact with subsequent layers and negated objects.
DENY Traffic matching a rule with a Deny action is blocked for that specific rule and layer.
Allow rule that matches the same traffic, the traffic will ultimately be permitted.Example Trace (Allowed by later layer):
FORCE DENY Traffic matching a Force Deny action is blocked across the entire policy.
Force Deny.Example Trace (Blocked despite later Allow):
Interaction with Negated Objects When a subnet or URL is negated (excluded) from a combined object, traffic from that source will result in a "No Match" for the rule using that object. Evaluation will continue to the next rule. If the next rule is a Force Deny catch-all, the negated traffic will be blocked.