Creates a deny rule and configures the match criteria based on which packets are filtered and the deny access action applied
deny [app-category [<APP-CATEGORY-NAME>|all]|application <APPLICATION-NAME>] schedule <SCHEDULE-POLICY-NAME> (precedence <1-256>)
deny [app-category [<APP-CATEGORY-NAME>|all]|application <APPLICATION-NAME>] schedule <SCHEDULE-POLICY-NAME> (precedence <1-256>)
deny | Creates a deny rule and configures the match criteria. The options are app-category and application. |
app-category [<APP-CATEGORY-NAME>|all] | Uses application category as the match criteria
|
application <APPLICATION-NAME> | Uses application name as the match criteria
There are approximately 300 canned applications in the database. In addition to these, the database displays custom-made applications also. These are application definitions created using the application command. |
schedule <SCHEDULE-POLICY-NAME> | Schedules an enforcement time for this deny rule by
associating a schedule policy with it. Use this parameter to
apply rule-specific enforcement time.
In case of no schedule policy being applied, the rule is enforced as per the enforcement-time configured in the application policy. For more information, see enforcement-time. |
precedence <1-256> | Assigns a precedence value for this deny rule. The
precedence value differentiates between rules applicable to applications and the
application categories to which they belong. The allow, deny, mark, rate-limit
options are mutually exclusive. In other words, in an application policy, for a
specific application or application category, you can create either an allow rule,
or a deny rule, or a mark and rate-limit rule. Let us consider application youtube belonging to app-category streaming. The rules can
be defined
as:
#allow application youtube precedence 1 #deny app-category streaming precedence 2 The
following configuration is
incorrect:
#deny app-category streaming precedence 1 #allow application youtube precedence 2 Once the deny app-category streaming precedence 1 rule is hit, all streaming packets, including youtube, are dropped. Consequently, there are no packets left to apply the subsequent allow rule. The mark and rate-limit rules are the only two actions that can be combined for a specific application or application category type. |
The following example shows one deny rule, denying access to all packets belonging to the application category ‘social\ networking‘:
nx9500-6C8809(config-app-policy-Bing)#deny app-category social\ networking precedence 3
nx9500-6C8809(config-app-policy-Bing)#show context
application-policy Bing
allow application Bing precedence 1
allow app-category business precedence 2
deny app-category "social networking" precedence 3
nx9500-6C8809(config-app-policy-Bing)#
The following example displays the schedule policy ‘DenyS-N‘ settings. The time-rule defined in the policy is all weekdays from 9:30 AM to 11:30 PM.
nx9500-6C8809(config-schedule-policy-DenyS-N)#show context schedule-policy DenyS-N description "Denies all social Networking sites on weekdays." time-rule days weekdays start-time 09:30 end-time 23:30 nx9500-6C8809(config-schedule-policy-DenyS-N)#
The following example displays the schedule policy ‘FaceBook‘ settings. The time-rule defined in the policy is Friday from 1:00 PM to 6:00 PM.
nx9500-6C8809(config-schedule-policy-FaceBook)#show context schedule-policy FaceBook description "Allows FaceBook traffic on Fridays." time-rule days friday start-time 13:00 end-time 18:00 nx9500-6C8809(config-schedule-policy-FaceBook)#
nx9500-6C8809(config-app-policy-SocialNet)#show context application-policy SocialNet description "This application policy relates to Social Networking sites." allow application facebook schedule FaceBook precedence 1 deny app-category "social networking" schedule DenyS-N precedence 2 nx9500-6C8809(config-app-policy-SocialNet)#
no | Removes this deny rule from the application policy |