User Guide for Cisco Security Manager 4.19

Enable API Service

Whether to enable or disable the API service.

Result Set Page Size

Allowed values are 100 through 1000, inclusive.

Active client sessions

Allowed values are 1 through 10, inclusive.

Save button

Saves and applies changes.

Reset button

Resets changes to the last saved values.

Restore Defaults button

Resets values to Security Manager defaults.

Enable AutoLink for 10.0.0.0/8

Enable AutoLink for 172.16.0.0/12

Enable AutoLink for 192.168.0.0/16

Whether to automatically include or omit (deselected) these private networks from the maps you create.

Enable AutoLink for 127.0.0.0/8

Whether to automatically include or omit (deselected) the loopback network from the maps you create.

Enable AutoLink for 224.0.0.0/4

Whether to automatically include or omit (deselected) the multicast networks from the maps you create.

Save button

Saves and applies changes.

Reset button

Resets changes to the last saved values.

Restore Defaults button

Resets values to Security Manager defaults.

Hit Count History Persist Limit (per ACE)

The Hit Count History Persist Limit is the limit for the Hit Count history details that can be stored for the particular ACE in the database. The default value is 5 and you can enter a maximum value of 10.

Purge Scheduler Process Time

The Purge Scheduler Process Time is used by the Hit Count Scheduler to schedule the Hit Count purge job at the given time on a daily basis. Select a time from the drop-down list. The default is 12 AM.

Use IPS Updates Settings

If checked, the other settings on this page are disabled and the default prevails (the Cisco.com credentials from the IPS Updates page apply).

Username

The username Security Manager should use to log in to Cisco.com.

Password

Confirm

The password for the username. Enter the password in both fields.

Enable Proxy

Enables Image Manager to connect to Cisco.com via a web proxy server. When Enable Proxy is selected, the other proxy fields (including IP or Hostname, Port, Username, and Password) are enabled and used to connect to the web proxy.

Test Connection

Used to test for connectivity and credentials for Cisco.com.

Contact URL

• When selected, "Image Meta-data Locator" is used. This is the URL on Cisco.com that is used to obtain meta-data information about images. Meta-data information consists of the images applicable to a particular product, name, size, checksum, and URL to download for each image.
• When selected, "Other" is used. You can enter any valid HTTPS URL. This URL is intended primarily for the HTTPS URL to download the image as obtained from the meta-data information about the image. This URL may be different from the URL of the image meta-data locator described in the previous paragraph; the certificate may be different, as well.

Retrieve Certificate

Used to connect to and retrieve the certificate from the selected ‘"Contact URL’." After retrieving the certificate it opens the Certificate Verification dialog, which along with a brief summary of the certificate, i.e., who the certificate is issued to, by whom, and the validity period of the certificate, gives you the following choices:

• View Certificate —Opens the Certificate Viewer, where you can see all the details of the certificate: Certificate Authority, version, serial number, thumbprint, and other details. It shows the complete certificate chain information all the way up to the root issuing certificate Authority.
• Accept —Accepts the certificate and adds it to the Cisco Security Manager.
• Reject —Rejects the certificate and no action is taken.
• Cancel —Closes the Certificate Verification dialog with no action taken.

You must view and accept the following recommended certificates:

• https://www.cisco.com
• https://www.dl3.cisco.com
• https://www.cloudsso.cisco.com
• https://www.api.cisco.com

Certificates

A table that displays, for each certificate in your Security Manager installation, Subject, Issued By, and Accepted By.

View

Opens the Certificate Viewer for a certificate selected in the Certificate table.

Remove

Removes a certificate selected in the Certificate table.

Save button

Saves your changes.

Reset button

Resets changes to the last saved values.

Restore Defaults button

Resets values to Security Manager defaults.

Max. Versions per Device

Purge Now button

Enable Configuration Archive Versions Auto Purge

The number of configuration versions you want to retain for each managed device, from 1 to 100. If you reduce the number, you can click Purge Now to immediately delete extra versions.

Security Manager automatically deletes extra versions during its normal cleanup cycle if you select the Enable Configuration Archive Versions Auto Purge option.

TFTP Server for Rollback

The fully-qualified DNS hostname or IP address of the server to use for TFTP file transfers. TFTP is used during rollback for IOS devices when the configuration cannot be updated using the configure replace command, which does not force a system reload. Enter localhost to use the Security Manager server.

By default, a TFTP server is enabled on the Security Manager server. If you specify a remote TFTP server, you must configure that server appropriately to provide TFTP services.

TFTP Root Directory

The root directory for configuration file transfers if you are using the Security Manager server as the TFTP server. Click Browse to select a directory on the Security Manager server.

If you specify a server other than the Security Manager server as the TFTP host, Security Manager always uses the root directory of that TFTP server. You cannot specify a non-root directory for remote TFTP servers.

Save button

Saves and applies changes.

Reset button

Resets changes to the last saved values.

Restore Defaults button

Resets values to Security Manager defaults.

CS-MARS Devices

The CS-MARS servers that are registered with Security Manager.

• To add a server, click the Add (+) button and fill in the New or Edit CS-MARS Device Dialog Box.
• To edit a server, select it and click the Edit (pencil) button.
• To delete a server, select it and click the Delete (trash can) button. When you delete a server, the device properties for all devices that use the server are updated to remove the server connection. If a device is also monitored by another CS-MARS server on the list, its properties are updated to point to the other server.

When Launching CS-MARS

Allow User to Save Credentials

The type of credentials Security Manager should use to log into CS-MARS when obtaining event information:

• Prompt users —When the user tries to get event information from CS-MARS, prompt the user to log into CS-MARS. If you select this option, you can also select Allow User to Save Credentials, which gives users the option to save their credentials so they do not have to log into CS-MARS again the next time they request event status.
• Use CS-Manager Credentials —When the user tries to get event information from CS-MARS, log into CS-MARS using the same username and password the user used to log into Security Manager.

Save button

Saves and applies changes.

Reset button

Resets changes to the last saved values.

Enable CSM Mobile Feature

Lets you enable or disable the CSM Mobile feature. If you disable this feature, you cannot access device health summary information from mobile devices.

Save button

Saves and applies changes.

If you change whether the service is enabled, it stops or starts, as appropriate. You are shown a progress indicator.

Reset button

Resets changes to the last saved values.

Reset ‘Do Not Ask’ on Warnings button

Click this button to reestablish ‘Are you sure...?’ pop-up warnings. When you perform some actions, you are warned about the consequences and you are given the option to not be warned again. If you selected Do Not Ask Me Again for any of these warnings, clicking this button reenables the warning.

Enable Idle Timeout

Idle Timeout (minutes)

Whether to have the Security Manager client applications close automatically if you do not use them for the specified period of time. The timeout applies across all applications; working in one application resets the timer in all applications.

If you select this option, enter the number of minutes that must elapse before closing the client in the Idle Timeout field. The default is to close the client after 120 minutes of inactivity.

Enable Client side file browser

Whether to allow file operations on the Security Manager client. If you select this option, you will be able to choose between client and server file systems when performing the following file operations:

• Installing Security Manager license files
• Installing IPS license files
• Importing/exporting device inventory files
• Importing/exporting shared policies
• Creating the following file objects:

– Cisco Secure Desktop Package

– Plug-In—For browser plug-in files.

– AnyConnect Profile

– AnyConnect Image

– Hostscan Image

This option is enabled by default.

Enable Global Search

Whether to enable or disable the Global Search feature. This feature is enabled by default.

Recreate Index

Click this button to regenerate the search index. The global search feature is not available while the index is being recreated.

Save button

Saves and applies changes.

Reset button

Resets changes to the last saved values.

Restore Defaults button

Resets values to Security Manager defaults.

Capture Discovery/Deployment Debugging Snapshots to File

Whether Security Manager generates data files about configuration generation, deployment, and discovery as these functions are performed. The temporary data files are stored in the MDC\temp directory in the Security Manager installation folder on the server, and you can use these files for debugging purposes.

Enable this setting if you encounter problems with deployment or discovery.

Note Selecting this check box slows down Security Manager response time. Enable this option only in limited circumstances.

If you need to send these files to Cisco TAC for debugging, encrypt the files, because they can contain sensitive data such as passwords.

Note Do not delete any snapshot files under MDC\temp directory in the Security Manager installation folder while discovery (or) deployment is in progress. You can delete them when Security Manager is idle. In addition, ensure you are not deleting any of the default files.

Deployment Debug Level

The message severity level for deployment-related actions such as device communication.

Event Manager Debug Level

The message severity level for the Event Manager subsystem.

Health and Performance Monitor Debug Level

The message severity level for the Health and Performance Monitor subsystem.

Image Manager Debug Level

The message severity level for the Image Manager subsystem.

Firewall Services Debug Level

The message severity level for firewall-related policies.

IOS Platform Debug Level

The message severity level for Cisco IOS Software platform policies.

PIX Platform Debug Level

The message severity level for PIX, ASA, and FWSM platform policies.

Report Manager Debug Level

The message severity level for the Report Manager subsystem.

VPN Services Debug Level

