Web Usage Controls and Acceptable Use Policies
Domain 4 covers URL filtering, web reputation, dynamic content analysis, application control, and the Acceptable Use Policy (AUP) page. Expect questions on how a URL is categorized, what happens when it is uncategorized, and how AUP acknowledgment is enforced.
Filtering layers
- Cisco Talos URL categories (roughly 100) classify destinations; the Web Reputation Score (WBRS) ranges from -10 to +10, with negative scores indicating risky sites.
- Custom URL categories hold your own allow/block lists and can be referenced by access, decryption, and data security policies.
- Dynamic Content Analysis (DCA) fetches and classifies uncategorized pages in real time.
- Application Visibility and Control (AVC) identifies applications that URL categories miss, such as streaming, P2P, and social apps.
- Without HTTPS decryption the appliance sees only hostname/SNI; path-level categorization and content controls require decryption.
Acceptable Use Policy
- AUP text is displayed to users, optionally on first access or at a configurable interval such as every 30 days, and can require acknowledgment.
- The AUP is configured per access policy, and acceptance events are logged for audit.
- It is usually paired with a branded block page and Warn page so users understand the policy reason.
Worked example
A newly popular file-sharing SaaS domain is uncategorized and users are uploading company files. Reasoning: confirm in URL lookup that the domain is uncategorized with neutral reputation; add it to a custom category; block the File Sharing/Online Storage category in the relevant access policy; attach a Warn page and AUP. Do not rely on DCA alone - first-seen pages take time to classify. Then verify with Policy Trace.
Traps that cost marks
- Treating reputation as a category, or a category as reputation.
- Blocking the whole Uncategorized category and breaking legitimate new sites.
- Expecting the AUP to appear on HTTPS responses without decryption.
- Confusing Warn (proceed allowed), Quarantine (acknowledgment required), and Block.
- Assuming custom category entries are overridden by Talos categories; policy order decides.