4-61
Device Manager Guide, Cisco ACE 4700 Series Application Control Engine Appliance
OL-26645-02
Chapter 4 Configuring Virtual Contexts
Configuring Security with ACLs
Note To add, modify, or delete Object Groups, see the “Configuring Object Groups” section on
page 4-70.
Step 4 Do one of the following:
• Click Deploy to deploy this configuration on the ACE appliance.
• Click Cancel to exit this procedure without saving your entries and to return to the ACLs table.
Related Topics
• Configuring Security with ACLs, page 4-58
• Setting EtherType ACL Attributes, page 4-67
• Setting Extended ACL Attributes, page 4-61
• Resequencing Extended ACLs, page 4-66
• Editing or Deleting ACLs, page 4-69
Setting Extended ACL Attributes
Note By default, all traffic is denied by the ACE unless explicitly allowed. Only traffic that is explicitly
allowed in an ACL can pass. All other traffic is denied.
An extended ACL allows you to specify both the source and the destination IP addresses of traffic as
well as the protocol and the action to be taken.
For TCP, UDP, and ICMP connections, you do not need to also apply an ACL on the destination interface
to allow returning traffic, because the ACE allows all returning traffic for established connections.
Note The ACE does not explicitly support standard ACLs. To configure a standard ACL, specify the
destination address as any and do not specify the ports in an extended ACL.
Procedure
Step 1 Choose Config > Virtual Contexts > context > Security > ACLs.
The ACLs table appears, listing the existing ACLs.
Interfaces
•
Input/Output
Direction
• Currently Assigned
(ACL:Direction)
Allows you to associate the ACL with one or more interfaces allowing only
one input and one output ACL for each interface. The top left check box
under the Interfaces section allows you to select and apply to all interfaces
“access-group input.”
Table 4-16 ACL Configuration Attributes (continued)
Field Description
Comments to this Manuals