Create a Custom URL Category for Cloud NGFW on AWS
Palo Alto Networks provides a set of predefined URL filtering categories. You can also specify your own URL filtering categories using a customer URL category object. For example, create a custom list of URLs that you want to use as match criteria in a Security policy rule. This is a good way to specify exceptions to URL categories, where you’d like to enforce specific URLs differently than the URL category to which they belong.
Create a Custom URL Category
- SelectRulestacksand select a previously-created rulestack on which to configure a custom URL category.
- Select.ObjectsCustom URL CategoryCreate Custom URL Category
- Enter a descriptiveNamefor your custom URL category.
- (optional) Enter a description for your custom URL category.
- Enter one or moreURL List, one per line.
Basic Guidelines For URL Category Exception Lists
- Enter the URLs of websites that you want to enforce separately from the associated URL category.
- List entries must be an exact match and are case-insensitive.
- Enter a string that is an exact match to the website (and possibly, specific subdomain) for which you want to control access, or use wildcard characters to allow an entry to match to multiple website subdomains. For details on using wildcard characters, review Wildcard Guidelines for URL Category Exception Lists.
- Omithttpandhttpsfrom URL entries.
- Each URL entry can be up to 255 characters in length.
Wildcard Guidelines for URL Category Exception Lists
You can use wildcards in URL category exception lists to easily configure a single entry to match to multiple website subdomains and pages, without having to specify exact subdomains and pages.
Follow these guidelines when creating wildcard entries:
- The following characters are considered token separators: . / ? & = ; +Every string separated by one or two of these characters is a token. Use wildcard characters as token placeholders, indicating that a specific token can contain any value.
- In place of a token, use either an asterisk (*) or a caret (^) to indicate a wildcard value.
- Wildcard characters must be the only character within a token. For example, www.gmail*.com would be invalid because the asterisk follows other characters. An entry can contain multiple wildcards, however.
How to Use Asterisk (*) and Caret (^) Wildcards
Use to indicate one or more variable subdomains. If you use
*, the entry will match any additional subdomains, whether at the beginning or the end of the URL.
Use to indicate one variable subdomain.
mail.^.commatches to mail.company.com but not mail.company.sso.com.
Do not create an entry with consecutive asterisk (*) wildcards or more than nine consecutive caret (^) wildcards—entries like these can affect firewall performance.
For example, do not add an entry like
mail.*.*.com; instead, depending on the range of websites you want to control access to, enter
mail.^.^.com. An entry like
mail.*.commatches to a greater number of sites than
mail.*.commatches to sites with any number of subdomains and
mail.^.^.commatches to sites with exactly two subdomains.
URL Category Exception List—Wildcard Examples
The following table displays example URL list entries using wildcards and sites matching these entries.
URL Exception List Entry
Example Set 1
Example Set 2
Example Set 3
any site.com subdirectory
Recommended For You
Recommended videos not found.