The message severity level for VPN services policies.

API Debug Level

The message severity level for the Application Programming Interface subsystem.

Save button

Saves your changes.

Reset button

Restores all fields to their previous values.

Restore Defaults button

Resets values to Security Manager defaults.

Purge Debugging Files Older Than (days)

The maximum number of days the system should keep debugging files. Debug files are automatically deleted. If you decrease the number of days, you can click Purge Now to immediately delete all debugging files older than the number of days specified.

Default Deployment Method

Directory

The method to use as the default method for deploying configurations to devices:

• Device—Deploys the configuration directly to the device or to the transport mechanism specified for the device. For more information, see Deploying Directly to a Device.
• File—Deploys the configuration file to a directory on the Security Manager server. If you select File, specify the directory to which you want to deploy the configuration file in the Destination column. Even if you select file as the default, the setting does not apply to IPS devices; you can use device deployment only for IPS devices. For more information, see Deploying to a File.

You can override this method when you create deployment jobs.

When Out of Band Changes Detected

How Security Manager should respond when it detects that changes were made directly on the device CLI since a configuration was last deployed to the device. Out of band change detection works correctly only when deploying to device, not to file, and applies only when the deployment method is configured to obtain the reference configuration from the device (see below for a description of the Reference Configuration setting).

This setting specifies the default action, which you can override when you create deployment jobs. You can choose one of the following:

• Overwrite changes and show warning (default)—If changes were made to the device manually, Security Manager continues with the deployment, overwrites the changes, and displays a warning notifying you of this action.
• Cancel deployment —If changes were made to the device manually, Security Manager cancels the deployment and displays a warning notifying you of this action.
• Do not check for changes —Security Manager does not check for changes and deploys the changes to the device, overwriting any local modifications.

For a more complete discussion of out-of-band change handling, see Understanding How Out-of-Band Changes are Handled.

Note For devices in which failover is not configured, if you select the Cancel Deployment option when Out of Band changes are detected, the bootstrap configuration may cause deployments to fail. For deployments to be successful, you must configure failover before discovering the device in Security Manager.

Deploy to File Reference Configuration

The configuration that Security Manager uses to compare new policies against the previous configuration for the device, if you are deploying the configuration to a file on the Security Manager server.

• Archive (default)—The most recently archived configuration.
• Device—The current running device configuration, which is obtained from the device.

After comparing the configurations, Security Manager generates the correct CLI for deployment.

Deploy to Device Reference Configuration

The configuration that Security Manager uses to compare new policies against the previous configuration for the device, if you are deploying the configuration directly to the device (or to a transport server).

• Archive—The most recently archived configuration.
• Device (default)—The current running device configuration, which is obtained from the device.

After comparing the configurations, Security Manager generates the correct CLI for deployment.

Allow Download on Error

Whether deployments to devices should continue even if there are minor device configuration errors.

Save Changes Permanently on Device

Whether to save the running configuration to the startup configuration (using the write memory command) after deploying a configuration to a device. This applies to PIX, FWSM, ASA, or Cisco IOS devices. If you deselect this check box, the startup configuration is not changed, which means your configuration changes will be lost if the device reloads for any reason.

Preselect Devices with Undeployed Changes

Whether the list of changed devices you see when you create a deployment job has all changed devices preselected. If you deselect this option, users must manually select the devices to include in the deployment job.

Enable Auto Refresh in Deployment Main Panel

Whether the deployment job and schedule status information should be automatically refreshed in the Deployment Manager window. If you deselect this option, you must click the Refresh button to refresh the information manually.

Remove Unreferenced SSL VPN Files on Device

(ASA Only)

Whether to have Security Manager delete files related to the SSL VPN configuration from the device if the files are no longer referred to by the device’s SSL VPN configuration. If you deselect this option, unused files remain on the device after deployment.

Mask Passwords and Keys When Viewing Configs and Transcripts

Mask Passwords and Keys When Deploying to File

The conditions, if any, under which Security Manager will mask the following items so that they cannot be read: passwords for users, enable mode, Telnet, and console; SNMP community strings; keys, including those for TACACS+, Preshared Key, RADIUS server, ISAKMP, failover, web VPN attributes, logging policy attributes, AAA, AUS, OSPF, RIP, NTP, logging FTP server, point-to-point protocol, Storage Key, single sign-on server, load balancing, HTTP/HTTPS proxy, and the IPSEC shared key.

• Mask Passwords and Keys When Viewing Configs and Transcripts—This option affects only the screen display of the credentials, which guards against unauthorized personnel viewing them. If you do not select this option, credentials in full transcripts might still be masked depending on how the device handles them.
• Mask Passwords and Keys When Deploying to File—This option affects the contents of configuration files that are deployed to file, making them undeployable to actual devices. Select this option only if you will never need to actually deploy these configurations to real devices. Selecting this option has no effect on whether credentials are masked when viewed.

Deploy only new or modified Flexconfigs

Whether to deploy FlexConfigs only one time after creation or modification of a FlexConfig, or to deploy all FlexConfigs with each deployment. This option is selected by default.

Note If you have FlexConfigs that need to be deployed with each deployment, then you will need to disable this option. After changing this setting, you will need to manage one-time FlexConfigs by deleting them after they have been deployed.

Optimize the Deployment of Access Rules For

(IPv4 and IPv6 access rules.)

How firewall rules are deployed. You can choose one of the following:

• Speed (default)—Increases deployment speed by sending only the delta (difference) between the new and old ACLs. This is the recommended option. By making use of ACL line numbers, this approach selectively adds, updates, or deletes ACEs at specific positions and avoids resending the entire ACL. Because the ACL being edited is still in use, there is a small chance that some traffic might be handled incorrectly between the time an ACE is removed and the time that it is added to a new position. The ACL line number feature is supported by most Cisco IOS, PIX and ASA versions, and became available in FWSM from FWSM 3.1(1).
• Traffic—This approach switches ACLs seamlessly and avoids traffic interruption. However, deployment takes longer and uses more device memory before the temporary ACLs are deleted. First, a temporary copy is made of the ACL that is intended for deployment. This temporary ACL binds to the target interface. Then the old ACL is recreated with its original name but with the content of the new ACL. It also binds to the target interface. At this point, the temporary ACL is deleted.

Note For FWSM devices, this option affects processing only if you also select the Let FWSM Decide When to Compile Access Lists option.

Firewall Access-List Names

(IPv4 and IPv6 access rules.)

How ACL names are deployed to devices if the access rule does not have a name in Security Manager.

• Reuse existing names—Reuse the ACL name that is configured in the reference configuration (which is usually from the device).
• Reset to CS-Manager generated names—Reset the name to a Security Manager auto-generated ACL name.

Enable ACL Sharing for Firewall Rules

(IPv4 and IPv6 access rules.)

Whether Security Manager should share a single access control list (ACL) for an access rule policy with more than one interface. If you do not select this option, Security Manager creates unique ACLs for every interface to which you apply an IPv4 or IPv6 access rule policy. The sharing of ACLs is done only for ACLs created by access rule policies.

If you select this option, Security Manager evaluates the access rules policy for each interface and deploys the minimum number required to implement your policy while preserving your ACL naming requirements. For example, if you use an interface role to assign the same rules to four interfaces, you specify Reset to CS-Manager generated names for the Firewall Access-List Names property, and you do not specify ACL names for the interfaces in the access control settings policy, only a single ACL is deployed, and each interface uses that ACL.

If you select this option, keep the following in mind:

• An interface might use an ACL that is named for a different interface.
• If you specify a name for the ACL in the access control settings policy, an ACL by that name is created even if it is otherwise identical to one used by another interface. Names specified in this policy have precedence over any other settings.
• If you select Reuse existing names for the Firewall Access-List Names property, the existing names are preserved (unless you override them in the access control settings policy). This means that you might end up with duplicate ACLs under different names if duplicate ACLs already exist on the device.
• Hit count statistics are based on ACL, not on interface, so a shared ACL provides statistics that are combined from all interfaces that share the ACL.
• Sharing ACLs is primarily beneficial for memory-constrained devices such as the FWSM.

Let FWSM Decide When to Compile Access Lists

(IPv4 access rules only.)

Whether to have the Firewall Services Module (FWSM) automatically determine when to compile access lists. Selecting this option might increase deployment speed but traffic might be disrupted and the system might become incapable of reporting ACL compilation error messages. If you select this option, you can use the Optimize the Deployment of Access Rules For Traffic setting to mitigate potential traffic disruptions.

When deselected, Security Manager controls ACL compilation to avoid traffic interruption and to minimize peak memory usage on the device.

Remove Unreferenced Access-lists on Device

(IPv4 and IPv6 access rules.)

Whether to delete any access lists that are not being used by other CLI commands managed by Security Manager from devices during deployment.

Note After enabling this option, Security Manager will remove access lists during deployment that are not used in any policies managed or discovered by Security Manager. If any policy that is NOT discovered or managed by Security Manager is using such an access list, Security Manager will still attempt to delete that object during deployment. This also applies to access lists that are used in FlexConfigs but are not used in any other policies managed by Security Manager.

Generate ACL Remarks During Deployment

(IPv4 and IPv6 access rules.)

Whether to display ACL warning messages and remarks during deployment.

Preserve Sections for Access Rules

Whether to deploy the section name under which access rules are organized. This option ensures that if a device is discovered or rediscovered, the section names will not be lost.

Generate CSM Rule Number

Whether to deploy the rule number used in the Cisco Security Manager user interface. This option helps in correlating an access rule in a device configuration to its position in rule table.

Remove Unreferenced Object Groups from Device (PIX, ASA, FWSM, IOS 12.4(20)T+)

(IPv4 and IPv6 objects.)

Whether Security Manager should remove object groups that are not being used by other CLI commands managed by Security Manager from devices during deployment. Object groups include network/host, service, and identity user groups.

Note After enabling this option, Security Manager will remove objects during deployment that are not used in any policies managed or discovered by Security Manager. If any policy that is NOT discovered or managed by Security Manager is using such an object, Security Manager will still attempt to delete that object during deployment. In such cases, deployment will fail with a transcript error indicating that it was unable to delete the object.

Create Object Groups for Policy Objects (PIX, ASA, FWSM, IOS 12.4(20)T+)

Create Object Groups for Multiple Sources, Destinations or Services in a Rule (PIX, ASA, FWSM, IOS 12.4(20)T+)

Optimize Network Object Groups During Deployment (PIX, ASA, FWSM, IOS 12.4(20)T+)

(IPv4 and IPv6 objects.)

Whether Security Manager should create object groups, such as network objects, service group objects, and identity user group objects, to replace comma-separated values in a rule table cell for the indicated devices. When deselected, Security Manager flattens the object groups to display the IP addresses, sources and destinations, users, ports, and protocols for these devices.

If you select this option, you can also select these options:

• Create Object Groups for Multiple Sources, Destinations or Services in a Rule—Whether to automatically create network objects, service objects, and identity user group objects to replace comma-separated values in a rule table cell that resulted when multiple rules were combined. The objects are created during deployment and are in the format of ‘CSM_INLINE...’ for example, ‘CSM_INLINE_src_rule_8589960758’. For more information, see Combining Rules.
• Optimize Network Object Groups During Deployment—Whether to optimize network object groups by making them more succinct. For more information on optimizing policy objects, see Optimizing Network Object Groups When Deploying Firewall Rules.

Generate transcripts for IPS Auto-Update Jobs

Attach transcripts to email for IPS Auto-Update Jobs

Remove Unreferenced Signature and Event Action Variables from IPS Device (IPS Parameters object group)

Whether to delete the unused variables from the sensor (IPS device) configuration during the next deployment. IPS Event and Signature Variables are defined as policy objects in Security Manager.

Disabled by default (checkbox is cleared by default); that is, do not remove the unreferenced variables.

Applies to the following variables; applies to both IPv4 and IPv6:

• signature source and destination addresses
• signature service port variables in signature engine parameters
• victim and attacker addresses in event action filters
• network information target addresses

Does not apply to the following variables:

• signature source port
• OS identification address
• signature destination port

Save button

Saves and applies changes.

Reset button

Resets changes to the last saved values.

Restore Defaults button

Resets values to Security Manager defaults.

Device Connection Timeout

The number of seconds that Security Manager has to establish a connection with a device before timing out.

Retry Count

The number of times that Security Manager should try to establish a connection to a device before concluding that the connection cannot be completed. The default value is 3.

Socket Read Timeout

For SSH and Telnet sessions, the maximum number of seconds Security Manager can wait for incoming data before concluding that the connection is lost.

Transport Protocol (IPS)

The default transport protocol for IPS sensors and routers that include the IPS feature. The default is HTTPS.

Transport Protocol (IOS Routers 12.3 and above)

The default transport protocol for routers that run Cisco IOS software release 12.3 and above. The default is HTTPS.

Transport Protocol (Catalyst Switch/7600)

The default transport protocol for Catalyst 6500/7600 devices and all other Catalyst switches, regardless of the Cisco IOS software version running on the devices. The default is SSH.

Transport Protocol (IOS Routers 12.2, 12.1)

The default transport protocol for routers that run Cisco IOS software releases 12.1 and 12.2. The default is Telnet.

Connect to Device Using

The type of credentials Security Manager should use when accessing devices. For more information, see Understanding Device Credentials.

• Security Manager User Login Credentials —Security Manager contacts the device using the credentials that you entered while logging in to Security Manager. The same set of credentials are used for all devices regardless of the credentials configured for each device on the Device Credentials page.
• Security Manager Device Credentials —Security Manager contacts the device using the credentials specified in the Device Properties Credentials page. This is the default.

SSL Certificate Parameters

Device Authentication Certificates (IPS)

Device Authentication Certificates (Router)

PIX/ ASA/ FWSM Device Authentication Certificates

Add Certificate button

How to handle device authentication certificates for SSL (HTTPS) communications. You can configure different behaviors for different types of devices, but the settings have the same meaning:

• Retrieve while adding devices —Security Manager automatically obtains certificates from the devices while you add devices from the network or from an export file.
• Manually add certificates —Security Manager does not automatically accept certificates from the device. Click Add Certificate to open the Add Certificate dialog box (see Add Certificate Dialog Box) where you can manually add the thumbprint before you try to add the device from the network or from an export file. You can also add certificates for devices that you create manually from the Device Properties Credentials page to be successful. For more information, see Manually Adding SSL Certificates for Devices that Use HTTPS Communications.
• Do not use certificate authentication —Security Manager ignores device authentication certificates. This option leaves your system vulnerable to third-party interference with device validation. We recommend that you do not use this option.

Accept Device SSL Certificate after Rollback

For devices that use SSL, whether to obtain the certificate installed on an IPS device, firewall device, FWSM, ASA, or Cisco IOS router from the device when you roll back the configuration on the device.

HTTPS Port Number

The default port number that the device uses for secure communication with Security Manager (as well as other management applications that use these protocols). This value overrides the HTTPS port number that you configure in the HTTP policy for a device.

Note If you configure the local HTTP policy to be a shared policy and assign the HTTP policy to multiple devices, the HTTPS port number setting in the shared policy overrides the port number configured in the Device Properties Credentials page for all devices to which the policy is assigned.

In addition to providing access to the device through the Cisco web browser user interface, the HTTPS port number is used by device management applications (such as the Cisco Router and Security Device Manager (SDM)) and monitoring tools to communicate with the device.

Note The security appliance can support both SSL VPN connections and HTTPS connections for device manager administrative sessions simultaneously on the same interface. Both HTTPS and SSL VPN use port 443 by default. Therefore, to enable both HTTPS and SSL VPN on the same interface, you must specify a different port number for either HTTPS or WebVPN. An alternative is to configure SSL VPN and HTTPS on different interfaces.

Overwrite SSH Keys

Whether Security Manager can overwrite the SSH key for a device when it changes on the device. For SSH connections, a correct key is required for successful communication.

Deselect this check box with caution, and only if you require a greater level of security. Security Manager does not communicate with the device if keys are changed on the device.

Save button

Saves and applies changes.

Reset button

Resets changes to the last saved values.

Restore Defaults button

Resets values to Security Manager defaults.

Groups

Displays the device groups and group types.

To rename a group or type, select it and then click it again to make the text editable. Type in the new name and press Enter.

Add Type button

Click this button to create a new group type. The type is added with a default name. Overtype the name and press Enter.

Add Group to Type button

Click this button to add a device group to the selected device group or group type.

Delete button (trash can)

Click this button to delete the selected device group or group type and all device groups that it contains. Deleting a device group or group type does not delete any devices it contains.

Save button

Saves your changes.

Reset button

Restores all fields to their previous values.

Prepend Device Name when Generating Security Context Names

Whether the name of the device that contains the security context should be added to the front of the security context’s name. For example, if a security context is named admin, and it is contained in the device with the display name 10.100.15.16, the name that will appear in the Device selector is 10.100.15.16_admin.

If you do not prepend the device name, the security context name appears in the inventory by itself. Because Security Manager does not place security contexts in a folder related to the parent device, the only way to easily see contexts that are related to a device is to prepend the device name.

If you do not prepend device names, Security Manager adds a numbered suffix to distinguish identically named devices. For example, if the admin context exists in more than one firewall, you will see admin_01, admin_02, and so on, in the Device selector.

Purge Discovery Tasks Older Than

The number of days to save discovery and device-import tasks. Tasks older than the number of days you enter are deleted.

Reuse Policy Objects for Inline Values

Whether to substitute any named policy objects, such as network/host or identity user group objects already defined in Security Manager, for inline values in the CLI. For more information on policy objects, see Chapter 6, “Managing Policy Objects”.

Allow Device Override for Discovered Policy Objects

For the types of objects for which overrides are possible, whether to allow users to override the parent object values at the device level for policy objects that are discovered. For example, if you select this option, if you run policy discovery on a device that has an ACL with the same name as an ACL policy object in Security Manager, the name of the discovered policy object is reused, but a device-level override is created for the object. If you deselect this option, a new policy object is created with a number appended to the name.

For more information, see Understanding Policy Object Overrides for Individual Devices.

On Error, Rollback Discovery for Entire Device

Whether Security Manager should roll back all discovered policies if even one error is encountered for a single policy during policy discovery. When deselected, Security Manager keeps the policies successfully discovered and discards only those policies with errors. For more information on policy discovery, see Discovering Policies.

Auto-Expand Object Groups with Prefixes

Expands object groups, such as network or identity user group, with the listed prefixes during the device import process. Separate the prefixes with a comma. This expansion causes the elements of the object group to display as separate items in the discovered policies. For more information, see Expanding Object Groups During Discovery.

Save button

Saves your changes.

Reset button

Resets changes to the previously applied values.

Restore Defaults button

Resets values to Security Manager defaults.

Enable Event Management

Whether to enable the Event Manager service, which allows Security Manager to collect event information. If you disable this feature, you cannot use the Event Viewer or Report Manager applications.

Event Data Store Location

The directory to use for collecting event information. This is known as the primary event store. Click Browse to select a directory on the Security Manager server.

If the directory does not yet exist, create it in Windows Explorer. You cannot create the directory from within Security Manager.

Event Data Store Disk Size

The amount of disk space you want to allocate for storing event data, in gigabytes (GB). Events are incrementally deleted (rotated out) from the extended store when it becomes 90% full. Before changing this setting, consider the following:

• If you reduce the size below the amount of disk space already used by event data, the oldest events are deleted until your new size limit is reached.
• You can see a visual representation of the amount of space currently used for event data. Open the Event Viewer (Launch > Event Viewer), then from Event Viewer, select Views > Show Event Store Disk Usage.

Event Syslog Capture Port

The port on which you want to enable syslog event capture. The default is 514.

You must ensure that the Security Manager server, and intervening firewalls, allow incoming traffic on this port for Security Manager to collect the events. Managed devices must be configured to send syslog information to this port on the Security Manager server.

Event Data Pagination Size

The maximum number of events per page each query response can contain. The default is 20000, but you can select a different size from the list of supported values.

Note In Security Manager 4.10, the maximum number of events per page has been increased to 100000.

Auto Copy Events to Extended Store

Whether you want to define an extended storage location for event storage. Events are copied from the regular event storage location to the extended location so that they remain available for use. When you query for historical events in Event Viewer, events in the extended storage location are automatically retrieved if they are needed.

Extended Data Store Location

The location of the extended data store for events. This location can be on directly-attached storage that appears as a drive on the server and that uses DAS protocols. For example, SAN storage attached through fiber channel. CIFS storage is not supported. Click Browse to select the desired drive and directory.

Tips

• When you select an extended storage location and save your changes, Security Manager checks that it can be accessed and that it has write permissions. The primary storage location is used as a reference, and any data that exists in the primary storage location that does not exist in the extended storage location is copied to the extended storage location. Any data that already exists in the extended storage location is not evaluated and is left untouched, although it can be deleted later to make room for new data.
• If you change the extended data store location, you cannot query events that exist only in the previous extended data store location (that is, you cannot query events that have already be removed from the primary location). If you want to preserve these events, copy the data from the old location to the new location.

Extended Data Store Disk Size

The amount of space you want to allocate to the extended event storage location, in gigabytes (GB). Events are incrementally deleted (rotated out) from the extended store when it becomes 90% full. The size must be equal to or larger than the primary event data storage location.

You can see a visual representation of the amount of space currently used for event data. Open the Event Viewer (Launch > Event Viewer), then from Event Viewer, select Views > Show Event Store Disk Usage.

Error Notification Email IDs

The email addresses that should receive notifications if problems arise with the use of the extended storage location. Separate multiple addresses with commas. For notifications to be sent successfully, you must also configure an SMTP server as described in Configuring an SMTP Server and Default Addresses for E-Mail Notifications.

The message indicates the problem, cause, and recommended action. For example, you get notifications if the extended storage is chronically unreachable, if data copy fails repeatedly, or if a partition was deleted from the primary storage area before it could be copied to the extended storage area (which might happen if the storage is chronically unreachable or if there are persistent copy problems).

Process Syslogs from Failover Standby Device

Enables or disables processing of syslog messages from the standby ASA. When enabled, syslog messages generated by the standby or failover ASA will be displayed in the Device Identifier column in the Event Monitoring window.

Note By default, the processing of syslog messages from the standby ASA is disabled.

Note Staring with version 4.13, Cisco Security Manager supports syslogs over IPv6 in Event Viewer but the Syslog Relay Service will not be supported for syslogs over IPv6.

Enable Syslog Relay Service

Enables or disables the Syslog Relay Service. Select the Enable Syslog Relay Service check box to enable the fields required for configuring the Syslog Relay Service.

Syslog Relay Capture Port

Specifies the UDP port on which the Syslog Relay Service listens for syslogs. The default is 514.

If the Syslog Relay Service is enabled, devices must send syslogs to the Syslog Relay Capture Port so that they can be forwarded to the local collector and remote collectors. If the Syslog Relay Service is turned off, devices should send syslogs to the Event Syslog Capture Port.

Note The Syslog Relay Capture Port and the Event Syslog Capture Port cannot be the same. When enabling the Syslog Relay Service, if devices are currently configured to send syslogs to the Event Syslog Capture Port, you should instead use that port number for the Syslog Relay Capture Port and then change the Event Syslog Capture Port to something else.

You must ensure that the Security Manager server, and intervening firewalls, allow incoming traffic on this port for Security Manager to collect the events. Managed devices must be configured to send syslog information to this port on the Security Manager server.

Relay to Local Event Collector

Enables or disables syslog relay for the local event collector.

Relay to Remote Collector 1

Enables or disables syslog relay for Remote Collector 1.

Collector 1 IP address

Specifies the IP address to which syslogs should be sent for Remote Collector 1.

Collector 1 Syslog Capture Port

Specifies the UDP port on which Remote Collector 1 is listening for relayed syslogs.

Relay to Remote Collector 2

Enables or disables syslog relay for Remote Collector 2.

Collector 2 IP address

Specifies the IP address to which syslogs should be sent for Remote Collector 2.

Collector 2 Syslog Capture Port

Specifies the UDP port on which Remote Collector 2 is listening for relayed syslogs.

Device Filter

You can filter the devices for which syslogs should be relayed for a specific collector. Using this feature, you can configure syslogs for one set of devices to go to one collector and syslogs for a different set of devices to go to another collector:

1. Select the tab (Local Collector, Remote Collector 1, or Remote Collector 2) for which you want to filter devices.

2. To specify the devices for which you want relay syslogs for this collector, select Permit Relay. If instead you want to specify the devices for which you want to disable syslog relay for this collector, clear the Permit Relay check box. If the Permit Relay check box is not selected, then syslogs for the devices you add to the filter will not be relayed; however, syslogs for all other devices will be relayed.

Note For each enabled collector, syslog relays from all devices are enabled by default.

Note When adding a cluster to the filter list, the IP addresses for the cluster management pool will be included as part of filter configuration.

3. Select the devices or device groups from the Available Devices list that you want to add to the filter and click >> to move them to the Selected Devices list. For more information on selecting devices, see Using Selectors.

4. To add a device that is not managed in Security Manager, enter the IP address of the device in the Add Special Device field and then click the bottom >> to move the device to the Selected Devices list.

Restart

Restarts the Syslog Relay Service.

CPU Throttle Settings

Opens the CPU Throttling Policy dialog box in which you can control the CPU load used by the syslog relay service. For more information, see CPU Throttling Policy Dialog Box.

View Statistics

Opens the Syslog Relay Statistics dialog box in which you can see the average CPU and memory usage of the syslog relay service process as well as traffic rates for the different collectors. For more information, see Syslog Relay Statistics Dialog Box.

Save button

Saves and applies changes.

Most changes related to the Event Viewer settings require that the Event Manager service briefly stop and then restart. If you change whether the service is enabled, it stops or starts, as appropriate. You are shown a progress indicator.

Changes to Syslog Relay Service settings require that the Syslog Relay Service briefly stop and then restart. If you change whether the service is enabled, it stops or starts, as appropriate.

Reset button

Resets changes to the last saved values.

Restore Defaults button

Resets values to Security Manager defaults.

Enable Health and Performance Monitor

Lets you enable or disable the Health and Performance Monitoring service, which allows Security Manager to collect event information. If you disable this feature, you cannot use the HPM application.

Note To receive email notifications make sure that an SMTP server has been configured on the Security Manager Server. For more information, see, Configuring an SMTP Server and Default Addresses for E-Mail Notifications

Cisco Security Manager considers an out-of-band (OOB) change to be any change made to a device manually or outside of Security Manager control, for example, by logging into the (monitored) device directly and entering configuration commands through the CLI. For devices monitored by the HPM application, Cisco Security Manager monitors the OOB changes, detected by the HPM periodically. If any out-of-band changes are detected, HPM generates an alert displayed on the Device Status View page and sends an email, to the configured recipients.

Note If a Cisco Security Manager restart occurs during the update time, after an OOB change is detected and an email notification has already been sent, the same email maybe sent again after Cisco Security Manager starts up.

Enable OOB Email Notification

Lets you enable or disable email notifications for Out of Band changes.

Note When the email notification is disabled, only an alert is displayed on the Device Status View page.

Note When HPM detects the OOB change and syncs with the Configuration Manager, a separate email alert notification is sent for each device being monitored. To prevent duplication, emails sent for each OOB change are tracked and stored in a file, once in 5 minutes.

Recipient E-mail(s)

Specify the recipients who must be notified of the OOB change.

Save button

Saves and applies changes.

Most changes require that the Health and Performance Monitoring service briefly stop and then restart. If you change whether the service is enabled, it stops or starts, as appropriate. You are shown a progress indicator.

Reset button

Resets changes to the last saved values.

Enable Report Manager

Lets you enable or disable the Report Manager service. If you disable this feature, you cannot use the Report Manager application.

Save button

Saves and applies changes.

If you change whether the service is enabled, it stops or starts, as appropriate. You are shown a progress indicator.

Reset button

Resets changes to the last saved values.

Domain-AD Server Group Mapping table.

Each row in the table defines the Active Directory (AD) server group to use for a NetBIOS domain for use with identity-aware firewall policies on ASA devices.

• To add an entry, click the Add Row (+) button and fill in the Add AD Domain Server dialog box. See Domain AD Server Dialog Box. You need to enter the domain name and select the AAA server group object that specifies the LDAP AD servers.
• To edit an entry, select it and click the Edit Row (pencil) button.
• To delete an entry, select it and click the Delete Row (trash can) button.
• To test whether Security Manager can successfully contact the servers defined in a server group, select the row and click Test.

Default Domain

The NetBIOS domain to use when you do not type in a domain when specifying a user or group name in a firewall policy or an identity user group policy object.

The default is LOCAL, which means the name is defined on the ASA itself, either as a local user or as a VPN user who was authenticated by a means other than an LDAP server group associated with a domain name.

Other than LOCAL, only domains configured in the Domain-AD Server Group Mapping table appear in this list.

Route query via

When you use the Find feature while selecting users or user groups, Security Manager must query the AD server. Select whether the query comes from the Security Manager client (the workstation on which you are running the client) or the server.

By default, LDAP queries come from the client.

For user strings without domain

If you select something other than LOCAL for the default domain, how to handle username or user group names that you type in without a domain name:

• Auto determine user/user-group from AD —Check the AD server associated with the default domain to determine whether the name is for a user or user group, and add the appropriate string: Default-Domain\user or Default-Domain\\user-group. If the name cannot be found, you must manually type in the domain name and the one or two \ characters to indicate whether the name is for a user or a group.
• Change it to Default-Domain/user —Assume that typed in names are user names, not user group names, and add the default domain: Default-Domain\user.

Save button

Saves your changes.

Reset button

Resets changes to the previously applied values.

Restore Defaults button

Resets values to Security Manager defaults.

Edit CCO Settings

Use the Edit CCO Settings link to quickly navigate to the CCO Settings page. For information on the CCO Settings page, see CCO Settings Page.

Purge Jobs Older Than

Enter the length of time in days to hold Image Manager jobs before purging them. The default is 365 days. Select Purge Now to immediately clear previous Image Manager job specifications.

Include Repository

If checked, the image repository is part of Security Manager backup. The default is to exclude images.

Save button

Saves your changes.

Reset button

Resets changes to the last saved values.

Restore Defaults button

Resets values to Security Manager defaults.

Edit CCO Settings

Credentials for connecting to Cisco.com are required for automatic updates of the GeoIP database. You can use the Edit CCO Settings link to quickly navigate to the CCO Settings page where these credentials are configured. You can also configure settings for a proxy server on the CCO Settings page. For information on the CCO Settings page, see CCO Settings Page.

Enable Reverse DNS (FQDN) Lookup Service

Whether to enable or disable the Reverse DNS (FQDN) lookup service. Enable this service if you want to be able to determine the fully qualified domain name (FQDN) for an IPv4 address using the IP Intelligence tool.

Use CSM Server’s DNS Server

Select this option to use the DNS server defined on the Cisco Security Manager server for reverse DNS lookup requests.

Use custom DNS servers

Select this option to manually specify the DNS servers to use for reverse DNS lookup requests. You can enter up to three DNS server addresses in the fields provided.

Note Security Manager does not support the use of external DNS servers configured inside of a virtual machine.

Enable Load Balancing

Whether to distribute reverse DNS lookup requests amongst the DNS servers when multiple DNS servers are available.

Default Blocking Ranges

Lists the IP address ranges that are excluded from Reverse DNS lookup by default:

0.0.0.0, 255.255.255.255, 127.0.0.1, 169.254.0.0-169.254.255.255, 224.0.0.0-239.255.255.255

User-defined Blocking Ranges

Specifies additional IP addresses or address ranges that should be excluded from reverse DNS lookup requests. Click the Edit (pencil) button to open the Edit IPv4 Blocking Range Addresses dialog box in which you can specify the IPv4 addresses or address ranges to be excluded. Separate multiple entries using a comma ",".

Enable GeoIP Lookup Service

Whether to enable or disable the GeoIP lookup service. Enable this service if you want to be able to retrieve geographic location information for an IPv4 address using the IP Intelligence tool.

Note You will need to download the geographic location database from Cisco.com before GeoIP information will be included in the IP intelligence data. You will also need to download the geographic location database from Cisco.com after restoring the Security Manager database from a backup. Beginning with version 4.9, Security Manager mandates you to read and accept the End User License Agreement (EULA) before you can proceed to downloading updates from cisco.com.

GeoIP Manual Upload

Use the GeoIP Manual Upload fields to update the geographic location database in Security Manager using a MaxMind GeoLite City update package downloaded from Cisco.com.

Note New update packages are made available on Cisco.com on a monthly basis.

GeoIP Database Artifact Location

Click Browse and then navigate to and select the MaxMind GeoLite City update package that you downloaded from Cisco.com. Then, click Upload to upload the selected database to Cisco Security Manager.

Note Geolocation updates obtained directly from MaxMind or any other source are not supported in Cisco Security Manager.

GeoIP Maxmind Database Update Settings

MaxMind GeoLite City update packages are updated monthly on Cisco.com. Use the GeoIP Maxmind Database Update Settings to download an update package automatically from Cisco.com and to configure scheduled updates.

Note Credentials for connecting to Cisco.com are required for automatic updates of the geographic location database. You can use the Edit CCO Settings link to quickly navigate to the CCO Settings page where these credentials are configured. For information on the CCO Settings page, see CCO Settings Page.

Run immediate database update

Click Update Now to update the geographic location database in Security Manager using the latest update package from Cisco.com.

Enable scheduled update

Whether to enable or disable automatic updates of the geographic location database on a regular schedule. After enabling scheduled updates, click Edit Settings to specify the schedule for when the update should take place.

Using the Weekly option, you can specify the days of the week on which the automatic update should take place. Using the Monthly option, you can specify the day of the month on which the automatic update should take place. For either option, you can specify the time of day that the update should take place.

Note Beginning with version 4.9, Security Manager mandates you to read and accept the End User License Agreement (EULA) before you can proceed to downloading updates from cisco.com.

Default Blocking Ranges

Lists the IP address ranges that are excluded from GeoIP lookup by default:

0.0.0.0, 255.255.255.255, 127.0.0.1, 10.0.0.0-10.255.255.255, 169.254.0.0-169.254.255.255, 172.16.0.0-172.31.255.255, 192.168.0.0-192.168.255.255, 224.0.0.0-239.255.255.255

User-defined Blocking Ranges

Specifies additional IP addresses or address ranges that should be excluded from GeoIP lookup requests. Click the Edit (pencil) button to open the Edit IPv4 Blocking Range Addresses dialog box in which you can specify the IPv4 addresses or address ranges to be excluded. Separate multiple entries using a comma ",".

Enable Whois Lookup Service

Whether to enable or disable the Whois lookup service. Enable this service if you want to be able to retrieve WHOIS information for an IPv4 address using the IP Intelligence tool.

Enable External Proxy

Whether to enable or disable use of an external proxy for Whois requests. Proxy server configuration is specified on the CCO Settings page.

Default Blocking Ranges

Lists the IP address ranges that are excluded from Whois lookup by default:

0.0.0.0, 255.255.255.255, 127.0.0.1, 10.0.0.0-10.255.255.255, 169.254.0.0-169.254.255.255, 172.16.0.0-172.31.255.255, 192.168.0.0-192.168.255.255, 224.0.0.0-239.255.255.255

User-defined Blocking Ranges

Specifies additional IP addresses or address ranges that should be excluded from Whois lookup requests. Click the Edit (pencil) button to open the Edit IPv4 Blocking Range Addresses dialog box in which you can specify the IPv4 addresses or address ranges to be excluded. Separate multiple entries using a comma ",".

View Statistics

Opens the IP Intelligence Statistics dialog box which shows statistics for the IP Intelligence feature. Information provided in the IP Intelligence Statistics dialog box includes:

