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
Add or Edit 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 Group Policies Dialog Box
ASA Group Policies Client Configuration Settings
ASA Group Policies Client Firewall Attributes
ASA Group Policies Hardware Client Attributes
ASA Group Policies IPSec Settings
ASA Group Policies SSL VPN Clientless Settings
ASA Group Policies SSL VPN Full Client Settings
ASA Group Policies SSL VPN Settings
ASA Group Policies DNS/WINS Settings
ASA Group Policies Split Tunneling Settings
ASA Group Policies 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
Add or Edit IKE Proposal Dialog Box
Interface Role Dialog Box
Interface Name Conflict Dialog Box
Add or Edit IPSec Transform Set Dialog Box
Add and Edit LDAP Attribute Map Dialog Boxes
Add and Edit LDAP Attribute Map Value Dialog Boxes
Add and Edit Map Value Dialog Boxes
Add or Edit Class Maps Dialog Boxes
Zone-Based Firewall IM Application Class Maps Add or Edit Match Condition Dialog Boxes
Zone-Based Firewall P2P Application Class Maps Add or Edit Match Condition Dialog Boxes
H.323 (IOS) Class Maps Add or Edit Match Criterion Dialog Boxes
HTTP (IOS) Class Add or Edit Match Criterion Dialog Boxes
IMAP and POP3 Class Maps Add or Edit Match Criterion Dialog Boxes
SIP (IOS) Class Add or Edit Match Criterion Dialog Boxes
SMTP Class Maps Add or Edit Match Criterion Dialog Boxes
Sun RPC Class Maps Add or Edit Match Criterion Dialog Boxes
Local Web Filter Class Add or Edit Match Criterion Dialog Boxes
N2H2 and Websense Class Add or Edit Match Criterion Dialog Boxes
Add or Edit Inspect Parameter Map Dialog Boxes
Add or Edit Protocol Info Parameter Map Dialog Boxes
Add or Edit DNS Server for Protocol Info Parameters Dialog Box
Add or Edit Local Web Filter Parameter Map Dialog Boxes
Add or Edit N2H2 or WebSense Parameter Map Dialog Boxes
Add or Edit External Filter Dialog Box
Add or Edit Trend Parameter Map Dialog Boxes
Add or Edit URL Filter Parameter Map Dialog Boxes
Add or Edit URL Domain Name Dialog Box for URL Filter Parameters
Add or Edit URLF Glob Parameter Map 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 or Edit Policy Maps Dialog Boxes for Zone-Based Firewall Policies
Add or Edit Match Condition and Action Dialog Boxes for Zone-Based Firewall and Web Filter Policies
Add and Edit Web Filter 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
Add or Edit 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
Add or Edit Port Forwarding List Dialog Boxes
Add or Edit A Port Forwarding Entry Dialog Box
Add or Edit 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 Smart Tunnel List Dialog Boxes
Add and Edit A Smart Tunnel Entry Dialog Boxes
Add or Edit Text Object Dialog Box
Add or Edit Time Range Dialog Box
Recurring Ranges Dialog Box
Add and Edit Traffic Flow Dialog Boxes
Default Inspection Traffic
Add or Edit 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 Dialog Box
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 Dialog Box
•
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"
•
Creating Policy Objects, page 8-4
•
Object Usage Dialog Box
•
Policy Object Overrides Window
•
Selecting Objects for Policies, page 8-2
•
How Policy Objects are Provisioned as ASA/PIX/FWSM Object Groups, page 8-96
•
Filtering Tables, page 2-16
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.
|
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 8-6.
|
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 Managing Object Overrides, page 8-9.
|
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. Also, see Creating Policy Objects, page 8-4.
|
|
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 8-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 8-8.
|
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.
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. Also, see Creating Policy Objects, page 8-4.
|
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 8-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 8-8.
|
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 Managing Object Overrides, page 8-9.
|
Create Duplicate
|
Select this command to create a copy of the policy object. For more information, see Duplicating Objects, page 8-7.
|
Find Usage
|
Select this command to generate a usage report for the selected object using the Object Usage Dialog Box. The usage report tells you where the object is currently being used. for more information, see Generating Object Usage Reports, page 8-8.
|
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 8-8.
|
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
•
Add or Edit AAA Server Dialog Box
•
Add or Edit Access List Dialog Boxes
•
ASA Group Policies 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
•
Add or Edit IKE Proposal Dialog Box
•
Interface Role Dialog Box
•
Add or Edit IPSec Transform Set Dialog Box
•
Add and Edit LDAP Attribute Map Dialog Boxes
•
Add or Edit Class Maps Dialog Boxes
•
Add or Edit Inspect Parameter Map Dialog Boxes
•
Add or Edit Protocol Info Parameter Map Dialog Boxes
•
Add or Edit Local Web Filter Parameter Map Dialog Boxes
•
Add or Edit N2H2 or WebSense Parameter Map Dialog Boxes
•
Add or Edit Trend Parameter Map Dialog Boxes
•
Add or Edit URL Filter Parameter Map Dialog Boxes
•
Add or Edit URLF Glob Parameter Map 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 or Edit Policy Maps Dialog Boxes for Zone-Based Firewall Policies
•
Add and Edit Web Filter 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 or Edit Network/Host Dialog Box
•
PKI Enrollment Dialog Box
•
Add or Edit Port Forwarding List Dialog Boxes
•
Add or Edit 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 Smart Tunnel List Dialog Boxes
•
Add or Edit Text Object Dialog Box
•
Add or Edit Time Range Dialog Box
•
Add and Edit Traffic Flow Dialog Boxes
•
Add or Edit 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 and select New Object or right-click a row and select Edit Object.
Related Topics
•
Creating AAA Server Group Objects, page 8-22
•
Understanding AAA Server and Server Group Objects, page 8-15
•
Creating Policy Objects, page 8-4
•
Add or Edit 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.
Consider the following important points:
• 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.
• 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
|
An optional description of the object.
|
Protocol
|
The protocol used by the AAA servers in the group. For more information about these options, see Supported AAA Server Types, page 8-16 and Additional AAA Support on ASA, PIX, and FWSM Devices, page 8-17.
|
AAA Servers
|
The AAA server policy objects that comprise the server group. Enter the names of the objects or click Select to select them from a list that is filtered to show only those AAA server objects that use the selected protocol. Separate multiple objects with commas. You can also create new objects from the selection list.
|
Make this Group the Default AAA Server Group (IOS)
(IOS devices only.)
|
Whether to designate this AAA server group as the default group for the RADIUS or TACACS+ protocol. Select this option if you intend to use a single global group for the selected protocol for all policies on a specific device requiring AAA.
Do not select this option 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 called CSM-rad-grp (for RADIUS) and CSM-tac-grp (for TACACS+), both of which are marked as default groups. These two groups 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 8-19.
|
Max Failed Attempts
(PIX, ASA, FWSM devices only.)
|
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 devices only.)
|
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 devices only.)
|
When you select Depletion as the 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 devices only.)
|
When using the RADIUS or TACACS+ protocols, 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 8-6.
|
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 Policy Object to Be Overridden, page 8-10 and Understanding Policy Object Overrides for Individual Devices, page 8-9.
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 AAA Server Dialog Box
Use Add or Edit AAA Server dialog box to create, copy, and edit a AAA server object. These objects are collected into AAA server group objects, and identify the AAA servers that you want to use when defining various AAA policies.
For a description of the protocols you can use, see Supported AAA Server Types, page 8-16 and Additional AAA Support on ASA, PIX, and FWSM Devices, page 8-17.
Note
You cannot edit the protocol if the object is already included in a AAA server group.
Navigation Path
Select Tools > Policy Object Manager, then select AAA Servers 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 AAA Server Objects, page 8-20
•
Understanding AAA Server and Server Group Objects, page 8-15
•
Policy Object Manager Window
Field Reference
Table F-4 AAA Server Dialog Box—General Settings
Element
|
Description
|
Name
|
The object name, which can be up to 128 characters. Object names are not case-sensitive. For more information, see Creating Policy Objects, page 8-4.
|
Description
|
An optional description of the object.
|
Host
|
The address of the AAA server to which authentication requests will be sent. Specify one of the following:
• IP Address—The IP address or (for ASA or PIX 7.2+ devices) host name of the AAA server. You can also enter the name of a network/host object that contains the host IP address, or click Select to select the object.
• DNS Name (For PIX/ASA 7.2+ devices only)—The DNS hostname of the AAA server, up to 128 characters. The hostname can contain alphanumeric characters and hyphens, but each element of the hostname must begin and end with an alphanumeric character.
|
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 select it from a list or to create a new interface role.
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.
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 8-22.
|
Timeout
|
The amount of time to wait until the AAA server is considered unresponsive:
• Values for Cisco IOS routers range from 1-1000 seconds. The default is 5 seconds.
• Values for ASA/PIX 7.x+ devices is 1-60 seconds. The default is 10 seconds.
• 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. The fields to the right of the protocol list change depending on your selection.
For specific information about the fields, see the topics indicated.
• The following protocols are supported for all device types:
– RADIUS—See AAA Server Dialog Box—RADIUS Settings.
– TACACS+—See AAA Server Dialog Box—TACACS+ Settings.
• The following protocols are supported for ASA/PIX 7.x+ and FWSM 3.1+ devices:
– Kerberos—See AAA Server Dialog Box—Kerberos Settings.
– LDAP—See AAA Server Dialog Box—LDAP Settings.
– NT—See AAA Server Dialog Box—NT Settings.
– SDI—See AAA Server Dialog Box—SDI Settings.
– HTTP-FORM—See AAA Server Dialog Box—HTTP-FORM Settings.
|
Category
|
The category assigned to the object. Categories help you organize and identify rules and objects. See Using Category Objects, page 8-6.
|
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 Add or Edit AAA Server Dialog Box and select RADIUS in the Protocol field.
Related Topics
•
Creating AAA Server Objects, page 8-20
•
Understanding AAA Server and Server Group Objects, page 8-15
•
AAA Server Group Dialog Box
Field Reference
Table F-5 AAA Server Dialog Box—RADIUS Settings
Element
|
Description
|
Key
Confirm
|
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 the following:
• Activity validation fails if you try defining a key with a space on a PIX, ASA, or FWSM device.
• If you do not define a key, all traffic between the AAA server and its AAA clients is sent unencrypted.
|
Authentication/Authorization Port
|
The port on which AAA authentication and authorization are performed. The default is 1645.
|
Accounting Port
|
The port on which AAA accounting is performed. The default is 1646.
|
RADIUS Password
Confirm
(ASA, PIX 7.x+, and FWSM 3.x+ devices only.)
|
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
(ASA, PIX 7.x+, and FWSM 3.x+ devices only.)
|
The interval between attempts to contact the AAA server. Values are:
• ASA/FWSM devices—1 to 10 seconds.
• PIX devices—1 to 5 seconds.
|
ACL Netmask Convert
(ASA, PIX 7.x+, and FWSM 3.x+ devices only.)
|
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 (used by Cisco IOS software), 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 Add or Edit AAA Server Dialog Box and select TACACS+ in the Protocol field.
Related Topics
•
Creating AAA Server Objects, page 8-20
•
Understanding AAA Server and Server Group Objects, page 8-15
•
AAA Server Group Dialog Box
Field Reference
Table F-6 AAA Server Dialog Box—TACACS+ Settings
Element
|
Description
|
Key
Confirm
|
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 the following:
• Activity validation fails if you try defining a key with a space on a PIX, ASA, or FWSM device.
• If you do not define a key, all traffic between the AAA server and its AAA clients is sent unencrypted.
|
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, PIX 7.x+, and FWSM 3.1+ devices.
Navigation Path
Go to the Add or Edit AAA Server Dialog Box and select Kerberos in the Protocol field.
Related Topics
•
Creating AAA Server Objects, page 8-20
•
Understanding AAA Server and Server Group Objects, page 8-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. The 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. 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 an LDAP AAA server object.
Note
This type of AAA server can be configured only on ASA, PIX 7.x+, and FWSM 3.1+ devices.
Navigation Path
Go to the Add or Edit AAA Server Dialog Box and select LDAP in the Protocol field.
Related Topics
•
Creating AAA Server Objects, page 8-20
•
Understanding AAA Server and Server Group Objects, page 8-15
•
AAA Server Group Dialog Box
Field Reference
Table F-8 AAA Server Dialog Box—LDAP Settings
Element
|
Description
|
Enable LDAP over SSL
|
Whether to establish a secure SSL connection between the ASA/PIX/FWSM device and the LDAP server.
Tip  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. The 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 the ASA/PIX/FWSM 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. 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
SASL Kerberos Authentication
Kerberos Server Group
|
These options establish a Simple Authentication and Security Layer (SASL) mechanism to authenticate an LDAP client (the ASA/PIX/FWSM device) with an LDAP server.
You can define one or both SASL authentication mechanisms. When negotiating SASL authentication, the ASA/PIX/FWSM device retrieves the list of SASL mechanisms configured on the LDAP server and selects the strongest mechanism configured on both devices.
• SASL MD5 Authentication—Whether to have the device send the LDAP server an MD5 value computed from the username and password.
• SASL Kerberos Authentication—Whether to have the device send 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.
If you select Kerberos, you must also enter 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/PIX/FWSM device tries to determine the server type automatically. This is the default.
• Microsoft—The LDAP server is a Microsoft Active Directory server.
Note You must configure LDAP over SSL to enable password management with Microsoft Active Directory.
• Sun—The LDAP server is a Sun Microsystems JAVA System Directory Server.
• OpenLDAP—The server is an Open LDAP server. You can use this only with ASA/PIX 8.0+ devices.
• Novell—The server is a Novell LDAP server. You can use this only with ASA/PIX 8.0+ devices.
|
LDAP Attribute Map
|
The LDAP attribute configuration to bind to the LDAP server. Enter the name of an LDAP attribute map policy object or click Select to select it from a list or to create a new object.
LDAP attribute maps take the attribute names that you define and map them to Cisco-defined attributes. For more information, see Creating LDAP Attribute Map Objects, page 8-37.
|
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, PIX 7.x+, and FWSM 3.1+ devices.
Navigation Path
Go to the Add or Edit AAA Server Dialog Box and select NT in the Protocol field.
Related Topics
•
Creating AAA Server Objects, page 8-20
•
Understanding AAA Server and Server Group Objects, page 8-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, PIX 7.x+, and FWSM 3.1+ devices.
Navigation Path
Go to the Add or Edit AAA Server Dialog Box and select SDI in the Protocol field.
Related Topics
•
Creating AAA Server Objects, page 8-20
•
Understanding AAA Server and Server Group Objects, page 8-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. 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
• SDI-5—SDI version 5.0 or later.
|
SDI pre-5 Slave Server
|
(Optional) A secondary server to be used for authentication if the primary server fails when using an SDI version prior to 5.0. Enter the IP address or the name of a network/host object, or click Select to select an object or create a new one.
|
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, PIX 7.x+, and FWSM 3.1+ devices.
Navigation Path
Go to the Add or Edit AAA Server Dialog Box and select HTTP-FORM in the Protocol field.
Related Topics
•
Creating AAA Server Objects, page 8-20
•
Understanding AAA Server and Server Group Objects, page 8-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 might 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.
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.
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 8-23
•
Creating Extended Access Control List Objects, page 8-23
•
Creating Standard Access Control List Objects, page 8-25
•
Creating Web Access Control List Objects, page 8-26
•
Contiguous and Discontiguous Network Masks, page 8-65
•
Understanding Network/Host Objects, page 8-65
•
Understanding and Specifying Services and Service and Port List Objects, page 8-75
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 Creating Policy Objects, page 8-4.
|
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 8-6.
|
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 Policy Object to Be Overridden, page 8-10 and Understanding Policy Object Overrides for Individual Devices, page 8-9.
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 8-23
•
Understanding Access Rule Address Requirements and How Rules Are Deployed, page 11-19
•
Understanding Network/Host Objects, page 8-65
•
Understanding and Specifying Services and Service and Port List Objects, page 8-75
•
Filtering Items in Selectors, page 2-14
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.
|
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 8-6.
|
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 Specifying IP Addresses During Policy Definition, page 8-68.
• 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/24 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 8-65).
|
Services
|
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 service objects and service types (which are typically a protocol and port combination). 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 or Tab.
For complete information on how to specify services, see Understanding and Specifying Services and Service and Port List Objects, page 8-75.
|
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 8-25
•
Understanding Access Rule Address Requirements and How Rules Are Deployed, page 11-19
•
Understanding Network/Host Objects, page 8-65
•
Understanding and Specifying Services and Service and Port List Objects, page 8-75
•
Filtering Items in Selectors, page 2-14
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.
|
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 8-6.
|
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 Specifying IP Addresses During Policy Definition, page 8-68.
• 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/24 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 8-65).
|
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 8-26
•
Understanding Access Rule Address Requirements and How Rules Are Deployed, page 11-19
•
Understanding Network/Host Objects, page 8-65
•
Understanding and Specifying Services and Service and Port List Objects, page 8-75
•
Filtering Items in Selectors, page 2-14
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.
|
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 Specifying IP Addresses During Policy Definition, page 8-68.
• 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/24 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 8-65).
|
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 Creating Time Range Objects, page 8-92.
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 8-6.
|
Description
|
An optional description of the object.
|
ASA Group Policies Dialog Box
Use the Add or Edit ASA Group Policies dialog box to create, copy, and edit an ASA user group policies object.
ASA group policies are configured on ASA security appliances in Easy VPN topologies, IPSec VPNs, and SSL VPNs. When you configure an Easy VPN, IPSec VPN or SSL VPN connection, you must create group policies to which remote clients will belong. A user group policy is a set of user-oriented attribute/value pairs for SSL VPN connections that are stored either internally (locally) on the device or externally on a AAA server. The tunnel group uses a user group policy that sets terms for user connections after the tunnel is established. Group policies let you apply whole sets of attributes to a user or a group of users rather than having to specify each attribute individually for each user.

Note
You must select the technology (Easy VPN/IPSec VPN, SSL VPN, or Easy VPN/IPSec VPN and SSL VPN) for which you are creating the object. If you are editing an existing ASA group policies object, the technology is already selected, and you cannot change it. Depending on the selected technology, the appropriate settings are available for configuration.
Navigation Path
Select ASA Group Policies in the Policy Object Manager Window. Right-click inside the work area and select New Object or right-click a row and select Edit Object.
Tip
You can also access this dialog box from the Remote Access VPN > Group Policies policy.
Related Topics
•
Creating ASA User Group Objects, page 8-28
•
Creating Group Policies (ASA), page 10-30
Field Reference
Table F-16 Add or Edit ASA Group Policies Dialog Box, including Technology Settings
Element
|
Description
|
Name
|
The object name, which can be up to 128 characters. Object names are not case-sensitive. For more information, see Creating Policy Objects, page 8-4.
|
Description
|
An optional description of the object.
|
Settings Pane
The body of the dialog box is a pane with a table of contents on the left and settings related to the item selected in the table of contents on the right.
You must first configure technology settings, then you can select items from the table of contents on the left and configure the options you require. Your selections on the Technology page control which options are available on these pages and in the table of contents.
The top folders in the table of contents represent the VPN technologies or other settings that you can configure, and are explained next.
|
Technology settings
|
These settings control what you can define in the group policy:
• Group Policy Type—Whether you are storing the group policy on the ASA device itself (Internal) or on a AAA server (External). You cannot change this option when editing an object.
If you select External, the only attributes you can configure are the name of the AAA server group object that identifies the AAA server and its password.
• Technology—The types of VPN for which this object defines group policies. You cannot change this option when editing an object. You can configure settings for Easy VPN/IPSec VPN, SSL VPN, or both. The default is both.
• External Server Group—If you are storing the group policy attributes on an external AAA server, specify the AAA server group that will be used for authentication. Click Select to select the object from a list or to create a new object.
After you select an external server group, the Password and Confirm fields become active. Enter the alphanumeric password to use for authenticating with the server in both fields. The password can be a maximum of 128 characters; spaces are not allowed.
|
DNS/WINS
|
The DNS and WINS servers and the domain name that should be pushed to clients associated with the group. See ASA Group Policies DNS/WINS Settings.
|
Split Tunneling
|
Settings to allow a remote client to conditionally direct encrypted packets through a secure tunnel to the central site and simultaneously allow clear text tunnels to the Internet through a network interface. See ASA Group Policies Split Tunneling Settings.
|
Easy VPN/IPSec VPN
|
Settings for Easy VPN and remote access IPSec VPNs:
• Client Configuration—The Cisco client parameters for the group. See ASA Group Policies Client Configuration Settings.
• Client Firewall Attributes—The firewall settings for VPN clients for the group. See ASA Group Policies Client Firewall Attributes.
• Hardware Client Attributes—The VPN 3002 Hardware Client settings for the group. See ASA Group Policies Hardware Client Attributes.
• IPSec—The tunneling protocols, filters, connection settings, and servers for the group. See ASA Group Policies IPSec Settings.
|
SSL VPN
|
Settings for SSL VPN:
• Clientless—Settings for the clientless mode of access to the corporate network in an SSL VPN. See ASA Group Policies SSL VPN Clientless Settings.
• Full Client—Settings for the full client mode of access to the corporate network in an SSL VPN. See ASA Group Policies SSL VPN Full Client Settings.
• Settings—The general settings that are required for clientless/port forwarding in an SSL VPN. See ASA Group Policies SSL VPN Settings.
|
Connection Settings
|
The connection settings for the group, such as the session and idle timeouts, including the banner text. See ASA Group Policies Connection Settings.
|
ASA Group Policies Client Configuration Settings
Use the Client Configuration settings page to configure the Cisco client parameters for the ASA group policy for Easy VPN or remote access VPN.
Navigation Path
Select Easy VPN/IPSec VPN > Client Configuration from the table of contents in the ASA Group Policies Dialog Box.
Field Reference
Table F-17 ASA Group Policies Client Configuration Settings
Element
|
Description
|
Store Password on Client System
|
Whether to allow users to store a password on their local systems. Enable this feature only if you are certain that the local systems will be in secure sites.
|
Enable IPsec over UDP
UDP Port
|
Whether to allow a Cisco VPN client or hardware client to connect using UDP to a security appliance that is running NAT.
If you select this option, specify the UDP port number within the range of 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.
Note The Cisco VPN client must also be configured to use IPsec over UDP, which is configured by default on certain devices.
|
IPsec Backup Servers
Servers List
|
Specify the backup server configuration:
• 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—Use the backup servers you specify in the servers list. Enter the IP addresses of the servers, or the name of a network/host object. Click Select to select the object from a list or to create a new object.
You can 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.
|
ASA Group Policies Client Firewall Attributes
Use the Client Firewall Attributes settings to configure the firewall settings for VPN clients for the ASA group policy for Easy VPN or IPSec VPN. Only VPN clients running Microsoft Windows can use these firewall settings.
Navigation Path
Select Easy VPN/IPSec VPN > Client Firewall Attributes from the table of contents in the ASA Group Policies Dialog Box.
Field Reference
Table F-18 ASA Group Policies Client Firewall Attributes
Element
|
Description
|
Firewall Mode
|
The firewall requirements for client systems for the group:
• No Firewall—Do not use a firewall. You cannot configure any other options on the page.
• Firewall Required—All users in this group must use the designated firewall. The security appliance drops any session that attempts to connect without the designated 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 if you require a client firewall.
• Firewall Optional—Users can use a firewall but it is not required. This option allows all 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 firewalls and others do not. For example, you might have clients with systems that do not run Microsoft windows, or your clients have not all had the opportunity to install firewall software.
|
Firewall Type
|
The type of firewall that you are making required or optional. The list shows all of the supported firewall software, which includes software from Cisco, Network ICE, Sygate, and Zone Labs.
• If you select Custom Firewall, you must fill in the fields in the Custom Firewall group. You also need to configure the policy source; select options only if they are supported by the vendor.
• Some firewall types require you to specify the source of the policy implemented by the firewall.
|
Policy Source
|
Some types of firewall allow you to configure where the client firewall should obtain its policies:
• Get Policy From Remote Firewall—The policy is configured in the client firewall application. This is how most client firewalls work.
• Use Specified Policy—The policy you specify should be pushed to the client firewall application, which should use your policy.
You must enter the name of an extended access control list policy object, or click Select to select one from a list or to create a new one, in both in the Inbound Traffic Policy and Outbound Traffic Policy fields.
|
Custom Firewall
|
The attributes that define the required or optional firewall if you select custom firewall as the firewall type:
• Vendor ID—The number that identifies the vendor of the custom firewall. Values are 1-255.
• Product ID—The number that identifies the product or model of the custom firewall. Values are 1-32 or 255. Multiple ranges are allowed, for example, 4-12, 24-32. Use 255 for all supported products.
• Description—An optional description of the custom firewall, for example, the name of the vendor and product.
|
ASA Group Policies Hardware Client Attributes
Use the Hardware Client Attributes settings to configure the VPN 3002 Hardware Client settings for the ASA group policy in an Easy VPN or IPSec VPN.
Navigation Path
Select Easy VPN/IPSec VPN > Hardware Client Attributes from the table of contents in the ASA Group Policies Dialog Box.
Field Reference
Table F-19 ASA Group Policies Hardware Client Attributes
Element
|
Description
|
Require Interactive Client Authentication
|
Whether to enable 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
|
Whether to require 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.
If you do not select this option, the security appliance allows inheritance of a value for user authentication from another group policy.
|
Enable Cisco IP Phone Bypass
|
Whether to allow IP phones behind hardware clients to connect without undergoing a user authentication processes. Secure unit authentication remains in effect for other users.
|
Enable LEAP Bypass
|
Whether to enable Lightweight Extensible Authentication Protocol (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 LEAP is an 802.1X wireless authentication method that 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
|
Whether to enable 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
|
How to handle periods of inactivity from individual clients:
• Specified Timeout—If there is no communication activity by a user behind a hardware client for the number of minutes you specify, the security appliance terminates the client's access. Values are 1-35791394 minutes.
• Unlimited Timeout—User sessions are not terminated due to inactivity.
|
ASA Group Policies IPSec Settings
Use the IPsec settings to specify tunneling protocols, filters, connection settings, and servers for the ASA group policy for Easy VPN or IPSec VPN. This creates security associations that govern authentication, encryption, encapsulation, and key management.
Navigation Path
Select Easy VPN/IPSec VPN > IPsec from the table of contents in the ASA Group Policies Dialog Box.
Field Reference
Table F-20 ASA Group Policies IPSec Settings
Element
|
Description
|
Enable Re-Authentication on IKE Re-Key
|
Whether the security appliance should prompt the user to enter a username and password during initial Phase 1 IKE negotiation and also prompt for user authentication whenever an IKE rekey occurs, providing additional security. Reauthentication fails if no user is at the other end of the connection.
|
Enable IPsec Compression
|
Whether to enable data compression, which speeds up 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)
|
Whether to enable 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
|
Tunnel 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 specify a tunnel name, the security appliance authenticates users without regard to the assigned group. Group locking is disabled by default.
|
Client Access Rules table
|
The access rules for clients. These rules control which types of clients are denied access, if any. You can have up to 25 rules, and combined they are limited to 255 characters.
Tip  If you define any rule, an implicit deny all rule is added. Thus, if a client matches no permit rule, the client is denied access. If you create rules, ensure that you have permit rules for all allowed clients. You can use * as a wildcard to match partial strings.
The rule with the lowest integer has the highest priority. Therefore, the rule with the lowest integer that matches a client type or version is the rule that applies. If a lower priority rule contradicts, the security appliance ignores it.
• To add a rule, click the Add Row button to open the Add or Edit Client Access Rules Dialog Box.
• To edit a rule, select it and click the Edit Row button.
• To delete a rule, select it and click the Delete button.
|
Add or Edit Client Access Rules Dialog Box
Use the Client Access Rules dialog box to create or edit the priority, action, VPN client type and VPN client version for a client access rule.
Navigation Path
From ASA Group Policies IPSec Settings, click the Add Row button beneath the Client Access Rules table, or select a rule and click the Edit Row button.
Field Reference
Table F-21 Add or Edit Client Access Rules Dialog Box
Element
|
Description
|
Priority
|
The relative priority of the rule.
The rule with the lowest integer has the highest priority. Therefore, the rule with the lowest integer that matches a client type or version is the rule that applies. If a lower priority rule contradicts, the security appliance ignores it. Values are 1-65535.
|
Action
|
Whether this rule permits or denies traffic access to the client.
|
VPN Client Type
VPN Client Version
|
The type or version of VPN client to which this rule applies. Spaces are allowed.
You can use * as a wildcard to match zero or more characters. You can use n/a for clients that do not send their type or version. The strings you enter in these fields must match the strings displayed using the show vpn-sessiondb remote command on the ASA device.
Following are some examples, where priority, permit/deny, type, and version are shown in order:
• 3 Deny * version 3.* is a priority 3 rule that denies all client types with software version 3.x.
• 5 Permit VPN3002 * is a priority 5 rule that allows VPN3002 clients of all software versions.
• 255 Permit * * is a priority 255 rule that allows all types and versions of clients. This is useful if you are only trying to deny specific types of clients without wanting to create permit rules for all the other types.
|
ASA Group Policies SSL VPN Clientless Settings
Use the Clientless settings to configure the clientless mode of access to the corporate network in an SSL VPN for the ASA group policy object.
When a user connects to the SSL VPN in clientless mode, the user logs into the SSL VPN portal page. 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, depending on how you configure the portal.
Navigation Path
Select SSL VPN > Clientless from the table of contents in the ASA Group Policies Dialog Box.
Field Reference
Table F-22 ASA Group Policies SSL VPN Clientless Settings
Element
|
Description
|
Portal Page Websites
|
The name of the SSL VPN bookmarks policy object that includes the web site URLs to display on the portal page. These web sites help users access desired resources. Enter the name of the object or click Select to select it from a list or to create a new object.
|
Allow Users to Enter Websites
|
Whether to allow the remote user to enter web site URLs directly into the browser. If you do not select this option, the user can access only those URLs included on the portal.
|
Enable File Server Browsing
|
Whether to allow the remote user to browse for file shares on the CIFS file servers.
|
Enable File Server Entry
|
Whether to allow the remote user to locate file shares on the CIFS file servers by entering the names of the file shares.
|
Enable Hidden Shares
|
Whether to make hidden CIFS shares visible, and thus accessible, to users.
|
HTTP Proxy
|
The type of access you want to allow to the external HTTP proxy server to which the security appliance forwards HTTP connections. You can enable access, disable access, or select Auto Start, which starts the proxy automatically upon user login.
|
Filter ACL
|
The name of the web type access control list policy object to use to restrict user access to the SSL VPN. Enter the name of the object or click Select to select it from a list or to create a new object.
|
Enable ActiveX Relay
|
Whether to enable ActiveX relay, which allows users to start ActiveX programs from the portal page. This allows users to start Microsoft Office applications from the web browser and upload and download Office documents.
|
UNIX Authentication Group ID
|
The UNIX authentication group ID.
|
UNIX Authentication User ID
|
The UNIX authentication user ID.
|
Smart Tunnel
|
The name of the smart tunnel list policy object assigned to this group. Click Select to select it from a list or to create a new object.
A smart tunnel is a connection between a Winsock 2, TCP-based application and a private site. The connection uses a clientless (browser-based) SSL VPN session with the security appliance as the pathway, and the security appliance as a proxy server. Thus, smart tunnels do not require users to have administrator privileges. For more information, see Configuring SSL VPN Smart Tunnels for ASA Devices, page 8-87.
|
Auto Start Smart Tunnel
|
Whether to start smart tunnel access automatically upon user login. If you do not select this option, the user must start the tunnel manually through the Application Access tools on the portal page.
Auto sign-on supports only applications that use HTTP and HTTPS using the Microsoft WININET library on a Microsoft Windows operating system. For example, Microsoft Internet Explorer uses the WININET dynamic linked library to communicate with web servers.
|
Port Forwarding List
|
The name of the port forwarding list policy object assigned to this group. Port forwarding lists contain the set of applications that users of clientless SSL VPN sessions can access over forwarded TCP ports. Enter the name of the object or click Select to select it from a list or to create a new object.
|
Auto Start Port Forwarding
|
Whether to start port forwarding automatically upon user login.
|
Port Forwarding Applet Name
|
The application name or short description to display on the Port Forwarding Java applet screen on the portal, up to 64 characters. This is the name of the applet users will download to act as a TCP proxy on the client machine for the services configured on the SSL VPN gateway.
|
ASA Group Policies SSL VPN Full Client Settings
Use the Full Client settings to configure the full client mode of access to the corporate network in an SSL VPN for the ASA group policy 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) or AnyConnect, is downloaded to the remote client, so that a tunnel connection is established when the remote user logs in to the SSL VPN gateway.
Tip
To enable full client access, you must configure the Remote Access VPN > SSL VPN > Other Settings policy on the device to identify AnyConnect image packages to install on the device. The images must be on the device so that users can download them. For more information, see Understanding SSL VPN Client Settings, page 10-54 and Add and Edit File Object Dialog Boxes.
Navigation Path
Select SSL VPN > Full Client from the table of contents in the ASA Group Policies Dialog Box.
Field Reference
Table F-23 ASA Group Policies SSL VPN Full Client Settings
Element
|
Description
|
Enable Full Client
|
Whether to enable full client mode.
|
Mode
|
The mode in which to operate the SSL VPN:
• Use Other Access Modes if AnyConnect Client Download Fails—If the full client fails to download to the remote user, allow the user to make clientless or thin client access to the VPN.
• Full Client Only—Prohibit clientless or thin client access. The user must have the full client installed and functional to connect to the VPN.
|
Keep AnyConnect Client on Client System
|
Whether to leave the AnyConnect client installed on the client system after the client disconnects. If you do not leave the client installed, it must be download each time the user connects to the gateway.
|
Enable Compression
|
Whether to enable data compression, which speeds up 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 Keepalive Messages
|
Whether to exchange keepalive messages 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.
If you select this option, 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.
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.
Enter the time interval (in minutes) between the tunnel refresh cycles in the Interval field.
|
Enable Datagram Transport Layer Security
|
Whether to enable Datagram Transport Layer Security (DTLS) connections for the group.
Enabling DTLS allows the AnyConnect client establishing an SSL VPN connection to use two simultaneous tunnels, an SSL tunnel and a DTLS tunnel. Using DTLS avoids latency and bandwidth problems associated with some SSL connections and improves the performance of real-time applications that are sensitive to packet delays.
|
AnyConnect Module
|
The module that the AnyConnect client needs to enable optional features.
• vpngina—Select this module to enable the Start Before Logon (SBL) feature, which is a graphical identification and authentication (GINA) module for the AnyConnect client VPN connection.
• If other options are listed, see the release notes for the Cisco AnyConnect VPN Client for an explanation of the feature.
|
AnyConnect MTU
|
The maximum transmission unit (MTU) size for SSL VPN connections established by the Cisco AnyConnect VPN Client.
|
AnyConnect Profile Name
|
The name of the AnyConnect profile to use for the group. You must configure this name and relate it to a profile in the Remote Access VPN > SSL VPN > Other Settings policy.
|
Prompt User to Choose Client
Time User Has to Choose
Default Location
|
Whether to ask the user to download the client. Enter the number of seconds the user has to make a selection in the Time User Has to Choose field. The default is 120 seconds.
If you do not select this option, the user is immediately taken to the default location. The user is also taken to the default location after the time to choose expires.
• Web Portal—The portal page is loaded in the web browser.
• AnyConnect Client—The AnyConnect client is downloaded.
|
ASA Group Policies SSL VPN Settings
Use the SSL VPN Settings to configure attributes that are required for clientless and port forwarding (thin client) 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.
Navigation Path
Select SSL VPN > Settings from the table of contents in the ASA Group Policies Dialog Box.
Field Reference
Table F-24 ASA Group Policies SSL VPN Settings
Element
|
Description
|
Home Page
|
The URL of the SSL VPN home page. The page is displayed when users log into the VPN. If you do not enter a URL, no home page is displayed.
|
Authentication Failure Message
|
The message to deliver to a remote user who successfully logs into the VPN but has no VPN privileges, and so can do nothing. The default message is:
"Login was successful, but because certain criteria have not been met or due to some specific group policy, you do not have permission to use any of the VPN features. Contact your IT administrator for more information."
|
Minimum Keepalive Object Size (kilobytes)
|
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
|
The name of the single sign on (SSO) server policy object that identifies the server to use for this group, if any. An SSO server allows users to enter their username and password once and be able to access other server in the network without logging into each of them. If configure an SSO server, also configure the auto signon rules table.
Enter the name of the object or click Select to select it from a list or to create a new object. For more information, see Configuring Single Sign-On Server Objects, page 8-77.
|
Enable HTTP Compression
|
Whether to allow an HTTP compressed object to be cached on the security appliance.
|
Auto Signon Rules table
|
If you configure a single sign on server, the auto signon rules table contains the rules that determine which internal servers are provided the user's credentials. Thus, you can provide single sign on for some servers in your network but not others.
Each rule is an allow rule, and indicates the IP address, subnet, or Universal Resource Identifier (URI) that identifies the server, and the type of authentication that will be sent to the server when the user tries to access it (either basic HTML, NTLM, FTP, or all of these). The rules are processed in order, top to bottom, and the first match is applied. Therefore, be sure to order the rules correctly using the up and down arrow buttons.
If the user accesses a server that is not identified in one of these rules, the user must log into the server to gain access.
• To add a rule, click the Add Row button to open the Add or Edit Auto Signon Rules Dialog Box.
• To edit a rule, select it and click the Edit Row button.
• To delete a rule, select it and click the Delete Row button.
|
Portal Page Customization
|
The name of the SSL VPN customization policy object that defines the appearance of the portal web page. The portal page allows the remote user access to all the resources available on the SSL VPN network. If you do not specify an object, the default page appearance is used.
Enter the name of the object or click Select to select it from a list or to create a new object. For more information, see Configuring ASA Portal Appearance Using SSL VPN Customization Objects, page 8-79.
|
User Storage Location
|
The location where personalized user information is stored between clientless SSL VPN sessions. If you do not specify a location, information is not stored between sessions. Stored information is encrypted.
Enter a file system designation in the following format:
protocol://username:password@host:port/path
Where protocol is the protocol of the server, username and password are a valid user account on the server, and host is the name of the server. Also indicate the port number (if you do not use the default for the protocol) and directory path of the location on the server to use. For example:
cifs://newuser:12345678@anyfiler02a/new_share
|
Storage Key
|
The storage key used to protect data stored between sessions. Spaces are not supported.
|
Post Max Size
|
The maximum size allowed for a posted object. The range is 0 through 2147483647 (which is the default). Specify 0 to prevent posting.
|
Upload Max Size
|
The maximum size allowed for a uploaded object. The range is 0 through 2147483647 (which is the default). Specify 0 to prevent uploading.
|
Download Max Size
|
The maximum size allowed for a downloaded object. The range is 0 through 2147483647 (which is the default). Specify 0 to prevent downloads.
|
Add or Edit Auto Signon Rules Dialog Box
Use the Add or Edit Auto Signon Rules 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.
Navigation Path
Open the ASA Group Policies SSL VPN Settings, then click Create, or select an item in the table and click Edit.
Related Topics
•
ASA Group Policies Dialog Box
•
Configuring Single Sign-On Server Objects, page 8-77
Field Reference
Table F-25 Add or Edit Auto Signon Rules Dialog Box
Element
|
Description
|
Allow IP
|
Select this option to configure an IP address or subnet for the rule. Any server within this subnet is supplied the specified login credentials.
• To enter the IP address of a single server, enter the full IP address and use 255.255.255.255 as the subnet mask.
• To specify a subnet, enter the network address and subnet mask, for example, IP address 10.100.10.0 mask 255.255.255.0.
If you want the appliance to send credentials to any internal server the user tries to access, create rules for all of your internal networks. You might be able to do this with a single rule.
|
Allow URI
|
Select this option to configure a Universal Resource Identifier (URI) for the rule. This identifies the internal server based on URI rather than IP address. For example, https://*.example.com/* creates a rule for all web pages on any server in the example.com domain. Use the asterisk as a wildcard to apply to zero or more characters.
|
Authentication Type
|
The type of credentials that the security appliance will pass on to the servers covered by this rule: Basic HTML, NTLM (NT LAN Manager) authentication, FTP, or all of these methods.
The default option is All. Use the default unless you want to limit logins to a certain type.
|
ASA Group Policies DNS/WINS Settings
Use the DNS/WINS settings to define the DNS and WINS servers and the domain name that should be pushed to clients associated with the ASA group policy. These settings apply to Easy VPN, remote access IPSec VPN, and SSL VPN configurations.
Navigation Path
Select DNS/WINS from the table of contents in the ASA Group Policies Dialog Box.
Field Reference
Table F-26 ASA Group Policies DNS/WINS Settings
Element
|
Description
|
Primary DNS Server
|
The IP address of the primary DNS server for the group. Enter the IP address or the name of a network/host object, or click Select to select an object from a list or to create a new object.
|
Secondary DNS Server
|
The IP address of the secondary DNS server for the group. Enter the IP address or the name of a network/host object, or click Select to select an object from a list or to create a new object.
|
Primary WINS Server
|
The IP address of the primary WINS server for the group. Enter the IP address or the name of a network/host object, or click Select to select an object from a list or to create a new object.
|
Secondary WINS Server
|
The IP address of the primary WINS server for the group. Enter the IP address or the name of a network/host object, or click Select to select an object from a list or to create a new object.
|
DHCP Network Scope
|
The scope of the DHCP network for the group. Enter the IP network address or the name of a network/host object, or click Select to select an object from a list or to create a new object.
|
Default Domain
|
The default domain name for the group. The default, blank, is none.
|
ASA Group Policies Split Tunneling Settings
Use the Split Tunneling settings to configure a secure tunnel to the central site and simultaneous clear text tunnels to the Internet. These settings apply to Easy VPN, remote access IPSec VPN, and SSL VPN configurations.
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 specific networks.
Tip
For optimum security, we recommend that you not enable split tunneling.
Navigation Path
Select Split Tunneling from the table of contents in the ASA Group Policies Dialog Box.
Field Reference
Table F-27 ASA Group Policies Split Tunneling Settings
Element
|
Description
|
DNS Names
|
A list of domain names to be resolved through the split tunnel. All other names are resolved using the public DNS server. If you do not enter a list, the list is inherited from the default group policy.
Separate multiple entries with spaces or commas. The entire string can be a maximum of 255 characters.
|
Tunnel Option
|
The policy you want to enable for split tunneling:
• Disabled—(Default) No traffic goes in the clear or to any other destination than the security appliance. Remote users reach networks through the corporate network and do not have access to local networks.
• Tunnel Specified Traffic—Tunnel all traffic from or to the networks permitted in the network ACL. Traffic to all other addresses travels in the clear and is routed by the remote user's Internet service provider.
• Exclude Specified Traffic—Traffic goes in the clear from and to the networks permitted in the network ACL. This 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
|
The name of a standard access control list policy object that identifies the networks that require traffic to travel across the tunnel and those that do not require tunneling. How permit and deny are interpreted depends on your selection for Tunnel Option.
Enter the name of the object, or click Select to select it from a list or to create a new object. If you do not specify an ACL, the network list is inherited from the default group policy.
|
ASA Group Policies Connection Settings
Use the Connection Settings to configure the connection characteristics for the ASA group policy, including access control and session timeouts. These settings are used for Easy VPN, remote access VPN, or SSL VPN sessions.
Navigation Path
Select Connection Settings from the table of contents in the ASA Group Policies Dialog Box.
Field Reference
Table F-28 ASA Group Policies Connection Settings
Element
|
Description
|
Filter ACL
|
The name of the extended access control list (ACL) policy object to use to restrict user access to the VPN. Enter the name of the object or click Select to select it from a list or to create a new object.
|
Banner Text
|
The banner, or welcome text, to display on remote clients when they connect to the VPN. You can enter up to 500 characters.
|
Access hours
|
The name of a time range policy object that specifies the times that users are allowed to access the VPN. If you do not specify a time range, users can access the VPN at all times. Specify a time range if you want to limit access to the network to certain hours, such as the typical work days and work hours for your organization.
Enter the name of the object or click Select to select it from a list or to create a new object. For more information, see Add or Edit Time Range Dialog Box.
|
Max Simultaneous Logins
|
The number of simultaneous logins a single user is allowed. Values are 0-2147483647. The default is 3. Specify 0 to disable logins and prevent user access.
|
Max Connection Time
|
The maximum amount of time a user is allowed to be connected to the VPN. Select one of the following:
• Specified Connection time—Use the maximum time value that you enter. Values are 1-35791394 minutes. After the time is exceeded, the security appliance closes the connection.
• Unlimited Connection time—The security appliance does not close connections based on connection time.
|
Idle Timeout
|
The amount of time a user is allowed to be connected to the VPN while the connection is idle, that is, there is no communication activity. Select one of the following:
• Specified Timeout—Use the time out value you enter. Values are 1-35791394 minutes. When the idle time is exceeded, the security appliance closes the connection. The default is 30 minutes.
• Unlimited Timeout—The security appliance does not close idle connections.
|
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 8-6
•
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.
This policy object uses the Secure Desktop Manager application to configure the settings. For an example of configuring settings, see Cisco Secure Desktop on IOS Configuration Example Using SDM at http://www.cisco.com/en/US/products/ps6496/products_configuration_example09186a008072aa7b.shtml. The first part of the configuration example explains setting up SDM, which you can ignore. Instead, look for the sections that describe setting up Windows locations midway through the example. The screen shots will help you identify when you are looking at CSD configuration.
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 8-73
•
Policy Object Manager Window
Field Reference
Table F-30 Add or Edit Secure Desktop Configuration 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 Creating Policy Objects, page 8-4.
|
Description
|
An optional description of the object (up to 1024 characters).
|
Windows Location Settings
|
Windows Locations
|
The names of the locations that you want to configure for Windows clients connecting from specific locations, such as Work, Home, or Insecure.
When you create a location, an item for the location is added to the table of contents, where you can select the settings folders related to the location and configure its properties. The settings include a definition of how to determine if a client is connecting from that particular location.
For each location you want to configure, enter its name in the Location to Add field and click Add to move it to the Locations list.
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. You can create a default location, such as Insecure, as the final location and configure the strictest security for it. For more information, see Creating Cisco Secure Desktop Configuration Objects, page 8-73.
|
Close all open browser windows after installation
|
Whether to close all the open browser windows after installing the Secure Desktop application.
|
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. You cannot configure locations for these clients.
|
Mac and Linux Cache Cleaner
|
Launch Cleanup Upon Global Timeout
|
Whether to set a global timeout after which CSD launches the cache cleaner. Select a timeout (the default is 30 minutes), and select whether to allow the user to reset the timeout value.
|
Launch Cleanup Upon Exiting of Browser
|
Whether to start the cache cleaner when the user closes all web browser windows.
|
Enable Canceling of Cleaning
|
Whether to allow the remote user to cancel the cleaning of the cache.
|
Secure Delete
|
The number of passes for CSD to perform a secure 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
|
Whether to allow web browsing (but not other remote access features) if the cache cleaner installation fails.
|
VPN Feature Policy
|
Whether to allow web browsing, remote server file access, and port forwarding for Macintosh and Linux clients. 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 8-6.
|
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) when authenticating user access to the network and network services. When negotiating tunnel parameters for establishing IPsec tunnels in an Easy VPN configuration, Xauth identifies the user who requests the IPsec connection. If the VPN server is configured for Xauth, the client waits for a "username/password" challenge after the IKE SA has been established. When the end user responds to the challenge, the response is forwarded to the IPsec peers for an additional level of authentication. You can save the Xauth credentials (username and password) on the device itself so you do not need to enter them manually each time the Easy VPN tunnel is established.
Navigation Path
Select Tools > Policy Object Manager, then select Credentials 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 Credential Objects, page 8-30
•
Policy Object Manager Window
•
Easy VPN and IKE Extended Authentication (Xauth)
Field Reference
Table F-31 Credentials 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 Creating Policy Objects, page 8-4.
|
Description
|
An optional description of the object (up to 1024 characters).
|
Username
|
The name that will be used to identify the user during Xauth authentication.
|
Password
Confirm
|
The password for the user, entered in both fields. The password must be alphanumeric and a maximum of 128 characters. Spaces are not allowed.
|
Category
|
The category assigned to the object. Categories help you organize and identify rules and objects. See Using Category Objects, page 8-6.
|
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 Policy Object to Be Overridden, page 8-10 and Understanding Policy Object Overrides for Individual Devices, page 8-9.
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. File objects represent files that are used in device configurations, typically for remote access VPN policies and policy objects. Such files include Anyconnect client profile and image files, image (graphic) files, plug-in jar files, and Cisco Secure Desktop package files.
Tip
Before you can add a file to a file object, you must copy the file to the Security Manager server. You cannot select files from a network server or your workstation. Do not copy the file directly to the file repository.
When you create a file object, Security Manager makes a copy of the file in its storage system. These files are backed up whenever you create a backup of the Security Manager database, and they are restored if you restore the database. When you deploy configurations that specify a file object, the associated file is download to the device in the appropriate directory.
After you create a file object, you typically should not edit it. If you need to replace the file, edit the file object to select the new file, or create a new file object. If the file is editable, you can edit the file object to identify the file's location in the file repository, and use the desired editor to open and edit the file outside of Security Manager. The file repository is the CSCOpx\MDC\FileRepository folder in the installation directory (typically, C:\Program Files). The files are organized in subfolders named for the file type.
When you delete a file object, the associated file is not deleted from the file repository.
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
•
Creating File Objects, page 8-31
Field Reference
Table F-32 Add and Edit File Object 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 Creating Policy Objects, page 8-4.
If you do not enter a name, the name of the file is used for the object name.
|
Description
|
An optional description of the object.
|
File Type
|
The type of file. If you create the object while configuring a policy, the correct file type is pre-selected. Options are:
• Image—For graphic files.
• Cisco Secure Desktop Package
• Plug-In—For browser plug-in files.
• AnyConnect Profile
• AnyConnect Image
|
File
|
The name and full path of the file. The file must be on the Security Manager server. Click Browse to select the file.
For file objects that you are editing, the path indicates the location in the Security Manager file repository.
Tip  Security Manager comes with a number of files that you can use with SSL VPN configurations. If you are creating a file object for Anyconnect images or profiles, Cisco Secure Desktop clients, or plug-ins, you can find some files in the C:\Program Files\CSCOpx\objects\sslvpn folder.
|
File Name on Device
|
The file name you want to use when the file is downloaded to the device when you deploy policies. The default is to use the same file name as the original file.
If the object was created by discovering policies from the device, this field uses the original name of the file as it existed on the device. This might not be the same name as it exists on the Security Manager server if the original name duplicated existing file names on the server.
|
Category
|
The category assigned to the object. Categories help you organize and identify rules and objects. See Using Category Objects, page 8-6.
|
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 18-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 18-26
•
Editing FlexConfig Policies, page 18-28
•
Chapter 18, "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 Creating Policy Objects, page 8-4.
|
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 18-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 18-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 18-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 8-91.
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 18-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 18-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.
|
Add or Edit IKE Proposal Dialog Box
Use the IKE Proposal dialog box to create, copy, and edit an IKE proposal object.
Internet Key Exchange (IKE) proposal objects contain the parameters required for IKE proposals when defining remote access and site-to-site VPN policies. IKE is a key management protocol that facilitates the management of IPsec-based communications. It is used to authenticate IPsec peers, negotiate and distribute IPsec encryption keys, and automatically establish IPsec security associations (SAs).
The IKE negotiation comprises two phases. Phase 1 negotiates a security association between two IKE peers, which enables the peers to communicate securely in Phase 2. During Phase 2 negotiation, IKE establishes security associations (SAs) for other applications, such as IPsec. Both phases use proposals when they negotiate a connection. For more information about IKE proposals, see the following topics:
•
Understanding IKE, page 9-45
•
Deciding Which Encryption Algorithm to Use, page 9-45
•
Deciding Which Hash Algorithm to Use, page 9-46
•
Deciding Which Diffie-Hellman Group to Use, page 9-46
•
Deciding Which Authentication Method to Use, page 9-47
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 8-32
•
Policy Object Manager Window
•
Add or Edit IPSec Transform Set Dialog Box
•
Creating Policy Objects, page 8-4
Field Reference
Table F-36 IKE Proposal Dialog Box
Element
|
Description
|
Name
|
The name of the policy object. A maximum of 128 characters is allowed.
|
Description
|
A description of the policy object. A maximum of 1024 characters is allowed.
|
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 security association (SA). If the remote IPsec peer does not support the parameters selected in your first priority policy, the device tries to use the parameters defined in the policy with the next lowest priority number.
Valid values range from 1 to 10000. The lower the number, the higher the priority. 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. It is less secure than AES. 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 without transmitting it to each other. A larger modulus provides higher security but requires more processing time. The two peers must have a matching modulus group. Options are:
• 1—Diffie-Hellman Group 1 (768-bit modulus).
• 2—Diffie-Hellman Group 2 (1024-bit modulus).
• 5—Diffie-Hellman Group 5 (1536-bit modulus, considered good protection for 128-bit keys, but group 14 is better).
• 7—Diffie-Hellman Group 7 (163-bit elliptical curve field size).
• 14—Diffie-Hellman Group 14 (2048-bit modulus, considered good protection for 128-bit keys).
• 15—Diffie-Hellman Group 15 (3072-bit modulus, considered good protection for 192-bit keys).
• 16—Diffie-Hellman Group 16 (4096-bit modulus, considered good protection for 256-bit keys).
|
Lifetime
|
The lifetime of the security association (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. However, with longer lifetimes, future IPsec security associations can be set up more quickly than with shorter lifetimes.
You can specify a value from 60 to 86400 seconds.
|
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 8-6.
|
Interface Role Dialog Box
Use the Interface Role dialog box to create, copy, or edit an interface role object. Interface Role objects have the following uses:
•
Specifying multiple interfaces— Interface role objects allow you to apply policies to specific interfaces on multiple devices without having to manually define the names of each interface.
•
Zones—You use interface role objects to define the zones in a zone-based firewall rules policy.
Navigation Path
Select Tools > Policy Object Manager, then select Interface Roles 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 Policy Objects, page 8-4
•
Creating Interface Role Objects, page 8-34
•
Exceptional Cases When Using Interface Roles, page 8-35
•
Specifying Interfaces During Policy Definition, page 8-35
•
Understanding Interface Role Objects, page 8-33
•
Understanding the Zone-based Firewall Rules, page 11-62
•
Policy Object Manager Window
Field Reference
Table F-37 Interface Role Dialog Box
Element
|
Description
|
Name
|
The name of the policy object. A maximum of 128 characters is allowed.
|
Description
|
A description of the policy object. A maximum of 1024 characters is allowed.
|
Interface Name Patterns
|
The names to include in this interface role. The names are the complete or partial names of interfaces, subinterfaces, and other virtual interfaces. Separate multiple name patterns with commas.
You can use these wildcards to create name patterns that apply to multiple interfaces:
• Use a period (.) as a wildcard for a single character.
To use a period as part of the pattern itself (for example, when defining subinterfaces), enter a backslash (\) before the period.
• Use an asterisk (*) as a wildcard for one or more characters at the end of the interface pattern. For example, FastEthernet* would include interfaces named FastEthernet0 and FastEthernet1.
|
Category
|
The category assigned to the object. Categories help you organize and identify rules and objects. See Using Category Objects, page 8-6.
|
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 Policy Object to Be Overridden, page 8-10 and Understanding Policy Object Overrides for Individual Devices, page 8-9.
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.
|
Interface Name Conflict Dialog Box
When defining a policy requiring an interface, you might enter a name that corresponds to both an interface role and an actual interface on the device. When you save or update the policy, the Interface Name Conflict dialog box opens automatically so that you can select whether you want to specify the interface or the interface role. The dialog box lists only those names for which there are conflicts.
For more information about the exact circumstances that lead to this conflict, see Exceptional Cases When Using Interface Roles, page 8-35.
Related Topics
•
Understanding Interface Role Objects, page 8-33
•
Basic Interface Settings on Cisco IOS Routers, page 13-13
Add or Edit IPSec Transform Set Dialog Box
Use the Add or Edit IPSec Transform Set dialog box to create, copy and edit IPSec transform set objects.
You can create IPSec transform set objects for use in IPSec proposals when defining IPSec-protected traffic in site-to-site and remote access VPNs. When you create an IPSec transform set object, you select the mode in which IPSec should operate, as well as define the required encryption and authentication types. Additionally, you can select whether to include compression in the transform set. During IPSec security association negotiation, the peers agree to use a particular transform set when protecting a particular data flow.
Two different security protocols are included within the IPSec standard:
•
Encapsulating Security Protocol (ESP)—Provides authentication, encryption, and anti-replay services. ESP is IP protocol type 50.
•
Authentication Header (AH)—Provides authentication and anti-replay services. AH does not provide encryption and has largely been superseded by ESP. AH is IP protocol type 51.
Note
We recommend using both encryption and authentication on IPSec tunnels.
Navigation Path
Select Tools > Policy Object Manager, then select IPSec Transform Sets 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
•
About Transform Sets, page 9-49
•
Creating IPSec Transform Set Objects, page 8-36
•
Policy Object Manager Window
•
Add or Edit IKE Proposal Dialog Box
•
Creating Policy Objects, page 8-4
Field Reference
Table F-38 IPSec Transform Set Dialog Box
Element
|
Description
|
Name
|
The name of the policy object. A maximum of 128 characters is allowed.
|
Description
|
A description of the policy object. A maximum of 1024 characters is allowed.
|
Mode
|
The mode in which the IPSec tunnel operates:
• Tunnel—Tunnel mode encapsulates the entire IP packet. The IPSec header is added between the original IP header and a new IP header. This is the default.
Use tunnel mode when the firewall is protecting traffic to and from hosts positioned behind the firewall. Tunnel mode is the normal way regular IPSec is implemented between two firewalls (or other security gateways) that are connected over an untrusted network, such as the Internet.
• Transport—Transport mode encapsulates only the upper-layer protocols of an IP packet. The IPSec header is inserted between the IP header and the upper-layer protocol header (such as TCP).
Transport mode requires that both the source and destination hosts support IPSec, and can only be used when the destination peer of the tunnel is the final destination of the IP packet. Transport mode is generally used only when protecting a Layer 2 or Layer 3 tunneling protocol such as GRE, L2TP, and DLSW.
|
ESP Encryption
|
The Encapsulating Security Protocol (ESP) encryption algorithm that the transform set should use:
• (Blank)—Do not use ESP encryption.
• 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.
• 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.
• ESP-Null—A null encryption algorithm. Transform sets defined with ESP-Null provide authentication without encryption; this is typically used for testing purposes only.
|
ESP Hash Algorithm
AH Hash Algorithm
|
The ESP or AH hash algorithm to use in the transform set for authentication. The default is to use SHA for ESP authentication and to not use AH authentication.
• None—Does not perform ESP or AH authentication.
• SHA (Secure Hash Algorithm)—Produces a 160-bit digest. SHA is more resistant to brute-force attacks than MD5, but requires more processing time.
• MD5 (Message Digest 5)—Produces a 128-bit digest. MD5 uses less processing time than SHA, but is less secure.
Note We recommend using both encryption and authentication on IPSec tunnels.
|
Compression
(IOS devices only.)
|
Whether to compress the data in the IPSec tunnel using the Lempel-Ziv-Stac (LZS) algorithm.
|
Category
|
The category assigned to the object. Categories help you organize and identify rules and objects. See Using Category Objects, page 8-6.
|
Add and Edit LDAP Attribute Map Dialog Boxes
Use the Add and Edit LDAP (Lightweight Directory Access Protocol) Attribute Map dialog boxes to populate the attribute map with name mappings that translate Cisco LDAP attribute names to custom, user-defined attribute names.
If you are introducing a security appliance to an existing LDAP directory, your existing custom LDAP attribute names and values are probably different from the Cisco attribute names and values. Rather than renaming your existing attributes, you can create LDAP attribute maps that map your custom attribute names and values to Cisco attribute names and values. By using simple string substitution, the security appliance then presents you with only your own custom names and values. You can then bind these attribute maps to LDAP servers or remove them as needed. You can also delete entire attribute maps or remove individual name and value entries.
For more information regarding LDAP support on ASA, PIX, and FWSM devices, see Additional AAA Support on ASA, PIX, and FWSM Devices, page 8-17.
Navigation Path
Select Tools > Policy Object Manager, then select LDAP Attribute Map from the Object Type selector. Right-click inside the table and select New Object, or right-click a row and select Edit Object.
Related Topics
•
Creating LDAP Attribute Map Objects, page 8-37
•
Creating AAA Server Objects, page 8-20
•
AAA Server Dialog Box—LDAP Settings
Field Reference
Table F-39 Add and Edit LDAP Attribute Map 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 Creating Policy Objects, page 8-4.
|
Description
|
An optional description of the object.
|
Attribute Map table
|
The table shows the mapped values. Each entry shows the customer map name, Cisco map name, and the attribute mapping of customer name to Cisco name.
• To add a mapping, click the Add Row button to open the Add and Edit LDAP Attribute Map Value Dialog Boxes.
• To edit a mapping, select it and click the Edit Row button.
• To delete a mapping, select it and click the Delete Row button.
|
Category
|
The category assigned to the object. Categories help you organize and identify rules and objects. See Using Category Objects, page 8-6.
|
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 Policy Object to Be Overridden, page 8-10 and Understanding Policy Object Overrides for Individual Devices, page 8-9.
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 LDAP Attribute Map Value Dialog Boxes
Use the Add and Edit LDAP Attribute Map Value dialog boxes to populate the attribute map with value mappings that apply user-defined attribute values to the custom attribute name and to the matching Cisco attribute name and value.
Navigation Path
From the Add and Edit LDAP Attribute Map Dialog Boxes, click the Add Row button to add a new mapping, or select a row and click the Edit Row button.
Field Reference
Table F-40 Add and Edit LDAP Attribute Map Value Dialog Boxes
Element
|
Description
|
Customer Map Name
|
The name of your attribute map that relates to the Cisco map.
|
Cisco Map Name
|
The Cisco attribute map name you want to map to the customer map name.
|
Customer to Cisco Map Value table
|
The mappings of customer names to Cisco names.
• To add a mapping, click the Add Row button to open the Add and Edit Map Value Dialog Boxes.
• To edit a mapping, select it and click the Edit Row button.
• To delete a mapping, select it and click the Delete Row button.
|
Add and Edit Map Value Dialog Boxes
Use the Add and Edit Map Value dialog boxes to map a customer LDAP attribute value to a Cisco map value. Enter the value from your LDAP map that you want to equate with a Cisco value.
Navigation Path
From the Add and Edit LDAP Attribute Map Value Dialog Boxes, click the Add Row button to add a new mapping, or select a row and click the Edit Row button.
Add or Edit Class Maps Dialog Boxes
Use the Add and Edit Class Map dialog boxes to define class maps to be used in policy maps of the same type. The name of the dialog box indicates the type of map you are creating.
A class map defines application traffic based on criteria specific to the application. You then select the class map in the corresponding policy map and configure the action to take for the selected traffic. Thus, each class map must contain traffic that you want to handle in the same way (for example, to allow it or to drop it).
You can create class maps for the following purposes:
•
Devices running ASA/PIX 7.2 or higher—For inspection using Inspection rules. You can create classes for the inspection of the following types of traffic: DNS, FTP, H.323, HTTP, IM, and SIP.
You can also define class criteria in the related policy map. However, creating class maps allows you to reuse the map in multiple policy maps.
The following topics describe the available match criteria:
–
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
•
Devices running Cisco IOS Software 12.4(6)T and higher—For inspection or web filtering using Zone-Based Firewall rules.
–
For 12.4(6)T and higher, you can create classes for the inspection of the following types of traffic: H.323, HTTP, IMAP, POP3, SIP, SMTP, and Sun RPC. You can create classes for web filtering using the following class types: Local, N2H2 (SmartFilter), and WebSense. See the following topics for information on the match criteria:
–
H.323 (IOS) Class Maps Add or Edit Match Criterion Dialog Boxes
–
HTTP (IOS) Class Add or Edit Match Criterion Dialog Boxes
–
IMAP and POP3 Class Maps Add or Edit Match Criterion Dialog Boxes
–
SIP (IOS) Class Add or Edit Match Criterion Dialog Boxes
–
SMTP Class Maps Add or Edit Match Criterion Dialog Boxes
–
Sun RPC Class Maps Add or Edit Match Criterion Dialog Boxes
–
Local Web Filter Class Add or Edit Match Criterion Dialog Boxes
–
N2H2 and Websense Class Add or Edit Match Criterion Dialog Boxes
–
For 12.4(9)T and higher, you can create classes for the inspection of the following types of traffic: AOL, eDonkey, FastTrack, Gnutella, ICQ, Kazaa2, MSN Messenger, Windows Messenger, and Yahoo Messenger. See the following topics for information on the match criteria:
–
Zone-Based Firewall IM Application Class Maps Add or Edit Match Condition Dialog Boxes
–
Zone-Based Firewall P2P Application Class Maps Add or Edit Match Condition Dialog Boxes
–
For 12.4(20)T and higher, you can create classes for web filtering using the Trend policy object. Match criteria for Trend Content Filter class maps is described in the table below.
Navigation Path
Select Tools > Policy Object Manager, then select any item in the folders in the 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 Map Objects, page 8-38
•
Creating Class Map Objects, page 8-41
•
Configuring Maps for Inspection in Zone-Based Firewall Rules Policies, page 8-57
•
Configuring Maps for Content Filtering in Zone-Based Firewall Rules Policies, page 8-59
•
Understanding Inspection Rules, page 11-33
•
Understanding the Zone-based Firewall Rules, page 11-62
Field Reference
Table F-41 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 table
Match Type
(Except for Trend Content Filter class maps.)
|
The Match 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.
The name of the table indicates whether every one of the criteria must be met for the traffic to match the class (Match All), or whether matching any of the listed criteria is sufficient (Match Any). For the HTTP (IOS) and SMTP classes, you can choose whether to match all or any. When using a Match All table, if you add more than one criteria, ensure that you are not defining a set of characteristics that no traffic can match.
Tip  Match All works for devices running Cisco IOS Software version 12.4(20)T or higher only.
• To add a criterion, click the Add button and fill in the Match Criterion dialog box. For more information, see the topics referenced above.
• To edit a criterion, select it and click the Edit button.
• To delete a criterion, select it and click the Delete button.
|
Trend Content Filter Match Criteria
|
The match criteria for Trend Content Filter class maps differs from that of all other class maps. Instead of adding items to a table, you simply select the items you want from a list. Select the Enable checkbox for any of the Trend-Micro classifications on the following tabs. Traffic matches the class if it matches any of your selections.
• Productivity Categories—Matches the traffic to the category to which the URL belongs. For example, you can target traffic associated with gambling or pornography.
• Security Ratings—Matches the traffic to the security rating assigned to it by Trend-Micro. For example, you can target adware, which is traffic associated with advertising.
See the Trend-Micro documentation for specific information on these categories or security classifications.
|
Category
|
The category assigned to the object. Categories help you organize and identify rules and objects. See Using Category Objects, page 8-6.
|
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 Policy Object to Be Overridden, page 8-10 and Understanding Policy Object Overrides for Individual Devices, page 8-9.
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.
|
Zone-Based Firewall IM Application Class Maps Add or Edit Match Condition Dialog Boxes
Use the Add or Edit Match Criterion dialog boxes for the various instant messenger (IM) application classes used with zone-based firewall policies to define a match criterion and value for the class map.
You can match the following types of services:
•
Any—Any type of traffic from the application except text chat traffic.
•
Text-chat—Text chat traffic.
Navigation Path
From the Add or Edit Class Maps Dialog Boxes for AOL, ICQ, MSN Messenger, Windows Messenger, or Yahoo Messenger classes, right-click inside the table and select Add Row or right-click a row and select Edit Row.
Related Topics
•
Understanding Map Objects, page 8-38
•
Creating Class Map Objects, page 8-41
•
Configuring Maps for Inspection in Zone-Based Firewall Rules Policies, page 8-57
•
Understanding the Zone-based Firewall Rules, page 11-62
Zone-Based Firewall P2P Application Class Maps Add or Edit Match Condition Dialog Boxes
Use the Add or Edit Match Criterion dialog boxes for the various person-to-person (P2P) application classes used with zone-based firewall policies to define a match criterion and value for the class map.
Navigation Path
From the Add or Edit Class Maps Dialog Boxes for eDonkey, FastTrack, Gnutella, or Kazaa2 classes, right-click inside the table and select Add Row or right-click a row and select Edit Row.
Related Topics
•
Understanding Map Objects, page 8-38
•
Creating Class Map Objects, page 8-41
•
Configuring Maps for Inspection in Zone-Based Firewall Rules Policies, page 8-57
•
Understanding the Zone-based Firewall Rules, page 11-62
Field Reference
Table F-42 Zone-Based Firewall P2P Application Class Maps Add or Edit Match Condition Dialog Boxes
Element
|
Description
|
Criterion
|
Specifies which criterion of traffic to match:
• File Transfer—Matches file transfer traffic.
• Search Filename—Matches the names of files for which the user is searching. You can use this criterion to block users from searching for particular files using eDonkey.
• Text Chat—Matches eDonkey text chat traffic.
|
Type
|
Specifies that the map includes traffic that matches the criterion.
|
File Name
|
The name of the file associated with the traffic. You can use regular expressions to specify a name pattern. For information on the metacharacters you can use to build regular expressions, see Metacharacters Used to Build Regular Expressions, page 8-63.
Tip  eDonkey does not require a file name.
|
H.323 (IOS) Class Maps Add or Edit Match Criterion Dialog Boxes
Use the Add or Edit Match Criterion dialog boxes for the H.323 (IOS) class used with zone-based firewall policies to define a match criterion and value for the class map. You can match traffic based on the H.323 protocol message type. Select the message that you want to match.
Navigation Path
From the Add or Edit Class Maps Dialog Boxes for the H.323 (IOS) class, right-click inside the table and select Add Row or right-click a row and select Edit Row.
Related Topics
•
Understanding Map Objects, page 8-38
•
Creating Class Map Objects, page 8-41
•
Configuring Maps for Inspection in Zone-Based Firewall Rules Policies, page 8-57
•
Understanding the Zone-based Firewall Rules, page 11-62
HTTP (IOS) Class Add or Edit Match Criterion Dialog Boxes
Use the Add or Edit Match Criterion dialog boxes for the HTTP (IOS) class used with zone-based firewall policies to define a match criterion and value for the class map.
The fields on this dialog box change based on the criterion you select. You can use the following criteria:
•
Request/Response Body Length, Request Body Length, Response Body Length—Specifies that the body length of the request, response, or both, is less than or greater than the specified number. This allows you to set a minimum or maximum message length.
•
Request/Response Body, Request Body, Response Body—Applies a regular expression to match the body of the request, response, or both.
•
Request/Response Header, Request Header, Response Header—You can match a regular expression against the header, test for repeated fields, check the content type, or check the total length or number of records in the header.
•
Request/Response Protocol Violation—Matches non-compliant HTTP traffic.
•
Request Argument, Request URI—Matches the length or content (with a regular expression) of the argument (parameters) or uniform resource identifier (URI) in a request message.
•
Request Port Misuse—Matches the misuse of ports by certain types of applications.
•
Response Body Java Applet—Matches Java applets in an HTTP connection.
•
Response Header Status Line—Applies a regular expression to match the content of the status line in the header.
Navigation Path
From the Add or Edit Class Maps Dialog Boxes for the HTTP (IOS) class, right-click inside the table and select Add Row or right-click a row and select Edit Row.
Related Topics
•
Understanding Map Objects, page 8-38
•
Creating Class Map Objects, page 8-41
•
Configuring Maps for Inspection in Zone-Based Firewall Rules Policies, page 8-57
•
Configuring Maps for Content Filtering in Zone-Based Firewall Rules Policies, page 8-59
•
Understanding the Zone-based Firewall Rules, page 11-62
Field Reference
Table F-43 HTTP (IOS) Class Add or Edit Match Criterion Dialog Boxes
Element
|
Description
|
Criterion
|
Specifies which criterion of HTTP traffic to match. The criteria are described above.
|
Type
|
Specifies that the map includes traffic that matches the criterion.
|
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.
|
Less Than Length
|
The minimum length in bytes of the evaluated field. The criterion matches if the length is less than the specified number.
|
Greater Than Length
|
The maximum length in bytes of the evaluated field. The criterion matches if the length is greater than the specified number.
|
Header Option
|
The type of header record. If you do not select a record type, the count or expression is applied to all records in the header. If you select a record type, those selections are applied only to the records of the selected type. If you select content type or transfer encoding, you can make additional selections related to those types.
|
Request Method
|
The request method you want to match.
|
Value (Content Type)
|
If you select content-type in the Header Option field, you can select these types:
• Mismatch—Verifies the content-type of the response message against the accept field value of the request message.
• Unknown—The content type is not known. Select Unknown when you want to evaluate the item against all known MIME types.
• Violation—The content-type definition and the content type of the actual body do not match.
|
Encoding Type
|
If you select transfer encoding in the Header Option field, you can select these types:
• All—All of the transfer encoding types.
• Chunked—The message body is transferred as a series of chunks; each chunk contains its own size indicator.
• Compress—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.
|
Greater Than Count
|
The maximum number of records allowed in the header. If you select a specific header option, the count applies to those types of records. If you do not select a specific header option, the count applies to the total number of records in the header without regard to type.
|
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.
|
Port Misuse
|
The type of request port misuse you want to match. Your options are:
• Any—Any of the listed types of misuse.
• IM—Instant messaging protocol applications subject to inspection.
• P2P—Peer-to-peer protocol applications subject to inspection.
• Tunneling—Tunneling applications subject to inspection: HTTPPort/HTTPHost.
|
IMAP and POP3 Class Maps Add or Edit Match Criterion Dialog Boxes
Use the Add or Edit Match Criterion dialog boxes for the Internet Message Access Protocol (IMAP) and Post Office Protocol 3 (POP3) classes used with zone-based firewall policies to define a match criterion and value for the class map.
You can select the following criteria to identify matching traffic:
•
Invalid Command—Matches commands that are not valid on a POP3 server or IMAP connection.
•
Login Clear Text—Matches non-secure logins, where the password is being provided in clear text.
Navigation Path
From the Add or Edit Class Maps Dialog Boxes for the IMAP or POP3 classes, right-click inside the table and select Add Row or right-click a row and select Edit Row.
Related Topics
•
Understanding Map Objects, page 8-38
•
Creating Class Map Objects, page 8-41
•
Configuring Maps for Inspection in Zone-Based Firewall Rules Policies, page 8-57
•
Understanding the Zone-based Firewall Rules, page 11-62
SIP (IOS) Class Add or Edit Match Criterion Dialog Boxes
Use the Add or Edit Match Criterion dialog boxes for the SIP (IOS) class used with zone-based firewall policies to define a match criterion and value for the class map.
The fields on this dialog box change based on the criterion you select.
Navigation Path
From the Add or Edit Class Maps Dialog Boxes for the SIP (IOS) class, right-click inside the table and select Add Row or right-click a row and select Edit Row.
Related Topics
•
Understanding Map Objects, page 8-38
•
Creating Class Map Objects, page 8-41
•
Configuring Maps for Inspection in Zone-Based Firewall Rules Policies, page 8-57
•
Understanding the Zone-based Firewall Rules, page 11-62
Field Reference
Table F-44 SIP (IOS) Class Add or Edit Match Criterion Dialog Boxes
Element
|
Description
|
Criterion
|
Specifies which criterion of traffic to match. You can select from the following:
• Protocol Violation—Matches traffic that violates the protocol.
• Request/Response Header Options—Matches a regular expression against the selected request or response header field.
• Request Options—Matches the request method or matches a regular expression against the selected request header field.
• Response Options—Matches a regular expression against the selected response header field or status message.
|
Type
|
Specifies that the map includes traffic that matches the criterion.
|
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.
|
Header
|
The type of header in the request or response message. The regular expression is matched against the content of headers of the selected type.
|
Method
|
The request method you want to inspect:
• ack—Acknowledges that the previous message is valid and accepted.
• bye—Signifies the intention to terminate a call.
• cancel—Terminates any pending request.
• info—Communicates mid-session signaling information along the signaling path for the call.
• invite—Sets up a call.
• message—Sends an instant message.
• notify—Informs subscribers of state changes.
• options—Queries the capabilities of another user agent or a proxy server.
• prack—Provides reliable transfer of provisional response messages.
• refer—Indicates that the recipient should contact a third party using the contact information provided in the request.
• register—Includes a contact address to which SIP requests for the address-of-record should be forwarded.
• subscribe—Requests notification of an event or set of events at a later time.
• update—Permits a client to update parameters of a session but has no impact on the state of a dialog.
|
Status
|
The regular expression is matched against the status line in the response.
|
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.
|
SMTP Class Maps Add or Edit Match Criterion Dialog Boxes
Use the Add or Edit Match Criterion dialog boxes for the SMTP classes used with zone-based firewall policies to define a match criterion and value for the class map.
Tip
Only the Data Length criterion is available for routers running Cisco IOS Software lower than 12.4(20)T.
The fields on this dialog box change based on the criterion you select. You can use the following criteria:
•
Data Length—Specifies that the data length of the traffic is greater than the specified number. You can match the data length of the traffic to determine if the data transferred in an SMTP connection exceeds the specified length in bytes. By default, inspection keeps data length below 20.
•
Body Regular Expression—Applies a regular expression to match the content types and content encoding types for text and HTML in the body of an e-mail message. Only text or HTML that uses 7-bit or 8-bit encoding is checked. The regular expression cannot be scanned in messages that use another encoding type (such as base64 or zip files).
•
Command Line Length—Specifies that the length of the ESMTP command line not be greater than the specified number. Use this to thwart Denial of Service (DoS) attacks.
•
Command Verb—Limits inspection to the selected SMTP or ESMTP command. If you configure inspection for SMTP, all commands are inspected unless you limit them.
•
Header Length—Specifies that the length of the SMTP header is greater than the specified number. Use this to thwart DoS attacks by limiting the possible size of the header.
•
Header Regular Expression—Applies a regular expression to match the content of the header of an e-mail message. For example, you can use this to test for particular patterns in the subject, from, or to fields.
•
Mime Content-Type Regular Expression—Applies a regular expression to match the Multipurpose Internet Message Exchange (MIME) content type of an e-mail attachment. Use this to prevent the transmission of undesired types of attachments.
•
Mime Encoding—Specifies the MIME encoding type for e-mail attachments that you want to inspect. You can use this to identify unknown or non-standard encodings to restrict their transmission.
•
Recipient Address—Applies a regular expression to match the recipient of an e-mail message in the SMTP RCPT command. Use this to search for a non-existent recipient, which might help you identify the source of spam.
•
Recipient Count—Specifies that the number of recipients for an e-mail message cannot be greater than the specified number. Use this to prevent spammers from sending e-mails to a large number of users.
•
Recipient Invalid Count—Specifies that the number of invalid recipients for an e-mail message cannot be greater than the specified number. Use this prevent spammers from sending e-mails to a large number common names, where they are fishing for real addresses. SMTP typically replies with a "no such address" message when an address is invalid; by putting a limit on the number of invalid addresses, you can prevent these replies to spammers.
•
Reply EHLO—Specifies the service extension parameter in an EHLO server reply. Use this to prevent a client from using a particular service extension.
•
Sender Address—Applies a regular expression to match the sender of an e-mail message. Use this to block specific senders, such as known spammers, from sending e-mail messages through the device.
Navigation Path
From the Add or Edit Class Maps Dialog Boxes for SMTP classes, right-click inside the table and select Add Row or right-click a row and select Edit Row.
Related Topics
•
Understanding Map Objects, page 8-38
•
Creating Class Map Objects, page 8-41
•
Configuring Maps for Inspection in Zone-Based Firewall Rules Policies, page 8-57
•
Understanding the Zone-based Firewall Rules, page 11-62
Field Reference
Table F-45 SMTP Class Add or Edit Match Criterion Dialog Boxes
Element
|
Description
|
Criterion
|
Specifies which criterion of SMTP traffic to match. The criteria are described above.
|
Type
|
Specifies that the map includes traffic that matches the criterion.
|
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 maximum length in bytes of the evaluated field. The criterion matches if the length is greater than the specified number.
|
Greater Than Count
|
The maximum number of recipients or invalid recipients allowed in the e-mail message. The criterion matches if the number is greater than the specified number.
|
Verb Option
User Defined Format
(For the Command Verb criterion.)
|
The SMTP or ESMTP command that you want to inspect. If you select User Defined, you must enter the text string that corresponds to a word in the body of the e-mail message. The word cannot include spaces or special characters; only alphanumeric characters.
|
Service Extension Parameter
User Defined Format
(For the Reply EHLO criterion.
|
The service extension parameter of an EHLO server reply that you want to inspect. Select one of the well-known parameters, or select User Defined to specify a private extension in the User Defined Format field.
|
Encoding Format
User Defined Format
|
The MIME encoding format for which you want to test. Encoding types are:
• 7-bit—ASCII encoding.
• 8-bit—Used for the exchange of e-mail messages containing octets outside the 7-bit ASCII range.
• base64—Encodes binary data by treating it numerically and translating it into a base 64 representation.
• quoted-printable-Encoding that uses printable characters to transmit 8-bit data over a 7-bit data path.
• binary—Encodes using only 0 and 1.
• unknown—Encoding type is not known.
• x-uuencode-Nonstandard encoding.
• user defined—An encoding type you define. If you select User Defined, you must enter the text string that defines the encoding type you are looking for.
|
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.
|
Sun RPC Class Maps Add or Edit Match Criterion Dialog Boxes
Use the Add or Edit Match Criterion dialog boxes for the Sun Remote Procedure Call (RPC) classes used with zone-based firewall policies to define a match criterion and value for the class map. You can enter the RPC protocol number that you want to match. See the Sun RPC documentation for information about protocol numbers.
Navigation Path
From the Add or Edit Class Maps Dialog Boxes for Sun RPC classes, right-click inside the table and select Add Row or right-click a row and select Edit Row.
Related Topics
•
Understanding Map Objects, page 8-38
•
Creating Class Map Objects, page 8-41
•
Configuring Maps for Inspection in Zone-Based Firewall Rules Policies, page 8-57
•
Understanding the Zone-based Firewall Rules, page 11-62
Local Web Filter Class Add or Edit Match Criterion Dialog Boxes
Use the Add or Edit Match Criterion dialog boxes for the Local web filter class to define a match criterion and value for the class map.
Navigation Path
From the Add or Edit Class Maps Dialog Boxes for the Local web filter class, right-click inside the table and select Add Row or right-click a row and select Edit Row.
Related Topics
•
Understanding Map Objects, page 8-38
•
Creating Class Map Objects, page 8-41
•
Configuring Maps for Content Filtering in Zone-Based Firewall Rules Policies, page 8-59
•
Understanding the Zone-based Firewall Rules, page 11-62
Field Reference
Table F-46 Local Web Filter Class Add or Edit Match Criterion Dialog Boxes
Element
|
Description
|
Criterion
|
Specifies which criterion of traffic to match. You can select from the following:
• Server Domain—Matches traffic based on the name of the server. The URLF Glob parameter map you select should specify server domain names such as *.cisco.com or www.cisco.com.
• URL Keyword—Matches traffic based on keywords in the URLs. A key word is any complete string that occurs between / characters in a URL. For example, in the URL segment www.cisco.com/en/US, en and US are examples of keywords.
|
Type
|
Specifies that the map includes traffic that matches the criterion.
|
URLF Glob Parameter Map
|
The URLF Glob parameter map object that defines the URL patterns that you want to match. Ensure that the object you select has the appropriate content for the type of matching you selected.
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 object.
|
N2H2 and Websense Class Add or Edit Match Criterion Dialog Boxes
Use the Add or Edit Match Criterion dialog boxes for the N2H2 (SmartFilter) and Websense web filter classes to define a match criterion and value for the class map. The only match criterion available is to match any response from the SmartFilter or Websense server.
Navigation Path
From the Add or Edit Class Maps Dialog Boxes for the N2H2 or Websense web filter class, right-click inside the table and select Add Row or right-click a row and select Edit Row.
Related Topics
•
Understanding Map Objects, page 8-38
•
Creating Class Map Objects, page 8-41
•
Configuring Maps for Content Filtering in Zone-Based Firewall Rules Policies, page 8-59
•
Understanding the Zone-based Firewall Rules, page 11-62
Add or Edit Inspect Parameter Map Dialog Boxes
Use the Add and Edit Inspect Parameter Map dialog boxes to define a parameter map for inspection for zone-based firewall policies on routers. If you configure the action of a zone-based firewall policy rule as Inspect or Content Filter, you can select an inspect parameter map to define connection, timeout, and other settings for the inspection action. If you do not select an inspect parameter map for a zone-based firewall rule, the system uses default values for these settings.
Navigation Path
Select Tools > Policy Object Manager, then select Maps > Parameter Maps > Inspect > Inspect Parameters in the table of contents. Right-click inside the work area and select New Object, or right-click a row and select Edit Object.
Related Topics
•
Understanding Map Objects, page 8-38
•
Configuring Maps for Inspection in Zone-Based Firewall Rules Policies, page 8-57
•
Configuring Maps for Content Filtering in Zone-Based Firewall Rules Policies, page 8-59
•
Understanding the Zone-based Firewall Rules, page 11-62
Field Reference
Table F-47 Add or Edit Inspect Parameter 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.
|
DNS Timeout
|
The length of time, in seconds, for which a DNS lookup session is managed while there is no activity.
|
ICMP Timeout
|
The length of time, in seconds, for which an inactive ICMP (Internet Control Message Protocol) session is maintained.
|
Max Incomplete Low
Max Incomplete High
|
The number of existing half-open sessions that will cause the software to start (at the high threshold) and stop (at the low threshold) deleting half-open sessions.
Ensure that you enter a lower number in the Low field than you enter in the High field, for example, 400 and 500. The default is unlimited half-open sessions.
|
One Minute Low
One Minute High
|
The number of new unestablished sessions that causes the system to start and stop deleting half-open sessions. Ensure that you enter a lower number in the Low field than you enter in the High field. The default is unlimited.
|
Max Sessions
|
The maximum number of inspection sessions on a zone pair, for example, 200. The default is unlimited.
|
TCP FINWAIT Timeout
|
How long to maintain TCP session state information after the firewall detects a FIN-exchange, in seconds. The FIN-exchange occurs when the TCP session is ready to close.
|
TCP SYNWAIT Timeout
|
How long to wait for a TCP session to reach the established state before dropping the session, in seconds.
|
TCP Idle Timeout
|
How long to maintain a TCP session while there is no activity in the session, in seconds.
|
TCP Max Incomplete Hosts
TCP Max Incomplete Block Time
|
The threshold and blocking time (in minutes) for TCP host-specific denial-of-service (DoS) detection and prevention.
The maximum incomplete hosts is the number of half-open TCP sessions with the same host destination address that can simultaneously exist before the software starts deleting half-open sessions to that host. An unusually high number of half-open sessions with the same destination host address could indicate that a DoS attack is being launched against the host.
When the threshold is exceeded, half-open sessions are dropped based on the maximum incomplete block time:
• If the block time is 0, the software deletes the oldest existing half-open session for the host for every new connection request to the host. This ensures that the number of half-open sessions to a given host never exceeds the threshold.
• If the block time is greater than 0, the software deletes all existing half-open sessions for the host and then blocks all new connection requests to the host. The software continues to block all new connection requests until the block time expires.
The software sends syslog messages whenever the specified threshold is exceeded and when blocking of connection initiations to a host starts or ends.
|
UDP Idle Timeout
|
How long to maintain a UDP session while there is no activity in the session, in seconds.
When the software detects a valid UDP packet, the software establishes state information for a new UDP session. Because UDP is a connectionless service, there are no actual sessions, so the software approximates sessions by examining the information in the packet and determining if the packet is similar to other UDP packets (for example, it has similar source or destination addresses) and if the packet was detected soon after another similar UDP packet.
If the software detects no UDP packets for the UDP session for the period of time defined by the UDP idle timeout, the software will not continue to manage state information for the session.
|
Enable Alert
|
Whether to generate stateful packet inspection alert messages on the console.
|
Enable Audit Trail
|
Whether audit trail messages are logged to the syslog server or router.
|
Category
|
The category assigned to the object. Categories help you organize and identify rules and objects. See Using Category Objects, page 8-6.
|
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 Policy Object to Be Overridden, page 8-10 and Understanding Policy Object Overrides for Individual Devices, page 8-9.
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 Protocol Info Parameter Map Dialog Boxes
Use the Add and Edit Protocol Info Parameter Map dialog boxes to define a parameter map for the inspection of Instant Messaging (IM) applications or the Stun-ice protocol for zone-based firewall policies on routers. If you configure the action of a zone-based firewall policy rule as Inspect, you must select a protocol info parameter map when you configure any of these applications: AOL, ICQ, MSN Messenger, Windows Messenger, Yahoo Messenger, Stun-ice. The protocol info parameter map defines the DNS servers that interact with these applications, which helps the instant messenger application engine to recognize the instant messenger traffic and to enforce the configured policy for that instant messenger application.
Navigation Path
Select Tools > Policy Object Manager, then select Maps > Parameter Maps > Inspect > Protocol Info Parameters in the table of contents. Right-click inside the work area and select New Object, or right-click a row and select Edit Object.
Related Topics
•
Understanding Map Objects, page 8-38
•
Configuring Maps for Inspection in Zone-Based Firewall Rules Policies, page 8-57
•
Understanding the Zone-based Firewall Rules, page 11-62
Field Reference
Table F-48 Add or Edit Protocol Info Parameter 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.
|
DNS Server Table
|
The DNS servers for which traffic will be permitted (and inspected) or denied.
• To add servers, click the Add button and fill in the Add Server dialog box (see Add or Edit DNS Server for Protocol Info Parameters Dialog Box).
• To edit a server, select it and click the Edit button.
• To delete a server, 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 8-6.
|
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 Policy Object to Be Overridden, page 8-10 and Understanding Policy Object Overrides for Individual Devices, page 8-9.
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 DNS Server for Protocol Info Parameters Dialog Box
Use the Add or Edit DNS Server dialog box to identify DNS servers for which traffic will be permitted (and inspected) or denied. These servers are defined in a Protocol Info parameter map for use with the inspection of protocols that require them in a zone-based firewall policy.
You can identify a server using any of these types:
•
Server Name—The name of the DNS server. You can use an asterisk (*) as a wildcard character to match one or more characters. For example, if you want to identify all DNS servers on the cisco.com domain, you can specify *.cisco.com.
•
IP Address—The IP address of a single DNS server.
•
IP Address Range—A range of IP addresses identifying any DNS server within the start and end addresses.
Navigation Path
From the Add or Edit Protocol Info Parameter Map Dialog Boxes, click the Add button beneath the server table, or select a server and click the Edit button.
Add or Edit Local Web Filter Parameter Map Dialog Boxes
Use the Add and Edit Local Parameter Map dialog boxes to define a parameter map for local web filtering for zone-based firewall policies on routers. If you configure the action of a zone-based firewall policy rule as Content Filter, you can select a Web Filter policy map that incorporates a Local web filter parameter map (when you select Local for the parameter type on the Parameter tab). For more information about Web Filter policy maps, see Add and Edit Web Filter Map Dialog Boxes.
Navigation Path
Select Tools > Policy Object Manager, then select Maps > Parameter Maps > Web Filter > Local in the table of contents. Right-click inside the work area and select New Object, or right-click a row and select Edit Object.
Related Topics
•
Understanding Map Objects, page 8-38
•
Configuring Maps for Content Filtering in Zone-Based Firewall Rules Policies, page 8-59
•
Understanding the Zone-based Firewall Rules, page 11-62
Field Reference
Table F-49 Add or Edit Local Web Filter Parameter 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.
|
Enable Alert
|
Whether to generate stateful packet inspection alert messages on the console.
|
Enable Allow Mode
|
Whether to allow or block URL requests when the URL filtering process does not have connectivity to a URL filtering database. When allow-mode is on, all unmatched URL requests are allowed; when off, all unmatched URL requests are blocked.
|
Block Page
|
The web page you want to present to the user if the user attempts to access a page that you block. You can select from the following:
• None—The user is not presented with any information.
• Message—The user is presented with the text message you enter in the edit box.
• Redirect URL—The user is redirected to the URL you enter in the edit box.
|
Category
|
The category assigned to the object. Categories help you organize and identify rules and objects. See Using Category Objects, page 8-6.
|
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 Policy Object to Be Overridden, page 8-10 and Understanding Policy Object Overrides for Individual Devices, page 8-9.
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 N2H2 or WebSense Parameter Map Dialog Boxes
Use the Add and Edit N2H2 or Websense Parameter Map dialog boxes to define a parameter map for Smartfilter (N2H2) or Websense web filtering for zone-based firewall policies on routers. If you configure the action of a zone-based firewall policy rule as Content Filter, you can select a Web Filter policy map that incorporates an N2H2 or Websense web filter parameter map (when you select N2H2 or Websense for the parameter type on the Parameter tab). For more information about Web Filter policy maps, see Add and Edit Web Filter Map Dialog Boxes.
Navigation Path
Select Tools > Policy Object Manager, then select N2H2 or WebSense from the Maps > Parameter Maps > Web Filter folder in the table of contents. Right-click inside the work area and select New Object, or right-click a row and select Edit Object.
Related Topics
•
Understanding Map Objects, page 8-38
•
Configuring Maps for Content Filtering in Zone-Based Firewall Rules Policies, page 8-59
•
Understanding the Zone-based Firewall Rules, page 11-62
Field Reference
Table F-50 Add or Edit N2H2 or WebSense Parameter 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.
|
URL Filtering Server Table
|
The list of URL filtering servers and their attributes.
• To add servers, click the Add button and fill in the Add External Filter dialog box (see Add or Edit External Filter Dialog Box).
• To edit a server, select it and click the Edit button.
• To delete a server, select it and click the Delete button.
|
Enable Alert
|
Whether to generate stateful packet inspection alert messages on the console.
|
Enable Allow Mode
|
Whether to allow or block URL requests when the URL filtering process does not have connectivity to a URL filtering database. When allow-mode is on, all unmatched URL requests are allowed; when off, all unmatched URL requests are blocked.
|
Block Page
|
The web page you want to present to the user if the user attempts to access a page that you block. You can select from the following:
• None—The user is not presented with any information.
• Message—The user is presented with the text message you enter in the edit box.
• Redirect URL—The user is redirected to the URL you enter in the edit box.
|
Source Interface
|
The interface whose IP address should be used as the source IP address when a TCP connection is established between the system and the URL filtering server.
|
Maximum Cache Entries
|
The maximum number of entries to store in the categorization cache. The default is 5000.
|
Cache Life Time
|
How long, in hours, an entry remains in the cache table. The default is 24.
|
Maximum Requests
|
The maximum number of pending requests. The range is from 1 to 2147483647. The default is 1000.
|
Maximum Responses
|
The maximum number of HTTP responses that can be buffered. The range is from 0 and 20000. The default is 200.
|
Truncate Hostname
Truncate Script Parameters
|
Whether to truncate the URLs:
• If you do not select an option, URLs are not truncated.
• If you select Hostname, URLs are truncated at the end of the domain name.
• If you select Script Parameters, URLs are truncated at the left-most question mark in the URL.
Tip  Although you can select both options, it is illogical to do so.
|
Enable Server Log
|
Whether to send information about HTTP requests to the URL filtering server's log server. The information includes the URL, the hostname, the source IP address, and the destination IP address.
|
Category
|
The category assigned to the object. Categories help you organize and identify rules and objects. See Using Category Objects, page 8-6.
|
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 Policy Object to Be Overridden, page 8-10 and Understanding Policy Object Overrides for Individual Devices, page 8-9.
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 External Filter Dialog Box
Use the Add or Edit External Filter dialog box to add a URL filtering server to an N2H2, Websense, or URL Filter parameter map policy object.
Navigation Path
Click the Add button beneath the server table, or select a server and click the Edit button, from any of the following dialog boxes:
•
Add or Edit N2H2 or WebSense Parameter Map Dialog Boxes
•
Add or Edit URL Filter Parameter Map Dialog Boxes
Field Reference
Table F-51 Add or Edit External Filter Dialog Box
Element
|
Description
|
Server
|
The fully-qualified domain name or IP address of the URL filtering server.
|
Port
|
The port that is listening for requests.
|
Retransmission Count
|
The number of times the router retransmits the lookup request when a response is not received from the server. The range is from 1 to 10.
|
Timeout
|
The number of seconds that the router waits for a response from the server. The range is from 1 to 300.
|
Outside
|
Whether the server is outside the network.
|
Add or Edit Trend Parameter Map Dialog Boxes
Use the Add and Edit Trend Parameter Map dialog boxes to define a parameter map for Trend Micro web filtering for zone-based firewall policies on routers. If you configure the action of a zone-based firewall policy rule as Content Filter, you can select a Web Filter policy map that incorporates a Trend web filter parameter map (when you select Trend for the parameter type on the Parameter tab). For more information about Web Filter policy maps, see Add and Edit Web Filter Map Dialog Boxes.
Navigation Path
Select Tools > Policy Object Manager, then select Maps > Parameter Maps > Web Filter > Trend in the table of contents. Right-click inside the work area and select New Object, or right-click a row and select Edit Object.
Related Topics
•
Understanding Map Objects, page 8-38
•
Configuring Maps for Content Filtering in Zone-Based Firewall Rules Policies, page 8-59
•
Understanding the Zone-based Firewall Rules, page 11-62
Field Reference
Table F-52 Add or Edit Trend Parameter 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.
|
Enable Allow Mode
|
Whether to allow or block URL requests when the URL filtering process does not have connectivity to a URL filtering database. When allow-mode is on, all unmatched URL requests are allowed; when off, all unmatched URL requests are blocked.
|
Block Page
|
The web page you want to present to the user if the user attempts to access a page that you block. You can select from the following:
• None—The user is not presented with any information.
• Message—The user is presented with the text message you enter in the edit box.
• Redirect URL—The user is redirected to the URL you enter in the edit box.
|
Maximum Requests
|
The maximum number of pending requests. The range is from 1 to 2147483647. The default is 1000.
|
Maximum Responses
|
The maximum number of HTTP responses that can be buffered. The range is from 0 and 20000. The default is 200.
|
Truncate Hostname
|
Whether to truncate URLs at the end of the domain name.
|
Category
|
The category assigned to the object. Categories help you organize and identify rules and objects. See Using Category Objects, page 8-6.
|
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 Policy Object to Be Overridden, page 8-10 and Understanding Policy Object Overrides for Individual Devices, page 8-9.
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 URL Filter Parameter Map Dialog Boxes
Use the Add and Edit URL Filter Parameter Map dialog boxes to define the parameters and match criterion and values for an inspection map used in a zone-based firewall policy for a router.
If you configure the action of a zone-based firewall policy rule as Content Filter, you can select a URL Filter parameter map to define web filtering parameters and match criteria. However, if the router is running Cisco IOS Software release 12.4(20)T or higher, the recommended approach is to configure a Web Filter policy map along with parameter and class maps for the appropriate server type (local, N2H2, Trend, or Websense). For more information, see Add and Edit Web Filter Map Dialog Boxes.
Navigation Path
Select Tools > Policy Object Manager, then select Maps > Parameter Maps > Web Filter > URL Filter in the table of contents. Right-click inside the work area and select New Object, or right-click a row and select Edit Object.
Related Topics
•
Understanding Map Objects, page 8-38
•
Configuring Maps for Content Filtering in Zone-Based Firewall Rules Policies, page 8-59
•
Understanding the Zone-based Firewall Rules, page 11-62
Field Reference
Table F-53 Add or Edit URL Filter Parameter 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.
|
Local Filtering Tab
The fields on this tab define the properties for local URL filtering.
|
Whitelisted and Blacklisted Domains tables
|
These tables define the domain names for which the software will not contact the external URL filtering server. Domain names on the whitelist are always allowed. Domain names on the blacklist are always blocked. Use these lists to identify entire domains that you want to allow without restriction (such as your company's web site) or block completely (such as pornography sites).
Domain names can be complete (including the host name, such as www.cisco.com), or partial (such as cisco.com). For partial names, all web site hosts on that domain are either permitted or denied. You can also enter host IP addresses.
• To add a domain name, click the Add button and fill in the Add Server dialog box (see Add or Edit URL Domain Name Dialog Box for URL Filter Parameters).
• To edit a domain name, select it and click the Edit button.
• To delete a domain name, select it and click the Delete button.
|
Enable Alert
|
Whether to generate stateful packet inspection alert messages on the console.
|
Enable Audit Trail
|
Whether to log URL information to the syslog server or router.
|
Enable Allow Mode
|
Whether to allow or block URL requests when the URL filtering process does not have connectivity to a URL filtering database. When allow-mode is on, all unmatched URL requests are allowed; when off, all unmatched URL requests are blocked.
|
External Filtering Tab
The fields on this tab define the properties for an external URL filtering server.
|
Server Type
Server Table
|
The type of external URL filtering server you are configuring, either SmartFilter (N2H2) or Websense.
• To add servers, click the Add button and fill in the Add External Filter dialog box (see Add or Edit External Filter Dialog Box).
• To edit a server, select it and click the Edit button.
• To delete a server, select it and click the Delete button.
|
Source Interface
|
The interface whose IP address should be used as the source IP address when a TCP connection is established between the system and the URL filtering server.
|
Maximum Cache Entries
|
The maximum number of entries to store in the categorization cache. The default is 5000.
|
Maximum Requests
|
The maximum number of pending requests. The range is from 1 to 2147483647. The default is 1000.
|
Maximum Responses
|
The maximum number of HTTP responses that can be buffered. The range is from 0 and 20000. The default is 200.
|
Truncate Hostname
Truncate Script Parameters
|
Whether to truncate the URLs:
• If you do not select an option, URLs are not truncated.
• If you select Hostname, URLs are truncated at the end of the domain name.
• If you select Script Parameters, URLs are truncated at the left-most question mark in the URL.
Do not select any truncate options for devices running software releases lower than 12.4(15)T or you will receive a validation error.
Tip  Although you can select both options, it is illogical to do so.
|
Enable Server Log
|
Whether to send information about HTTP requests to the URL filtering server's log server. The information includes the URL, the hostname, the source IP address, and the destination IP address.
|
Additional Fields
|
Category
|
The category assigned to the object. Categories help you organize and identify rules and objects. See Using Category Objects, page 8-6.
|
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 Policy Object to Be Overridden, page 8-10 and Understanding Policy Object Overrides for Individual Devices, page 8-9.
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 URL Domain Name Dialog Box for URL Filter Parameters
Use the Add URL Domain Name dialog box to add web site domain names to the whitelisted (allowed) or blacklisted (not allowed) lists.
Domain names can be complete (including the host name, such as www.cisco.com), or partial (such as cisco.com). For partial names, all web site hosts on that domain are either permitted or denied. You can also enter host IP addresses.
Navigation Path
From the Add or Edit URL Filter Parameter Map Dialog Boxes, click the Add button beneath the whitelist or blacklist tables, or select a name and click the Edit button.
Add or Edit URLF Glob Parameter Map Dialog Boxes
Use the Add and Edit URLF Glob Parameter Map dialog boxes to define a parameter map for the inspection of URLs in a Local web filter class map.
A single URLF Glob should contain only segments of URLs that you want to block or allow. Your goal is to create class maps of white listed (allowed) or blacklisted (blocked) URLs. You can then define Local web filter policy maps to allow or block the identified URLs.
A single URLF Glob must also be limited to one of these types of URL segments:
•
Strings that appear in the server name of a URL, which includes the name of the server and the domain name of the network. For example, www.cisco.com.
•
Strings that appear in URL keywords, which are the strings that appear between / characters in a URL, or which are the file names. For example, in the URL segment www.cisco.com/en/US/, both en and US are keywords. The file name in a URL, such as index.html, is also considered a keyword.
You cannot use the characters /, {, }, and ? in a URLF glob.
To match a server name or URL keyword, the string in the URL must match exactly the string included in the URLF glob unless you use wildcard metacharacters to specify a variable string pattern. You can use the following metacharacters for pattern matching for either server names or URL keywords:
•
* (Asterisk). Matches any sequence of zero or more characters. For example, *.edu matches all servers in the education domain, and you could use hack* to block www.example.com/hacksite/123.html.
•
[abc] (Character class). Matches any character in the brackets. The character matching is case sensitive. For example, [abc] matches a, b, or c, but not A, B, or C. Thus, you could use www.[ey]xample.com to block both www.example.com and www.yxample.com.
•
[a-c] (Character range class). Matches any character in the range. The character matching is case sensitive. [a-z] matches any lowercase letter. You can mix characters and ranges; for example, [abcq-z] matches a, b, c, q, r, s, t, u, v, w, x, y, z, and so does [a-cq-z].The dash (-) character is literal only if it is the last or the first character within the brackets, [abc-] or [-abc].
•
[0-9] (Numerical range class). Matches any number in the brackets. For example [0-9] matches 0, 1, 2, 3, 4, 5, 6, 7, 8, or 9. Thus, you can use www.example[0-9][0-9].com to block www.example01.com, www.example33.com, and www.example99.com (and so forth).
Navigation Path
Select Tools > Policy Object Manager, then select Maps > Parameter Maps > Web Filter > URLF Glob Parameters in the table of contents. Right-click inside the work area and select New Object, or right-click a row and select Edit Object.
Related Topics
•
Understanding Map Objects, page 8-38
•
Local Web Filter Class Add or Edit Match Criterion Dialog Boxes
•
Configuring Maps for Content Filtering in Zone-Based Firewall Rules Policies, page 8-59
•
Understanding the Zone-based Firewall Rules, page 11-62
Field Reference
Table F-54 Add or Edit URLF Glob Parameter 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.
|
Value
|
The server domains or keywords for the URLs you are targeting. Enter only one type of glob: either all server domains, or all URL keywords, but not a mixture of both.
If you include more than one entry, separate the entries with new lines. For example, the following entries identify all government or education web servers:
|
Category
|
The category assigned to the object. Categories help you organize and identify rules and objects. See Using Category Objects, page 8-6.
|
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 Policy Object to Be Overridden, page 8-10 and Understanding Policy Object Overrides for Individual Devices, page 8-9.
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 Maps > Policy Maps > Inspect > DCE/RPC 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 Map Objects, page 8-38
•
Creating DCE/RPC Map Objects, page 8-42
Field Reference
Table F-55 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 8-6.
|
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 Policy Object to Be Overridden, page 8-10 and Understanding Policy Object Overrides for Individual Devices, page 8-9.
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 Maps > Policy Maps > Inspect > DNS 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 Map Objects, page 8-38
•
Creating DNS Map Objects, page 8-43
•
Creating Class Map Objects, page 8-41
Field Reference
Table F-56 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 8-6.
|
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 Policy Object to Be Overridden, page 8-10 and Understanding Policy Object Overrides for Individual Devices, page 8-9.
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 Map Objects, page 8-38
•
Creating DNS Map Objects, page 8-43
Field Reference
Table F-57 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 Map Objects, page 8-38
•
Creating DNS Map Objects, page 8-43
Field Reference
Table F-58 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
•