Configure Application Policies

This option allows the administrator to create policies to deny application access, to set QoS traffic shaping priorities for certain traffic types, or to enforce rate limiting policies for applications.

Application Denial Policies

Using application denial policies, administrators can block specific applications if they are seen to be consuming excessive network resources, or enforce network usage policies such as blocking social media sites.

The following usage guidelines need to be taken into consideration when defining Application Denial Policies:

  • "www.corporate.com": This will block access to the host web server at the organization "corporate.com", i.e. the FQDN. It will not block access to any other hosts such as ftp, ntp, smtp, etc. at the organization "corporate.com".
  • "corporate.com": This will block access to all hosts at the domain "corporate.com" i.e. it will block access to www.corporate.com, ftp.corporate.com, smtp.corporate.com, etc.
  • "corporate": This will block access to any FQDN containing the text "corporate" in any part of the FQDN. Care should be taken to use as long as possible string for matching to prevent inadvertently blocking sites that may contain a shorter string match i.e. if the rule is "net" then this will block access to any sites that have the text "net" in any part of the FQDN or ".net" as the FQDN suffix.
  • *.corporate.com: This is an invalid rule. Wildcard "*" and other regular expressions cannot be used in any part of the FQDN.
  • "www.corporate.com/games": This is an invalid rule. The filter cannot parse and block access on text after the FQDN, i.e., in this example it cannot filter the micro-site "/games".

Note: Many global organizations have both a ".com" suffix and country specific suffix such as ".co.uk", ".fr", ".au" etc. To block access to, for example, the host web server in all regional specific web sites for an organization, a rule like "www.corporate" could be used.
Note: Many global organizations use distributed content delivery networks such as Akamai. In such cases creating a rule such as "www.corporate.com" may not prevent access to the entire site. Further investigation of the content network behavior may need to be undertaken to fully prevent access.

QoS Rules

Implement application Quality of Service (QoS) rules to mark traffic with 802.1p or DSCP headers and prioritize according to the uplink and downlink priority selected. QoS rules can be created and applied to any of the system-defined applications or to user-defined applications.

Rate Limiting

Rate limiting rules can be applied to any of the system defined or user defined applications. Set the maximum uplink and downlink rates (0.25 ~ 20 Mbps) that the application can consume.