• Average number of IP Intelligence lookup requests during the last 5 minutes and last 15 minutes
• Average lookup time for all IP Intelligence service requests
• Average lookup times for each individual service that is currently enabled
• Counts of the number of lookups, both successful and failed, for each individual service that is currently enabled
• Cache hit ratios for each individual service that is currently enabled
• Upload information for GeoIP updates: last update time, status, and version information for the update

Click Refresh to update the data in the IP Intelligence Statistics dialog box.

Save button

Saves your changes.

Reset button

Resets changes to the last saved values.

Restore Defaults button

Resets values to Security Manager defaults.

Enable Eventing Email Notification

Select to enable notification of IPS events through email.

Notification Interval (15 - 60 minutes)

Enter the interval at which you want Security Manager to send email notifications for IPS events or critical events.

Note If Security Manager receives more than 50000 events during the configured time interval, only the first 50000 events are selected and sent through email.

Email IDs (for IPS Events)

Enter one or more email addresses (comma separated).

Select Severity of Events

The severity level that the IPS signature reports: High, Medium, Low, or Informational. By default, High and Medium severity are selected.

Notification Content

Whether to send summarized or detailed notifications through email. If you select Detailed Notifications, select the fields that you want information for, in the email notification. Some fields are selected by default.

Event ID

A unique sequential number for each event, assigned internally.

Severity

The Firewall or IPS severity values.

Device

The source of the event; usually the device ID.

A device identified as Not Available has been deleted from the Security Manager inventory.

Application Name

The name of the application originating the event.

Receive Time

The time the event was received by Security Manager.

Event Time

The time the event was generated by the device.

Sensor Local Time

The local time of the sensor where the event originated.

Sig ID

The Sig ID value is used by the alert originator to identify the activity. It identifies the pre-defined signature defined for this activity.

Sub Sig. ID

Identifies the unique numerical value assigned to the sub signature. The Sub Sig. Id identifies a more granular version of a broad signature.

Sig. Name

The name assigned to the signature.

Sig. Details

The details of the reported signature that was triggered and resulted in the generation of the alert.

Sig. Version

The version of the signature definition used to generate an alert.

Attacker IP

The IP address of the host that sent the offending packet.

Attacker Port

The port used by the attacker host. This is the port from which the offending packet originated.

Attacker Locality

Identifies whether the attacker address is located inside or outside of a given network, as specified by the intrusion detection device’s configuration.

Victim IP

The IP address of the host being attacked.

Victim Port

The port of the host being attacked (the recipient of the offending packet). This is the port to which the offending packet was sent.

Victim OS

The OS of the host being attacked.

Victim Locality

Identifies whether the target address is located inside or outside of a given network, as specified by the intrusion detection device’s configuration.

Summary Count

Specifies that this is a summary alert, representing one or more alerts with common characteristics. The numeric value indicates the number of times the signature fired since the last summary alert with a matching initialAlert attribute value.

Initial Alert

This field applies to a summary alert, representing one or more alerts with common characteristics. The value of InitialAlert provides the event ID of the last nonsummary evIdsAlert with the same characteristic (sigid/ subsigid).

Summary Type

Defines the common characteristics of all alerts in a summary alert.

Is Final

Applies to a summary alert, representing one or more alerts with common characteristics. It indicates whether this is the last event alert containing the same value in the initialAlert attribute.

Interface

Name of the IPS interface.

VLAN

The VLAN number associated with packets involved in the activity that triggered the alert.

Virtual Sensor

The name of the virtual sensor associated with the event.

Action Taken

The action performed on the flow. For example: Terminated or denied.

Alert Details

The details regarding the alerts.

Risk Rating

A value that represents the calculated risk associated with the event.

Threat Rating

The threat rating of the event, if any.

Reputation

The attacker’s reputation score in the range -10.0 to +10.0. A lower (more negative) score indicates a greater likelihood that the host is malicious.

Reputation Details

Deny Attacker: Whether a deny-attacker action occurred (or would have occurred) because an internal override was exceeded due to the calculated risk rating: true or false.

Protocol

The Level-3 or Level-4 protocol.

Enable

Email IDs

Whether to send email notification for critical events. If you select this option, also enter one or more email addresses (comma separated).

Save button

Saves your changes.

Reset button

Resets changes to the previously applied values.

Restore Defaults button

Resets values to Security Manager defaults.

Update Status group

Refresh button

Displays the following items. Click Refresh to update the information.

• Latest Available—The most recent signature and sensor update available on Cisco.com or the local HTTP server when you last checked for updates.
• Latest Downloaded—The most recent signature and sensor update downloaded to Security Manager.
• Latest Applied—The most recent signature and sensor update applied to any device in Security Manager.
• Latest Deployed—The most recent signature and sensor update deployed to any device in Security Manager.
• Last Check On—The time that the last check of Cisco.com was performed.
• Last Download On—The time that the last update was downloaded to Security Manager.
• Last Deployed On—The time that the last update was deployed to any of the devices.

Check for Updates button

Download Latest Updates button

These buttons check for updates, or download signature and sensor updates that have not already been downloaded to the Security Manager server, from the IPS Update server. You must configure an IPS Update server before checking for updates or downloading them (click Edit Settings in the Update Server group).

When you click one of these buttons, a dialog box opens to display the results of the operation. Security Manager logs into the IPS Update server, checks for updates, and downloads them if you clicked the Download button. If a Cisco.com download fails, ensure that the account you are using has applied for eligibility to download strong encryption software. For details, see the description of User Name in Edit Update Server Settings Dialog Box.

Note Beginning with version 4.9, Security Manager mandates you to read and accept the End User License Agreement (EULA) before you can proceed to downloading updates from cisco.com.

Update Server group

Displays the settings used to access Cisco.com or the local server that contains the IPS update packages. The fields indicate whether the update server is Cisco.com or a locally-configured HTTP server, the name of the local server if you are using one, the user account for logging into the server, and the name of the proxy server, if any. To configure or change the IPS Update server, click Edit Settings to open the Edit Update Server Settings dialog box (see Edit Update Server Settings Dialog Box).

For more information, see Configuring the IPS Update Server

Beginning with version 4.4, Security Manager has a certificate trust management feature. This feature helps you with improved handling of Cisco.com certificates. For detailed documentation of this feature, refer to Certificate Trust Management.

Signature Filter Settings group

Enables you to download IPS signature updates selectively. Click Edit Settings to open the Edit Signature Download Filter Settings dialog box (see Edit Signature Download Filter Settings Dialog Box).

Auto Update Settings group

Contains the settings specific to automatic updates. For more information, see Automating IPS Updates.

Auto Update Mode

Establishes whether, and to what extent, automatic updates are performed. Contains the following options:

• Download, Apply, and Deploy Updates
• Disable Auto Update
• Check for Updates
• Download Updates
• Download and Apply Updates

By default, auto update is disabled. The other options are a combination of one or more of the following options:

• Check for Updates—Security Manager contacts the IPS Update server to check if an update is available and sends e-mail if e-mail notification is configured. No files are downloaded.
• Download Updates—Security Manager downloads the latest updates from the IPS Update server, and sends e-mail notification if e-mail notification is configured.
• Apply Updates—Security Manager modifies the configuration of the devices selected in the Apply Update To list based on the downloaded update packages. You have to separately deploy these updates unless you also select Deploy Updates.
• Deploy Updates—Security Manager starts a deployment job to send the applicable update packages to the devices selected in the Apply Update To list. The device must have the required license for a signature update to be successful.

Update Schedule

Edit Update Schedule button

The schedule for the actions selected in the Auto Update Mode field. To change the schedule, click Edit Update Schedule and define the schedule in the Edit IPS Updates Schedule dialog box. You can specify that Security Manager perform the updates based on hourly, daily, weekly, or monthly schedules, or specify a one-time event. When entering the start time, use the 24-hour clock and the hh:mm format.

Note If you schedule an update to occur in less than 10 minutes from your Security Manager server time, the "Next Update" field will show tomorrow’s date and the job will run accordingly. This is a safety feature designed to guarantee the first occurrence to run.

Notify Email

The e-mail address to which notifications of automatic updates are sent. If you enter more than one address, separate the addresses with commas. A notification is sent when an update:

• Is available for download.
• Has been downloaded.
• Has been downloaded and applied.
• Has been downloaded, applied, and deployed.

Apply Update To

Type

Edit Row button

Devices to be Auto Updated

The selector includes the IPS devices that have local signature policies and the shared signature policies that are defined in Security Manager. The columns in the selector indicate whether a local device policy or a shared policy is selected for these types of updates:

• Signature—For auto updating the signature update level.
• Minor—For minor updates and service packs.
• S.P.—For service pack updates.

For shared policies, a partial grey checked box indicates that some, but not all, of the devices that use the policy are selected. If you change the devices assigned to the shared policy between automatic update events, the shared policy is grayed out, and only the old assignments are shown on this page. After the update runs, the assignment list will be synchronized with the shared policy device assignments. To update the device list proactively prior to the next auto update run, select the policy and edit it (to select auto update settings), and the device assignment list will be corrected.

