Application Control, URL Filtering, and Content Security
Core concepts
Application Control identifies applications by signature (not just port), so you can allow/block by application, category, and risk. URL Filtering categorizes websites and blocks by category or explicit list. Content Security covers Anti-Virus, Anti-Bot, Threat Emulation, and file types. These blades appear as columns in the rule base (Application, URL Filtering, Content) and are enforced per rule.
How the blades combine
A rule can allow an application but apply a content-security profile that scans downloads. Understand profiles (predefined vs custom) and how they attach to rules. Know that HTTPS inspection may be required for URL/application visibility, and that bypassing inspection reduces effectiveness.
Traps in questions
- Assuming blocking a port blocks an application - Application Control matches by signature, so apps can run over any port.
- Forgetting that URL Filtering needs a category database and license.
- Confusing Application Control (what the app is) with URL Filtering (what the site is).
- Overlooking that content profiles are applied per rule, not globally by default.
Rule of thumb
Match the control to the intent: block the application with Application Control, block the site category with URL Filtering, and scan the payload with a Content Security profile.