Table Of Contents
Policy Object Manager User Interface Reference
Policy Object Manager Window
Policy Object Manager Window Shortcut Menu
Policy Object Add or Edit Dialog Boxes
AAA Server Group Dialog Box
AAA Server Dialog Box
AAA Server Dialog Box—RADIUS Settings
AAA Server Dialog Box—TACACS+ Settings
AAA Server Dialog Box—Kerberos Settings
AAA Server Dialog Box—LDAP Settings
AAA Server Dialog Box—NT Settings
AAA Server Dialog Box—SDI Settings
AAA Server Dialog Box—HTTP-FORM Settings
Add or Edit Access List Dialog Boxes
Add and Edit Extended Access Control Entry Dialog Boxes
Add and Edit Standard Access Control Entry Dialog Boxes
Add and Edit Web Access Control Entry Dialog Boxes
ASA User Group Dialog Box
ASA User Group Dialog Box: Client Configuration Settings
ASA User Group Dialog Box: Client Firewall Attributes
ASA User Group Dialog Box: Hardware Client Attributes
ASA User Group Dialog Box: IPsec Settings
ASA User Group Dialog Box: SSL VPN Clientless Settings
ASA User Group Dialog Box: SSL VPN Full Client Settings
ASA User Group Dialog Box: SSL VPN Settings
ASA User Group Dialog Box: DNS/WINS Settings
ASA User Group Dialog Box: Split Tunneling
ASA User Group Dialog Box: Connection Settings
Category Editor Dialog Box
Add or Edit Secure Desktop Configuration Dialog Box
Credentials Dialog Box
Add and Edit File Object Dialog Boxes
Add or Edit FlexConfig Dialog Box
Create Text Object Dialog Box
FlexConfig Undefined Variables Dialog Box
Property Selector Dialog Box
IKE Proposal Dialog Box
Add or Edit Class Maps Dialog Boxes
Add or Edit DCE/RPC Dialog Box
Add and Edit DNS Map Dialog Boxes
DNS Map Protocol Conformance Tab
DNS Map Filtering Tab
DNS Class and Policy Maps Add or Edit Match Condition (and Action) Dialog Boxes
Add or Edit ESMTP Map Dialog Boxes
ESMTP Policy Maps Add or Edit Match Condition and Action Dialog Boxes
Add and Edit FTP Map Dialog Boxes
FTP Class and Policy Maps Add or Edit Match Condition (and Action) Dialog Boxes
Add and Edit GTP Map Dialog Boxes
Add and Edit Country Network Codes Dialog Boxes
Add and Edit Permit Response Dialog Boxes
GTP Map Timeouts Dialog Box
GTP Policy Maps Add or Edit Match Condition and Action Dialog Boxes
Add and Edit H.323 Map Dialog Boxes
Add or Edit HSI Group Dialog Boxes
Add or Edit HSI Endpoint IP Address Dialog Boxes
H.323 Class and Policy Maps Add or Edit Match Condition (and Action) Dialog Boxes
Add and Edit HTTP Map Dialog Boxes for ASA 7.1.x/PIX 7.1.x/FWSM 3.x/IOS Devices
HTTP Map General Tab
HTTP Map Entity Length Tab
HTTP Map RFC Request Method Tab
HTTP Map Extension Request Method Tab
HTTP Map Port Misuse Tab
HTTP Map Transfer Encoding Tab
Add or Edit HTTP Map Dialog Boxes for ASA 7.2+/PIX 7.2+ Devices
HTTP Class and Policy Map (ASA 7.2+/PIX 7.2+) Add or Edit Match Condition (and Action) Dialog Boxes
Add and Edit IM Map Dialog Boxes (for ASA 7.2+/PIX 7.2+)
IM Class and Policy Map (ASA 7.2+/PIX 7.2+) Add or Edit Match Condition (and Action) Dialog Boxes
Add or Edit IM Map (IOS) Dialog Boxes
Add or Edit IPsec Pass Through Map Dialog Boxes
Add or Edit NetBIOS Map Dialog Boxes
Add or Edit SIP Map Dialog Boxes
SIP Class and Policy Maps Add or Edit Match Condition (and Action) Dialog Boxes
Add or Edit Skinny Map Dialog Boxes
Skinny Policy Maps Add or Edit Match Condition and Action Dialog Boxes
Add and Edit SNMP Map Dialog Boxes
Add and Edit Regular Expression Group Dialog Boxes
Add and Edit Regular Expression Dialog Boxes
Add and Edit TCP Map Dialog Boxes
Add and Edit TCP Option Range Dialog Boxes
Interface Role Dialog Box
Interface Name Conflict Dialog Box
IPsec Transform Set Dialog Box
Add and Edit LDAP Attribute Map Dialog Boxes
Add and Edit LDAP Attribute Map > Add and Edit LDAP Attribute Map Value
Add and Edit LDAP Attribute Map > Add and Edit LDAP Attribute Map Value > Add and Edit Map Value
Network/Host Dialog Box
PKI Enrollment Dialog Box
PKI Enrollment Dialog Box—CA Information Tab
PKI Enrollment Dialog Box—Enrollment Parameters Tab
PKI Enrollment Dialog Box—Certificate Subject Name Tab
PKI Enrollment Dialog Box—Trusted CA Hierarchy Tab
Port Forwarding List Dialog Box
Add/Edit Port Forwarding Entry Dialog Box
Port List Dialog Box
Add and Edit Service Dialog Boxes
Add or Edit Single Sign On Server Dialog Boxes
Add or Edit SLA Monitor Dialog Box
Add or Edit Bookmarks Dialog Boxes
Add and Edit Bookmark Entry Dialog Boxes
Add and Edit Post Parameter Dialog Boxes
Add and Edit SSL VPN Customization Dialog Boxes
SSL VPN Customization Dialog Box—Title Panel
SSL VPN Customization Dialog Box—Language
SSL VPN Customization Dialog Box—Logon Form
SSL VPN Customization Dialog Box—Informational Panel
SSL VPN Customization Dialog Box—Copyright Panel
SSL VPN Customization Dialog Box—Full Customization
SSL VPN Customization Dialog Box—Toolbar
SSL VPN Customization Dialog Box—Applications
SSL VPN Customization Dialog Box—Custom Panes
SSL VPN Customization Dialog Box—Home Page
SSL VPN Customization Dialog Box—Logout Page
Add or Edit SSL VPN Gateway Dialog Box
Add and Edit SSL VPN Smart Tunnel List Dialog Boxes
Add and Edit Smart Tunnel Entry Dialog Boxes
Style Objects Dialog Box
Add or Edit Text Object Dialog Box
Time Range Dialog Box
Recurring Ranges Dialog Box
Add and Edit Traffic Flow Dialog Boxes
Default Inspection Traffic
User Group Dialog Box
User Group Dialog Box—General Settings
User Group Dialog Box—DNS/WINS Settings
User Group Dialog Box—Split Tunneling
User Group Dialog Box—IOS Client Settings
User Group Dialog Box—IOS Xauth Options
User Group Dialog Box—IOS Client VPN Software Update
User Group Dialog Box—Advanced PIX Options
User Group Dialog Box—Clientless Settings
User Group Dialog Box—Thin Client Settings
User Group Dialog Box—SSL VPN Full Tunnel Settings
User Group Dialog Box—SSL VPN Split Tunneling
User Group Dialog Box—Browser Proxy Settings
User Group Dialog Box—SSL VPN Connection Settings
Add or Edit WINS Server List Dialog Box
Add or Edit WINS Server Dialog Box
Object Selectors
Object Usage Window
Policy Object Overrides Window
Create Overrides for Device Dialog Box
Policy Object Manager User Interface Reference
The Policy Object Manager is used to create and globally manage all the policy objects configured with Cisco Security Manager. You use policy objects to simplify the creation of device-level and shared policies.
This chapter contains the following topics:
•
Policy Object Manager Window
•
Policy Object Add or Edit Dialog Boxes
•
Object Selectors
•
Object Usage Window
•
Policy Object Overrides Window
Policy Object Manager Window
Use the Policy Object Manager window to:
•
View all the available objects grouped according to object type.
•
Create, copy, edit, and delete policy objects.
•
Generate usage reports, which describe how selected objects are being used by other Security Manager objects and policies.
Navigation Path
Click the Policy Object Manager button on the toolbar or select Tools > Policy Object Manager.
Related Topics
•
"Policy Object Manager User Interface Reference"
•
Guidelines for Managing Objects, page 9-5
•
Object Usage Window
•
Policy Object Overrides Window
•
Selecting Objects for Policies, page 9-120
•
How Policy Objects are Provisioned as PIX/ASA Object Groups, page 9-122
Field Reference
Table F-1 Policy Object Manager Window
Element
|
Description
|
Object Type selector or table of contents
(Left pane.)
|
Lists the object types available in Security Manager. When you select an object type, all existing objects of that type are listed in the table in the right pane.
|
Filter area
(Right pane.)
|
Use the filter controls above the policy object table to reduce the number of objects displayed. This can help you find an object you want to work with. For information on filtering tables, see Filtering Tables, page 3-17.
|
Policy Object Table (Right Pane)
The policy object table in the right pane lists existing objects of the type selected in the table of contents. Using this table, you create new objects and work with existing ones. You can use the buttons below the table, or right-click within the table to see additional commands (see Policy Object Manager Window Shortcut Menu).
Except for the Access Control Lists (ACL) object, there is one table per object type. For ACLs, there are tabs to separate Extended, Standard, and Web ACLs. Select the appropriate tab to work with the desired object type.
The columns in the table vary based on the type of object you select. You can alter the columns displayed in the table by right-clicking the table heading and selecting or deselecting columns in the Show Columns command. You can also sort the information by the contents in a column by clicking the column heading; click the heading to toggle between alphabetical and reverse alphabetical sorting.
For detailed information on the settings that are displayed in the table, click the Create or Edit buttons below the table and click Help in the dialog box that is opened. Following is a description of the columns that you typically see.
|
Icon (unlabeled field)
|
The icon displayed for a policy object type identifies objects of that type wherever they appear, such as in rules tables. If the icon includes the image of a pencil, you can edit it.
|
Name
|
The name of the policy object.
|
Content
|
A summary of the object definition that might not include all defined settings.
|
Permit
|
For ACL objects, if the Access Control Entry (ACE) allows traffic, a check mark appears in the Permit column. If the action is deny, a red circle with a slash appears.
|
Category
|
The category object that is assigned to the object, if any. Categories help you organize and identify rules and objects. For more information, see Using Category Objects, page 9-4.
|
Overridable
|
Whether a user can override the object properties at the device level. A check mark indicates that the object can be overridden. Not all object types are overridable.
For more information about device overrides, see Creating Device-Level Object Overrides, page 9-117.
|
Description
|
If a paper icon appears in this column, there is a description for the object. Double-click the icon to view the description or mouse-over the icon.
|
Buttons Below Table
|
|
Click the New Object button to create a new object. The same icon is used for any button that adds an item to a table.
Clicking this button opens a dialog box to create the object. Click the Help button in the dialog box for information on the selected object type.
|
|
Click the Edit Object button to edit the selected object. The same icon is used for editing any object in a table.
The dialog box used for editing the object is the same as the one used for creating the object. If you try to edit a system-defined default object, you are allowed only to view the object contents. Click the Help button in the dialog box for information on the settings. For more information, see Editing Objects, page 9-6.
|
|
Click the Delete Object button to delete the selected object. You can delete only user-defined objects that are not currently being used in a policy or another policy object. For more information, see Deleting Objects, page 9-7.
|
Policy Object Manager Window Shortcut Menu
Right-clicking inside the policy object table in the Policy Object Manager window displays a shortcut menu for performing various functions on the selected object type.
Navigation Path
Click the Policy Object Manager button on the toolbar or select Tools > Policy Object Manager.
Related Topics
•
Policy Object Manager Window
Field Reference
Table F-2 Policy Object Manager Window Shortcut Menu
Menu Command
|
Description
|
New Object
|
Select this command to create a new policy object. Click Help in the dialog box that is opened for information specific to the object type.
|
Edit Object
|
Select this command to edit the policy object selected in the table. If you select a system-defined default object, you are presented with a view-only look at the object definition. For more information, see Editing Objects, page 9-6.
|
Delete Object
|
Select this command to delete the policy object selected in the table. You can delete only user-defined objects that are not being used in a policy or in another policy object. For more information, see Deleting Objects, page 9-7.
|
Edit Device Overrides
|
Select this command to change the device-level overrides for this object using the Policy Object Overrides Window. You can create, edit, and delete overrides. For more information, see Creating Device-Level Object Overrides, page 9-117.
|
Create Duplicate
|
Select this command to create a copy of the policy object. For more information, see Duplicating Objects, page 9-8.
|
Find Usage
|
Select this command to generate a usage report for the selected object using the Object Usage Window. The usage report tells you where the object is currently being used. for more information, see Generating Object Usage Reports, page 9-9.
|
View Object
|
Select this command to view the definition of the object using a read-only version of the edit dialog box for the object. For more information, see Viewing Object Details, page 9-10.
|
Policy Object Add or Edit Dialog Boxes
When you add or edit a policy object, a dialog box is opened that contains the settings for that type of policy object. Click Help in the dialog box for detailed information on the settings available for that type of object.
This section contains the following topics:
•
AAA Server Group Dialog Box
•
AAA Server Dialog Box
•
Add or Edit Access List Dialog Boxes
•
ASA User Group Dialog Box
•
Category Editor Dialog Box
•
Add or Edit Secure Desktop Configuration Dialog Box
•
Credentials Dialog Box
•
Add and Edit File Object Dialog Boxes
•
Add or Edit FlexConfig Dialog Box
•
IKE Proposal Dialog Box
•
Add or Edit Class Maps Dialog Boxes
•
Add or Edit DCE/RPC Dialog Box
•
Add and Edit DNS Map Dialog Boxes
•
Add or Edit ESMTP Map Dialog Boxes
•
Add and Edit FTP Map Dialog Boxes
•
Add and Edit GTP Map Dialog Boxes
•
Add and Edit H.323 Map Dialog Boxes
•
Add and Edit HTTP Map Dialog Boxes for ASA 7.1.x/PIX 7.1.x/FWSM 3.x/IOS Devices
•
Add or Edit HTTP Map Dialog Boxes for ASA 7.2+/PIX 7.2+ Devices
•
Add and Edit IM Map Dialog Boxes (for ASA 7.2+/PIX 7.2+)
•
Add or Edit IM Map (IOS) Dialog Boxes
•
Add or Edit IPsec Pass Through Map Dialog Boxes
•
Add or Edit NetBIOS Map Dialog Boxes
•
Add or Edit SIP Map Dialog Boxes
•
Add or Edit Skinny Map Dialog Boxes
•
Add and Edit SNMP Map Dialog Boxes
•
Add and Edit Regular Expression Group Dialog Boxes
•
Add and Edit Regular Expression Dialog Boxes
•
Add and Edit TCP Map Dialog Boxes
•
Interface Role Dialog Box
•
IPsec Transform Set Dialog Box
•
Add and Edit LDAP Attribute Map Dialog Boxes
•
Network/Host Dialog Box
•
PKI Enrollment Dialog Box
•
Port Forwarding List Dialog Box
•
Port List Dialog Box
•
Add and Edit Service Dialog Boxes
•
Add or Edit Single Sign On Server Dialog Boxes
•
Add or Edit SLA Monitor Dialog Box
•
Add or Edit Bookmarks Dialog Boxes
•
Add and Edit SSL VPN Customization Dialog Boxes
•
Add or Edit SSL VPN Gateway Dialog Box
•
Add and Edit SSL VPN Smart Tunnel List Dialog Boxes
•
Style Objects Dialog Box
•
Add or Edit Text Object Dialog Box
•
Time Range Dialog Box
•
Add and Edit Traffic Flow Dialog Boxes
•
User Group Dialog Box
•
Add or Edit WINS Server List Dialog Box
AAA Server Group Dialog Box
Use the AAA Server Group dialog box to create, copy, and edit AAA server groups. When defining a policy that uses a AAA server for authentication, authorization, or accounting, you select the server by selecting the server group to which the server belongs.
Navigation Path
Select Tools > Policy Object Manager, then select AAA Server Groups from the Object Type Selector. Right-click inside the work area, then select New Object or right-click a row, then select Edit Object.
Related Topics
•
Creating AAA Server Group Objects, page 9-13
•
Understanding AAA Server Group Objects, page 9-10
•
AAA Server Dialog Box
•
Policy Object Manager Window
Field Reference
Table F-3 AAA Server Group Dialog Box
Element
|
Description
|
Name
|
The object name (up to 16 characters when using this object with firewall devices; up to 128 characters for Cisco IOS routers). Object names are not case-sensitive. Spaces are not supported.
For more information, see Guidelines for Managing Objects, page 9-5.
Note Cisco IOS routers do not support AAA server groups named RADIUS, TACACS, or TACACS+. In addition, we do not recommend using an abbreviation of one of these names, such as "rad" or "tac".
Note If you define this AAA server group as the RADIUS or TACACS+ default group, any name you define here is automatically replaced in the device configuration by the default name (RADIUS or TACACS+) upon deployment.
|
Description
|
Additional information about the object (up to 1024 characters).
|
Protocol
|
The protocol used by the AAA servers in the group:
• RADIUS
• Kerberos
• TACACS+
• LDAP
• NT
• SDI
• HTTP-FORM
|
AAA Servers
|
The AAA servers that comprise the server group. Enter the names of AAA servers or click Select to display an Object Selectors. The selector displays only those AAA servers that match the protocol you selected for the group.
Tip  If the AAA server group you want is not listed, click the Create button or the Edit button in the selector to display the AAA Server Dialog Box. From here you can define a AAA server object. Bear in mind, however, that the group must include servers that use the protocol you selected.
|
Make this Group the Default AAA Server Group (IOS)
|
Applies only to IOS devices.
When selected, designates this AAA server group as the default group for the RADIUS or TACACS+ protocol. Select this check box if you intend to use a single global group for the selected protocol for all policies on a specific device requiring AAA.
When deselected, creates a AAA server group that is not designated as the default group for that protocol. Leave this check box deselected if you intend to create multiple RADIUS or TACACS+ AAA server groups. Multiple groups can be used to separate different AAA functions (for example, use one group for authentication and a different group for authorization) or to separate different customers in a VRF environment.
Note When you discover an IOS router, any AAA servers in the device configuration that are not members of a AAA server group are placed in special groups created by Security Manager called CSM-rad-grp (for RADIUS) and CSM-tac-grp (for TACACS+). These two groups, which are marked as default AAA server groups in the Policy Object Manager, are created solely to enable Security Manager to manage these servers. During deployment, the AAA servers in these special groups are deployed back to the device as individual servers. For more information, see Default AAA Server Groups and IOS Devices, page 9-12.
|
Max Failed Attempts (PIX, ASA, FWSM)
|
Applies only to PIX/ASA/FWSM devices.
The number of connection attempts that can fail before an unresponsive AAA server in the group is deactivated.
Values range from 1 to 5.
|
Reactivation Mode (PIX, ASA, FWSM)
|
Applies only to PIX/ASA/FWSM devices.
The method to use when reactivating failed AAA servers in the group:
• Depletion—Reactivate failed servers only after all of the servers in the group fail. This is the default.
• Timed—Reactivate failed servers after 30 seconds of downtime.
Note You must use the Timed option when using Simultaneous as the Group Accounting Mode.
|
Reactivation Deadtime (PIX, ASA, FWSM)
|
Applies only to PIX/ASA/FWSM devices and only when Depletion is the selected reactivation mode.
The number of minutes that should elapse between the deactivation of the last server in the group and the reactivation of all the servers in the group. Values range from 0 to 1440 minutes (24 hours).
|
Group Accounting Mode (PIX, ASA, FWSM)
|
Applies only to PIX/ASA/FWSM devices using RADIUS or TACACS+.
The method for sending accounting messages to the AAA servers in the group:
• Simultaneous—Accounting messages are sent to all servers in the group simultaneously.
Note If you select this option, you must select Timed as the Reactivation Mode.
• Single—Accounting messages are sent to a single server in the group. This is the default.
|
Category
|
The category assigned to the object. Categories help you organize and identify rules and objects. See Using Category Objects, page 9-4.
|
Allow Value Override per Device
Overrides
Edit button
|
Whether to allow the object definition to be changed at the device level. For more information, see Allowing a Global Object to Be Overridden, page 9-116 and Overriding Global Objects for Individual Devices, page 9-116.
If you allow device overrides, you can click the Edit button to create, edit, and view the overrides. The Overrides field indicates the number of devices that have overrides for this object.
|
AAA Server Dialog Box
Use AAA Server dialog box to create, copy, and edit a AAA server object. These objects are collected into AAA server group objects.
Navigation Path
Select Tools > Policy Object Manager, then select AAA Servers from the Object Type Selector. Right-click inside the work area, then select New Object or right-click a row, then select Edit Object.
Related Topics
•
Creating AAA Server Objects, page 9-18
•
Understanding AAA Server Objects, page 9-15
•
Policy Object Manager Window
•
AAA Server Group Dialog Box
Field Reference
Table F-4 AAA Server Dialog Box—General Settings
Element
|
Description
|
Name
|
The object name (up to 128 characters). Object names are not case-sensitive. For more information, see Guidelines for Managing Objects, page 9-5.
|
Description
|
Additional information about the object (up to 1024 characters).
|
Host
|
• IP Address—The IP address of the AAA server to which authentication requests will be sent. Enter one or more host addresses or network/host objects, or click Select to display an Object Selectors.
• DNS Name—(For PIX/ASA devices running 7.2 and above) The DNS hostname of the AAA server. The maximum length is 128 characters. The hostname can contain alphanumeric characters and hyphens, but each element of the hostname must begin and end with an alphanumeric character. Use a period (`.') to separate elements.
|
Interface
|
The interface whose IP address should be used for all outgoing RADIUS or TACACS packets (known as the source interface). Enter the name of an interface or interface role, or click Select to display an Object Selectors.
If you enter the name of an interface, make sure the policy that uses this AAA object is assigned to a device containing an interface with this name.
If you enter the name of an interface role, make sure the role represents a single interface, not multiple interfaces.
Tip  If the interface role you want is not listed, click the Create button or the Edit button in the selector to display the Interface Role Dialog Box. From here you can define an interface role object.
Note Only one source interface can be defined for the AAA servers in a AAA server group. An error is displayed when you submit your changes if different AAA servers in the group use different source interfaces. See Creating AAA Server Group Objects, page 9-13.
|
Timeout
|
The amount of time to wait until the AAA server is considered unresponsive.
Valid values for Cisco IOS routers range from 1-1000 seconds. The default is 5 seconds.
Valid values for ASA devices and other firewall devices running PIX 7.0 is 1-60 seconds. The default is 10 seconds.
Valid values for PIX devices running PIX 6.3 is 1-30 seconds. The default is 5 seconds.
|
Protocol
|
The protocol used by the AAA server:
• RADIUS—See AAA Server Dialog Box—RADIUS Settings.
• TACACS+—See AAA Server Dialog Box—TACACS+ Settings.
• Kerberos (ASA devices only)—See AAA Server Dialog Box—Kerberos Settings.
• LDAP (ASA devices only)—See AAA Server Dialog Box—LDAP Settings.
• NT (ASA devices only)—See AAA Server Dialog Box—NT Settings.
• SDI (ASA devices only)—See AAA Server Dialog Box—SDI Settings.
• HTTP-FORM (ASA devices only)—See AAA Server Dialog Box—HTTP-FORM Settings.
Note You cannot edit the protocol if the server is defined as part of a AAA server group.
|
Category
|
The category assigned to the object. Categories help you organize and identify rules and objects. See Using Category Objects, page 9-4.
|
AAA Server Dialog Box—RADIUS Settings
Use the RADIUS settings in the AAA Server dialog box to configure a RADIUS AAA server object.
Navigation Path
Go to the AAA Server Dialog Box, then click RADIUS in the Protocol field.
Related Topics
•
Creating AAA Server Objects, page 9-18
•
Understanding AAA Server Objects, page 9-15
•
AAA Server Group Dialog Box
Field Reference
Table F-5 AAA Server Dialog Box—RADIUS Settings
Element
|
Description
|
Key
|
The shared secret that is used to encrypt data between the client and AAA server. The key is a case-sensitive, alphanumeric string of up to 127 characters (U.S. English). Spaces and special characters are permitted.
The key you define in this field must match the key on the RADIUS server. Enter the key again in the Confirm field.
Note Spaces are not allowed in keys defined for PIX/ASA/FWSM devices. A key with a space causes activity validation to fail.
Note You can discover encrypted keys defined on Cisco IOS routers. However, if you make any changes to the key, the key type is changed to clear text.
Note If you do not define a key, all traffic between the AAA server and its AAA clients is sent unencrypted. A warning message is displayed.
|
Authentication/Authorization Port
|
The port on which AAA authentication and authorization are performed. Default is 1645.
|
Accounting Port
|
The port on which AAA accounting is performed. Default is 1646.
|
RADIUS Password (PIX 7.x, ASA/FWSM 3.x)
|
Applies to PIX 7.x/ASA/FWSM 3.1 and later devices.
The alphanumeric keyword that serves as the password to the RADIUS server (maximum of 128 characters; spaces are not allowed). Enter the password again in the Confirm field.
|
Retry Interval (PIX 7.x, ASA/FWSM 3.x)
|
Applies to PIX 7.x/ASA/FWSM 3.1 and later devices.
The interval between attempts to contact the AAA server. Valid values are:
• ASA devices—1 to 10 seconds.
• PIX devices—1 to 5 seconds.
|
ACL Netmask Convert (PIX 7.x, ASA/FWSM 3.x)
|
Applies to PIX 7.x/ASA/FWSM 3.1 and later devices.
The method for handling the netmask expressions that are contained in downloadable ACLs received from the RADIUS server:
• Standard—The security appliance assumes that all downloadable ACLs received from the RADIUS server contain only standard netmask expressions. No translation from wildcard netmask expressions is performed. This is the default.
• Auto-Detect—The security appliance tries to determine the type of netmask expression used in the downloadable ACL. If it detects a wildcard netmask expression, it converts it to a standard netmask expression.
• Wildcard—The security appliance assumes that all downloadable ACLs received from the RADIUS server contain only wildcard netmask expressions, which it converts to standard netmask expressions.
Some Cisco products, including Cisco IOS routers, require that downloadable ACLs be configured with wildcards instead of network masks. ASA devices, on the other hand, require that downloadable ACLs be configured with network masks. This feature allows the ASA device to internally convert a wildcard to a netmask. Translation of wildcard netmask expressions means that downloadable ACLs written for Cisco IOS routers can be used by ASA devices without altering the configuration of the ACLs on the RADIUS server.
|
AAA Server Dialog Box—TACACS+ Settings
Use the TACACS+ settings in the AAA Server dialog box to configure a TACACS+ AAA server object.
Navigation Path
Go to the AAA Server Dialog Box, then click TACACS+ in the Protocol field.
Related Topics
•
Creating AAA Server Objects, page 9-18
•
Understanding AAA Server Objects, page 9-15
•
AAA Server Group Dialog Box
Field Reference
Table F-6 AAA Server Dialog Box—TACACS+ Settings
Element
|
Description
|
Key
|
The shared secret that is used to encrypt data between the client and the AAA server. The key is a case-sensitive, alphanumeric string of up to 127 characters (U.S. English). Spaces and special characters are permitted.
The key you define in this field must match the key on the TACACS+ server. Enter the key again in the Confirm field.
Note Activity validation fails if you try defining a key with a space on a PIX/ASA/FWSM device.
Note You can discover encrypted keys defined on Cisco IOS routers. However, if you make any changes to the key, the key type is changed to clear text.
Note If you do not define a key, all traffic between the AAA server and its AAA clients is sent unencrypted. A warning message is displayed.
|
Server Port
|
The port used for communicating with the AAA server. The default is 49.
|
AAA Server Dialog Box—Kerberos Settings
Use the Kerberos settings in the AAA Server dialog box to configure a Kerberos AAA server object.
Note
This type of AAA server can be configured only on ASA security appliances.
Navigation Path
Go to the AAA Server Dialog Box, then click Kerberos in the Protocol field.
Related Topics
•
Creating AAA Server Objects, page 9-18
•
Understanding AAA Server Objects, page 9-15
•
AAA Server Group Dialog Box
Field Reference
Table F-7 AAA Server Dialog Box—Kerberos Settings
Element
|
Description
|
Server Port
|
The port used for communicating with the AAA server. Default is 88.
|
Kerberos Realm Name
|
The name of the realm containing the Kerberos authentication server and ticket granting server (maximum of 64 characters).
|
Retry Interval
|
The interval between attempts to contact the AAA server. Valid values range from 1 to 10 seconds.
|
AAA Server Dialog Box—LDAP Settings
Use the LDAP settings in the AAA Server dialog box to configure a LDAP AAA server object.
Note
This type of AAA server can be configured only on ASA security appliances.
Navigation Path
Go to the AAA Server Dialog Box, then click LDAP in the Protocol field.
Related Topics
•
Creating AAA Server Objects, page 9-18
•
Understanding AAA Server Objects, page 9-15
•
AAA Server Group Dialog Box
Field Reference
Table F-8 AAA Server Dialog Box—LDAP Settings
Element
|
Description
|
Enable LDAP over SSL
|
When selected, establishes a secure SSL connection between the ASA device and the LDAP server.
When deselected, SSL is not used for communications between the ASA device and the LDAP server.
Note You must select this option when using a Microsoft Active Directory LDAP server in order to enable password management.
|
Server Port
|
The port used for communicating with the AAA server. Default is 389.
|
LDAP Hierarchy Location
|
The base distinguished name (DN), which is the location in the LDAP hierarchy where the authentication server should being searching when it receives an authorization request. For example, OU=Cisco. The maximum length is 128 characters.
The string is case-sensitive. Spaces are not permitted, but other special characters are allowed.
|
LDAP Scope
|
The scope of LDAP searches:
• onelevel—Searches only one level beneath the base DN. This type of search scope is faster than a subtree search, because it is less comprehensive. This is the default.
• subtree—Searches all levels beneath the base DN.
|
LDAP Distinguished Name
|
The DN and password that uniquely identify this ASA device in the LDAP schema (maximum of 128 characters). The DN is similar to a unique key in a database or a fully qualified path for a file.
Note These parameters are used only when the LDAP server requires them for authentication.
|
LDAP Login Directory
|
The name of the directory object in the LDAP hierarchy used for authenticated binding (maximum of 128 characters). Authenticated binding is required by some LDAP servers (including the Microsoft Active Directory server) before other LDAP operations can be performed.
This string is case-sensitive. Spaces are not permitted in the string, but other special characters are allowed.
|
LDAP Login Password
|
The case-sensitive, alphanumeric password for accessing the LDAP server (maximum of 64 characters). Spaces are not allowed.
|
SASL MD5 Authentication
|
Establishes a Simple Authentication and Security Layer (SASL) mechanism to authenticate an LDAP client (the ASA device) with an LDAP server.
When selected, the ASA device sends the LDAP server an MD5 value computed from the username and password.
When deselected, the MD5 authentication option is not used.
|
SASL Kerberos Authentication
|
Establishes an SASL mechanism to authenticate an LDAP client (the ASA device) to an LDAP server.
When selected, the ASA device sends the LDAP server the username and realm using the GSSAPI (Generic Security Services Application Programming Interface) Kerberos mechanism. This mechanism is stronger than the MD5 mechanism.
When deselected, the Kerberos authentication option is not used.
Note You can define one or both SASL authentication mechanisms. When negotiating SASL authentication, the ASA device retrieves the list of SASL mechanisms configured on the LDAP server and selects the strongest mechanism configured on both devices.
|
Kerberos Server Group
|
Applies only when SASL Kerberos authentication is enabled.
The name of the Kerberos AAA server group used for SASL authentication. The maximum length is 16 characters.
|
LDAP Server Type
|
The type of LDAP server used for AAA:
• Auto-Detect—The ASA device tries to determine the server type automatically. This is the default.
• Microsoft—The LDAP server is a Microsoft Active Directory server.
• Sun—The LDAP server is a Sun Microsystems JAVA System Directory Server.
Note You must configure LDAP over SSL to enable password management with Microsoft Active Directory.
|
LDAP Attribute Map
|
The LDAP attribute configuration to bind to the LDAP server. Enter the name of an LDAP attribute map or click Select to display an Object Selectors.
LDAP attribute maps take the attribute names that you define and map them to Cisco-defined attributes. For more information, see Understanding LDAP Attribute Map Objects, page 9-67.
|
AAA Server Dialog Box—NT Settings
Use the NT settings in the AAA Server dialog box to configure an NT AAA server object.
Note
This type of AAA server can be configured only on ASA security appliances.
Navigation Path
Go to the AAA Server Dialog Box, then click NT in the Protocol field.
Related Topics
•
Creating AAA Server Objects, page 9-18
•
Understanding AAA Server Objects, page 9-15
•
AAA Server Group Dialog Box
Field Reference
Table F-9 AAA Server Dialog Box—NT Settings
Element
|
Description
|
Server Port
|
The port used for communicating with the AAA server. The default is 139.
|
NT Authentication Host
|
The name of the authentication domain controller hostname (maximum of 16 characters).
|
AAA Server Dialog Box—SDI Settings
Use the SDI settings in the AAA Server dialog box to configure an SDI AAA server object.
Note
This type of AAA server can be configured only on ASA security appliances.
Navigation Path
Go to the AAA Server Dialog Box, then click SDI in the Protocol field.
Related Topics
•
Creating AAA Server Objects, page 9-18
•
Understanding AAA Server Objects, page 9-15
•
AAA Server Group Dialog Box
Field Reference
Table F-10 AAA Server Dialog Box—SDI Settings
Element
|
Description
|
Server Port
|
The port used for communicating with the AAA server. The default is 5500.
|
Retry Interval
|
The interval between attempts to contact the AAA server. Valid values range from 1 to 10 seconds. The default is 10 seconds.
|
SDI Server Version
|
The SDI server version:
• SDI-pre-5 (all SDI versions before version 5.0; this is the default)
• SDI-5 (SDI version 5.0)
|
SDI pre-5 Slave Server
|
Applies only when using a version of SDI prior to version 5.0.
A secondary server to be used for authentication if the primary server fails. Enter an IP address or the name of a network/host object, or click Select to display a selector.
|
AAA Server Dialog Box—HTTP-FORM Settings
Use the HTTP-FORM settings in the AAA Server dialog box to configure an HTTP-Form AAA server object for single sign-on authentication (SSO).
Note
This type of AAA server can be configured only on ASA security appliances.
Navigation Path
Go to the AAA Server Dialog Box, then click HTTP-FORM in the Protocol field.
Related Topics
•
Creating AAA Server Objects, page 9-18
•
Understanding AAA Server Objects, page 9-15
•
AAA Server Group Dialog Box
Field Reference
Table F-11 AAA Server Dialog Box—HTTP-Form Settings
Element
|
Description
|
Start URL
|
The URL from which the WebVPN server of the security appliance should retrieve an optional pre-login cookie. The maximum URL length is 1024 characters.
The authenticating web server may execute a pre-login sequence by sending a Set-Cookie header along with the login page content. The URL in this field defines the location from which the cookie is retrieved.
Note The actual login sequence starts after the pre-login cookie sequence.
|
Action URI
|
The Uniform Resource Identifier (URI) that defines the location and name of the authentication program on the web server to which the security appliance sends HTTP POST requests for single sign-on (SSO) authentication.
The maximum length of the action URI is 2048 characters.
Tip  You can discover the action URI on the authenticating web server by connecting to the web server's login page directly with a browser. The URL of the login web page displayed in your browser is the action URI for the authenticating web server.
|
Username Parameter
|
The name of the username parameter included in HTTP POST requests for SSO authentication. The maximum length is 128 characters.
Note At login, the user enters the actual name value, which is entered into the HTTP POST request and passed on to the authenticating web server.
|
Password Parameter
|
The name of the password parameter included in HTTP POST requests for SSO authentication. The maximum length is 128 characters.
Note At login, the user enters the actual password value, which is entered into the HTTP POST request and passed on to the authenticating web server.
|
Hidden Values
|
The hidden parameters included in HTTP POST requests for SSO authentication. They are referred to as hidden parameters because, unlike the username and password, they are not visible to the user.
The maximum length of the hidden parameters is 2048 characters.
Tip  You can discover the hidden parameters that the authenticating web server expects in POST requests by using an HTTP header analyzer on a form received from the web server.
|
Authentication Cookie Name
|
The name of the authentication cookie used for SSO by the security appliance. The maximum length is 128 characters.
If SSO authentication succeeds, the authenticating web server passes this authentication cookie to the client browser. The client browser then authenticates to other web servers in the SSO domain by presenting this cookie.
|
Add or Edit Access List Dialog Boxes
Use the Add and Edit Access List dialog boxes to define access control entries (ACEs) for an ACL object. From this page, you can change the order of the ACEs and ACL objects within the table, add or edit ACEs and ACL objects, and delete ACEs and ACL objects.
The title of the dialog box indicates the type of ACL you are creating: Extended, Standard, or Web Type. The dialog boxes are essentially the same, the difference being the columns displayed in the ACE table.
Navigation Path
Select Tools > Policy Object Manager, then select Access Control Lists from the Object Type selector. Select the tab for the type of ACL object you want to create, and then right-click inside the work area and select New Object or right-click a row and select Edit Object.
Related Topics
•
Creating Access Control List Objects, page 9-20
•
Creating Extended Access Control List Objects, page 9-20
•
Creating Standard Access Control List Objects, page 9-22
•
Creating Web Access Control List Objects, page 9-23
•
Contiguous and Discontiguous Network Masks, page 9-70
•
Understanding Network/Host Objects, page 9-68
•
Understanding Service Objects, page 9-86
Field Reference
Table F-12 Add and Edit Access List Dialog Boxes
Element
|
Description
|
Name
|
The object name, which can be up to 128 characters. Object names are not case-sensitive. For more information, see Guidelines for Managing Objects, page 9-5.
|
Description
|
An optional description of the object.
|
Access Control Entry table
|
The access control entries (ACEs) and ACL objects that are part of the ACL. The table displays the name of the entry or object, description, options, services, and other attributes of the entry.
In the Permit column, a green checkmark indicates that the entry permits traffic, whereas a red circle with a slash indicates that traffic is denied.
The source and, if applicable, destination addresses can be host IP addresses, network addresses, or network/host policy objects.
• To add an ACE, click the Add button and fill in the dialog box for the type of ACL you are creating:
– Add and Edit Extended Access Control Entry Dialog Boxes
– Add and Edit Standard Access Control Entry Dialog Boxes
– Add and Edit Web Access Control Entry Dialog Boxes
• To edit an ACE, select it and click the Edit button.
• To delete an ACE, select it and click the Delete button.
• To change the position of an entry, select it and click the Up/Down arrow buttons as required. Entries are evaluated top to bottom, so correct positioning is crucial for you to get the results you intend.
|
Category
|
The category assigned to the object. Categories help you organize and identify rules and objects. See Using Category Objects, page 9-4.
|
Allow Value Override per Device
Overrides
Edit button
|
Whether to allow the object definition to be changed at the device level. For more information, see Allowing a Global Object to Be Overridden, page 9-116 and Overriding Global Objects for Individual Devices, page 9-116.
If you allow device overrides, you can click the Edit button to create, edit, and view the overrides. The Overrides field indicates the number of devices that have overrides for this object.
|
Add and Edit Extended Access Control Entry Dialog Boxes
Use the Add or Edit Extended Access Control Entry dialog box to add an access control entry (ACE) or an ACL object to an Extended ACL object.
Navigation Path
From the Add or Edit Access List Dialog Boxes for Extended ACL objects, click the Add button in the ACE table, or select a row and click the Edit button.
Related Topics
•
Creating Extended Access Control List Objects, page 9-20
•
Understanding Network/Host Objects, page 9-68
•
Understanding Service Objects, page 9-86
Field Reference
Table F-13 Add and Edit Extended Access Control Entry Dialog Boxes
Element
|
Description
|
Type
|
The type of entry you are adding. The fields on the dialog box change based on your selection.
• Access Control Entry—You want to define an ACE.
• ACL Objects—You want to include an existing ACL object. You are presented with a list of available ACL objects. Select the objects you want to include and click the >> button to move them to the list of selected objects. You can remove an object by selecting it and clicking <<. You can also edit objects in the selected objects list. For information on filtering the contents of the list of available objects, see Filtering Items in Selectors, page 3-14.
|
Action
|
The action to take on traffic defined in the entry, either to permit (allow) the traffic or to deny (prohibit) it.
|
Category
|
The category assigned to the object. Categories help you organize and identify rules and objects. See Using Category Objects, page 9-4.
|
Source
Destination
|
The source or destination of the traffic. You can enter more than one value by separating the items with commas.
You can enter any combination of the following address types. For more information, see Supported IP Address Formats, page 9-69 and Specifying IP Addresses During Policy Definition, page 9-74.
• Network/host object. Enter the name of the object or click Select to select it from a list. You can also create new network/host objects from the selection list.
• Host IP address, for example, 10.10.10.100.
• Network address, including subnet mask, in either the format 10.10.10.0/28 or 10.10.10.0/255.255.255.0.
• A range of IP addresses, for example, 10.10.10.100-10.10.10.200.
• An IP address pattern in the format 10.10.0.10/255.255.0.255, where the mask is a discontiguous bit mask (see Contiguous and Discontiguous Network Masks, page 9-70).
|
Service
|
The services that define the type of traffic to act on. You can enter more than one value by separating the items with commas.
You can enter any combination of the service types. If you type in a service, you are prompted as you type with valid values. You can select a value from the list and press Enter.
• Service object. Enter the name of the object or click Select to select it from a list. You can also create new service objects from the selection list.
• TCP or UDP / Destination port or port range (for example, TCP / 80).
• TCP or UDP / Source port or port range / Destination port or port range (for example, TCP / 1024-65535/80).
• ICMP / ICMP message (for example, ICMP / echo-reply, ICMP / 200).
|
Description
|
An optional description of the object.
|
Advanced button
|
Click this button to define logging options for the entry:
• For PIX, ASA, and FWSM devices, you can enable:
– Default logging—If a packet is denied, message 106023 is generated. If a packet is permitted, no message is generated.
– Per ACE logging—If a packet is denied, message 106100 is generated. You can select the logging severity level for the messages, and the interval (in seconds from 1 to 600) for generating messages.
• For IOS devices, when you enable logging, informational messages about packets that match the entry are sent to the console. You can also elect to include the input interface and source MAC address or VC in the logging output.
|
Add and Edit Standard Access Control Entry Dialog Boxes
Use the Add or Edit Standard Access Control Entry dialog box to add an access control entry (ACE) or an ACL object to a Standard ACL object.
Navigation Path
From the Add or Edit Access List Dialog Boxes for Standard ACL objects, click the Add button in the ACE table, or select a row and click the Edit button.
Related Topics
•
Creating Standard Access Control List Objects, page 9-22
•
Understanding Network/Host Objects, page 9-68
•
Understanding Service Objects, page 9-86
Field Reference
Table F-14 Add and Edit Standard Access Control Entry Dialog Boxes
Element
|
Description
|
Type
|
The type of entry you are adding. The fields on the dialog box change based on your selection.
• Access Control Entry—You want to define an ACE.
• ACL Objects—You want to include an existing ACL object. You are presented with a list of available ACL objects. Select the objects you want to include and click the >> button to move them to the list of selected objects. You can remove an object by selecting it and clicking <<. You can also edit objects in the selected objects list. For information on filtering the contents of the list of available objects, see Filtering Items in Selectors, page 3-14.
|
Action
|
The action to take on traffic defined in the entry, either to permit (allow) the traffic or to deny (prohibit) it.
|
Category
|
The category assigned to the object. Categories help you organize and identify rules and objects. See Using Category Objects, page 9-4.
|
Source
|
The source of the traffic. You can enter more than one value by separating the items with commas.
You can enter any combination of the following address types. For more information, see Supported IP Address Formats, page 9-69 and Specifying IP Addresses During Policy Definition, page 9-74.
• Network/host object. Enter the name of the object or click Select to select it from a list. You can also create new network/host objects from the selection list.
• Host IP address, for example, 10.10.10.100.
• Network address, including subnet mask, in either the format 10.10.10.0/28 or 10.10.10.0/255.255.255.0.
• A range of IP addresses, for example, 10.10.10.100-10.10.10.200.
• An IP address pattern in the format 10.10.0.10/255.255.0.255, where the mask is a discontiguous bit mask (see Contiguous and Discontiguous Network Masks, page 9-70).
|
Description
|
An optional description of the object.
|
Log Option
|
Whether to create log entries when traffic meets the entry criteria. ACL logging generates syslog message 106023 for denied packets. Deny packets must be present to log denied packets.
|
Add and Edit Web Access Control Entry Dialog Boxes
Use the Add or Edit Web Access Control Entry dialog box to add an access control entry (ACE) or an ACL object to a Web Type ACL object.
Navigation Path
From the Add or Edit Access List Dialog Boxes for Web Type ACL objects, click the Add button in the ACE table, or select a row and click the Edit button.
Related Topics
•
Creating Web Access Control List Objects, page 9-23
•
Understanding Network/Host Objects, page 9-68
•
Understanding Service Objects, page 9-86
Field Reference
Table F-15 Add and Edit Web Access Control Entry Dialog Boxes
Element
|
Description
|
Type
|
The type of entry you are adding. The fields on the dialog box change based on your selection.
• Access Control Entry—You want to define an ACE.
• ACL Objects—You want to include an existing ACL object. You are presented with a list of available ACL objects. Select the objects you want to include and click the >> button to move them to the list of selected objects. You can remove an object by selecting it and clicking <<. You can also edit objects in the selected objects list. For information on filtering the contents of the list of available objects, see Filtering Items in Selectors, page 3-14.
|
Action
|
The action to take on traffic defined in the entry, either to permit (allow) the traffic or to deny (prohibit) it.
|
Filter Destination
|
Whether the entry specifies a network filter (host or network address) or a URL filter (web site address). Your selection changes the fields on the dialog box. The fields are described below.
|
Destination
(Network Filter only.)
|
The destination of the traffic. You can enter more than one value by separating the items with commas.
You can enter any combination of the following address types. For more information, see Supported IP Address Formats, page 9-69 and Specifying IP Addresses During Policy Definition, page 9-74.
• Network/host object. Enter the name of the object or click Select to select it from a list. You can also create new network/host objects from the selection list.
• Host IP address, for example, 10.10.10.100.
• Network address, including subnet mask, in either the format 10.10.10.0/28 or 10.10.10.0/255.255.255.0.
• A range of IP addresses, for example, 10.10.10.100-10.10.10.200.
• An IP address pattern in the format 10.10.0.10/255.255.0.255, where the mask is a discontiguous bit mask (see Contiguous and Discontiguous Network Masks, page 9-70).
|
Ports
(Network Filter only.)
|
The port numbers or port list policy objects that define the port the traffic uses, if you want to use port identification. You can enter more than one value by separating the items with commas.
You can enter any combination of the following types:
• Port list object. Enter the name of the object or click Select to select it from a list. You can also create new port list objects from the selection list.
• Port number, for example, 80.
• A range of ports, for example, 80-90.
|
URL Filter
(URL Filter only.)
|
The Universal Resource Locator (URL), or web address, of the traffic. You can use an asterisk as a match-all wildcard. For example, http://*.cisco.com matches all servers on the cisco.com network. You can specify any valid URL.
|
Logging
|
The type of logging to use for this entry:
• Select Log Disabled to not create log entries.
• Select Default to use the default settings on the device.
• All other available options enable logging and identify the log level that will be used.
|
Logging Interval
|
The interval of time, in seconds, used to generate logging messages, from 1 to 600. The default is 300. You can modify this field only if you select a logging level in the Logging field.
|
Time Range
|
The time range policy object that defines the time range associated with the entry. The time range defines the access to the device and relies on the device's system clock. For more information, see Understanding Time Range Objects, page 9-108.
Enter the name of the object or click Select to select it from a list. You can also create new time range objects from the selection list.
Note Time range is not supported on FWSM 2.x or PIX 6.3 devices.
|
Category
|
The category assigned to the object. Categories help you organize and identify rules and objects. See Using Category Objects, page 9-4.
|
Description
|
An optional description of the object.
|
ASA User Group Dialog Box
Use the ASA User Group dialog box to create, copy, and edit an ASA user group object. ASA user groups define a set of user-oriented attributes and values for IPsec connections (Easy VPN, remote access and SSL VPN) that are stored either internally (locally) on the device or externally on an AAA server.
Navigation Path
Select Tools > Policy Object Manager, then select ASA Group Policies from the Object Type Selector. Right-click inside the work area, then select New Object or right-click a row, then select Edit Object.
Tip
You can also access this dialog box from the Remote Access VPN > Group Policies policy.
Related Topics
•
Understanding ASA User Group Objects, page 9-31
•
Creating ASA User Group Objects, page 9-33
•
Policy Object Manager Window
Field Reference
Table F-16 ASA User Group Dialog Box > Technology Settings
Element
|
Description
|
Name
|
The name of the object (up to 128 characters). The object name is displayed in the ASA User Groups page.
Object names are not case sensitive. For more information, see Guidelines for Managing Objects, page 9-5.
|
Description
|
Additional information about the object (up to 1024 characters).
|
Settings pane
|
A list of settings that you can configure for an ASA user group object.
When you open the ASA user group dialog box, the Technology settings are displayed.
Note Settings (apart from Technology) are available for configuration only if you selected to store the ASA user group's attributes locally on the device (when configuring the Technology settings). When configuring on the local device, the list of settings available for configuration differ depending on whether you are configuring the ASA user group for an Easy VPN/remote access VPN, or SSL VPN, or both.
|
Technology settings
|
Group Policy Type
|
Unavailable if you are editing an ASA user group object.
If you are creating or copying an ASA user group object, select where the ASA user group's attributes and values are stored:
• Internal—Internally (locally) on the device. This is the default.
• External—Externally on an AAA server.
Note If you select to store the ASA user group's attributes on an external AAA server, you do not need to configure any of the Technology settings.
|
Technology
|
Unavailable if you are editing an ASA user group object.
If you are creating or copying an ASA user group object, and the ASA user group's attributes are stored on the device, select the type of VPN for which you are creating the ASA user group object:
• Easy VPN/IPSec VPN
• SSL VPN
• Easy VPN/IPSec and SSL—the user group object can be shared between Easy VPN/IPsec VPN and SSL VPN. This is the default.
|
External Server Group
|
If the ASA user group's attributes are stored on an external AAA server, specify the AAA server group that will be used for authentication.
You can click Select to open the AAA Server Groups Selector from which you can make your selection.
|
Password
|
Available after you have specified the AAA server group that will be used for authentication.
Enter an alphanumeric keyword that will serve as the password to the AAA server. The keyword can be a maximum of 128 characters; spaces are not allowed.
|
Confirm
|
After you have entered the alphanumeric keyword that will serve as the password to the AAA server, enter the password again to confirm it.
|
ASA User Group Dialog Box: Client Configuration Settings
Use the Client Configuration settings page to configure the Cisco client parameters for the ASA user group in an Easy VPN or remote access VPN.
Navigation Path
Open the ASA User Group Dialog Box, select the Easy VPN/Remote Access VPN (or Both) technology, then select Client Configuration under the Easy VPN/ Remote Access VPN folder in the Settings pane.
Related Topics
•
Understanding ASA User Group Objects, page 9-31
•
Creating ASA User Group Objects, page 9-33
•
ASA User Group Dialog Box
Field Reference
Table F-17 ASA User Group Dialog Box > Client Configuration Settings
Element
|
Description
|
Store Password on Client System
|
When selected, enables users to store a password on their LOCAL system.
Note It is recommended that you enable password storage only on systems that you know to be in secure sites.
|
Enable IPsec over UDP
|
When selected, allows a Cisco VPN client or hardware client to connect via UDP to a security appliance that is running NAT.
Note The Cisco VPN client must also be configured to use IPsec over UDP, which is configured by default on certain devices.
|
UDP Port
|
Specifies a port value when IPsec over UDP is enabled, within the range 4001-49151.
In IPsec negotiations, the security appliance listens on the configured port and forwards UDP traffic for that port even if other filter rules drop UDP traffic. Port values are 4001-49151.
|
IPsec Backup Servers
|
Specify the backup servers configuration from these options:
• Keep Client Configuration—The security appliance sends no backup server information to the client. The client uses its own backup server list, if configured. This is the default.
• Clear Client Configuration—The client uses no backup servers. The security appliance pushes a null server list.
• Use Specified Backup Servers—Enables you to configure backup servers either on the client or on the primary security appliance. If you configure backup servers on the security appliance, it pushes the backup server policy to the clients in the group, replacing the backup server list on the client if one is configured. When selected, you must specify the IPsec Backup Server addresses.
|
Servers List
|
Specifies the backup server IP addresses.
You can click Select to open the Network/Hosts Selector from which you can make your selection.
|
ASA User Group Dialog Box: Client Firewall Attributes
Use the Client Firewall Attributes settings to configure the firewall settings for VPN clients for the ASA user group in an Easy VPN or IPSec VPN.
Note
Only VPN clients running Microsoft Windows can use these firewall settings.
Navigation Path
Open the ASA User Group Dialog Box, select the Easy VPN/Remote Access VPN (or Both) technology, then select Client Firewall Attributes under the Easy VPN/ Remote Access VPN folder in the Settings pane.
Related Topics
•
Understanding ASA User Group Objects, page 9-31
•
Creating ASA User Group Objects, page 9-33
•
ASA User Group Dialog Box
Field Reference
Table F-18 ASA User Group Dialog Box > Client Firewall Attributes Settings
Element
|
Description
|
Firewall Mode
|
Remote users connecting to the security appliance with the VPN client can select from the following firewall mode options:
• No Firewall—No firewall exists. If you select this option, the remaining fields on the page are unavailable.
• Firewall Required—(The default). A firewall exists and is required. All users in this group must use the designated firewall. The security appliance drops any session that attempts to connect without the designated, supported firewall installed and running. In this case, the security appliance notifies the VPN client that its firewall configuration does not match.
Note Make sure the group does not include any clients other than Windows VPN Clients. Any other clients in the group (including VPN 3002 Hardware Clients) are unable to connect.
• Firewall Optional—A firewall exists and is optional. This is beneficial if you have remote users in this group who do not yet have firewall capacity. This option allows all the users in the group to connect. Those who have a firewall can use it; users that connect without a firewall receive a warning message. This setting is useful if you are creating a group in which some users have firewall support and others do not. For example, you may have a group that is in gradual transition, in which some members have set up firewall capacity and others have not yet done so.
|
Firewall Type
|
Lists firewalls from several vendors, including Cisco.
• Cisco Integrated Client Firewall
• Cisco Security Agent—Specifies Cisco Intrusion Prevention Security Agent firewall type.
• Custom Firewall—When selected, the fields in the Custom Firewall and Firewall Policy group boxes become active. The firewall you designate must correlate with the firewall policies available. The specific firewall you configure determines which firewall policy options are supported.
• Network ICE BlackICE Defender
• Sygate Personal Firewall
• Sygate Personal Firewall Pro
• Sygate Security Agent
• Zone Labs Zone Alarm
|
Get Policy From Remote Firewall
|
Select this option when the client PC firewall application controls the firewall policy.
When selected, the security appliance checks to make sure that the firewall is running. It asks, "Are You There?" If there is no response, the security appliance tears down the tunnel.
|
Use Specified Policy
|
When selected, enables you to specify the actual VPN client firewall policy that must be applied by the specified client firewall type.
|
Inbound Traffic Policy
|
When selected, enables you to enter an ACL to specify the policy the client uses for inbound traffic.
You can click Select to open the Access Control Lists Selector from which you can make your selection.
|
Outbound Traffic Policy
|
When selected, enables you to enter an ACL to specify the policy the client uses for outbound traffic.
You can click Select to open the Access Control Lists Selector from which you can make your selection.
|
Custom Firewall
|
Vendor ID
|
Specifies the vendor of the custom firewall being configured for this ASA user group. Values are 1-32.
|
Product ID
|
Specifies the product or model name of the custom firewall being configured for this ASA user group.
Values are 1-32 or 255. Multiple ranges are allowed, for example, 4-12, 24-32. Use 255 for all supported products.
|
Description
|
Enables you to enter a description to help you identify the custom firewall.
Maximum characters allowed is 1024.
|
ASA User Group Dialog Box: Hardware Client Attributes
Use the Hardware Client Attributes settings to configure the VPN 3002 Hardware Client settings for the ASA user group in an Easy VPN or IPSec VPN.
Navigation Path
Open the ASA User Group Dialog Box, select the Easy VPN/IPsec Remote Access VPN (or Both) technology, then select Hardware Client Attributes under the Easy VPN/Remote Access VPN folder in the Settings pane.
Related Topics
•
Understanding ASA User Group Objects, page 9-31
•
Creating ASA User Group Objects, page 9-33
•
ASA User Group Dialog Box
Field Reference
Table F-19 ASA User Group Dialog Box > Hardware Client Attributes
Element
|
Description
|
Require Interactive Client Authentication
|
When selected, enables secure unit authentication, which provides additional security by requiring VPN hardware clients to authenticate with a username and password each time that the client initiates a tunnel. The hardware client does not have a saved username and password.
Note Secure unit authentication requires that you have an authentication server group configured for the tunnel group the hardware clients use. If you require secure unit authentication on the primary security appliance, be sure to configure it on any backup servers as well.
|
Require Individual User Authentication
|
When selected, requires that individual users behind a hardware client authenticate to gain access to the network across the tunnel. Individual users authenticate according to the order of authentication servers that you configure.
When deselected, allows inheritance of a value for user authentication from another user group policy.
|
Enable Cisco IP Phone Bypass
|
When selected, allows IP phones behind hardware clients to connect without undergoing a user authentication processes. Secure unit authentication remains in effect.
|
Enable LEAP Bypass
|
When selected, enables LEAP packets from wireless devices behind a VPN hardware client to travel across a VPN tunnel prior to user authentication. This action lets workstations using Cisco wireless access point devices establish LEAP authentication and then authenticate again per user authentication.
Note Cisco Systems has developed an 802.1X wireless authentication type called Cisco LEAP. LEAP (Lightweight Extensible Authentication Protocol) implements mutual authentication between a wireless client on one side of a connection and a RADIUS server on the other side. The credentials used for authentication, including a password, are always encrypted before they are transmitted over the wireless medium.
|
Allow Network Extension Mode
|
When selected, enables network extension mode for hardware clients.
Network Extension mode lets hardware clients present a single, routable network to the remote private network over the VPN tunnel. IPsec encapsulates all traffic from the private network behind the hardware client to networks behind the security appliance. PAT does not apply. Devices behind the security appliance have direct access to devices on the private network behind the hardware client over the tunnel, and only over the tunnel, and vice versa. The hardware client must initiate the tunnel, but after the tunnel is up, either side can initiate data exchange.
|
Idle Timeout Mode
|
Specified Timeout
|
When selected, enables you to specify an idle timeout for individual users behind hardware clients. If there is no communication activity by a user behind a hardware client in the idle timeout period, the security appliance terminates the client's access.
Values are 1-35791394 minutes.
|
Unlimited Timeout
|
When selected, permits an unlimited idle timeout period.
|
ASA User Group Dialog Box: IPsec Settings
Use the IPsec settings to specify tunneling protocols, filters, connection settings, and servers for the ASA user group in an Easy VPN or IPSec VPN. This creates security associations that govern authentication, encryption, encapsulation, and key management.
Navigation Path
Open the ASA User Group Dialog Box, select the Easy VPN/Remote Access VPN (or Both) technology, then select IPsec under the Easy VPN/Remote Access VPN folder in the Settings pane.
Related Topics
•
Understanding ASA User Group Objects, page 9-31
•
Creating ASA User Group Objects, page 9-33
•
ASA User Group Dialog Box
Field Reference
Table F-20 ASA User Group Dialog Box > IPsec Settings
Element
|
Description
|
Enable Re-Authentication on IKE Re-Key
|
When selected, the security appliance prompts the user to enter a username and password during initial Phase 1 IKE negotiation and also prompts for user authentication whenever an IKE rekey occurs, providing additional security.
Note Reauthentication fails if no user is at the other end of the connection.
|
Enable IPsec Compression
|
When selected, enables data compression that speeds up data transmission rates for remote dial-in users connecting with modems.
Caution  Data compression increases the memory requirement and CPU usage for each user session and consequently decreases the overall throughput of the security appliance. For this reason, it is recommended that you enable data compression only for remote users connecting with a modem. Design a group policy specific to modem users, and enable compression only for them.
|
Enable Perfect Forward Secrecy (PFS)
|
When selected, enables the use of Perfect Forward Secrecy (PFS) to generate and use a unique session key for each encrypted exchange.
In IPsec negotiations, PFS ensures that each new cryptographic key is unrelated to any previous key.
|
Tunnel Group Lock
|
Specifies whether to restrict remote users to access through the tunnel group only.
Group-lock restricts users by checking if the group configured in the VPN client is the same as the tunnel group to which the user is assigned. If it is not, the security appliance prevents the user from connecting. If you do not configure group-lock, the security appliance authenticates users without regard to the assigned group. Group locking is disabled by default.
|
Client Access Rules
|
Priority
|
Identifies the priority for this rule.
The rule with the lowest integer has the highest priority. Therefore, the rule with the lowest integer that matches a client type and/or version is the rule that applies. If a lower priority rule contradicts, the security appliance ignores it.
|
Action
|
Specifies whether this rule permits or denies access.
|
Client Type
|
Specifies the type of VPN client to which this rule applies, software or hardware, and for software clients, all Windows clients or a subset.
|
VPN Client Version
|
Specifies the versions of the VPN client (software or firmware) to which this rule applies. Multiple entries are separated by a comma.
|
Create button
|
Opens a dialog box in which you can create a client access rule. See ASA User Group Dialog Box: Client Access Rules Dialog Box.
|
Edit button
|
Opens a dialog box in which you can edit a selected client access rule. See ASA User Group Dialog Box: Client Access Rules Dialog Box.
|
Delete button
|
Enables you to delete selected client access rules from the table.
|
ASA User Group Dialog Box: Client Access Rules Dialog Box
In the Client Access Rules dialog box, you can create or edit the priority, action, VPN client type and VPN client version for a client access rule.
Navigation Path
Open the ASA User Group Dialog Box: IPsec Settings, then click Create, or select an item in the table and click Edit.
Related Topics
•
ASA User Group Dialog Box: IPsec Settings
Field Reference
Table F-21 ASA User Group Dialog Box > IPsec Settings > Client Access Rules Dialog Box
Element
|
Description
|
Priority
|
Associates priority with a value.
The rule with the lowest integer has the highest priority. Therefore, the rule with the lowest integer that matches a client type and/or version is the rule that applies. If a lower priority rule contradicts, the security appliance ignores it. Values are 1-65535.
|
Action
|
Specifies whether this rule permits or denies traffic access.
|
VPN Client Type
|
Specifies the type of VPN client to which this rule applies, software or hardware, and for software clients, all Windows clients or a subset.
|
VPN Client Version
|
Specifies the version or versions of the VPN client (software or firmware) to which this rule applies. Multiple entries are separated by a comma.
|
ASA User Group Dialog Box: SSL VPN Clientless Settings
Clientless settings enable you to configure the Clientless mode of access to the corporate network in an SSL VPN, for the ASA user group object.
In clientless access mode, once a user is authenticated and a session is established, an SSL VPN portal page and toolbar is displayed on the user's web browser. From the portal page, the user can access all available HTTP sites, access web e-mail, and browse Common Internet File System (CIFS) file servers.
Navigation Path
Open the ASA User Group Dialog Box, select the SSL VPN (or Easy VPN/IPSec and SSL) technology, then select Clientless under the SSL VPN folder in the Settings pane.
Related Topics
•
Understanding ASA User Group Objects, page 9-31
•
Creating ASA User Group Objects, page 9-33
•
ASA User Group Dialog Box
Field Reference
Table F-22 ASA User Group Dialog Box > SSL VPN Clientless Settings
Element
|
Description
|
Portal Page Websites
|
A list of websites that will be displayed on the portal page as a bookmark to enable users to access the resources available on the SSL VPN websites.
You can click Select to open the URL List Selector from which you can select the required URL List from a list of URL List objects. For information about the object selector dialog box that opens, see Object Selectors.
|
Allow Users to Enter Websites
|
When selected, enables the remote user to input the website URLs directly.
|
Enable File Server Browsing
|
When selected, enables the remote user read-only access to browse the shared files on the Common Internet File System (CIFS) file servers.
|
Enable File Server Entry
|
When selected, enables the remote user full-write access to modify the shared files on the Common Internet File System (CIFS) file servers.
|
Enable Hidden Shares
|
When selected, controls the visibility of hidden shares for CIFS files,
|
HTTP Proxy
|
Select one of the following options:
• Enabled—When selected, enables user access to the external HTTP proxy server to which the security appliance forwards HTTP connections.
• Disabled—When selected, disables user access to the external HTTP proxy server to which the security appliance forwards HTTP connections.
• Auto Start—
When selected, starts HTTP proxy automatically upon user login.
|
Filter ACL
|
Specifies the WebType access control list that will be used to restrict user access to the SSL VPN.
You can click Select to open the Access Control Lists Selector from which you can make your selection.
|
UNIX Authentication Group ID
|
Specifies the UNIX authentication group ID.
|
UNIX Authentication User ID
|
Specifies the UNIX authentication user ID.
|
Smart Tunnel
|
Specifies the name of the smart tunnel assigned to this ASA user group.
|
Auto Start Smart Tunnel
|
When selected, starts smart tunnel access automatically upon user login.
|
Port Forwarding List
|
Specifies the name of the port forwarding list assigned to this ASA user group. Port forwarding lists contain the set of applications that users of clientless SSL VPN sessions can access over forwarded TCP ports.
|
Auto Start Port Forwarding
|
When selected, starts port forwarding automatically upon user login.
|
Port Forwarding Applet Name
|
Provides the application name or short description that displays on the end user Port Forwarding Java applet screen. Maximum 64 characters.
|
ASA User Group Dialog Box: SSL VPN Full Client Settings
Full Client settings enable you to configure the Full Client mode of access to the corporate network in an SSL VPN, for the ASA user group object.
Full Client mode enables access to the corporate network completely over an SSL VPN tunnel. In Full Client access mode, the tunnel connection is determined by the group policy configuration. The full client software, SSL VPN Client (SVC), is downloaded to the remote client, so that a tunnel connection is established when the remote user logs in to the SSL VPN gateway.
Navigation Path
Open the ASA User Group Dialog Box, select the SSL VPN (or Easy VPN/IPSec and SSL) technology, then select Full Client under the SSL VPN folder in the Settings pane.
Related Topics
•
Understanding ASA User Group Objects, page 9-31
•
Creating ASA User Group Objects, page 9-33
•
ASA User Group Dialog Box
Field Reference
Table F-23 ASA User Group Dialog Box > SSL VPN Full Client Settings
Element
|
Description
|
Enable Full Client
|
When selected, enalbes Full Client mode.
|
Mode
|
Use Other Access Modes if AnyConnect Client Download Fails
|
For the full tunnel access mode to work properly, the SSL VPN Client (SVC) software must be installed on the device.
When selected, this option enables the remote client to use clientless or thin client access modes if the SVC download fails.
|
Full Client Only
|
When selected, enables only the Full Client access mode to be configured.
|
Keep AnyConnect Client on Client System
|
When selected, enables the Full Client software to remain on the client's PC after the client has logged out.
When deselected, clients must download the software each time they establish communication with the gateway.
|
Enable Compression
|
When selected, enables data compression that speeds up data transmission rates for remote users connecting with modems.
|
Enable Keepalive Messages
|
When selected, enables keepalive messages to be exchanged between peers to demonstrate that they are available to send and receive data in the tunnel.
Keepalive messages transmit at set intervals, and any disruption in that interval results in the creation of a new tunnel, using a backup device.
Then enter the time interval (in seconds) that the remote client waits between sending IKE keepalive packets, in the Interval field.
|
Client Dead Peer Detection Timeout (sec)
|
The time interval, in seconds, that the Dead Peer Detection (DPD) timer is reset each time a packet is received over the SSL VPN tunnel from the remote user.
Note DPD is used to send keepalive messages between peer devices only when no incoming traffic is received and outbound traffic needs to be sent.
|
Gateway Dead Peer Detection Timeout (sec)
|
The time interval, in seconds, that the Dead Peer Detection (DPD) timer is reset each time a packet is received over the SSL VPN tunnel from the gateway.
|
Key Renegotiation Method
|
The method by which the tunnel key is refreshed for the remote user group client:
• Disabled—Disables the tunnel key refresh.
• Use Existing Tunnel—Renegotiates the SSL tunnel connection.
• Create New Tunnel—Initiates a new tunnel connection.
Then enter the time interval (in minutes) between the tunnel refresh cycles, in the Interval field.
|
Enable Datagram Transport Layer Security
|
When selected, enables datagram transport layer security on an interface.
|
AnyConnect Module
|
Specifies an optional module that the Cisco AnyConnect VPN Client (CVC) requires for optional features.
|
AnyConnect MTU
|
Specifies the maximum transmission unit (MTU) size for SSL VPN connections established by the Cisco AnyConnect VPN Client.
|
AnyConnect Profile Name
|
Specifies a CVC profiles package downloaded to Cisco AnyConnect VPN Client (CVC) users.
|
Prompt User to Choose Client
|
When selected, the user chooses which client to use.
Enter the number of seconds the user has to make a selection in the Time User Has to Choose field.
|
Default Location
|
Specify one of the following locations as the default:
1. Web Portal—
2. AnyConnect Client—
|
ASA User Group Dialog Box: SSL VPN Settings
SSL VPN Settings enable you to configure attributes that are required for Clientless and Port Forwarding access modes to work, including auto signon rules for user access to servers. Auto Signon configures the security appliance to automatically pass SSL VPN user login credentials (username and password) on to internal servers. You can configure multiple auto signon rules. For more information, see Understanding Single Sign-On Server Objects, page 9-89.
Navigation Path
Open the ASA User Group Dialog Box, select the SSL VPN (or Easy VPN/IPSec and SSL) technology, then select Settings under the SSL VPN folder in the Settings pane.
Related Topics
•
Understanding Single Sign-On Server Objects, page 9-89
•
Understanding ASA User Group Objects, page 9-31
•
Creating ASA User Group Objects, page 9-33
•
ASA User Group Dialog Box
Field Reference
Table F-24 ASA User Group Dialog Box > SSL VPN Settings
Element
|
Description
|
Clientless/Port Forwarding Setting
|
Home Page
|
The URL of the SSL VPN home page on which the available websites appear as links.
|
Authentication Failure Message
|
The error message displayed on the login page if a user authentication failure occurs.
|
Minimum Keepalive Object Size (kilobytes)
|
Specifies the minimum size (in kilobytes) of an IKE keepalive packet that can be stored in the cache on the security appliance.
|
Single Sign On Server
|
Specifies the Single Sign On (SSO) server that allows users to enter their username and password once, and be able to access a range of servers.
You can click Select to open a dialog box that lists all available SSO servers from which you can make your selection, or create an SSO server object. See Understanding Single Sign-On Server Objects, page 9-89.
|
Enable HTTP Compression
|
When selected, enables an HTTP compressed object to be cached on the security appliance.
|
Auto Signon Rules table
|
IP Address
|
The IP address of the SSO server that receives the login credentials.
|
Mask
|
The IP mask of the SSO server that receives the login credentials.
|
URL
|
The URL used to specify the SSO server that receives the login credentials.
|
Authentication Type
|
The authentication method used to configure SSO—HTTP Basic, NTLM authentication, or both of these.
|
Up/Down buttons
|
Enable you to change the order of the Auto Signon rules.
Note The security appliance processes the rules according to the order in the table.
|
Add button
|
Opens a dialog box in which you can create an Auto Signon rule. See ASA User Group Dialog Box: Auto Signon Rules Dialog Box.
|
Edit button
|
Opens a dialog box in which you can edit the parameters of a selected Auto Signon rule. See ASA User Group Dialog Box: Auto Signon Rules Dialog Box.
|
Delete button
|
Removes selected Auto Signon rules from the table.
|
Portal Page Customization
|
Specifies the customization profile that defines the appearance of the portal page that allows the remote user access to all the resources available on the SSL VPN networks.
You can click Select to open a dialog box that lists all available SSL VPN customization objects, from which you can make your selection. See Understanding SSL VPN Customization Objects, page 9-97.
|
User Storage Location
|
Specifies the location where personalized user information is stored between clientless SSL VPN sessions.
|
Storage Key
|
Specifies the storage key used to protect data stored between sessions.
|
Post Max Size
|
Specifies the maximum size allowed for a posted object. The range is 0 through 2147483647.
|
Upload Max Size
|
Specifies the maximum size allowed for a uploaded object. The range is 0 through 2147483647.
|
Download Max Size
|
Specifies the maximum size allowed for a downloaded object. The range is 0 through 2147483647.
|
ASA User Group Dialog Box: Auto Signon Rules Dialog Box
Use this dialog box to configure the Auto Signon rules that the security appliance uses to pass SSL VPN user login credentials on to an internal server. You can configure multiple Auto Signon rules—the security appliance processes them according to the input order.
Navigation Path
Open the ASA User Group Dialog Box: SSL VPN Settings, then click Create, or select an item in the table and click Edit.
Related Topics
•
ASA User Group Dialog Box
•
ASA User Group Dialog Box: SSL VPN Settings
•
Understanding Single Sign-On Server Objects, page 9-89
Field Reference
Table F-25 ASA User Group Dialog Box > Settings > Auto Signon Rules Dialog Box
Element
|
Description
|
Allow IP
|
When selected, enables you to specify the IP address and IP mask of the SSO server that receives the login credentials, in the fields provided.
|
Allow URL
|
When selected, enables you to specify the URL of the SSO server that receives the login credentials, in the field provided.
|
Authentication Type
|
Select the required SSO authentication method.
Options are Basic, NTLM (NT LAN Manager) authentication, FTP, or all of these methods.
|
ASA User Group Dialog Box: DNS/WINS Settings
Configuring the DNS/WINS settings for your ASA user group enable you to define the DNS and WINS servers and the domain name that should be pushed to clients associated with the ASA user group.
Note
The DNS/WINS settings you configure for an ASA user group apply in Easy VPN, remote access VPN and SSL VPN configurations.
Navigation Path
Open the ASA User Group Dialog Box, select the On Device group policy source, then select DNS/WINS in the Settings pane.
Related Topics
•
ASA User Group Dialog Box
•
Understanding ASA User Group Objects, page 9-31
•
Creating ASA User Group Objects, page 9-33
Field Reference
Table F-26 ASA User Group Dialog Box > DNS/WINS Settings
Element
|
Description
|
Primary DNS Server
|
The IP address of the primary DNS server you want to configure on the ASA user group.
You can click Select to open the Network/Hosts Selector from which you can make your selection.
|
Secondary DNS Server
|
The IP address of the secondary DNS server you want to configure on the ASA user group.
You can click Select to open the Network/Hosts Selector from which you can make your selection.
|
Primary WINS Server
|
The IP address of the primary WINS server you want to configure on the ASA user group.
You can click Select to open the Network/Hosts Selector from which you can make your selection.
|
Secondary WINS Server
|
The IP address of the secondary WINS server you want to configure on the ASA user group.
You can click Select to open the Network/Hosts Selector from which you can make your selection.
|
DHCP Network Scope
|
The scope of the DHCP network to be configured on the ASA user group.
You can click Select to open the Network/Hosts Selector from which you can make your selection.
|
Default Domain
|
Specifies the default domain name for the ASA user group.
A blank field = none.
|
ASA User Group Dialog Box: Split Tunneling
Split tunneling lets a remote client conditionally direct packets over an IPsec or SSL VPN tunnel in encrypted form or to a network interface in clear text form. With split tunneling enabled, packets not bound for destinations on the other side of the tunnel do not have to be encrypted, sent across the tunnel, decrypted, and then routed to a final destination. The split tunneling policy is applied to a specific network.
Configuring split tunneling for your ASA user group enables you to specify a secure tunnel to the central site and simultaneous clear text tunnels to the Internet.
Note
The split tunneling settings you configure for an ASA user group apply in Easy VPN, remote access VPN, and SSL VPN configurations.
Navigation Path
Open the ASA User Group Dialog Box, select the On Device group policy source, then select Split Tunneling in the Settings pane.
Related Topics
•
ASA User Group Dialog Box
•
Understanding ASA User Group Objects, page 9-31
•
Creating ASA User Group Objects, page 9-33
Field Reference
Table F-27 ASA User Group Dialog Box > Split Tunneling
Element
|
Description
|
DNS Names
|
A list of domain names that must be tunneled or resolved to the private network. All other names will be resolved via the public DNS server.
Entries in the list of domains are separated by a single space. There is no limit on the number of entries, but the entire string can be no longer than 255 characters. You can use only alphanumeric characters, hyphens (-), and periods (.).
|
Tunnel Option
|
Specifies the traffic that will be secured or transmitted unencrypted across the public network:
• Disabled—(Default) When selected, specifies that no traffic goes in the clear or to any other destination than the security appliance. This, in effect, disables split tunneling. Remote users reach Internet networks through the corporate network and do not have access to local networks.
• Tunnel Specified Traffic—When selected, tunnels all traffic from or to the specified networks. This option enables split tunneling. It lets you create a network list of addresses to tunnel. Data to all other addresses travels in the clear and is routed by the remote user's Internet service provider.
• Exclude Specified Traffic—When selected, enables you to specify a list of networks to which traffic goes in the clear. This feature is useful for remote users who want to access devices on their local network, such as printers, while they are connected to the corporate network through a tunnel. This option applies only to the Cisco VPN client.
|
Networks
|
A list of networks/hosts to which traffic is transmitted secured or unencrypted, depending on the selected Tunnel Policy option.
Multiple entries are separated by commas. Accepted formats are:
• a.b.c.d where a,b,c,d = 0-255 (host).
• a.b.c.d/e where a,b,c,d = 0-255 and e = 1-32 (subnet).
• a.b.c.d-e.f.g.h where a,b,c,d,e,f,g,h = 0-255 (range).
• Freeform text that is the name of the network/host object.
You can click Select to open the Networks/Hosts Selector from which you can make your selection(s).
|
ASA User Group Dialog Box: Connection Settings
An Easy VPN, remote access VPN, or SSL VPN session is disconnected if the client is connected longer than the session timeout, or if it is idle longer than the idle timeout.
Use this page to configure the connection settings for the ASA user group, including the banner text.
Navigation Path
Open the ASA User Group Dialog Box, select the Internal group policy type, then select Connection Settings in the Settings pane.
Related Topics
•
ASA User Group Dialog Box
•
Understanding ASA User Group Objects, page 9-31
•
Creating ASA User Group Objects, page 9-33
Field Reference
Table F-28 ASA User Group Dialog Box > Connection Settings
Element
|
Description
|
Filter ACL
|
Specifies the Access Control List (ACL) that will be used to restrict user access to the SSL VPN.
You can click Select to open the Access Control Lists Selector from which you can make your selection.
|
Banner Text
|
The banner, for example, a welcome message that is displayed on remote clients when they connect. Banner text can be a maximum of 500 characters.
|
Connection Settings
|
Access hours
|
Enables you to enter a time range value that allows VPN access based on specific times of the day and weekly access.
The time range relies on the system clock of the security appliance; therefore, the feature works best with NTP synchronization.
Note Time range is not supported on FWSM or PIX 6.3 devices.
You can click Select to open the Time Ranges Selector from which you can make your selection. See Understanding Time Range Objects, page 9-108.
|
Max Simultaneous Logins
|
Specifies the number of simultaneous logins allowed for any user.
Values are 0-2147483647. A zero (0) value disables login and prevents user access. A user group policy can inherit this value from another user group policy.
Note While there is no maximum limit to the number of simultaneous logins, allowing several could compromise security and affect performance.
|
Max Connect Time
|
Enables you to specify the amount of time that the security appliance should allow for a connection. Options are:
• Specified Connection time—When selected, enables you to specify the connection timeout period. Values are 1-35791394 minutes.
• Unlimited Connection time—When selected, permits an unlimited session timeout period.
|
Idle Timeout (min)
|
Enables you to specify the amount of time that the security appliance should terminate a connection if there is no communication activity. Options are:
• Specified Timeout—When selected, enables you to specify the idle timeout period. Values are 1-35791394 minutes.
• Unlimited Timeout—When selected, permits an unlimited idle timeout period.
|
Category Editor Dialog Box
Use the Category Editor dialog box to edit the name or description of a category object. Category objects help you categorize and readily identify rules and other objects.
Navigation Path
Select Tools > Policy Object Manager, select Categories from the Object Type Selector, and click Edit Object.
Related Topics
•
Using Category Objects, page 9-4
•
Policy Object Manager Window
Field Reference
Table F-29 Category Editor Dialog Box
Element
|
Description
|
Label
|
The color associated with the category.
|
Name
|
The category name (up to 128 characters).
|
Description
|
Additional information about the object (up to 1024 characters).
|
Add or Edit Secure Desktop Configuration Dialog Box
Use the Add or Edit Cisco Secure Desktop Configuration dialog box to create, copy, and edit Cisco Secure Desktop Configuration objects for IOS routers. You can configure the settings required for Windows clients who are connecting from different location types, enable or restrict web browsing and file access for Windows CE clients, and configure the cache cleaner for Macintosh and Linux clients.
Cisco Secure Desktop (CSD) secures network endpoints by providing a reliable means of eliminating all traces of sensitive data by providing a single, secure location for session activity and removal on the client system.
Navigation Path
Select Tools > Policy Object Manager, then select Cisco Secure Desktop (Router) from the Object Type Selector. Right-click inside the work area and select New Object, or right-click a row and select Edit Object.
Related Topics
•
Creating Cisco Secure Desktop Configuration Objects, page 9-85
•
Policy Object Manager Window
Field Reference
Table F-30 Secure Desktop Configuration Dialog Box
Element
|
Description
|
Name
|
The Secure Desktop Configuration object name (up to 128 characters). Object names are not case-sensitive. For more information, see Guidelines for Managing Objects, page 9-5.
|
Description
|
Additional information about the Secure Desktop Configuration object (up to 1024 characters).
|
Windows Location Settings
|
Windows Locations
|
Enable you to create a group of settings for Windows clients connecting from a particular type of location, such as Work, Home, or Insecure. Once you create a location, you can specify how to determine that clients are connecting from that particular location.
For each location you want to configure, enter its name in the field provided, and click Add to move it to the Locations field. You can reorder the locations using the Move Up/Move Down buttons.
CSD checks locations in the order listed in this dialog box, and grants privileges to client PCs based on the first location definition they match. For more information, see Understanding Cisco Secure Desktop Configuration Objects, page 9-85.
|
Close all open browser windows after installation
|
When selected (the default), closes all the open browser windows after the Secure Desktop installation.
|
VPN Feature Policy
|
Select the check boxes to enable these features if installation or location matching fails:
• Web Browsing
• File Access
• Port Forwarding
• Full Tunneling
|
Windows CE
|
VPN Feature Policy
|
The Windows CE options enable you to configure a VPN feature policy to enable or restrict web browsing and remote server file access for remote clients running Microsoft Windows CE.
Select the Web Browsing and File Access check boxes to enable these features, if required.
Note CSD does not support location entries for Windows CE clients, but does let you enable or restrict web browsing and remote server file access for them.
|
Mac and Linux Cache Cleaner
|
Launch Cleanup Upon Global Timeout
|
When selected, enables you to set a global timeout after which CSD launches the cache cleaner, then specify the timeout period after which the cleanup will begin. The default is 5 minutes.
Note If required, you can select the check box to allow the user to reset the timeout period.
|
Launch Cleanup Upon Exiting of Browser
|
When selected, configures the cache cleaner to be launched when all the browser windows are closed.
|
Enable Canceling of Cleaning
|
When selected, enables the remote user to cancel the cleaning of the cache.
|
Secure Delete
|
Select the number of passes for CSD to perform a "Windows-delete" cleanup. The default is 1 pass.
CSD encrypts and writes the cache to the remote client's disk. Upon termination of the Secure Desktop, CSD converts all bits occupied by the cache to all 0's, then to all 1's, and then to randomized 0's and 1's.
|
Enable Web Browsing if Mac or Linux Installation Fails
|
When selected, allows web browsing (but disables other remote access features) if the cache cleaner installation fails.
|
VPN Feature Policy
|
Enables you to configure a VPN Feature Policy that allows or restricts web browsing, remote server file access, and port forwarding for Macintosh and Linux clients.
Select the check boxes if you want to enable these features after a successful installation:
• Web Browsing
• File Access
• Port Forwarding
Note Port forwarding permits the use of the Secure Desktop to connect a client application installed on the local PC to the TCP/IP port of a peer application on a remote server.
|
Category
|
The category assigned to the object. Categories help you organize and identify rules and objects. See Using Category Objects, page 9-4.
|
Credentials Dialog Box
Use the Credentials dialog box to create, copy and edit Credential objects. Credential objects are used in Easy VPN configuration during IKE Extended Authentication (Xauth).
Navigation Path
Select Tools > Policy Object Manager, then select Credentials from the Object Type Selector. Right-click inside the work area, then select New Object or right-click a row, then select Edit Object.
Related Topics
•
Understanding Credential Objects, page 9-35
•
Creating Credential Objects, page 9-35
•
Policy Object Manager Window
•
Configuring Client Connection Characteristics for Easy VPN, page 10-83
Field Reference
Table F-31 Credentials Dialog Box
Element
|
Description
|
Name
|
The Credentials object name (up to 128 characters). Object names are not case-sensitive. For more information, see Guidelines for Managing Objects, page 9-5.
|
Description
|
Additional information about the Credentials object (up to 1024 characters).
|
Username
|
Enter a name that will be used to identify the user during Xauth authentication.
|
Password
|
Enter an alphanumeric keyword that will serve as the password to identify the user during Xauth authentication (maximum of 128 characters; spaces are not allowed).
|
Confirm
|
Enter the password again to confirm it.
|
Category
|
The category assigned to the object. Categories help you organize and identify rules and objects. See Using Category Objects, page 9-4.
|
Allow Value Override per Device
Overrides
Edit button
|
Whether to allow the object definition to be changed at the device level. For more information, see Allowing a Global Object to Be Overridden, page 9-116 and Overriding Global Objects for Individual Devices, page 9-116.
If you allow device overrides, you can click the Edit button to create, edit, and view the overrides. The Overrides field indicates the number of devices that have overrides for this object.
|
Add and Edit File Object Dialog Boxes
Use the Add and Edit File Object dialog boxes to create, copy, and edit file objects.
Navigation Path
Select Tools > Policy Object Manager, then select File Objects from the Object Type Selector. Right-click inside the work area, then select New Object or right-click a row, then select Edit Object.
Related Topics
•
Understanding File Objects, page 9-36
•
Creating File Objects, page 9-37
Field Reference
Table F-32 Add and Edit File Object Dialog Boxes
Element
|
Description
|
Name
|
The customization object name (up to 128 characters). Object names are not case-sensitive. Names can be sorted in ascending or descending order. For more information, see Guidelines for Managing Objects, page 9-5.
|
Description
|
A description of the file object, if required.
You can use uppercase and lowercase characters and most alphanumeric or symbol characters. The value can be up to 1024 characters.
|
File Type
|
Identifies the file type:
• Image
• Cisco Secure Desktop Package
• Plug-In
• AnyConnect Profile
• AnyConnect Image
|
File
|
Allows you to enter the file selection manually, or click Browse to help you make your selection.
|
File Name on Device
|
Identifies the file name on the device. By default the same filename is deployed to the device. It is possible, however, to specify a different filename to be deployed.
During file discovery from devices when files from different devices are discovered into Security Manager, filenames might need to be modified to keep them unique within Security Manager. If renaming occurs, the file-name-on-device field is set automatically, by way of Security Manager's discovery process, to its original filename on the device.
|
Category
|
The category assigned to the object. Categories help you organize and identify rules and objects. See Using Category Objects, page 9-4.
|
Add or Edit FlexConfig Dialog Box
Use the Add or Edit FlexConfig dialog box to create or edit FlexConfig policy objects. FlexConfig objects are small programs that allow you to add configuration commands before or after the configurations generated from Security Manager policies, so that you can extend the abilities of the product to configure your devices. You use these policy objects in FlexConfig device or shared policies.
Before creating FlexConfig policy objects, read the sections in Understanding FlexConfig Policies and Policy Objects, page 19-1.
Navigation Path
Select Tools > Policy Object Manager, then select FlexConfigs from the Object Type Selector. Right-click inside the work area and select New Object or right-click a row and select Edit Object.
Related Topics
•
Creating FlexConfig Policy Objects, page 19-24
•
Editing FlexConfig Policies, page 19-26
•
Chapter 19, "Managing FlexConfigs"
Field Reference
Table F-33 FlexConfigs Editor Dialog Box
Element
|
Description
|
Name
|
The object name, which can be up to 128 characters. Object names are not case-sensitive. For more information, see Guidelines for Managing Objects, page 9-5.
|
Description
|
An optional description of the object.
|
Group
|
The name of the group of FlexConfig objects to which this object belongs, if any. You can type in a name, or select an existing name from the list. This field is for informational purposes only, and can help you find a FlexConfig object in the FlexConfig Objects page in the Policy Object Manager.
|
Type
|
Whether the commands in the object are prepended (put at the beginning) or appended (put at the end) of configurations.
|
Negate For
|
The name of the FlexConfig object whose commands are undone in this FlexConfig object. This field is for informational purposes only and does not affect the processing of the object.
For example, if FlexConfig A has the command banner login, and FlexConfig B has the command no banner login, FlexConfig B negates the configuration for FlexConfig A.
|
FlexConfig Object Body
|
Object Body edit box
|
The commands and instructions to produce the desired configuration file output. You can type in the following types of data:
• Scripting commands to control processing. For more information, see Using Scripting Language Instructions, page 19-3.
• CLI commands that are supported by the operating system running on the devices to which you will deploy the FlexConfig policy object. For more information, see Using CLI Commands in FlexConfig Policy Objects, page 19-2.
• Variables. You can insert variables using the right-click menu, which allows you to create simple single-value text variables (Create Text Object), select variables from existing policy objects (Insert Policy Object), or select system variables (Insert System Variable). For more information, see Understanding FlexConfig Object Variables, page 19-5.
|
Undo button
|
Deletes the previous action.
|
Redo button
|
Performs the previously undone action.
|
Cut button
|
Deletes the highlighted text and copies it to the clipboard.
|
Copy button
|
Copies the highlighted text to the clipboard.
|
Paste button
|
Pastes previously cut or copied text.
|
Find button
|
Locates the specified text string in the object body.
|
Validate FlexConfig button
|
Checks the integrity and deployability of the FlexConfig object.
|
FlexConfig Object Variables
This table lists the variables that are used in the FlexConfig object.
|
Name
|
The name of the variable. Click the cell to edit the name, which also changes the name in the FlexConfig object body.
|
Default Value
|
The value to use when one is not provided. Click the cell to edit the value for user-defined variables. You cannot edit system-defined variables.
Note Except for optional variables, if a default value is not provided, you must provide a value for the variable.
|
Object Property
|
The property of the object. The object property name is in the following format:
type.name.data.property
where
• Type—The type of object, for example Text, Network, AAA Server, and so on.
• Name—The name of the object.
• Data—Indicates that the property of the object is data.
• Property—The property of the data.
|
Dimension
|
The structure of the data in the variable. Possible values are:
• 0—scaler (a single string)
• 1—one-dimensional array (a list of strings)
• 2—two-dimensional table (a table of strings)
|
Optional
|
Whether the variable is required to have a value.
|
Description
|
A description of the contents of the object. Click the cell to edit the description.
|
Create Text Object Dialog Box
Use the Create Text Object dialog box as a shortcut to create text objects of dimension 0, which are single-value variables, for use in FlexConfig policy objects. Enter the name of the variable and the value to assign to it. When you click OK, the variable is added to the FlexConfig object at the cursor location and it is added to the list of variables for the object.
Navigation Path
In the Add or Edit FlexConfig Dialog Box, right-click in the object body field and select Create Text Object.
Tip
If you want to create a multiple-value text object, right-click and select Insert Policy Object > Text Objects, and click the Add button under the available objects list. For more information, see Creating Text Objects, page 9-107.
FlexConfig Undefined Variables Dialog Box
Use the FlexConfig Undefined Variables dialog box to define variables used in the FlexConfig object that have not yet been defined. You can choose from a list of policy object types or add a new policy object to use.
Each row in the table represents a single undefined variable.
Tip
You do not need to define local variables, those used by the scripting language for processing control. For more information about variables, see Understanding FlexConfig Object Variables, page 19-5.
Navigation Path
In the Add or Edit FlexConfig Dialog Box, if you enter a variable name but do not define its values, when you click OK, Security Manager displays a warning and asks if you want to define the variables. If you click Yes, this dialog box is opened.
Field Reference
Table F-34 FlexConfig Undefined Variables Dialog Box
Element
|
Description
|
Variable Name
|
The name of the undefined variable that you used in the FlexConfig object.
|
Object Type
|
The type of policy object that contains the value you want to assign to the variable. For local variables, use the Undefined object type.
For variables you want to define, you must select the specific policy object and value within that object to assign to the selected variable.
You start by selecting the type of policy object from this list. You are then prompted to select the specific policy object. When you click OK, you are prompted to select the specific property within that object that contains the desired value (see Property Selector Dialog Box). When you select the value on the Property Selector dialog box and click OK, the value is assigned to the variable.
|
Object Property
|
The property of the object. For a detailed explanation, see Add or Edit FlexConfig Dialog Box.
|
Optional
|
Whether the variable is required to have a value.
|
Property Selector Dialog Box
Use the Property Selector dialog box to select the specific property within a selected policy object that you want to assign to a variable within a FlexConfig policy object. The title of the dialog box indicates the type of policy object that you selected (for example, AAA Server Groups Property Selector).
For more information on variables, see Understanding FlexConfig Object Variables, page 19-5.
Navigation Path
•
In the Add or Edit FlexConfig Dialog Box, right-click and select a specific policy object group type from the Insert Policy Object menu, select a specific policy object when prompted, and click OK.
•
In the FlexConfig Undefined Variables Dialog Box, select a policy object type from the Object Type field, select a specific policy object when prompted, and click OK.
Field Reference
Table F-35 Property Selector Dialog Box
Element
|
Description
|
Object Property
|
The property of the object that contains the value you want to assign to the variable. For specific information on the properties, see the explanation of the fields for the dialog box used for adding or editing objects of that type. You can find a list of links to the relevant topics at Policy Object Add or Edit Dialog Boxes.
|
Name
|
The name of variable. This field is not available when you are defining undefined variables.
|
Description
|
An optional description of the variable. This field is not available when you are defining undefined variables.
|
IKE Proposal Dialog Box
Use the IKE Proposal dialog box to create, copy, and edit an IKE proposal object. IKE proposal objects contain the parameters required for IKE proposals when defining remote access and site-to-site VPN policies.
Navigation Path
Select Tools > Policy Object Manager, then select IKE Proposals from the Object Type Selector. Right-click inside the work area, then select New Object or right-click a row, then select Edit Object.
Tip
You can also access this dialog box by selecting a device, selecting Remote Access VPN > IPSec VPN > IKE Proposal, and clicking the Add or Edit button.
Related Topics
•
Creating IKE Proposal Objects, page 9-38
•
Understanding IKE Proposal Objects, page 9-38
•
Policy Object Manager Window
•
IPsec Transform Set Dialog Box
Field Reference
Table F-36 IKE Proposal Dialog Box
Element
|
Description
|
Name
|
The object name (up to 128 characters). Object names are not case-sensitive. For more information, see Guidelines for Managing Objects, page 9-5.
|
Description
|
Additional information about the object (up to 1024 characters).
|
Priority
|
The priority value of the IKE proposal. The priority value determines the order of the IKE proposals compared by the two negotiating peers when attempting to find a common SA.
Valid values range from 1 to 10000. The lower the number, the higher the priority.
Note If you leave this field blank, Security Manager assigns the lowest unassigned value starting with 1, then 5, then continuing in increments of 5.
|
Encryption Algorithm
|
The encryption algorithm used to establish the Phase 1 SA for protecting Phase 2 negotiations:
• AES-128—Encrypts according to the Advanced Encryption Standard using 128-bit keys.
• AES-192—Encrypts according to the Advanced Encryption Standard using 192-bit keys.
• AES-256—Encrypts according to the Advanced Encryption Standard using 256-bit keys.
• DES—Encrypts according to the Data Encryption Standard using 56-bit keys.
• 3DES—Encrypts three times using 56-bit keys. 3DES is more secure than DES, but requires more processing for encryption and decryption. A 3DES license is required to use this option.
|
Hash Algorithm
|
The hash algorithm used in the IKE proposal. The hash algorithm creates a message digest, which is used to ensure message integrity. Options are:
• SHA (Secure Hash Algorithm)—Produces a 160-bit digest. SHA is more resistant to brute-force attacks than MD5.
• MD5 (Message Digest 5)—Produces a 128-bit digest. MD5 uses less processing time than SHA.
|
Modulus Group
|
The Diffie-Hellman group to use for deriving a shared secret between the two IPsec peers:
• 1—Diffie-Hellman Group 1 (768-bit modulus).
• 2—Diffie-Hellman Group 2 (1024-bit modulus).
• 5—Diffie-Hellman Group 5 (1536-bit modulus).
• 7—Diffie-Hellman Group 7 (163-bit elliptical curve field size).
Note A larger modulus provides higher security but requires more processing time. The two peers must have a matching modulus group.
|
Lifetime
|
The lifetime of the SA, in seconds. When the lifetime is exceeded, the SA expires and must be renegotiated between the two peers.
As a general rule, the shorter the lifetime (up to a point), the more secure your IKE negotiations will be.
|
Authentication Method
|
The method of authentication to use between the two peers:
• Preshared Key—Preshared keys allow for a secret key to be shared between two peers and used by IKE during the authentication phase. If one of the participating peers is not configured with the same preshared key, the IKE SA cannot be established.
• Certificate—An authentication method in which RSA key pairs are used to sign and encrypt IKE key management messages. This method provides non-repudiation of communication between two peers, meaning that it can be proved that the communication actually took place. When you use this authentication method, the peers are configured to obtain digital certificates from a Certification Authority (CA).
|
Category
|
The category assigned to the object. Categories help you organize and identify rules and objects. See Using Category Objects, page 9-4.
|
Add or Edit Class Maps Dialog Boxes
Use the Add and Edit Class Map dialog boxes to define a class map for inspection for devices running ASA/PIX 7.2 and higher. You can create class maps for DNS, FTP, H.323, HTTP, IM, and SIP inspection, and the name of the dialog box indicates the type of map you are creating.
An inspection class map matches application traffic with criteria specific to the application. You then identify the class map in the inspect map and enable actions. The difference between creating a class map and defining the traffic match directly in the inspect map policy object is that you can reuse class maps.
Navigation Path
Select Tools > Policy Object Manager, then select any item in the Inspect Maps > Class Maps folder in the table of contents. Right-click inside the work area, then select New Object, or right-click a row, then select Edit Object.
Related Topics
•
Understanding Inspection Map Objects, page 9-39
•
Creating Class Map Objects, page 9-41
Field Reference
Table F-37 Add or Edit Class Maps Dialog Boxes
Element
|
Description
|
Name
|
The name of the policy object. A maximum of 40 characters is allowed.
|
Description
|
A description of the policy object. A maximum of 200 characters is allowed.
|
Match All table
|
The Match All table lists the criteria included in the class map. Each row indicates whether the inspection is looking for traffic that matches or does not match each criterion and the criterion and value that is inspected.
• To add a criterion, click the Add button and fill in the Match Criterion dialog box. For more information, see the following topic that relates to the type of map you are creating:.
– DNS Class and Policy Maps Add or Edit Match Condition (and Action) Dialog Boxes
– FTP Class and Policy Maps Add or Edit Match Condition (and Action) Dialog Boxes
– H.323 Class and Policy Maps Add or Edit Match Condition (and Action) Dialog Boxes
– HTTP Class and Policy Map (ASA 7.2+/PIX 7.2+) Add or Edit Match Condition (and Action) Dialog Boxes
– IM Class and Policy Map (ASA 7.2+/PIX 7.2+) Add or Edit Match Condition (and Action) Dialog Boxes
– SIP Class and Policy Maps Add or Edit Match Condition (and Action) Dialog Boxes
• To edit a criterion, select it and click the Edit button.
• To delete a criterion, select it and click the Delete button.
|
Category
|
The category assigned to the object. Categories help you organize and identify rules and objects. See Using Category Objects, page 9-4.
|
Allow Value Override per Device
Overrides
Edit button
|
Whether to allow the object definition to be changed at the device level. For more information, see Allowing a Global Object to Be Overridden, page 9-116 and Overriding Global Objects for Individual Devices, page 9-116.
If you allow device overrides, you can click the Edit button to create, edit, and view the overrides. The Overrides field indicates the number of devices that have overrides for this object.
|
Add or Edit DCE/RPC Dialog Box
Use the Add or Edit DCE/RPC Map dialog boxes to define a map for DCE/RPC inspection.
Navigation Path
Select Tools > Policy Object Manager, then select Inspect Maps > Policy Maps > DCE/RPC Maps from the Object Type selector. Right-click inside the work area, then select New Object or right-click a row and select Edit Object.
Related Topics
•
Understanding Inspection Map Objects, page 9-39
•
Creating DCE/RPC Map Objects, page 9-42
Field Reference
Table F-38 Add and Edit DCE/RPC Dialog Boxes
Element
|
Description
|
Name
|
The name of the policy object. A maximum of 40 characters is allowed.
|
Description
|
A description of the policy object. A maximum of 200 characters is allowed.
|
Pinhole Timeout
|
The timeout for DCE/RPC pinholes. The default is 2 minutes (00:02:00). Valid values are between 00:00:01 and 1193:00:00.
|
Enforce Endpoint Mapper Service
|
Whether to enforce the endpoint mapper service during binding. Using this service, a client queries a server, called the Endpoint Mapper, for the dynamically allocated network information of a required service.
|
Enable Endpoint Mapper Service Lookup
Service Lookup Timeout
|
Whether to enable the lookup operation of the endpoint mapper service. If you select this option, you can enter the time out for the lookup operation. If you do not specify a timeout, the pinhole timeout or default pinhole timeout value is used. Valid values are between 00:00:01 and 1193:00:00.
|
Category
|
The category assigned to the object. Categories help you organize and identify rules and objects. See Using Category Objects, page 9-4.
|
Allow Value Override per Device
Overrides
Edit button
|
Whether to allow the object definition to be changed at the device level. For more information, see Allowing a Global Object to Be Overridden, page 9-116 and Overriding Global Objects for Individual Devices, page 9-116.
If you allow device overrides, you can click the Edit button to create, edit, and view the overrides. The Overrides field indicates the number of devices that have overrides for this object.
|
Add and Edit DNS Map Dialog Boxes
Use the Add and Edit DNS Map dialog boxes to define DNS Maps for inspection.
Navigation Path
Select Tools > Policy Object Manager, then select Inspect Maps > Policy Maps > DNS Maps from the Object Type selector. Right-click inside the work area, then select New Object or right-click a row and select Edit Object.
Related Topics
•
Understanding Inspection Map Objects, page 9-39
•
Creating DNS Map Objects, page 9-43
•
Creating Class Map Objects, page 9-41
Field Reference
Table F-39 Add and Edit DNS Map Dialog Boxes
Element
|
Description
|
Name
|
The name of the policy object. A maximum of 40 characters is allowed.
|
Description
|
A description of the policy object. A maximum of 200 characters is allowed.
|
Protocol Conformance Tab
Defines DNS security settings and actions. For a description of the options on this tab, see DNS Map Protocol Conformance Tab.
|
Filtering Tab
Defines the filtering settings for DNS. For a description of the options on this tab, see DNS Map Filtering Tab.
|
Mismatch Rate Tab
The Log When DNS ID Mismatch Rate Exceeds option determines whether you want to report excessive instances of DNS identifier mismatches based on the following criteria:
• Threshold—The maximum number of mismatch instances before a system message log is sent. Values are 0 to 4294967295.
• Time Interval—The time period to monitor (in seconds). Values are 1 to 31536000.
|
Match Condition and Action Tab
The Match All table lists the criteria included in the policy map. Each row indicates whether the inspection is looking for traffic that matches or does not match each criterion, the criterion and value that is inspected, and the action to be taken for traffic that satisfies the conditions.
• To add a criterion, click the Add button and fill in the Match Condition and Action dialog box (see DNS Class and Policy Maps Add or Edit Match Condition (and Action) Dialog Boxes).
• To edit a criterion, select it and click the Edit button.
• To delete a criterion, select it and click the Delete button.
|
Category
|
The category assigned to the object. Categories help you organize and identify rules and objects. See Using Category Objects, page 9-4.
|
Allow Value Override per Device
Overrides
Edit button
|
Whether to allow the object definition to be changed at the device level. For more information, see Allowing a Global Object to Be Overridden, page 9-116 and Overriding Global Objects for Individual Devices, page 9-116.
If you allow device overrides, you can click the Edit button to create, edit, and view the overrides. The Overrides field indicates the number of devices that have overrides for this object.
|
DNS Map Protocol Conformance Tab
Use the Protocol Conformance tab to define DNS security settings and actions for a DNS map.
Navigation Path
Click the Protocol Conformance tab on the Add and Edit DNS Map Dialog Boxes.
Related Topics
•
Understanding Inspection Map Objects, page 9-39
•
Creating DNS Map Objects, page 9-43
Field Reference
Table F-40 DNS Map Protocol Conformance Tab
Element
|
Description
|
Enable DNS Guard Function
|
Whether to perform a DNS query and response mismatch check using the identification field in the DNS header. One response per query is allowed to go through the security appliance.
|
Generate Syslog for ID Mismatch
|
Whether to create syslog entries for excessive instances of DNS identifier mismatches.
|
Randomize the DNS Identifier for DNS Query
|
Whether to randomize the DNS identifier in the DNS query message.
|
Enable NAT Rewrite Function
|
Whether to enable IP address translation in the A record of the DNS response.
|
Enable Protocol Enforcement
|
Whether to enable DNS message format check, including domain name, label length, compression, and looped pointer check.
|
Require Authentication Between DNS Server (RFC2845)
Action
|
Whether to require authentication between DNS servers as defined in RFC 2845. If you select this option, select the action to take when there is no authentication.
|
DNS Map Filtering Tab
Use the Filtering tab to define DNS filtering settings and actions for a DNS map.
Navigation Path
Click the Filtering tab on the Add and Edit DNS Map Dialog Boxes.
Related Topics
•
Understanding Inspection Map Objects, page 9-39
•
Creating DNS Map Objects, page 9-43
Field Reference
Table F-41 DNS Map Filtering Tab
Element
|
Description
|
Drop Packets that Exceed Specified Length
Maximum Packet Length
|
Whether to drop packets that exceed the maximum length in bytes that you specify. This is a global setting.
|
Drop Packets Sent to Server that Exceed Specified Maximum Length
Maximum Length
|
Whether to drop packets sent to the server that exceed the maximum length in bytes that you specify.
|
Drop Packets Sent to Server that Exceed Length Indicated by Resource Record
|
Whether to drop packets sent to the server that exceed the length indicated by the resource record.
|
Drop Packets Sent to Client that Exceed Specified Length
Maximum Length
|
Whether to drop packets sent to a client that exceed the maximum length in bytes that you specify.
|
Drop Packets Sent to Client that Exceed Length Indicated by Resource Record
|
Whether to drop packets sent to the client that exceed the length indicated by the resource record.
|
DNS Class and Policy Maps Add or Edit Match Condition (and Action) Dialog Boxes
Use the Add or Edit DNS Match Criterion (for DNS class maps) or Match Condition and Action (for DNS policy maps) dialog boxes to do the following:
•
Define the match criterion and value for a DNS class map.
•
Select a DNS class map when creating a DNS policy map.
•
Define the match criterion, value, and action directly in a DNS policy map.
The fields on this dialog box change based on the criterion you select and whether you are creating a class map or policy map.
Navigation Path
When creating a DNS class map, in the Policy Object Manager, from the Add or Edit Class Maps Dialog Boxes for DNS, right-click inside the table, then select Add Row or right-click a row, then select Edit Row.
When creating a DNS policy map, in the Policy Object Manager, from the Match Condition and Action tab on the Add and Edit DNS Map Dialog Boxes, right-click inside the table, then select Add Row or right-click a row, then select Edit Row.
Related Topics
•
Understanding Inspection Map Objects, page 9-39
•
Creating Class Map Objects, page 9-41
•
Creating DNS Map Objects, page 9-43
Field Reference
Table F-42 DNS Class and Policy Maps Add and Edit Match Condition and Action Dialog Boxes
Element
|
Description
|
Match Type
Class Name
(Policy Map only)
|
Enables you to use an existing DNS class map or define a new DNS class map.
• Use Specified Values—You want to define the class map on this dialog box.
• Use Values in Class Map—You want to select an existing DNS class map policy object. Enter the name of the DNS class map in the Class Name field. Click Select to select the map from a list or to create a new class map object.
|
Criterion
|
Specifies which criterion of FTP traffic to match:
• DNS Class—Matches a DNS query or resource record class.
• DNS Type—Matches a DNS query or resource record type.
• Domain Name—Matches a domain name from a DNS query or resource record.
• Header Flag—Matches a DNS flag in the header.
• Question—Matches a DNS question.
• Resource Record—Matches a DNS resource record.
|
Type
|
Specifies whether the map includes traffic that matches or does not match the criterion. For example, if Doesn't Match is selected on the string "example.com," then any traffic that contains "example.com" is excluded from the map.
• Matches—Matches the criterion.
• Doesn't Match—Does not match the criterion.
|
Action
(Policy Map only)
|
The action you want the device to take for traffic that matches the defined criteria.
|
Variable Fields
The following fields vary based on what you select in the Criterion field. This list is a super-set of the fields you might see.
|
Value
(for DNS Class criterion)
|
The DNS class you want to inspect:
• Internet—Matches the Internet DNS class.
• DNS Class Field Value—Matches the specified number.
• DNS Class Field Range—Matches the specified range of numbers.
|
Value
(for DNS Type criterion)
|
The DNS type you want to inspect:
• DNS Type Field Name—Matches the name of a DNS type:
– A—IPv4 address.
– AXFR—Full (zone) transfer.
– CNAME—Canonical name.
– IXFR—Incremental (zone) transfer.
– NS—Authoritative name server.
– SOA—Start of a zone of authority.
– TSIG—Transaction signature.
• DNS Type Field Value—Matches the specified number.
• DNS Type Field Range—Matches the specified range of numbers.
|
Value
(for Domain Name criterion)
|
The regular expression you want to evaluate. You can select one of the following:
• Regular Expression—The regular expression object that defines the regular expression you want to use for pattern matching. Enter the name of the object. You can click Select to choose the object from a list of existing ones or to create a new regular expression object.
• Regular Expression Group—The regular expression group object that defines the regular expression you want to use for pattern matching. Enter the name of the object. You can click Select to choose the object from a list of existing ones or to create a new regular expression group object.
|
Options
Value
(for Header Flag criterion)
|
The header flag you want to inspect. Use the Options field to indicate whether you want an exact match (Equals) or a partial match (Contains).
• Header Flag Name—Matches the selected header flag names:
– AA (authoritative answer)
– QR (query)
– RA (recursion available)
– RD (recursion denied)
– TC (truncation) flag bits
• Header Flag Value—Matches the specified 16-bit hexadecimal value.
|
Resource Record
|
Lists the sections to match:
• Additional—DNS additional resource record.
• Answer—DNS answer resource record.
• Authority—DNS authority resource record.
|
Add or Edit ESMTP Map Dialog Boxes
Use the Add and Edit ESMTP Map dialog boxes to define the match criterion and values for the ESMTP inspect map.
Navigation Path
Select Tools > Policy Object Manager, then select Inspect Maps > Policy Maps > ESMTP Maps from the Object Type selector. Right-click inside the table, then select New Object or right-click a row and select Edit Object.
Related Topics
•
Understanding Inspection Map Objects, page 9-39
•
Creating ESMTP Map Objects, page 9-44
•
Editing Objects, page 9-6
Field Reference
Table F-43 Add and Edit ESMTP Map Dialog Boxes
Element
|
Description
|
Name
|
The name of the policy object. A maximum of 40 characters is allowed.
|
Description
|
A description of the policy object. A maximum of 200 characters is allowed.
|
Parameters tab
|
Mask Server Banner
|
Whether to mask the server banner to prevent the client from discovering server information.
|
Configure Mail Relay
Domain Name
Action
|
Whether to have ESMTP inspection detect mail relay. When you select this option, enter the domain name you are inspecting and select the action you want to take when mail relay is detected.
|
Special Character (ASA7.2.3+/PIX7.2.3+)
Action
|
Whether you want to detect special characters in sender or receiver email addresses. If you select this option, select the action you want to take when special characters are detected.
|
Allow TLS (ASA7.2.3+, 8.0.3+/PIX7.2.3)
Action Log
|
Whether to allow a TLS proxy on the security appliance. If you select this option, you can also select Action Log to create a log entry when TLS is detected.
|
Match Condition and Action Tab
The Match All table lists the criteria included in the policy map. Each row indicates whether the inspection is looking for traffic that matches or does not match each criterion, the criterion and value that is inspected, and the action to be taken for traffic that satisfies the conditions.
• To add a criterion, click the Add button and fill in the Match Condition and Action dialog box (see ESMTP Policy Maps Add or Edit Match Condition and Action Dialog Boxes).
• To edit a criterion, select it and click the Edit button.
• To delete a criterion, select it and click the Delete button.
|
Category
|
The category assigned to the object. Categories help you organize and identify rules and objects. See Using Category Objects, page 9-4.
|
Allow Value Override per Device
Overrides
Edit button
|
Whether to allow the object definition to be changed at the device level. For more information, see Allowing a Global Object to Be Overridden, page 9-116 and Overriding Global Objects for Individual Devices, page 9-116.
If you allow device overrides, you can click the Edit button to create, edit, and view the overrides. The Overrides field indicates the number of devices that have overrides for this object.
|
ESMTP Policy Maps Add or Edit Match Condition and Action Dialog Boxes
Use the Add or Edit Match Condition and Action dialog boxes to define the match criterion, value, and action for an ESMTP policy map.
The fields on this dialog box change based on the criterion you select. You can use the following criteria:
•
Body Length—Matches the message body length.
•
Body Line Length—Matches the length of a line in the message body.
•
Commands—Matches ESMTP commands.
•
Command Recipient Count—Matches the number of recipient email addresses.
•
Command Line Length—Matches the number of characters of a command line.
•
EHLO Reply Parameters—Matches the ESMTP EHLO reply parameters.
•
Header Length—Matches the number of characters of the header.
•
Header Line Length—Matches the number of characters of a line in the message header.
•
To Recipients Count—Matches the number of recipients in the To field of the header.
•
Invalid Recipients Count—Matches the number of invalid recipients in the header.
•
MIME File Type—Matches the MIME file type.
•
MIME Filename Length—Matches the number of characters of the filename.
•
MIME Encoding—Matches the MIME encoding scheme.
•
Sender Address—Matches the address of the sender.
•
Sender Address Length—Matches the number of characters of the sender's address.
Navigation Path
In the Policy Object Manager, from the Match Condition and Action tab on the Add or Edit ESMTP Map Dialog Boxes, right-click inside the table, then select Add Row or right-click a row, then select Edit Row.
Related Topics
•
Understanding Inspection Map Objects, page 9-39
•
Creating ESMTP Map Objects, page 9-44
Field Reference
Table F-44 ESMTP Policy Maps Add and Edit Match Condition and Action Dialog Boxes
Element
|
Description
|
Criterion
|
Specifies which criterion of ESMTP traffic to match. The criteria are described above.
|
Type
|
Specifies whether the map includes traffic that matches or does not match the criterion. For example, if Doesn't Match is selected on the string "example.com," then any traffic that contains "example.com" is excluded from the map.
• Matches—Matches the criterion.
• Doesn't Match—Does not match the criterion.
|
Action
|
The action you want the device to take for traffic that matches the defined criteria.
|
Variable Fields
The following fields vary based on what you select in the Criterion field. This list is a super-set of the fields you might see.
|
Greater Than Length
|
The length in bytes of the evaluated field. The criterion matches if the length is greater than the specified number, and does not match if the field is less than the specified number.
The dialog box indicates the valid range for the length, except for Body Length and Header length, which can be 1 to 4294967295.
|
Commands
|
The ESMTP command verbs you want to inspect.
|
Greater Than Count
|
The number of evaluated items. The criterion matches if the count is greater than the specified number, and does not match if the count is less than the specified number.
|
Parameters
|
The ESMTP EHLO reply parameters you want to inspect.
|
Value
|
The regular expression you want to evaluate. You can select one of the following:
• Regular Expression—The regular expression object that defines the regular expression you want to use for pattern matching. Enter the name of the object. You can click Select to choose the object from a list of existing ones or to create a new regular expression object.
• Regular Expression Group—The regular expression group object that defines the regular expression you want to use for pattern matching. Enter the name of the object. You can click Select to choose the object from a list of existing ones or to create a new regular expression group object.
|
MIME Encoding
|
The type of MIME encoding schemes you want to inspect.
|
Add and Edit FTP Map Dialog Boxes
Use the Add and Edit FTP Map dialog boxes to define the match criterion and values for an FTP inspect map. You can use an FTP map to block specific FTP protocol methods, such as an FTP PUT, from passing through the security appliance and reaching your FTP server. Security Manager uses the ftp-map command to configure the map on the device.
Navigation Path
Select Tools > Policy Object Manager, then select Inspect Maps > Policy Maps > FTP Maps from the Object Type selector. Right-click inside the table, then select New Object or right-click a row, then select Edit Object.
Related Topics
•
Understanding Inspection Map Objects, page 9-39
•
Creating FTP Map Objects, page 9-45
•
Editing Objects, page 9-6
Field Reference
Table F-45 Add and Edit FTP Map Dialog Boxes
Element
|
Description
|
Name
|
The name of the policy object. A maximum of 40 characters is allowed.
|
Description
|
A description of the policy object. A maximum of 200 characters is allowed.
|
Parameters tab
|
Mask Greeting Banner from Server
|
Whether to mask the greeting banner from the FTP server to prevent the client from discovering server information.
|
Mask Reply to SYST Command
|
Whether to mask the reply to the syst command to prevent the client from discovering server information.
|
Match Condition and Action Tab
The Match All table lists the criteria included in the policy map. Each row indicates whether the inspection is looking for traffic that matches or does not match each criterion, the criterion and value that is inspected, and the action to be taken for traffic that satisfies the conditions.
• To add a criterion, click the Add button and fill in the Match Condition and Action dialog box (see FTP Class and Policy Maps Add or Edit Match Condition (and Action) Dialog Boxes).
• To edit a criterion, select it and click the Edit button.
• To delete a criterion, select it and click the Delete button.
|
Category
|
The category assigned to the object. Categories help you organize and identify rules and objects. See Using Category Objects, page 9-4.
|
Allow Value Override per Device
Overrides
Edit button
|
Whether to allow the object definition to be changed at the device level. For more information, see Allowing a Global Object to Be Overridden, page 9-116 and Overriding Global Objects for Individual Devices, page 9-116.
If you allow device overrides, you can click the Edit button to create, edit, and view the overrides. The Overrides field indicates the number of devices that have overrides for this object.
|
Validate For
Validate button
|
The device platforms for which to validate the object. Select the platform for which you intend to use this object and click Validate to determine if the object is configured in a way that will prevent policy deployment.
|
FTP Class and Policy Maps Add or Edit Match Condition (and Action) Dialog Boxes
Use the Add or Edit FTP Match Criterion (for FTP class maps) or Match Condition and Action (for FTP policy maps) dialog boxes to do the following:
•
Define the match criterion and value for an FTP class map.
•
Select an FTP class map when creating an FTP policy map.
•
Define the match criterion, value, and action directly in an FTP policy map.
The fields on this dialog box change based on the criterion you select and whether you are creating a class map or policy map.
Navigation Path
When creating an FTP class map, in the Policy Object Manager, from the Add or Edit Class Maps Dialog Boxes for FTP, right-click inside the table, then select Add Row or right-click a row, then select Edit Row.
When creating an FTP policy map, in the Policy Object Manager, from the Match Condition and Action tab on the Add and Edit FTP Map Dialog Boxes, right-click inside the table, then select Add Row or right-click a row, then select Edit Row.
Related Topics
•
Understanding Inspection Map Objects, page 9-39
•
Creating Class Map Objects, page 9-41
•
Creating FTP Map Objects, page 9-45
Field Reference
Table F-46 FTP Class and Policy Maps Add and Edit Match Condition and Action Dialog Boxes
Element
|
Description
|
Match Type
Class Name
(Policy Map only)
|
Enables you to use an existing FTP class map or define a new FTP class map.
• Use Specified Values—You want to define the class map on this dialog box.
• Use Values in Class Map—You want to select an existing FTP class map policy object. Enter the name of the FTP class map in the Class Name field. Click Select to select the map from a list or to create a new class map object.
|
Criterion
|
Specifies which criterion of FTP traffic to match:
• Request Command—Matches an FTP request command.
• Filename—Matches a filename for FTP transfer.
• File Type—Matches a file type for FTP transfer.
• Server—Matches an FTP server name.
• Username—Matches an FTP username.
|
Type
|
Specifies whether the map includes traffic that matches or does not match the criterion. For example, if Doesn't Match is selected on the string "example.com," then any traffic that contains "example.com" is excluded from the map.
• Matches—Matches the criterion.
• Doesn't Match—Does not match the criterion.
|
Action
(Policy Map only)
|
The action you want the device to take for traffic that matches the defined criteria.
|
Variable Fields
The following fields vary based on what you select in the Criterion field. This list is a super-set of the fields you might see.
|
Request Commands
|
The FTP commands you want to inspect:
• Append (APPE)—Appends to a file.
• Delete (DELE)—Deletes a file at the server site.
• Help (HELP)—Provides help information from the server.
• Put (PUT)—FTP client command for the stor (store a file) command.
• Rename From (RNFR)—Specifies rename-from filename.
• Server Specific Command (SITE)—Specifies commands that are server specific. Usually used for remote administration.
• Change to Parent (CDUP)—Changes to the parent directory of the current working directory.
• Get (GET)—FTP client command for the retr (retrieve a file) command.
• Create Directory (MKD)—Creates a directory.
• Remove Directory (RMD)—Removes a directory.
• Rename To (RNTO)—Specifies rename-to filename.
• Store File with Unique Name (STOU)—Stores a file with a unique filename.
|
Value
|
The regular expression you want to evaluate. You can select one of the following:
• Regular Expression—The regular expression object that defines the regular expression you want to use for pattern matching. Enter the name of the object. You can click Select to choose the object from a list of existing ones or to create a new regular expression object.
• Regular Expression Group—The regular expression group object that defines the regular expression you want to use for pattern matching. Enter the name of the object. You can click Select to choose the object from a list of existing ones or to create a new regular expression group object.
|
Add and Edit GTP Map Dialog Boxes
Use the Add and Edit GTP Map dialog boxes to define the match criterion and values for a GTP inspect map.
Navigation Path
Select Tools > Policy Object Manager, then select Inspect Maps > Policy Maps > GTP Maps from the Object Type selector. Right-click inside the work area, then select New Object, or right-click a row and select Edit Object.
Related Topics
•
Understanding Inspection Map Objects, page 9-39
•
Creating GTP Map Objects, page 9-46
Field Reference
Table F-47 Add and Edit GTP Map Dialog Boxes
Element
|
Description
|
Name
|
The name of the policy object. A maximum of 40 characters is allowed.
|
Description
|
A description of the policy object. A maximum of 200 characters is allowed.
|
Parameters tab
|
Country and Network Codes Table
|
The three-digit Mobile Country Code (mcc) and Mobile Network Code (mnc) to include in the map. The codes are 000 to 999.
• To add codes, click the Add button and fill in the dialog box.
• To edit a row, select it and click the Edit button.
• To delete a row, select it and click the Delete button.
|
Permit Response Table
|
The Network/Host policy objects for which you will allow GTP responses from a GSN that is different from the one to which the response was sent.
• To add objects, click the Add button and fill in the dialog box. For more information, see Add and Edit Permit Response Dialog Boxes.
• To edit a row, select it and click the Edit button.
• To delete a row, select it and click the Delete button.
|
Request Queue
|
The maximum requests allowed in the queue. When the limit has been reached and a new request arrives, the request that has been in the queue for the longest time is removed. Values are 1-9999999. The default is 200.
|
Tunnel Limit
|
The maximum number of tunnels allowed.
|
Permit Errors
|
Whether to permit packets with errors or different GTP versions. By default, all invalid packets or packets that failed during parsing are dropped.
|
Edit Timeouts button
|
Click this button to configure time out values for various operations. For more information about the options, see GTP Map Timeouts Dialog Box.
|
Match Condition and Action Tab
The Match All table lists the criteria included in the policy map. Each row indicates whether the inspection is looking for traffic that matches or does not match each criterion, the criterion and value that is inspected, and the action to be taken for traffic that satisfies the conditions.
• To add a criterion, click the Add button and fill in the Match Condition and Action dialog box (see GTP Policy Maps Add or Edit Match Condition and Action Dialog Boxes).
• To edit a criterion, select it and click the Edit button.
• To delete a criterion, select it and click the Delete button.
|
Category
|
The category assigned to the object. Categories help you organize and identify rules and objects. See Using Category Objects, page 9-4.
|
Allow Value Override per Device
Overrides
Edit button
|
Whether to allow the object definition to be changed at the device level. For more information, see Allowing a Global Object to Be Overridden, page 9-116 and Overriding Global Objects for Individual Devices, page 9-116.
If you allow device overrides, you can click the Edit button to create, edit, and view the overrides. The Overrides field indicates the number of devices that have overrides for this object.
|
Validate For
Validate button
|
The device platforms for which to validate the object. Select the platform for which you intend to use this object and click Validate to determine if the object is configured in a way that will prevent policy deployment.
|
Add and Edit Country Network Codes Dialog Boxes
Use the Add and Edit Country Network Codes dialog boxes to add Mobile Country Code (mcc) and Mobile Network Code (mnc) values to the GTP policy map. The codes can be 000 to 999.
Navigation Path
From the Add and Edit GTP Map Dialog Boxes, click the Add button in the Country and Network codes table, or select a row and click the Edit button.
Add and Edit Permit Response Dialog Boxes
Use the Add and Edit Permit Response dialog boxes to permit GTP responses from a GSN that is different from the one to which the response was sent.
Enter the name of a Network/Host policy object that defines the destination (To Object Group) and source (From Object Group) of the traffic. You can click Select to select the object from a list, where you can also create an new object by clicking the Create button in the Object Selector dialog box.
You cannot use the Network/Host object named "any."
Navigation Path
From the Add and Edit GTP Map Dialog Boxes, click the Add button in the Permit Response table, or select a row and click the Edit button.
GTP Map Timeouts Dialog Box
Use the GTP Map Timeouts dialog box to set timeout values for a GTP Map.
Navigation Path
From the Add and Edit GTP Map Dialog Boxes, click the Edit Timeouts button on the Parameters tab.
Field Reference
Table F-48 GTP Map Timeouts Dialog Box
Element
|
Description
|
GSN Timeout
|
The period of inactivity (hh:mm:ss) after which a GSN is removed. The default is 30 minutes. Enter 0 to never tear down immediately.
|
PDP Context Timeout
|
The maximum period of time allowed (hh:mm:ss) before beginning to receive the PDP context. The default is 30 minutes. Enter 0 to specify no limit.
|
Request Queue Timeout
|
The maximum period of time allowed (hh:mm:ss) before beginning to receive the GTP message. The default is 60 seconds. Enter 0 to specify no limit.
|
Signaling Connections Timeout
|
The period of inactivity (hh:mm:ss) after which the GTP signaling is removed. The default is 30 minutes. Enter 0 to not remove the signal.
|
Tunnel Timeout
|
The period of inactivity (hh:mm:ss) after which the GTP tunnel is torn down. The default is 60 seconds (when a Delete PDP Context Request is not received). Enter 0 to never tear down immediately.
|
T3 Response Timeout
|
The maximum wait time for a response before removing the connection.
|
GTP Policy Maps Add or Edit Match Condition and Action Dialog Boxes
Use the Add or Edit Match Condition and Action dialog boxes to define the match criterion, value, and action for a GTP policy map.
The fields on this dialog box change based on the criterion you select.
Navigation Path
In the Policy Object Manager, from the Match Condition and Action tab on the Add and Edit GTP Map Dialog Boxes, right-click inside the table, then select Add Row or right-click a row, then select Edit Row.
Related Topics
•
Understanding Inspection Map Objects, page 9-39
•
Creating GTP Map Objects, page 9-46
Field Reference
Table F-49 GTP Policy Maps Add and Edit Match Condition and Action Dialog Boxes
Element
|
Description
|
Criterion
|
Specifies which criterion of GTP traffic to match:
• Access Point Name—Matches the access point name so you can define the access points to drop when GTP application inspection is enabled.
• Message ID—Matches the numeric identifier for the message that you want to drop. By default, all valid message IDs are allowed.
• Message Length—Matches the length of the UDP packet. Use this criterion to change the default for the maximum allowed message length for the UDP payload.
• Version—Matches the GTP version.
|
Type
|
Specifies whether the map includes traffic that matches or does not match the criterion. For example, if Doesn't Match is selected on the string "example.com," then any traffic that contains "example.com" is excluded from the map.
• Matches—Matches the criterion.
• Doesn't Match—Does not match the criterion.
|
Action
|
The action you want the device to take for traffic that matches the defined criteria.
• Drop Packet—By default, all invalid packets or packets that failed during parsing are dropped.
• Drop Packet and Log
• Rate Limit
|
Variable Fields
The following fields vary based on what you select in the Criterion field. This list is a super-set of the fields you might see.
|
Access Point Name
|
The access points to act on when GTP application inspection is enabled.
• Specified By—An access point name to be dropped. By default, all messages with valid APNs are inspected, and any APN is allowed.
• Regular Expression—The regular expression object that defines the regular expression you want to use for pattern matching. Enter the name of the object. You can click Select to choose the object from a list of existing ones or to create a new regular expression object.
• Regular Expression Group—The regular expression group object that defines the regular expression you want to use for pattern matching. Enter the name of the object. You can click Select to choose the object from a list of existing ones or to create a new regular expression group object.
|
ID Type
|
The numeric identifier of the message that you want to act on.
• Value—A single message ID.
• Range—A range of message IDs.
|
Minimum Length
|
The minimum number of bytes in the UDP payload.
|
Maximum Length
|
The maximum number of bytes in the UDP payload.
|
Version Type
|
The GTP version as a single value or range of values.
Use 0 to identify Version 0 and 1 to identify Version 1. Version 0 of GTP uses port 2123, while Version 1 uses port 3386. By default all GTP versions are allowed.
|
Add and Edit H.323 Map Dialog Boxes
Use the Add and Edit H.323 Map dialog boxes to define the match criterion and values for an H.323 inspect map.
Navigation Path
Select Tools > Policy Object Manager, then select Inspect Maps > Policy Maps > H.323 Maps from the Object Type selector. Right-click inside the work area, then select New Object, or right-click a row and select Edit Object.
Related Topics
•
Understanding Inspection Map Objects, page 9-39
•
Creating H.323 Map Objects, page 9-47
Field Reference
Table F-50 Add and Edit H.323 Map Dialog Boxes
Element
|
Description
|
Name
|
The name of the policy object. A maximum of 40 characters is allowed.
|
Description
|
A description of the policy object. A maximum of 200 characters is allowed.
|
Parameters tab
|
HSI Group table
|
The HSI groups to include in the map. The group number, IP address of the HSI host, and IP addresses and interface names of the clients connected to the security appliance are shown in the table. Up to five HSI hosts per group, and up to ten end points per HSI group, are allowed.
• To add a group, click the Add button and fill in the dialog box (see Add or Edit HSI Group Dialog Boxes).
• To edit a group, select it and click the Edit button.
• To delete a group, select it and click the Delete button.
|
Call Duration Limit
|
The call duration limit in seconds. The range is from 0:0:0 to 1163:0:0. A value of 0 means never timeout.
|
Enforce Presence of Calling and Called Party Numbers
|
Whether to enforce calling and called party numbers used in call setup.
|
Check State Transition on H.225 Messages
|
Whether to enable state checking validation on H.225 messages.
|
Check State Transition on RAS Messages
|
Whether to enable state checking validation on RAS messages.
|
Check for H.245 Tunneling
Action
|
Whether to enforce H.245 tunnel blocking and perform the action you select in the Action list box.
|
Check RTP Packets for Protocol Conformance
|
Whether to check RTP packets flowing through the pinholes for protocol conformance.
|
Payload Type must be Audio or Video based on Signaling Exchange
|
Whether to enforce the payload type to be audio or video based on the signaling exchange.
|
Match Condition and Action Tab
The Match All table lists the criteria included in the policy map. Each row indicates whether the inspection is looking for traffic that matches or does not match each criterion, the criterion and value that is inspected, and the action to be taken for traffic that satisfies the conditions.
• To add a criterion, click the Add button and fill in the Match Condition and Action dialog box (see H.323 Class and Policy Maps Add or Edit Match Condition (and Action) Dialog Boxes).
• To edit a criterion, select it and click the Edit button.
• To delete a criterion, select it and click the Delete button.
|
Category
|
The category assigned to the object. Categories help you organize and identify rules and objects. See Using Category Objects, page 9-4.
|
Allow Value Override per Device
Overrides
Edit button
|
Whether to allow the object definition to be changed at the device level. For more information, see Allowing a Global Object to Be Overridden, page 9-116 and Overriding Global Objects for Individual Devices, page 9-116.
If you allow device overrides, you can click the Edit button to create, edit, and view the overrides. The Overrides field indicates the number of devices that have overrides for this object.
|
Add or Edit HSI Group Dialog Boxes
Use the Add or Edit HSI group dialog boxes to add HSI groups to an H.323 policy inspection map.
Navigation Path
From the Parameters tab on the Add and Edit H.323 Map Dialog Boxes, click the Add Row button in the HSI group table, or select a row and click the Edit Row button.
Related Topics
•
Understanding Inspection Map Objects, page 9-39
•
Creating H.323 Map Objects, page 9-47
Field Reference
Table F-51 Add and Edit HSI Group Dialog Boxes
Element
|
Description
|
Group ID
|
The HSI group ID number (0 to 2147483647).
|
IP Address
|
The IP address of the HSI host.
|
Endpoint table
|
The end points associated with HSI group. You can add up to 10 end points per group. For each end point, you specify the IP address and interface policy group.
• To add an end point, click the Add button and fill in the dialog box (see Add or Edit HSI Endpoint IP Address Dialog Boxes).
• To edit an end point, select it and click the Edit button.
• To delete an end point, select it and click the Delete button.
|
Add or Edit HSI Endpoint IP Address Dialog Boxes
Us the Add or Edit HSI Endpoint IP Address dialog box to add end points to an HSI group.
Navigation Path
From the Add or Edit HSI Group Dialog Boxes, click the Add Row button in the end point table, or select a row and click the Edit Row button.
Related Topics
•
Understanding Inspection Map Objects, page 9-39
•
Creating H.323 Map Objects, page 9-47
Field Reference
Table F-52 Add and Edit HSI Endpoint IP Address Dialog Boxes
Element
|
Description
|
Network/Host
|
The IP address of the end point host or network.
|
Interface
|
The Interface policy group that identifies the interface connected to the security appliance. Enter the name of a policy group, or click Select to select it from a list, where you can also create new policy groups.
|
H.323 Class and Policy Maps Add or Edit Match Condition (and Action) Dialog Boxes
Use the Add or Edit H.323 Match Criterion (for H.323 class maps) or Match Condition and Action (for H.323 policy maps) dialog boxes to do the following:
•
Define the match criterion and value for an H.323 class map.
•
Select an H.323 class map when creating an H.323 policy map.
•
Define the match criterion, value, and action directly in an H.323 policy map.
The fields on this dialog box change based on the criterion you select and whether you are creating a class map or policy map.
Navigation Path
When creating an H.323 class map, in the Policy Object Manager, from the Add or Edit Class Maps Dialog Boxes for H.323, right-click inside the table, then select Add Row or right-click a row, then select Edit Row.
When creating an H.323 policy map, in the Policy Object Manager, from the Match Condition and Action tab on the Add and Edit H.323 Map Dialog Boxes, right-click inside the table, then select Add Row or right-click a row, then select Edit Row.
Related Topics
•
Understanding Inspection Map Objects, page 9-39
•
Creating Class Map Objects, page 9-41
•
Creating H.323 Map Objects, page 9-47
Field Reference
Table F-53 H.323 Class and Policy Maps Add and Edit Match Condition and Action Dialog Boxes
Element
|
Description
|
Match Type
Class Name
(Policy Map only)
|
Enables you to use an existing H.323 class map or define a new H.323 class map.
• Use Specified Values—You want to define the class map on this dialog box.
• Use Values in Class Map—You want to select an existing H.323 class map policy object. Enter the name of the H.323 class map in the Class Name field. Click Select to select the map from a list or to create a new class map object.
|
Criterion
|
Specifies which criterion of H.323 traffic to match:
• Called Party—Matches the called party address.
• Calling Party—Matches the calling party address.
• Media Type—Matches the media type.
|
Type
|
Specifies whether the map includes traffic that matches or does not match the criterion. For example, if Doesn't Match is selected on the string "example.com," then any traffic that contains "example.com" is excluded from the map.
• Matches—Matches the criterion.
• Doesn't Match—Does not match the criterion.
|
Action
(Policy Map only)
|
The action you want the device to take for traffic that matches the defined criteria.
|
Variable Fields
The following fields vary based on what you select in the Criterion field. This list is a super-set of the fields you might see.
|
Value
|
The regular expression you want to evaluate. You can select one of the following:
• Regular Expression—The regular expression object that defines the regular expression you want to use for pattern matching. Enter the name of the object. You can click Select to choose the object from a list of existing ones or to create a new regular expression object.
• Regular Expression Group—The regular expression group object that defines the regular expression you want to use for pattern matching. Enter the name of the object. You can click Select to choose the object from a list of existing ones or to create a new regular expression group object.
|
Media Type
|
The type of media you want to inspect, audio, video, or data.
|
Add and Edit HTTP Map Dialog Boxes for ASA 7.1.x/PIX 7.1.x/FWSM 3.x/IOS Devices
Use the Add and Edit HTTP Map dialog boxes to define HTTP maps for ASA 7.1.x, PIX 7.1.x, FWSM 3.x, and IOS devices.
The enhanced HTTP inspection feature, which is also known as an application firewall, verifies that HTTP messages conform to RFC 2616, use RFC-defined methods, and comply with various other criteria. This can help prevent attackers from using HTTP messages for circumventing network security policy.
When you enable HTTP inspection with an HTTP map, strict HTTP inspection with the action reset and log is enabled by default. You can change the actions performed in response to inspection failure, but you cannot disable strict inspection as long as the HTTP map remains enabled. Security Manager uses the http-map command to configure the map on the device.
Navigation Path
Select Tools > Policy Object Manager, then select Inspect Maps > Policy Maps > HTTP Maps (ASA 7.1.x/PIX 7.1.x/FWSM3.x/IOS) from the Object Type selector. Right-click inside the work area, then select New Object or right-click a row and select Edit Object.
Related Topics
•
Understanding Inspection Map Objects, page 9-39
•
Creating HTTP Map Objects (ASA 7.1.x/PIX 7.1.x/FWSM 3.x/IOS), page 9-49
Field Reference
Table F-54 Add and Edit HTTP Map Dialog Boxes for ASA 7.1.x/PIX 7.1.x/FWSM 3.x/IOS Devices
Element
|
Description
|
Name
|
The name of the policy object. A maximum of 40 characters is allowed.
|
Description
|
A description of the policy object. A maximum of 200 characters is allowed.
|
General tab
|
Defines the action taken when non-compliant HTTP requests are received and to enable verification of content type. For a description of the options, see HTTP Map General Tab.
|
Entity Length tab
|
Defines the action taken if the length of the HTTP content falls outside of configured targets. For a description of the options, see HTTP Map Entity Length Tab.
|
RFC Request Method tab
|
Defines the action that the security appliance should take when specific RFC request methods are used in the HTTP request. For a description of the options, see HTTP Map RFC Request Method Tab.
|
Extension Request Method tab
|
Defines the action taken when specific extension request methods are used in the HTTP request. For a description of the options, see HTTP Map Extension Request Method Tab.
|
Port Misuse tab
|
Defines the action taken when specific undesirable applications are encountered. For a description of the options, see HTTP Map Port Misuse Tab.
|
Transfer Encoding tab
|
Defines the action taken when specific transfer encoding types are used in the HTTP request. For a description of the options, see HTTP Map Transfer Encoding Tab.
|
Category
|
The category assigned to the object. Categories help you organize and identify rules and objects. See Using Category Objects, page 9-4.
|
Allow Value Override per Device
Overrides
Edit button
|
Whether to allow the object definition to be changed at the device level. For more information, see Allowing a Global Object to Be Overridden, page 9-116 and Overriding Global Objects for Individual Devices, page 9-116.
If you allow device overrides, you can click the Edit button to create, edit, and view the overrides. The Overrides field indicates the number of devices that have overrides for this object.
|
HTTP Map General Tab
Use the General tab to define the action taken when non-compliant HTTP requests are received and to enable verification of content type.
Navigation Path
Click the General tab on the Add and Edit HTTP Map Dialog Boxes for ASA 7.1.x/PIX 7.1.x/FWSM 3.x/IOS Devices.
Related Topics
•
Understanding Inspection Map Objects, page 9-39
•
Creating HTTP Map Objects (ASA 7.1.x/PIX 7.1.x/FWSM 3.x/IOS), page 9-49
Field Reference
Table F-55 HTTP Map General Tab
Element
|
Description
|
Take action for non-RFC 2616 compliant traffic
|
Whether you want to configure the action to be taken for traffic that does not comply with RFC 2616. Possible actions are:
• Allow Packet—Allow the message.
• Drop Packet—Close the connection.
• Reset Connection (default)—Send a TCP reset message to client and server.
You can also select Generate Syslog to write a message to the syslog if non-compliant traffic is encountered.
|
Verify Content-type field belongs to the supported internal content-type list.
|
Whether you want to configure the action to be taken for traffic whose content type does not belong to the supported internal content-type list. Possible actions are:
• Allow Packet—Allow the message.
• Drop Packet—Close the connection.
• Reset Connection (default)—Send a TCP reset message to client and server.
You can also select these options:
• Verify Content-type field for response matches the ACCEPT field of request—To also verify that the content type of the response matches the request.
• Generate Syslog—To write a message to the syslog if non-compliant traffic is encountered.
|
Override Global TCP Idle Timeout (IOS only)
|
Whether to change the TCP idle timeout default setting. An IOS device terminates a connection if there is no communication activity after this length of time. If you select this option, specify the desired timeout value in seconds.
|
Override Global Audit Trail Setting (IOS only)
Enable Audit Trail
|
Whether to change the audit trail setting for IOS devices. If you select this option, you can select Enable Audit Trail to generate audit trail messages.
|
HTTP Map Entity Length Tab
Use the Entity Length tab to enable inspection based on the length of the HTTP content.
Navigation Path
Click the Entity Length tab on the Add and Edit HTTP Map Dialog Boxes for ASA 7.1.x/PIX 7.1.x/FWSM 3.x/IOS Devices.
Related Topics
•
Understanding Inspection Map Objects, page 9-39
•
Creating HTTP Map Objects (ASA 7.1.x/PIX 7.1.x/FWSM 3.x/IOS), page 9-49
Field Reference
Table F-56 HTTP Map Entity Length Tab
Element
|
Description
|
Inspect URI Length
|
Whether to enable inspection based on the length of the URI. If you select this option, configure the following:
• Maximum—The desired maximum length, in bytes, of the URI, from 1 to 65535.
• Excessive URI Length Action—The action to take when the length is exceeded:
– Allow Packet—Allow the message.
– Drop Packet—Close the connection.
– Reset Connection—Send a TCP reset message to client and server.
• Generate Syslog—Whether to generate a syslog message when a violation occurs.
|
Inspect Maximum Header Length
|
Whether to enable inspection based on the length of the HTTP header. If you select this option, configure the following:
• Request—The desired maximum length, in bytes, of the request header, from 1 to 65535.
• Response—The desired maximum length, in bytes, of the response header, from 1 to 65535.
• Excessive Header Length Action—The action to take when the length is exceeded:
– Allow Packet—Allow the message.
– Drop Packet—Close the connection.
– Reset Connection—Send a TCP reset message to client and server.
• Generate Syslog—Whether to generate a syslog message when a violation occurs.
|
Inspect Body Length
|
Whether to enable inspection based on the length of the message body. If you select this option, configure the following:
• Minimum Threshold—The desired minimum length, in bytes, of the message body, from 1 to 65535.
• Maximum Threshold—The desired maximum length, in bytes, of the message body, from 1 to 65535.
• Body Length Threshold Action—The action to take when the message body falls outside of the configured boundaries:
– Allow Packet—Allow the message.
– Drop Packet—Close the connection.
– Reset Connection—Send a TCP reset message to client and server.
• Generate Syslog—Whether to generate a syslog message when a violation occurs.
|
HTTP Map RFC Request Method Tab
Use the RFC Request Method tab to define the action to take when specific request methods are used in the HTTP request.
Navigation Path
Click the RFC Request Method tab on the Add and Edit HTTP Map Dialog Boxes for ASA 7.1.x/PIX 7.1.x/FWSM 3.x/IOS Devices.
Related Topics
•
Understanding Inspection Map Objects, page 9-39
•
Creating HTTP Map Objects (ASA 7.1.x/PIX 7.1.x/FWSM 3.x/IOS), page 9-49
Field Reference
Table F-57 HTTP Map RFC Request Method
Element
|
Description
|
Available and Selected Methods
Action
Generate Syslog
|
The Available Methods list contains the request methods defined in RFC 2616.
To configure an action for a method, select it, then select an action and optionally select Generate Syslog if you want a message added to the syslog when an HTTP request containing the selected method is encountered. Click the >> button to add it to the Selected Methods list. (To remove a method from the selected list, select it and click the << button.)
Tip  You can select multiple methods at a time using Ctrl+click if the action and syslog requests are the same for each.
The actions you can specify are:
• Allow Packet—Allow the message.
• Drop Packet—Close the connection.
• Reset Connection (default)—Send a TCP reset message to client and server.
|
Specify the action to be applied for the remaining available methods above.
|
Whether to define a default action for the methods for which you have not configured specific actions above. If you select this option, select the action and syslog setting to use for the default action.
|
HTTP Map Extension Request Method Tab
Use the Extension Request Method tab to define the action taken when specific extension request methods are used in the HTTP request.
Navigation Path
Click the Extension Request Method tab on the Add and Edit HTTP Map Dialog Boxes for ASA 7.1.x/PIX 7.1.x/FWSM 3.x/IOS Devices.
Related Topics
•
Understanding Inspection Map Objects, page 9-39
•
Creating HTTP Map Objects (ASA 7.1.x/PIX 7.1.x/FWSM 3.x/IOS), page 9-49
Field Reference
Table F-58 HTTP Map Extension Request Method Tab
Element
|
Description
|
Available and Selected Methods
Action
Generate Syslog
|
The Available Methods list contains the extension request methods defined in RFC 2616.
To configure an action for a method, select it, then select an action and optionally select Generate Syslog if you want a message added to the syslog when an HTTP request containing the selected method is encountered. Click the >> button to add it to the Selected Methods list. (To remove a method from the selected list, select it and click the << button.)
Tip  You can select multiple methods at a time using Ctrl+click if the action and syslog requests are the same for each.
The actions you can specify are:
• Allow Packet—Allow the message.
• Drop Packet—Close the connection.
• Reset Connection (default)—Send a TCP reset message to client and server.
|
Specify the action to be applied for the remaining available methods above.
|
Whether to define a default action for the methods for which you have not configured specific actions above. If you select this option, select the action and syslog setting to use for the default action.
|
HTTP Map Port Misuse Tab
Use the Port Misuse tab to enable port misuse application firewall inspection. The application categories you can configure are:
•
IM—Instant Messaging. The applications checked for are Yahoo! Messenger, AIM, and MSN IM.
•
P2P—Peer-to-peer applications. The Kazaa application is checked.
•
Tunneling—Tunneling applications. The applications checked for are HTTPort/HTTHost, GNU Httptunnel, GotoMyPC, Firethru, and Http-tunnel.com Client.
Navigation Path
Click the Port Misuse tab on the Add and Edit HTTP Map Dialog Boxes for ASA 7.1.x/PIX 7.1.x/FWSM 3.x/IOS Devices.
Related Topics
•
Understanding Inspection Map Objects, page 9-39
•
Creating HTTP Map Objects (ASA 7.1.x/PIX 7.1.x/FWSM 3.x/IOS), page 9-49
Field Reference
Table F-59 HTTP Map Port Misuse Tab
Element
|
Description
|
Available and Selected Application Categories
Action
Generate Syslog
|
The Available Application Categories list contains the categories for which you can define firewall inspection settings.
To configure an action for a category, select it, then select an action and optionally select Generate Syslog if you want a message added to the syslog when an HTTP request containing the selected application is encountered. Click the >> button to add it to the Selected Categories list. (To remove a category from the selected list, select it and click the << button.)
Tip  You can select multiple categories at a time using Ctrl+click if the action and syslog requests are the same for each.
The actions you can specify are:
• Allow Packet—Allow the message.
• Drop Packet—Close the connection.
• Reset Connection (default)—Send a TCP reset message to client and server.
|
Specify the action to be applied for the remaining available categories above.
|
Whether to define a default action for the categories for which you have not configured specific actions above. If you select this option, select the action and syslog setting to use for the default action.
|
HTTP Map Transfer Encoding Tab
Use the Transfer Encoding tab to enable inspection based on the transfer encoding type. The encoding types that you can configure are:
•
Chunked—Identifies the transfer encoding type in which the message body is transferred as a series of chunks.
•
Compressed—Identifies the transfer encoding type in which the message body is transferred using UNIX file compression.
•
Deflate—Identifies the transfer encoding type in which the message body is transferred using zlib format (RFC 1950) and deflate compression (RFC 1951).
•
GZIP—Identifies the transfer encoding type in which the message body is transferred using GNU zip (RFC 1952).
•
Identity—Identifies connections in which no transfer encoding is performed in the message body.
Navigation Path
Click the Transfer Encoding tab on the Add and Edit HTTP Map Dialog Boxes for ASA 7.1.x/PIX 7.1.x/FWSM 3.x/IOS Devices.
Related Topics
•
Understanding Inspection Map Objects, page 9-39
•
Creating HTTP Map Objects (ASA 7.1.x/PIX 7.1.x/FWSM 3.x/IOS), page 9-49
Field Reference
Table F-60 HTTP Map Transfer Encoding Tab
Element
|
Description
|
Available and Selected Encoding Types
Action
Generate Syslog
|
The Available Encoding Types list contains the types of transfer encoding for which you can define firewall inspection settings.
To configure an action for a type, select it, then select an action and optionally select Generate Syslog if you want a message added to the syslog when an HTTP request containing the selected type is encountered. Click the >> button to add it to the Selected Encoding Types list. (To remove a type from the selected list, select it and click the << button.)
Tip  You can select multiple types at a time using Ctrl+click if the action and syslog requests are the same for each.
The actions you can specify are:
• Allow Packet—Allow the message.
• Drop Packet—Close the connection.
• Reset Connection (default)—Send a TCP reset message to client and server.
|
Specify the action to be applied for the remaining available encoding types above.
|
Whether to define a default action for the types for which you have not configured specific actions above. If you select this option, select the action and syslog setting to use for the default action.
|
Add or Edit HTTP Map Dialog Boxes for ASA 7.2+/PIX 7.2+ Devices
Use the Add and Edit HTTP Map dialog boxes to define the match criterion and values for the HTTP inspect map for ASA and PIX software releases 7.2 and higher.
Navigation Path
Select Tools > Policy Object Manager, then select Inspect Maps > Policy Maps > HTTP Maps (ASA 7.2+/PIX 7.2+) from the Object Type selector. Right-click inside the work area, then select New Object or right-click a row, then select Edit Object.
Related Topics
•
Understanding Inspection Map Objects, page 9-39
•
Configuring HTTP Policy Map Objects, page 9-48
•
Creating HTTP Map Objects (ASA 7.2+/PIX 7.2+), page 9-50
Field Reference
Table F-61 Add and Edit HTTP Map Dialog Boxes (ASA 7.2+/PIX 7.2+)
Element
|
Description
|
Name
|
The name of the policy object. A maximum of 40 characters is allowed.
|
Description
|
A description of the policy object. A maximum of 200 characters is allowed.
|
Parameters tab
|
Body Match Maximum
|
The maximum number of characters in the body of an HTTP message that should be searched in a body match.
Tip  A high value can have a significant impact on performance.
|
Check for protocol violations
|
Whether to check for protocol violations.
|
Action
|
The action to take based on the defined settings. You can drop, reset, or log the connection.
|
Spoof Server
|
Enables you to replace the server HTTP header value with the specified string.
|
Match Condition and Action Tab
The Match All table lists the criteria included in the policy map. Each row indicates whether the inspection is looking for traffic that matches or does not match each criterion, the criterion and value that is inspected, and the action to be taken for traffic that satisfies the conditions.
• To add a criterion, click the Add button and fill in the Match Condition and Action dialog box (see HTTP Class and Policy Map (ASA 7.2+/PIX 7.2+) Add or Edit Match Condition (and Action) Dialog Boxes).
• To edit a criterion, select it and click the Edit button.
• To delete a criterion, select it and click the Delete button.
|
Category
|
The category assigned to the object. Categories help you organize and identify rules and objects. See Using Category Objects, page 9-4.
|
Allow Value Override per Device
Overrides
Edit button
|
Whether to allow the object definition to be changed at the device level. For more information, see Allowing a Global Object to Be Overridden, page 9-116 and Overriding Global Objects for Individual Devices, page 9-116.
If you allow device overrides, you can click the Edit button to create, edit, and view the overrides. The Overrides field indicates the number of devices that have overrides for this object.
|
Overrides: None
|
Shows that no overrides exist on the device. You must manually set overrides in order to change the display. For more information, see Overriding Global Objects for Individual Devices, page 9-116.
Note Selecting Allow Value Override per Device does not automatically set overrides.
|
HTTP Class and Policy Map (ASA 7.2+/PIX 7.2+) Add or Edit Match Condition (and Action) Dialog Boxes
Use the Add or Edit HTTP Match Criterion (for HTTP class maps) or Match Condition and Action (for HTTP policy maps) dialog boxes to do the following:
•
Define the match criterion and value for an HTTP class map.
•
Select an HTTP class map when creating an HTTP policy map.
•
Define the match criterion, value, and action directly in an HTTP policy map.
These types of maps are used only for devices running ASA 7.2 or higher, or PIX 7.2 or higher, operating systems.
The fields on this dialog box change based on the criterion you select and whether you are creating a class map or policy map. You can use the following criteria:
•
Request/Response Content Type Mismatch—Specifies that the content type in the response must match one of the MIME types in the accept field of the request.
•
Request Arguments—Applies the regular expression match to the arguments of the request.
•
Request Body—Applies the regular expression match to the body of the request.
•
Request Body Length—Specifies that the body length of the request be matched as greater than or less than the specified number of bytes.
•
Request Header Count—Specifies that the number of headers in the request be matched as greater than or less than the specified number.
•
Request Header Length—Specifies that the header length of the request be matched as greater than or less than the specified number of bytes.
•
Request Header Field—Applies the regular expression match to the header of the request.
•
Request Header Field Count—Applies the regular expression match to the header of the request based on a specified number of header fields.
•
Request Header Field Length—Applies the regular expression match to the header of the request based on a specified field length.
•
Request Header Content Type—Specifies the content type to evaluate in the content-type header field of the request.
•
Request Header Transfer Encoding—Specifies the transfer encoding to evaluate in the transfer-encoding header field of the request.
•
Request Header Non-ASCII—Specifies whether there are non-ASCII characters in the header of the request.
•
Request Method—Specifies the method of the request to match.
•
Request URI—Applies the regular expression match to the URI of the request.
•
Request URI Length—Specifies that the URI length of the request be matched as greater than or less than the specified number of bytes.
•
Response Body ActiveX—Specifies whether there is ActiveX content in the body of the request.
•
Response Body Java Applet—Specifies whether there is a Java applet in the body of the request.
•
Response Body—Applies the regular expression match to the body of the response.
•
Response Body Length—Specifies that the body length of the response be matched as greater than or less than the specified number of bytes.
•
Response Header Count—Specifies that the number of headers in the response be matched as greater than or less than the specified number.
•
Response Header Length—Specifies that the header length of the response be matched as greater than or less than the specified number of bytes.
•
Response Header Field—Applies the regular expression match to the header of the response.
•
Response Header Field Count—Applies the regular expression match to the header of the response based on a specified number of header fields.
•
Response Header Field Length—Applies the regular expression match to the header of the response based on a specified field length.
•
Response Header Content Type—Specifies the content type to evaluate in the content-type header field of the response.
•
Response Header Transfer Encoding—Specifies the transfer encoding to evaluate in the transfer-encoding header field of the response.
•
Response Header Non-ASCII—Specifies whether there are non-ASCII characters in the header of the response.
•
Response Status Line—Applies the regular expression match to the status line of the response.
Navigation Path
When creating an HTTP class map, in the Policy Object Manager, from the Add or Edit Class Maps Dialog Boxes for HTTP, right-click inside the table, then select Add Row or right-click a row, then select Edit Row.
When creating an HTTP policy map, in the Policy Object Manager, from the Match Condition and Action tab on the Add or Edit HTTP Map Dialog Boxes for ASA 7.2+/PIX 7.2+ Devices, right-click inside the table, then select Add Row or right-click a row, then select Edit Row.
Related Topics
•
Understanding Inspection Map Objects, page 9-39
•
Creating HTTP Map Objects (ASA 7.2+/PIX 7.2+), page 9-50
•
Creating Class Map Objects, page 9-41
Field Reference
Table F-62 HTTP Class and Policy Maps (ASA 7.2+/PIX 7.2+) Add and Edit Match Condition and Action Dialog Boxes
Element
|
Description
|
Match Type
Class Name
(Policy Map only)
|
Enables you to use an existing HTTP class map or define a new HTTP class map.
• Use Specified Values—You want to define the class map on this dialog box.
• Use Values in Class Map—You want to select an existing HTTP class map policy object. Enter the name of the HTTP class map in the Class Name field. Click Select to select the map from a list or to create a new class map object.
|
Criterion
|
Specifies which criterion of HTTP traffic to match. The criteria are described above.
|
Type
|
Specifies whether the map includes traffic that matches or does not match the criterion. For example, if Doesn't Match is selected on the string "example.com," then any traffic that contains "example.com" is excluded from the map.
• Matches—Matches the criterion. For some criteria, this is the only available option.
• Doesn't Match—Does not match the criterion.
|
Action
(Policy Map only)
|
The action you want the device to take for traffic that matches the defined criteria. The types of action depend on the criterion you select.
|
Variable Fields
The following fields vary based on what you select in the Criterion field. This list is a super-set of the fields you might see.
|
Field Name
|
The name of the header field to evaluate. You can select one of the following:
• Predefined—The predefined HTTP header fields.
• Regular Expression—The regular expression object that defines the regular expression you want to use for pattern matching. Enter the name of the object. You can click Select to choose the object from a list of existing ones or to create a new regular expression object.
|
Value
|
The regular expression you want to evaluate. You can select one of the following:
• Regular Expression—The regular expression object that defines the regular expression you want to use for pattern matching. Enter the name of the object. You can click Select to choose the object from a list of existing ones or to create a new regular expression object.
• Regular Expression Group—The regular expression group object that defines the regular expression you want to use for pattern matching. Enter the name of the object. You can click Select to choose the object from a list of existing ones or to create a new regular expression group object.
When you are evaluating the Request Header Transfer Encoding or Response Header Transfer Encoding criteria, you can also select these options:
• Specified By—One of the following predefined types of transfer encoding:
– Chunked—The message body is transferred as a series of chunks.
– Compressed—The message body is transferred using UNIX file compression.
– Deflate—The message body is transferred using zlib format (RFC 1950) and deflate compression (RFC 1951).
– GZIP—The message body is transferred using GNU zip (RFC 1952).
– Identity—No transfer encoding is performed.
• Empty—The transfer-encoding field in request header is empty.
|
Greater Than Length
|
The length in bytes of the evaluated field. The criterion matches if the length is greater than the specified number, and does not match if the field is less than the specified number.
|
Greater Than Count
|
The number of evaluated items. The criterion matches if the count is greater than the specified number, and does not match if the count is less than the specified number.
|
Content Type
|
The content type to evaluate as specified in the content-type header field. You can select one of the following:
• Specified By—A predefined MIME type.
• Unknown—The MIME type is not known. Select Unknown when you want to evaluate the item against all known MIME types.
• Violation—The magic number in the body must correspond to the MIME type in the content-type header field.
• Regular Expression, Regular Expression Group—The regular expression or regular expression group to evaluate. See the explanation for the Value field for an explanation of these options.
|
Request Method
|
The specified request method to match. You can select one of the following:
• Specified By—The predefined request method.
• Regular Expression, Regular Expression Group—The regular expression or regular expression group to evaluate. See the explanation for the Value field for an explanation of these options.
|
Add and Edit IM Map Dialog Boxes (for ASA 7.2+/PIX 7.2+)
Use the Add and Edit IM Map dialog boxes to define settings for define an Instant Messenger (IM) inspect map for devices running ASA/PIX 7.2 or higher.
Navigation Path
Select Tools > Policy Object Manager, then select Inspect Maps > Policy Maps > IM Maps (ASA 7.2+/PIX 7.2+) from the Object Type selector. Right-click inside the work area, then select New Object or right-click a row and select Edit Object.
Related Topics
•
Understanding Inspection Map Objects, page 9-39
•
Creating IM Map Objects for Devices running ASA/PIX 7.2 and Higher, page 9-51
Field Reference
Table F-63 Add and Edit IM Map Dialog Boxes
Element
|
Description
|
Name
|
The name of the policy object. A maximum of 40 characters is allowed.
|
Description
|
A description of the policy object. A maximum of 200 characters is allowed.
|
Match Condition and Action Tab
The Match All table lists the criteria included in the policy map. Each row indicates whether the inspection is looking for traffic that matches or does not match each criterion, the criterion and value that is inspected, and the action to be taken for traffic that satisfies the conditions.
• To add a criterion, click the Add button and fill in the Match Condition and Action dialog box (see IM Class and Policy Map (ASA 7.2+/PIX 7.2+) Add or Edit Match Condition (and Action) Dialog Boxes).
• To edit a criterion, select it and click the Edit button.
• To delete a criterion, select it and click the Delete button.
|
Category
|
The category assigned to the object. Categories help you organize and identify rules and objects. See Using Category Objects, page 9-4.
|
Allow Value Override per Device
Overrides
Edit button
|
|