Note Also for shared policies: You can select only the shared policy assigned to the default virtual sensor (vs0). If you attempt to select the shared policy for a different virtual sensor, your changes will not be applied, and you will not receive an error message.

Use the Type field to toggle between viewing local and shared policies. Changing the view does not change your auto update selections.

To select a local or shared policy for auto update, select it in the selector and click the Edit Row button below the selector. This opens the Edit Auto Update Settings dialog box, where you can select the types of updates for the policy. When you select any type of auto update for a policy, the affected devices are listed in the Devices to be Auto Updated list to the right of the selector.

Save button

Saves your changes.

Reset button

Resets changes to the last saved values.

Restore Defaults button

Resets values to Security Manager defaults.

Enable ISE feature

Whether to enable communication with the ISE.

Username

The username Security Manager should use to log on to the ISE.

Password

The password for the username.

ISE Server (IP Address/Hostname)

The DNS hostname or IP address of the ISE.

ISE Version

Beginning with version 4.18, Cisco Security Manager supports integration of only ISE version 2.3.

Test Connectivity

Click Test Connectivity to ensure that Security Manager can communicate with the ISE given the settings you have entered.

Save button

Saves your changes.

Reset button

Resets changes to the previously applied values.

Restore Defaults button

Resets values to Security Manager defaults.

CSM tab

The license settings for the Security Manager application. For a description of the fields on this tab, see CSM Tab, Licensing Page.

IPS tab

The license settings for IPS devices managed by Security Manager. For a description of the fields on this tab, see IPS Tab, Licensing Page.

Manual Purging

Keep Audit Log in DB For (days)

The maximum number of days of Audit Log entries that has to be stored in the database before deleting it.

Keep Audit Log in DB For Last (entries)

The maximum number of audit log entries to be stored in the database. If an entry becomes older than the number of days specified in the Keep Audit Log For field, it is deleted even if the log has fewer than the maximum number of entries.

Purge Now

To delete the old entries from the database, click Purge Now. Based on the values entered in the Keep audit log in DB for Last (days) and Keep audit log in DB for Last (entries) fields, the audit log entries that is maximum gets deleted.

For example, if the value for Keep audit log in DB for Last (days) is 5 and Keep audit log in DB for Last (entries) is 5000, and last 5 days log entries is more than 5000, then Cisco Security Manager keeps the last 5000 entries and deletes the older entries even if they belong to the last 5 days.

Note The Purge Now button only removes audit report entries from the database. It does not remove the *.csv files from the <install_dir>\CSCOpx\MDC\log\audit folder. These *.csv files can be deleted directly.

Keep Audit Log File For (days)

Number of days an audit log file should be retained in the system.

Purge Now

Click this button to immediately delete the specified older audit log files.

Note The Purge Now button deletes the CSDL Audit log files from <install_dir>\MDC\log\CSDL Audit Log folder along with Audit log files from <install_dir>\MDC\log\audit folder.

Keep Operation Log Files For (days)

The number of days that Security Manager keeps operation logs before deleting them. These logs are used for debugging purposes.

Purge Now button

Click this button to immediately delete the specified older operation log files.

Scheduled Purging

Enable Scheduled Purging for Audit Log Database Entries

Click this check box to scheduled the purging of older log entries. The schedule options are enabled on clicking this check box.

Keep Audit Log in DB For (days)

The maximum number of days of Audit Log entries that has to be stored in the database before deleting it.

Keep Audit Log in DB For Last (entries)

The maximum number of audit log entries to be stored in the database. If an entry becomes older than the number of days specified in the Keep Audit Log For field, it is deleted even if the log has fewer than the maximum number of entries.

Enable Scheduled Purging for Audit Log Files

Click this check box to schedule purging of audit logs from the system.

Keep Audit Log File For (days)

Number of days an audit log file should be retained in the system.

Enable Scheduled Purging for Operation Log Files

Click this check box to schedule purging of operation logs from the system.

Keep Operation Log Files For (days)

The number of days that Security Manager keeps operation logs before deleting them. These logs are used for debugging purposes.

Log Level

The level of information, according to severity, that you would like collected in the operation logs. Each level collects different amounts of data. For example, the Info level yields the most data, and the Severe level collects the least.

Save button

Saves your changes.

Reset button

Resets changes to the previously applied values.

Restore Defaults button

Resets values to Security Manager defaults.

Policies to Manage

The policy types are organized in folders, with router and firewall (which includes all ASA, PIX, and FWSM devices) handled separately, and then by category (NAT, Interfaces, and Platform). Select or deselect policy types as desired and click Save. Deselecting the check box for a group of policies deselects all policies in that group. By default, all policies are selected.

Note Beginning with version 4.18, Cisco Security Manager provides support for ASA 9.10(1) devices that are configured on the Umbrella server.

Display a warning on all shared policies and imported objects

Whether to add a message to all shared policies and to objects that were imported using the File > Import command. If you select this option, messages appear on the following:

