Modify an access-list's execution order with Firewall Manager v2
Cisco firewalls execute access-list rules in order from first to last. If a customer request matches a rule, Cisco firewalls stop processing the request and perform the action.
Firewall Manager v2 always adds new access-list rules to the end of the access-list, so sometimes you need to change the execution order of the rules. This article provides more details about the execution of an access-list’s rule order and how to modify that order.
Why use access-lists?
Access control lists (ACLs), or access-lists, enable Cisco firewalls to filter traffic. The security of your Rackspace environment begins at your Cisco firewall. Misconfigurations in network access policies on your firewall can lead to unwanted network exposure and potential compromise.
The access-lists control the traffic that attempts to enter the internal networks from an external, unsecured network. If access-lists are not used, the Cisco firewall’s default security policy of security-levels is active, which does not provide the highest level of network security.
An access control entry (ACE) is an individual entry in an ACL. ACEs are referred to as rules in Firewall Manager v2. The Cisco firewall allows you to configure only one access-list per interface per direction. This access-list can contain as many ACEs, or rules, as necessary.
For more information about how to view, add, and delete access-lists, see the following articles:
Rule order and execution
Cisco firewalls use line numbers added to ACEs to identify the execution order of the access-list. When you create a new access-list rule in Firewall Manager v2, the rule is added to the end of the access-list by default. Depending on the content of the access-list, this default action might or might not be what you intend to configure. For example, if an encompassing deny rule is above a newly created rule, that deny rule prevents the new rule from triggering.
Therefore, you often need to place an access-list rule in a customized location within the access-list.
Cisco firewalls also use a fail-close approach that means that there is an implicit deny all rule at the end of each access-list. If traffic is not explicitly permitted, then it is implicitly denied.
Modify access-list rule order
Warning: Because of a Cisco limitation, when you change the execution order of a rule, the rule is temporarily removed and then re-added. Do not change the execution order of a rule unless a momentary change in access for that rule is acceptable.
Access Firewall Manager v2 by following the steps in the Firewall Manager v2 article.
In the navigation pane on the left side of the panel, click the firewall for which you want to see access-list rules.
Under Rules, click All Rules.
In the navigation pane on the left side of the panel, click the firewall for which you want to modify the execution order of the access-list’s rules.
Click the gear icon next to the line number of the rule that you want to move, and select Change Order.
Select the Change order option.
Specify the line number to which to move this entry to.
Note: Firewall Manager v2 does not allow you to place rules above the highest hidden Rackspace internal line.
- Firewall Manager v2 port-objects
- Firewall Manager v2 change log
- Firewall Manager v2 access-list theory and best practices
©2020 Rackspace US, Inc.
Except where otherwise noted, content on this site is licensed under a Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported License