Access Lists Tab

Configuration > Templates & Policies > Policies > ACLs > Access Lists

This tab lists the configured Access Control List (ACL) rules. An ACL is a reusable MATCH criteria for filtering flows. It is associated with an action: permit or deny. An ACL can be a MATCH condition in more than one policy—Route, QoS, or Optimization.

Field Description
Appliance Name of the appliance selected.
ACLs Access Control Lists. A list of one or more ordered access control rules.

NOTE: An ACL only becomes active when it is used in a policy.
Priority For ACL rules, you can set the priority to a value within the range 1 to 65535. When adding a rule, the priority is incremented by ten from the previous rule. You can change the priority, but this default behavior helps ensure that you can insert new rules without having to change subsequent priorities.
Match Criteria Configured ACL match criteria associated to the appliance. See below for more information about Match Criteria.
Permit Whether the ACL is set to Permit or Deny.

Permit allows the matching traffic flow to proceed to the policy entry’s associated SET actions.

Deny prevents further processing of the flow by that ACL, specifically. The appliance continues to the next entry in the policy.
Comment Any additional information about the ACL.

Click the edit icon to make add, delete, or modify rules to your ACLs.

Match Criteria

Match criteria are used universally across all policy maps for route, QoS, optimization, SaaS NAT, and firewall zone security policies.

To use the same match criteria in different maps, create an ACL (Access Control List), which is a named, reusable set of rules. For efficiency, navigate to Configuration > Templates & Policies > ACLs > Access Lists to create ACLs, and then apply them across your appliances.

Use the Match Criteria dialog box to select and configure a variety of match criteria options. Some are explained below:

  • Address Map: Use this option to sort by country, IP address owner, or SaaS application. You can also select and configure Microsoft Instance, Microsoft Category, and Proxy attributes for an address map. These attributes are secondary parameters to the address map. They are evaluated for a policy match only when the configured address map matches the flow. To select and configure these attributes, click +Attributes.

  • Match criteria options related to Secure Web Services include:

    • URL: Omit the protocol in URLs and include a slash character (/) or a slash followed by a query parameter. For example, google.com/ or google.com/maps are valid; https://google.com/ is not valid. You can also use the asterisk (*) wildcard character, such as in google.com/*, to specify a domain, but it is more appropriate to use the Domain match criteria option to specify google.com/. Separate multiple URL addresses with the pipe character (|). For example, you can specify two URL addresses as bing.com/*|google.com/*.

    • Web Category: If you select this option, click Select, and then click Strict, Moderate, or Custom. Strict and Moderate include predetermined web category selections, which you cannot change. However, if you attempt to select or clear a web category for these, the Custom group of web category selections opens automatically. You can customize web category selections in the Custom group. After you make your selections, click Ok.

    • Web Reputation: If you select this option, select one or more web reputation categories (High Risk, Suspicious, Moderate Risk, Low Risk, or Trustworthy) from the list. To select more than one, press and hold the Shift key, and then click the appropriate categories.

    • Bad IP Reputation: Selecting this option matches on flows for which the source or destination IP address (or both) has a High Risk reputation score.

  • Match criteria options related to RADIUS user role include:

    • User Role: This is the user role as specified in the authentication exchange with the ClearPass RADIUS server.

    • User Name

    • User Group

    • User Device

    • User MAC

    • User Vlan

    Configuring these match criteria related to user role enables an EdgeConnect to automatically assign traffic steering and firewall zone policies.

  • Use the Src:Dest check box associated with several match criteria options to specify separate criteria for inbound and outbound traffic. You can configure source and destination role-based policies when both source and destination users are in the same network.

Wildcard-based Prefix Matching Rules

  • Even when using a range or a wildcard, the IPv4 address must be specified in the 4-octet format, separated by the dot notation. For example, A.B.C.D.

  • Range is specified using a single dash. For example, 128-129.

  • Wildcard is specified as an asterisk (*).

  • Range and Wildcard can both be used in the same address, but an octet can only contain one or the other. For example, 10.136-137.*.64-95.

  • A wildcard can only be used to define an entire octet. For example, 10.13*.*.64-95 is not supported. Use 10.130-139.*.64-95 to specify this range.

  • The same rules apply to IPv6 addressing.

  • CIDR notation and (Range or Wildcard) are mutually exclusive in the same address. For example, 192.168.0.1-127/24 is not supported. Use either 192.168.0.0/24 or 192.168.0.1-127.

  • These prefix-matching rules apply to the following policies only: Route, QoS, Optimization, NAT, Security, and ACLs.

Access Lists Edit Row

The Access Lists dialog box lists the configured Access Control List (ACL) rules.

You can add, delete, or rename an ACL by clicking the buttons at the top of this dialog box. You can also add rules to an ACL.

  1. Click Add Rule.

  2. Enter a priority value.

  3. Click the edit icon to configure the match criteria. The Match Criteria dialog box opens and you can specify the match criteria. Click More Options to apply more rules.

  4. Select if you want to Permit or Deny traffic in the ACL.

  5. Enter any comments if you decide to do so.