• All shared policies, whether they were imported or locally created.
• Policy objects that were created by importing devices or shared policies using the File > Import command, but not imported policy objects created by the PolicyObjectImportExport.pl command (described in Importing and Exporting Policy Objects.

If you regularly import shared policies, the imported policies and objects replace any same-named policies and objects, so any changes made locally are removed. This message can notify users that policies might be imported and help users identify policy objects that they might not want to edit.

Save button

Saves your changes.

If you are unmanaging a policy, you are shown a list of devices that have the policy assigned to them. Security Manager must be able to obtain the required locks to unassign the policy from all devices, or you must manually unassign the policies (or remove the locks) before unmanaging the policy.

If you are managing a previously unmanaged policy, be sure to rediscover all affected devices to bring the existing configurations into Security Manager.

Reset button

Resets changes to the previously applied values.

Restore Defaults button

Resets values to Security Manager defaults.

When Redundant Objects Detected

The action you want Security Manager to take when you try to create a policy object that has the same definition as an existing object:

• Ignore—You can freely create objects with identical definitions. Any conflicts are ignored by Security Manager.
• Warn—Security Manager displays a warning if you attempt to create an object that is identical to an existing object. You may proceed to create the object, if you wish.
• Enforce—Security Manager prevents you from creating an object that is identical to an existing object. An error message is displayed.

Default Source Ports

The port range value that is used as the default source port range for service objects. You can choose one of the following:

• Use all ports—Includes all ports from 1 to 65535.
• Use secure ports—Includes all ports from 1024 to 65535.

If you change the default source ports, you must manually redeploy any previously deployed devices that might be affected. These changes might not be reflected in any open activities until you refresh the data.

For more information on port list objects, see Configuring Port List Objects.

Enable AutoComplete Dropdown Box

Whether to have Security Manager list matching service and port list names as you type them when you create a service. You can then easily select from names you have already defined. If you deselect AutoComplete, you have to remember the complete service and port list names and type them in yourself.

Save button

Saves your changes.

Reset button

Resets changes to the previously applied values.

Restore Defaults button

Resets values to Security Manager defaults.

Enable Process Monitoring

When selected, Security Manager will allow you to specify the processes that you want to monitor. You must proceed to configure other process monitoring settings.

By default, the Process Monitoring feature is disabled on the Cisco Security Manager Server.

Note Enabling or disabling the process monitor modifies the Windows registry and may generate a system alert.

Monitoring Interval (in minutes)

Specify the interval, at which, the process will be monitored. Valid values are between 1-60 minutes. The default monitoring interval is 5 minutes.

Note If the monitoring interval is changed, the monitoring task in progress stops and the new monitoring task starts with the updated interval.

Notification Recipient(s) E-mail(s)

Enter email IDs for the notification recipients.You can enter multiple email IDs, separated by a comma. These are the recipients that will be notified, when a process being monitored, stops.

Maximum Mail Alerts

Enter the maximum number of emails that will be sent to the recipients during the course of Security Manager runtime. The default value here, is 10.

Process List

Select one or more processes that you want to monitor. Whenever any of these selected processes stop, a notification email will be sent to the specified recipients.

Note When Event Management, Health and Performance Monitor and Report Manager are disabled from Tools > Security Manager Administration, email notifications will not be sent, even if, the VmsEventServer, CsmHPMServer and CsmReportServer processes are enabled in the process monitoring settings page.

Save button

Saves your changes.

Reset button

Resets changes to the previously applied values.

Restore Defaults button

Resets values to Security Manager defaults.

Enable for Prime Security Manager

[checkbox] Lets you enable or disable the SSO feature for Prime Security Manager. When disabled, the shared key is retained.

Enable for FireSIGHT Management Center

[checkbox] Lets you enable or disable the SSO feature for FireSIGHT Management Center. When disabled, the shared key is retained.

Shared Key for Single Sign-on

Use the features in this section to generate and view an encryption key for cross-launching Prime Security Manager or FireSIGHT Management Center.

Click the Generate button to randomly generate a 128-bit AES key, which is then displayed as a 32 hexadecimal string in the SSO Shared Key field.

Note This key must be provided when configuring single sign-on cross-launching in Prime Security Manager or FireSIGHT Management Center. Also, each allowed Security Manager user must be configured in the Prime Security Manager database or the FireSIGHT Management Center user database with the same username as that in the Security Manager user database (the password can be different).

Notify Email

The default e-mail address that should receive notifications of rule expiration. Users can override this address when configuring individual rules.

Notify Before Expiration

The default number of days before a rule expires that Security Manager should send the e-mail message. Users can override this value when configuring individual rules.

Sender

The e-mail address that Security Manager will use for sending e-mail notifications.

Email Format

The format of the e-mail message:

• Text—The e-mail is sent in HTML and plain text formats.
• XML—The e-mail is sent using an XML markup. This option might be appropriate if you decide to write a program to automatically process and respond to notifications.

Save button

Saves your changes.

Reset button

Restores all fields to their previous values.

Restore Defaults button

Resets values to Security Manager defaults.

AAA Setup button

Opens Common Services and displays the AAA Mode Setup page. From this page, you can set AAA as your fallback sign-on method. For more information about AAA, click Help from the AAA Mode Setup page.

Certificate Setup button

Opens Common Services and displays the Self-Signed Certificate Setup page. CiscoWorks enables you to create self-signed security certificates, which you can use to enable SSL connections between your client browser and management server. For more information about self-signed certificates, click Help from the Certificate Setup page.

Single Sign On button

Opens Common Services and displays the Single Sign-On Setup page. With Single Sign On (SSO), you can use your browser session to transparently navigate to multiple CiscoWorks servers without having to authenticate to each of them. Communication between multiple CiscoWorks servers is enabled by a trust mode addressed by certificates and shared secrets. For more information about setting up SSO, click Help from the Single Sign-On page.

Local User Setup

Opens Common Services and displays the Local User Setup page, from which you can add and delete users, edit user settings, and assign roles or permissions. For more information, click Help from the Local User Setup page and see the Installation Guide for Cisco Security Manager.

System Identity Setup

Opens Common Services and displays the System Identity Setup page. Communication between multiple CiscoWorks servers is enabled by a trust mode addressed by certificates and shared secrets. System Identity setup helps you to create a trust user on servers that are part of a multi- server setup. For more information about system identity setup, click Help from the System Identity Setup page.

Allow logon for user ids not available in Local User Database

For Security Manager installations integrated with an external authentication server like Active Directory, TACACS+, or RADIUS, specifies whether users can log in even when their user name is not defined in the Security Manager user list. When enabled, users are allowed to log in using the default role specified in Role Management Setup. If a default role is not configured, the user is not allowed to log in.

Enable Ticketing

Whether to enable Ticket Management.

System Generated Default Ticket Name

By default, this check box is checked. Clear the check box, if you do not want the ticket name to be appended with the system generated default name. The ticket name field in the activity creation dialog is left blank.

Ticketing System URL

The URL to use for launching an external change management system. When this field is configured, the Ticket ID is a hyperlink that will launch the URL specified. The URL must be formatted as a template that accepts the Ticket ID as part of the URL. The template format uses {0} in place of the actual Ticket ID.

For example, if the URL to launch an external ticket management system for a ticket with the ticket ID of TKT12345 is http://ticketsystem/displayticket?ticketid=TKT12345, then the template URL you would use would be http://ticketsystem/displayticket?ticketid={0}.

When you create a ticket, the Ticket ID you specify will be used in the hyperlink in place of the {0}.

Generate

Click to display the Generate Template URL dialog box that can be used to create a Ticketing System URL.

Using the example above, you would enter TKT12345 in the Ticket ID field and http://ticketsystem/displayticket?ticketid=TKT12345 in the Ticket URL field. When you click OK, the appropriate template URL is created and entered into the Ticketing System URL field.

Ticket History

Ticket History settings are only available in non-Workflow mode. In Workflow mode, purge settings are controlled via the settings for Activities (see Workflow Page).

Purge Tickets (including change report) Older than

The number of days that ticket information should be kept in the Ticket Manager table. The default is 30. You can specify from 1 to 120 days.

Click Purge Now to delete all tickets older than the number of days specified.

Purge Change Report older than

The number of days that change reports should be maintained. The default is 30. You can specify a value that is less than the Purge Tickets (including change report) Older than setting.

Click Purge Now to delete all change reports older than the number of days specified.

Save button

Saves your changes.

Reset button

Resets changes to the last saved values.

Restore Defaults button

Resets values to Security Manager defaults.

Server Name or IP Address

The DNS hostname or IP address of the TMS server.

Username

The username Security Manager should use to log on to the TMS server.

Password

Confirm Password

The password for the username. Enter the password in both fields.

Directory in the TMS Server for Config Files

The directory on the TMS server where deployed configuration files will be downloaded. The root FTP directory (“.”) is the default FTP location on the TMS server.

Public Key File Location

The location of the public and private key files on the Security Manager server, as copied from the TMS server. Security Manager uses the public key to encrypt data sent to the TMS server. Then the server uses its private key to decrypt the data. Security Manager comes with a default public key that matches the default private key on the server.

Note If needed, you can generate a new pair of public and private keys using the TMS server. If you do this, you need to copy the new public key to the Security Manager server.

Save button

Saves your changes.

Reset button

Resets changes to the last saved values.

Restore Defaults button

Resets values to Security Manager defaults.

DMVPN tab

Lists the policy types for which you can configure default policies for the Dynamic Multipoint VPN technology.

Large Scale DMVPN tab

Lists the policy types for which you can configure default policies for the Large Scale Dynamic Multipoint VPN technology.

Easy VPN tab

Lists the policy types for which you can configure default policies for the Easy VPN technology.

IPsec/GRE tab

Lists the policy types for which you can configure default policies for the IPsec/GRE VPN technology.

GRE Dynamic IP tab

Lists the policy types for which you can configure default policies for the GRE Dynamic IP VPN technology.

Regular IPsec tab

Lists the policy types for which you can configure default policies for regular IPsec VPN technology.

Regular IPsec VTI tab

Lists the policy types for which you can configure default policies for regular, tunnel-based IPSEC VPN technology.

GET VPN

Lists the policy types for which you can configure default policies for the Group Encrypted Transport (GET) VPN technology.

Remote Access VPN

Lists the policy types for which you can configure default policies for IPsec remote access VPNs.

S2S Endpoints tab

The interface roles that define the default endpoints for internal and external interfaces in site-to-site VPNs.

Enable Workflow

Whether to enable Workflow mode. When Workflow mode is enabled, you can select whether or not to have an approver for activities and deployment jobs.

Require Activity Approval

Whether to require that activities be approved explicitly by an assigned approver. For more information about the differences between working with and without an approver, see Activity Approval.

Submitter can Approve Activity

Activities can be approved by submitter.

Require Deployment & Install Image Approval

Whether to require that deployment jobs and install image jobs be approved explicitly by an assigned approver. For more information about the differences between working with and without an approver, see Understanding Deployment.

Submitter can Approve Deployment Jobs

Deployment jobs can be approved by submitter.

System Generated Default Activity Name

By default, this check box is checked. Clear the check box, if you do not want the activity name to be appended with the system generated default name. The activity name field in the activity creation dialog is left blank.

Sender

The e-mail address that Security Manager will use for sending e-mail notifications.

Activity Approver

The default e-mail address for the person responsible for approving activities. Users can override this address when submitting an activity for approval. For more information, see Submitting an Activity for Approval (Workflow Mode with Activity Approver).

Job/Schedule Approver

The default e-mail address of the person responsible for approving deployment jobs or schedules. Users can override this address when submitting a job or schedule for approval. For more information, see Submitting Deployment Jobs.

Require Deployment Status Notification

Include Job Deployer

Job Completion Notification

Whether to have e-mail notifications sent whenever the status of a deployment job changes. If you select this option, enter the e-mail addresses that should receive notification in the Job Completion Notification field. Separate multiple addresses with commas.

You can also select Include Job Deployer to include the e-mail address of the person who deployed the job on the notification e-mail message.

Keep Activity for

The number of days that activity information should be kept in the Activity table. The default is 30. You can specify from 1 to 180 days.

Click Purge Now to delete all activities older than the number of days specified.

Note If ticketing is enabled in non-Workflow mode, purge settings are controlled via the settings for Tickets (see Ticket Management Page).

Keep Job for

The number of days that deployment job information should be kept in the Deployment Job table. The default is 30. You can specify from 1 to 180 days.

Click Purge Now to delete all jobs older than the number of days specified.

Keep job per schedule for

The number of days that deployment job information should be kept in the Deployment Job table for each job schedule. This setting applies only to jobs that were initiated by a schedule. The default is 30. You can specify from 1 to 180 days.

Click Purge Now to delete all jobs older than the number of days specified.

Save button

Saves your changes.

Reset button

Resets changes to the previously applied values.

Restore Defaults button

Resets values to Security Manager defaults.

Enable users to send messages to others

Whether to enable or disable the Wall feature.

Save button

Saves and applies changes.

Reset button

Resets changes to the last saved values.

Restore Defaults button

Resets values to Security Manager defaults.