Application rule conditions
Application rule conditions are application awareness and control mechanisms that
-
identify and classify applications through IP traffic analysis
-
enable control with organized filters
-
require one enabled detector for each condition.
Application filters and control benefits
System-provided application filters help perform control by organizing applications according to basic characteristics, such as type, risk, business relevance, category, and tags. You can also create reuseable, user-defined filters using combinations of system-provided filters, or custom combinations of applications.
At least one detector must be enabled for each application rule condition in the policy. If no detector is enabled, the system automatically enables all available system-provided detectors, or the most recently modified user-defined detector. For more information about application detectors, see Application Detector Fundamentals.
You can utilize both application filters and individually specified applications to ensure complete coverage. Understand the application's requirements to effectively order access control rules.
Application filters help you to quickly configure application control effectively. For example, you can easily use system-provided filters to create an access control rule that identifies and blocks all high risk, low business relevance applications. If a user attempts to use one of those applications, the system blocks the session.
Using application filters simplifies policy creation and administration. It assures you that the system controls application traffic as expected. Because Cisco frequently updates and adds application detectors via system and vulnerability database (VDB) updates, you can ensure that the system uses up-to-date detectors to monitor application traffic. You can also create your own detectors and assign characteristics to the applications they detect, automatically adding them to existing filters.
The system characterizes detected applications using several criteria which form effective filters.
|
Characteristic |
Description |
Example |
|---|---|---|
|
Type |
Application protocols represent communications between hosts. Clients represent software running on a host. Web applications represent the content or requested URL for HTTP traffic. |
HTTP and SSH are application protocols. Web browsers and email applications are clients. MPEG video and Facebook are web applications. |
|
Risk |
The likelihood that the application is being used for purposes that might be against your organization's security policy. |
Peer-to-peer applications tend to have a very high risk. |
|
Business Relevance |
The likelihood that the application is being used within the context of your organization's business operations, as opposed to recreationally. |
Gaming applications tend to have a very low business relevance. |
|
Category |
A general classification for the application that describes its most essential function. Each application belongs to at least one category. |
Facebook is in the social networking category. |
|
Tag |
Additional information about the application. Applications can have any number of tags, including none. |
Video streaming web applications often are tagged high bandwidth and displays ads. |