Your
Show me an example of how this works
As routes are checked from the top of the table to the bottom:
- Traffic from Everyone to Trusted Sites will be allowed automatically. The content will be fetched from the site without being checked for the presence of embedded threats.
- Traffic from Everyone to Security Risks will be blocked automatically. No content will be fetched from these sites and any rules on the route will not be performed. This blocking action is repeated for a number of routes.
- Traffic from Everyone to Gambling will be blocked automatically.
icon. - Traffic from Everyone to Non-Business Related will be blocked automatically.
icon. - Traffic from Everyone to Chat & Instant Messaging will be allowed automatically, providing none of the associated content rules are triggered.
- All other HTTP and browser FTP traffic will be allowed, providing none of the associated content rules are triggered.
General considerations
You should remember that when a route has been satisfied the remaining routes are ignored. For example, when considering the route list as described in the above section, if traffic matches the route Everyone to Security Risks, any content rules for the route will be applied after which no further routes are processed. Therefore, when creating and positioning routes, you need to consider the following:
- Routes that allow or block access to particular zones should be placed at the top of the table.
- Below this, establish the most stringent acceptable use policy for allowing traffic that does not match another route.
- Routes for individuals or groups that are created to exempt them from rules should be placed higher in the table.