URL Filtering Use Cases

The following use cases show how to use App-ID to control a specific set of web-based applications and how to use URL categories as match criteria in a policy. When working with App-ID, it is important to understand that each App-ID signature may have dependencies that are required to fully control an application. For example, with Facebook applications, the App‑ID facebook‑base is required to access the Facebook website and to control other Facebook applications. For example, to configure the firewall to control Facebook email, you would have to allow the App-IDs facebook-base and facebook-mail. As another example, if you search Applipedia (the App-ID database) for LinkedIn, you will see that in order to control LinkedIn mail, you need to apply the same action to both App-IDs: linkedin-base and linkedin-mail. To determine application dependencies for App-ID signatures, visit Applipedia, search for the given application, and then click the application for details.
Use Case
Features Involved
Prevent users from submitting corporate credentials to specific URL categories.
Subscribe to an external malicious URL feed
Block, allow, or define granular actions such as continue, alert, or override for URLs before you attach the profile to a Security Policy rule. Unlike the allow list, block list, or a custom URL category on the firewall, an external dynamic list gives you the ability to update the list without a configuration change or commit on the firewall.
Control Web Access
Grant different groups of users varying levels of access to sites in particular URL categories.
Block download of high-risk file types
Prevent users from downloading risky file types from specific URL categories.
These use cases rely on User-ID to implement policies based on users and groups and a Decryption to identify and control websites that are encrypted using SSL/TLS.

Related Documentation