User Guide for Cisco Security Manager 4.1
Configuring Security Manager Administrative Settings
Downloads: This chapterpdf (PDF - 370.0KB) The complete bookPDF (PDF - 25.75MB) | Feedback

Configuring Security Manager Administrative Settings

Table Of Contents

Configuring Security Manager Administrative Settings

AutoLink Settings Page

Configuration Archive Page

CS-MARS Page

New or Edit CS-MARS Device Dialog Box

Customize Desktop Page

Debug Options Page

Deployment Page

Device Communication Page

Add Certificate Dialog Box

Device Groups Page

Device OS Management Page

Discovery Page

Event Management Page

IPS Updates Page

Edit Update Server Settings Dialog Box

Edit Auto Update Settings Dialog Box

Licensing Page

CSM Tab, Licensing Page

IPS Tab, Licensing Page

Verifying IPS Devices for License Update or Redeployment

Selecting IPS License Files

License Update Status Details Dialog Box

Logs Page

Policy Management Page

Policy Objects Page

Rule Expiration Page

Server Security Page

Status Page

Add or Edit Status Provider Dialog Box

Take Over User Session Page

Token Management Page

VPN Policy Defaults Page

Workflow Page


Configuring Security Manager Administrative Settings


Security Manager has default settings for many system functions that you can change if they do not fit the needs of your organization. To view and change these settings, select Tools > Security Manager Administration. You can then select items from the table of contents on the left of the window to view the default settings related to that item.

On most pages, when you change a setting, you must click Save to save your changes. If you make a mistake, you can click Reset to return the values to the previously saved values. You can also click Restore Defaults to return the settings to the Security Manager defaults.

Besides the pages that contain system defaults, the Security Manager Administration window includes items that relate to system administration activities, such as taking over another user's work or obtaining access to pages in Common Services to perform server security tasks.

The following topics describe the settings and actions available on each of the pages available in the Security Manager Administration window:

AutoLink Settings Page

Configuration Archive Page

CS-MARS Page

Customize Desktop Page

Debug Options Page

Deployment Page

Device Communication Page

Device Groups Page

Device OS Management Page

Discovery Page

Event Management Page

IPS Updates Page

Licensing Page

Logs Page

Policy Management Page

Policy Objects Page

Rule Expiration Page

Server Security Page

Status Page

Take Over User Session Page

Token Management Page

VPN Policy Defaults Page

Workflow Page

AutoLink Settings Page

The Security Manager Map view provides a graphical view of your VPN and layer 3 network topology. Using device nodes to represent managed devices and map objects to represent unmanaged objects such as devices, clouds, and networks, you can create topology maps with which to study your network. AutoLink settings enable you to exclude any one of five private or reserved networks from Map view. For example, you might want to exclude any test networks that are not relevant to the management tasks you are using Security Manager to perform.

Navigation Path

Click Tools > Security Manager Administration and select AutoLink from the table of contents.

Related Topics

Creating and Managing Layer 3 Links on the Map, page 31-19

Displaying Your Network on the Map, page 31-14

Field Reference

Table 11-1 AutoLink Page 

Element
Description

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.


Configuration Archive Page

Use the Configuration Archive page to define the default settings for the Configuration Archive tool, including how many configuration versions to save and the TFTP server to use for rolling back Cisco IOS software device configurations.

Navigation Path

Click Tools > Security Manager Administration and select Configuration Archive from the table of contents.

Related Topics

Configuration Archive Window, page 8-22

Rolling Back Configurations, page 8-56

Field Reference

Table 11-2 Configuration Archive Page 

Element
Description

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 Page

Use the CS-MARS page to register the Cisco Security Monitoring, Analysis and Response System servers that are monitoring your devices with Security Manager. By registering your CS-MARS servers, you can view messages and events captured in CS-MARS based on a device's firewall access rules or IPS signature rules configured in Security Manager. You must register a CS-MARS server before users can see events collected from it.


Tip If you are using CS-MARS global controllers, add them instead of the individual local controllers. By adding global controllers, Security Manager can identify the correct local controller for a device automatically, without you having to add each of the local controllers. This simplifies your CS-MARS configuration in Security Manager.


Navigation Path

Select Tools > Security Manager Administration and select CS-MARS from the table of contents.

Related Topics

Registering CS-MARS Servers in Security Manager, page 65-23

Field Reference

Table 11-3 CS-MARS Page 

Element
Description

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.


New or Edit CS-MARS Device Dialog Box

Use the New or Edit CS-MARS Device dialog box to register a CS-MARS server with Security Manager. Users can obtain messages or event status for a device's firewall or IPS policies from the CS-MARS server that is monitoring the device. For more information, see Registering CS-MARS Servers in Security Manager, page 65-23.

Navigation Path

From the CS-MARS Page, click the Add button to add a new server, or select a server and click the Edit button.

Field Reference

Table 11-4 Add or Edit CS-MARS Device Dialog Box 

Element
Description

CS-MARS Hostname/IP

The IP address or fully-qualified DNS host name of the CS-MARS server.

Tip If you add a CS-MARS global controller, do not add any of the local controllers that the global controller monitors. Security Manager will automatically determine the local controller that is monitoring a specific device. Adding global controllers simplifies your CS-MARS configuration.

Username

Password

User Type

The username and password for logging into the server to validate that the CS-MARS server is running the appropriate software version and to obtain other basic information. Security Manager also uses this account to determine which CS-MARS server is monitoring a particular device.

For CS-MARS local controllers, you can enter either a global or local user account. For global controllers, you must enter a global account. Identify the type of account in the User Type field.

Certificate Thumbprint

Retrieve From Device button

The CS-MARS server certificate, a hexadecimal string that is unique to the device. Click Retrieve From Device to have Security Manager retrieve the certificate from the CS-MARS server.

If the certificate is retrieved successfully, it is displayed. After verifying the certificate, click Accept to save it on the Security Manager server. You must have a correct certificate to use the CS-MARS server from Security Manager.


Customize Desktop Page

Use the Customize Desktop page to control whether Security Manager applications close automatically after being idle for a specified time, and to reset whether you are prompted to verify your actions in certain circumstances.

Navigation Path

Select Tools > Security Manager Administration and select Customize Desktop from the table of contents.

Field Reference

Table 11-5 Customize Desktop Page 

Element
Description

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.

Save button

Saves and applies changes.

Reset button

Resets changes to the last saved values.

Restore Defaults button

Resets values to Security Manager defaults.


Debug Options Page

Use the Debug Options page to configure the severity level of messages to include in debugging logs and to determine what other debugging information is collected.

You should change debugging levels only if the Cisco Technical Assistance Center (TAC) asks you to change them. This makes it possible for you to include more detailed information in the CSMDiagnostics.zip file.

After you change the message level for the appropriate subcomponent, redo the actions that are resulting in system problems. After the problems occur, create the CSMDiagnostics.zip file by selecting Tools > Security Manager Diagnostics. You can then reset the debug options to the default levels so that the Security Manager server does not become bogged down collecting extra debug information. For more information about generating the CSMDiagnostics.zip file, see Creating a Diagnostics File for the Cisco Technical Assistance Center, page 10-24.

By default, logs contain messages of the Error severity or worse. The severity levels in order of severity are:

Severe—Problems that make the system unusable.

Error—Problems from which Security Manager cannot recover.

Warning—Unexpected conditions from which Security Manager can recover.

Info—Informational messages.

Debug—Internal status information.

Navigation Path

Select Tools > Security Manager Administration, then select Debug Options from the table of contents.

Field Reference

Table 11-6 Debug Options Page 

Element
Description

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.

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 Selecting this check box slows down Security Manager response time. Enable this option only in limited circumstances.

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.

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.

Save button

Saves your changes.

Reset button

Restores all fields to their previous values.

Restore Defaults button

Resets values to Security Manager defaults.


Deployment Page

Use the Deployment page to define the default methods by which Security Manager deploys configurations to devices. You can override some of these settings when you create deployment jobs.

Navigation Path

Select Tools > Security Manager Administration and select Deployment from the table of contents.

Related Topics

Chapter 8, "Managing Deployment"

Chapter 6, "Managing Policy Objects"

Field Reference

Table 11-7 Deployment Page 

Element
Description

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, page 8-9.

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, page 8-11.

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, page 8-12.

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.

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.


Caution You should not select this option unless you are experiencing deployment problems and you are an advanced user.

Allow Download on Error

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

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 from devices during deployment.

Tip Network/host objects that include object NAT configurations on ASA 8.3+ devices are never considered unreferenced.

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 and service 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, ports, and protocols for these devices.

Tip These options do not apply to host, network, or address range network/host objects, or to service objects (as opposed to service group objects), which are always created as objects.

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 and service objects to replace comma-separated values in a rule table cell that resulted when multiple rules were combined. The objects are created during deployment. For more information, see Combining Rules, page 12-19.

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, page 12-30.

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 from devices during deployment.

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.

Generate ACL Remarks During Deployment

(IPv4 and IPv6 access rules.)

Whether to display ACL warning messages and remarks during deployment.

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

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.

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 Communication Page

Use the Device Communication page to define default settings for communicating with devices. These settings mainly affect device inventory and policy discovery and configuration deployment. You can override the transport settings for individual devices in the device properties for the device.

If you change the transport protocol settings, ensure that your devices are appropriately configured to accept those types of connections.

Navigation Path

Select Tools > Security Manager Administration and select Device Communication from the table of contents.

Related Topics

Adding Devices to the Device Inventory, page 3-7

Chapter 3, "Managing the Device Inventory"

Chapter 2, "Preparing Devices for Management"

Viewing or Changing Device Properties, page 3-35

Field Reference

Table 11-8 Device Communication Page 

Element
Description
Device Connection Parameters

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, page 3-4.

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, page 9-4.

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.


Add Certificate Dialog Box

Use the Add Certificate dialog box to add device certificates manually for devices that use the SSL transport protocol (firewall devices, FWSMs, ASAs, IPS devices, and Cisco IOS devices). Adding the device certificates manually gives you the highest level of security because then an intruder is prevented from introducing a fraudulent certificate thumbprint. Device certificates are stored in the database to be used for device authentication.

For more information about manually adding SSL certificates, see Manually Adding SSL Certificates for Devices that Use HTTPS Communications, page 9-4.

Navigation Path

Select Tools > Security Manager Administration, select Device Communication from the table of content, and click Add Certificate.

Field Reference

Table 11-9 Add Certificate Dialog Box 

Element
Description

Host Name or IP Address

The hostname or IP address of the device for which you are adding the certificate.

Certificate Thumbprint

The certificate thumbprint, which is a string of hexadecimal digits that is unique to the device.


Device Groups Page

Use the Device Groups page to manage the device groups and group types defined in the device inventory.

Navigation Path

Select Tools > Security Manager Administration, then select Device Groups from the table of contents.

Related Topics

Understanding Device Grouping, page 3-51

Working with Device Groups, page 3-51

Field Reference

Table 11-10 Device Groups Page 

Element
Description

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.


Device OS Management Page

Security Manager includes shortcut commands to access several key features of Resource Manager Essentials (RME). To enable these commands, you must identify the RME server to Security Manager on this page.

Navigation Path

Select Tools > Security Manager Administration and select Device OS Management from the table of contents.

Related Topics

Resource Manager Essentials Documentation

Managing the Device Operating System, page 3-50

Field Reference

Table 11-11 Device OS Management 

Element
Description

RME server address

The IP address or fully-qualified hostname of the RME server.

For information on the RME version supported for use with Security Manager, see the Release Notes for Cisco Security Manager for this version of the product.

Connect using https

Whether to connect to the RME server using SSL.

Save button

Saves your changes.

Reset button

Restores all fields to their previous values.

Restore Defaults button

Resets values to Security Manager defaults.


Discovery Page

Use the Discovery page to define how Security Manager should handle certain types of objects or events during inventory and policy discovery. You can also control how long Security Manager keeps discovery tasks.

Navigation Path

Select Tools > Security Manager Administration and select Discovery from the table of contents.

Field Reference

Table 11-12 Discovery Page 

Element
Description

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 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 certain types of objects, whether to allow users to override the parent object values at the device level for policy objects that are discovered. 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.

Tip For objects that have subtypes, such as network/host and service, overrides are limited to within a type. For example, an override can be created for a network/host group when discovering a same-named network/host group, but no override would be created when discovering a same-named network/host address range. Instead, the newly-discovered object will have a number appended to the name.

For more information, see Understanding Policy Object Overrides for Individual Devices, page 6-13.

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, page 5-12.

Auto-Expand Object Groups with Prefixes

Expands object groups 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, page 12-31.

Tip This option does not apply to policy objects created from the object network or object service commands from ASA 8.3+ devices. These commands create host, network, or address range network/host objects or service objects.

Save button

Saves your changes.

Reset button

Resets changes to the previously applied values.

Restore Defaults button

Resets values to Security Manager defaults.


Event Management Page

Use the Event Management page to enable event management, which allows you to view ASA, FWSM, and IPS events using the Event Viewer. You can also configure settings required for event collection.

The Event Manager service is also required by the Report Manager application, which allows you to view reports that aggregate information collected by the service.


Tip If you get a message that Event Viewer is unavailable when you select Launch > Event Viewer, but the Enable Event Management option is selected on this page, try restarting the Event Manager Service. First, deselect the Enable option and click Save. Wait for the service to stop. Then, select the Enable option, click Save, and wait for the service to finish restarting. You can then try opening Event Viewer again.


Navigation Path

Click Tools > Security Manager Administration and select Event Management from the table of contents.

Field Reference

Table 11-13 Event Management Page 

Element
Description
Event Management Options

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.

Tip If you change this setting and click Save, you are prompted to confirm that you want to start or stop the Event Manager Service. If you click Yes, the service is started or stopped immediately, and you are shown a progress indicator and told when the change is completed. Wait until the status change is completed before continuing.

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.

Tip If you change the location after you have started using the Event Manager service, you cannot query old events.

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.

Tip If you change this port, you must also change the Syslog Servers policies for all ASA and FWSM devices and security contexts that send events to Security Manager. For more information, see Syslog Servers Page, page 49-20.

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.

Extended Store Management Options

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.

Tip You are prompted to verify that you want to start the extended service and to make changes to the extended storage location.

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, page 1-21.

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).

Save button

Saves and applies changes.

Most changes 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.

Reset button

Resets changes to the last saved values.

Restore Defaults button

Resets values to Security Manager defaults.


IPS Updates Page

Use the IPS Updates page to perform administrative tasks associated with keeping your sensors up to date with regard to signatures, minor version updates, and service packs. You can use the IPS Updates page to:

Monitor update status.

Check the availability of updates and download them.

Configure an IPS update server.

Configure automatic update settings.

Tips

To apply IPS updates manually, select Tools > Apply IPS Update. For more information, see Manually Applying IPS Updates, page 40-7.

If you later decide that you did not want to apply a signature update, you can revert to the previous update level by selecting the Signatures policy on the device, clicking the View Update Level button, and clicking Revert.

Navigation Path

Select Tools > Security Manager Administration and select IPS Updates from the table of contents.

Related Topics

Configuring the IPS Update Server, page 40-4

Checking for IPS Updates and Downloading Them, page 40-5

Automating IPS Updates, page 40-6

Selecting a Signature Category for Cisco IOS IPS, page 41-6

Field Reference

Table 11-14 IPS Updates Page 

Element
Description

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.

Tip If you configure a server, and then try to check for updates, and you are told you did not configure a server, click Save at the bottom of the page and try again.

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, page 40-4

Auto Update Settings group

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

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.

Check for Updates

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.

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.

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.


Edit Update Server Settings Dialog Box

Use the Edit Update Server Settings dialog box to configure the server to use for obtaining IPS updates. If necessary, you can configure a proxy server for communicating with the update server.

Navigation Path

Select Tools > Security Manager Administration > IPS Updates and click Edit Settings in the Update Server group.

Field Reference

Table 11-15 Edit Update Server Settings Dialog Box 

Element
Description

Update From

Whether to get IPS updates from Cisco.com or from a local HTTP/HTTPS server. Your selection changes the fields on the dialog box.

If you select local, you must configure an HTTP or HTTPS server to use as the IPS update server.

IP Address/ Host Name

(Local server only.)

The hostname or IP address of the local IPS update web server.

Web Server Port

(Local server only.)

The port number that your local server listens to for connection requests. The default is 80.

User Name

The username to log into the IPS update server. If you are configuring a local server that does not require a user login, leave this field blank.

If you are specifying a Cisco.com username, the user account on Cisco.com must be eligible for downloading strong encryption software. If you are not certain that the account has the required permissions, use the account to log into Cisco.com and try to download an IPS update file (http://www.cisco.com/cgi-bin/tablebuild.pl/ips5-system). If the account does not have the appropriate permissions, you are prompted to read and accept the required conditions. If you meet the eligibility requirements, you can accept them. Otherwise, talk to your Cisco sales representative for help.

Password

Confirm

The password for the specified username, entered in both fields. If you are configuring a local server that does not require a password, leave these fields blank.

Path to Update Files

(Local server only.)

The path to the IPS update files location on your local server. For example, if update files can be accessed at http://local-server-ip:port/update_files_path/, then enter update_files_path in this field.

Connect Using HTTPS

(Local server only.)

Whether to use SSL when connecting to the local IPS Update server.

Certificate Thumbprint

Displays the certificate thumbprint after it is calculated from the certificate on the local server.

Retrieve From Server

Used to connect to the local server specified in this dialog box, retrieve the certificate from the local server given, and calculate the certificate thumbprint, which is displayed in the Certificate Thumbprint field.

Proxy Server Group

Enable Proxy Server

Whether a proxy server is needed to connect to Cisco.com or to your local server.

IP Address/ Host Name

The hostname or IP address of the proxy server.

You can configure the proxy server to use basic, digest, NT LAN Manager (NTLM) V1, or NTLM V2 authentication. NTLM V2 is the most secure scheme.

Web Server Port

The port number that the proxy server listens to for connection requests. The default is 80.

User Name

The username to log into the proxy server. If the proxy server does not require a user login, leave this field blank.

Password

Confirm

The password for the specified username, entered in both fields. If the proxy server does not require a password, leave these fields blank.


Edit Auto Update Settings Dialog Box

Use the Edit Auto Update Settings dialog box to configure the automatic update options for the device or policy selected in the Apply Update To table on the IPS Updates page. For information on configuring automatic updates, see Automating IPS Updates, page 40-6.

Navigation Path

Select a device or policy on in the Apply Update To table on the IPS Updates page (see IPS Updates Page) and click the Edit Row button.

Field Reference

Table 11-16 Edit Auto Update Settings Dialog Box 

Element
Description

Auto Update

(IPS sensors and shared policies only)

The type of sensor updates to apply to the selected devices or shared policies. You can apply both minor updates and service packs, service packs only, or select None to apply no sensor updates automatically.

Auto Update Signature Update Level

Whether to select the device or policy for automatic signature updates.


Licensing Page

Use the Licensing page to manage licenses for the Security Manager application and for IPS devices. For more information, see Managing IPS Licenses, page 40-1.

Navigation Path

Select Tools > Security Manager Administration and select Licensing from the table of contents.

Field Reference

Table 11-17 Licensing Page 

Element
Description

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.


CSM Tab, Licensing Page

Use the CSM tab on the Licensing page to view the list of installed Security Manager licenses and to install new licenses. For more information, see Installing Security Manager License Files, page 10-14.

Navigation Path

Select Tools > Security Manager Administration, select Licensing from the table of contents, and click CSM.

Field Reference

Table 11-18 CSM Tab, Licensing Page 

Element
Description

License Information

Displays information about the license registered with the product: the edition, license type, expiration date, the number of licensed devices, the number of devices in use, and the percentage of the device count used.

Install License

The list of installed licenses with their installation dates.

Install a License button

Click this button to install a license file. The dialog box that is opened includes links to Cisco.com, where you can obtain licenses if you have not already obtained them. You must copy license files to a local drive on the Security Manager server before you can install them.


IPS Tab, Licensing Page

Use the IPS tab on the Licensing page to view the list of installed IPS device licenses, to install new or updated licenses, or to redeploy licenses. The license list shows current licenses, unlicensed devices, devices with expired licenses, and devices with invalid licenses.

Navigation Path

Select Tools > Security Manager Administration, select Licensing from the table of contents, and click IPS.

Related Topics

Updating IPS License Files, page 40-1

Redeploying IPS License Files, page 40-2

Automating IPS License File Updates, page 40-3

License Update Status Details Dialog Box

Filtering Tables, page 1-37

Table Columns and Column Heading Features, page 1-38

Field Reference

Table 11-19 IPS Tab, Licensing Page 

Element
Description

IPS License Table

Displays all the IPS devices in the device inventory and their license status as of the last time you refreshed the information. Click the Refresh button to obtain the latest information from the devices.

Information includes the serial number for the device, which is used to register for licenses, the license status, and the expiration date of the license. The list shows not only current licenses, but also unlicensed devices, devices with expired licenses, and devices with invalid licenses.

Tip The list does not include Cisco IOS IPS devices. You cannot use Security Manager to manage licenses for routers running IPS.

Update Selected via CCO button

Click this button to update the license file for the selected devices by connecting to Cisco.com and retrieving a new license. When you click this button, a dialog box opens listing devices that can be updated from Cisco.com, which might not be all the devices you selected. Click OK to perform the update. For successful updates, the updated file is automatically applied to the device.

To successfully update the license using this method, you must have a Cisco.com support contract that includes the serial numbers of the selected devices.

Tip The Cisco software license server (SWIFT) that contains the licenses might block requests from the same server for more than 9 licenses within a three minute period. Thus, you should select fewer than 9 devices at a time when performing manual license updates.

Redeploy Selected Licenses button

Click this button to redeploy licenses to the selected devices. Redeploying licenses might be necessary when you have obtained an updated license file and it was not applied to the device successfully during an automatic update.

When you click this button, a dialog box opens listing devices whose licenses you are redeploying. Click OK to perform the update. For successful updates, the updated file is automatically applied to the device.

Update from License File button

Click this button to update licenses by selecting a license file from the Security Manager server. When you click this button, a dialog box opens where you can specify the license files. Click Browse to select the files, which must be on a local drive on the Security Manager server. When you click OK, the updated files are automatically applied to the devices.

Export button

Click this button to export the license list to a comma-separated values (CSV) file. You are prompted to select the folder on the Security Manager server and to specify a file name.

Refresh License button

Click this button to refresh the data in the IPS license table for the selected devices. The updated information is retrieved from the device. If you do not select any devices, all devices are refreshed; this can take a long time depending on the number of devices listed.

Download and apply licenses

Days before the expiration date.

Whether to automatically download IPS licenses from Cisco.com and apply them to the devices. To successfully configure automatic updates, you must have a Cisco.com support contract that includes the serial numbers of your IPS devices.

If you select this option, also specify the number of days before the license expiration date for downloading and applying licenses. Security Manager evaluates only those devices that do not have licenses, have expired licenses, or have valid licenses within this number of days of expiration. Licenses are applied only if they are valid and either have an expiration date farther out than the current one, or that have different license information.

Discover devices daily at

If you select automatic license updates, the time of day when Security Manager should contact devices for current licenses status and evaluate whether there are devices that have licenses that will expire within the specified number of days. Cisco.com is contacted only if one or more device meets the expiration requirements.

Email License Update Results

Email Notification

Whether to send email notifications of expiration alerts and license update job results. If you select this option, also enter one or more email addresses (comma separated).

Save button

Saves your changes to the automatic license update and e-mail notification settings.


Verifying IPS Devices for License Update or Redeployment

When you select a device on the Licensing > IPS tab (see IPS Tab, Licensing Page) and try to update the license from Cisco.com (CCO) or redeploy the license, you are first shown a list of devices that will be updated. The name of the dialog box is based on the action you are taking:

Updating Licenses via CCO dialog box—Review the IPS devices you selected to update from Cisco.com. The device list displays the IPS devices for which you can update the license from Cisco.com, which might not be all of the devices you selected.

To successfully update the license using this method, you must have a Cisco.com support contract that includes the serial numbers of the selected devices.


Tip The Cisco software license server (SWIFT) that contains the licenses might block requests from the same server for more than 9 licenses within a three minute period. Thus, you should select fewer than 9 devices at a time when performing manual license updates.


Redeploying Licenses dialog box—Review the IPS devices you selected for redeploying licenses. Before you can redeploy a license to a device, you must have already deployed the license. Security Manager uses the file already associated with the IPS device to redeploy the license.

When you click OK, the License Update Status Details dialog box opens so that you can view the status of the license redeployment task. See License Update Status Details Dialog Box.

Navigation Path

To open these dialog boxes, select one or more device on the Tools > Security Manager Administration > Licensing > IPS tab and click Update Selected via CCO or Redeploy Selected Licenses.

Selecting IPS License Files

If you select one or more device on the Tools > Security Manager Administration > Licensing > IPS tab and click Update from License File, you are prompted to select the license file you want to use with the Updating Licenses from File dialog box.

The license file must be stored on a local drive on the Security Manager server. Click Browse to select the license file. You can select multiple license files using Ctrl+click or a range of files using Shift+click. When you have selected the license files you want to use, click OK to apply them to the IPS devices.

License Update Status Details Dialog Box

Use the License Update Status Details dialog box to view the status of an IPS license update task. This dialog box opens whenever you start an update task from the IPS tab of the Licensing page. For more information, see IPS Tab, Licensing Page.

Field Reference

Table 11-20 License Update Status Details Dialog Box 

Element
Description

Progress bar

Indicates what percentage of the license update task on the current device has been completed.

Status

The current state of the update task.

Devices to be updated

The total number of devices being updated during this task.

Devices updated successfully

The number of devices updated without errors.

Devices updated with errors

The number of devices that generated errors during the update.

Device list

The devices that are being updated, including the device name, the status of the update, and summary information about the update. Select a device to see the messages generated during the update for that device in the message list below the summary list.

Messages list

The messages generated during the license update for the selected device. Select a message to see detailed information in the fields to the right of the list.

Description

Additional information about the message selected in the message list.

Action

The steps you should take to resolve the described problem.

Abort button

Aborts the license update task.


Logs Page

Use the Logs page to configure the default settings for the audit and operations logs. The audit log keeps a record of all state changes that occur in Security Manager.

Navigation Path

Select Tools > Security Manager Administration and select Logs from the table of contents.

Related Topics

Using the Audit Report Window, page 10-17

Understanding Audit Reports, page 10-16

Generating the Audit Report, page 10-16

Field Reference

Table 11-21 Logs Page 

Element
Description

Keep Audit Log For

Purge Now button

The maximum number of days to save audit report entries before deleting them. If the number of entries in the log exceeds the number entered in the Purge Audit Log After field, old log entries might be deleted before they reach this age.

If you reduce the number of days, you can click Purge Now to immediately delete the older entries.

Purge Audit Log After (entries)

The maximum number of audit report entries to save. 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.

Keep Operation Log For

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.


Policy Management Page

Use the Policy Management page to select the types of router and firewall policies you will manage in Security Manager. These selections apply to routers and firewall devices, but do not apply to IPS devices. By default, all policies are selected for management.

Unmanaged policies are removed from both Device view and Policy view. Any unmanaged policies, local or shared, are removed from the Security Manager database. The only exception is interface policies, which continue to appear in Security Manager but are marked as read-only policies. For firewall devices, interface and failover settings are considered a unit and are managed or unmanaged together.

For detailed information on managing and unmanaging policy types, including what you should do before and after changing these settings, see Customizing Policy Management for Routers and Firewall Devices, page 5-10.


Caution If you use AUS or CNS to deploy configurations to ASA or PIX devices, be aware that the device downloads a full configuration from AUS or CNS. Thus, reducing the policies managed by Security Manager actually removes the configurations from the device. If you intend to deselect some ASA/PIX policies for management to use other applications along with Security Manager to configure devices, do not use AUS or CNS.

Navigation Path

Select Tools > Security Manager Administration and select Policy Management from the table of contents.

Field Reference

Table 11-22 Policy Management Page 

Element
Description

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.

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, page 6-17.

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.

Tip When importing policies or devices, you are prompted to select a setting for this option. Thus, users who import policies or devices can change this setting without accessing this page provided they have the required authorization. The change is effective only after the importer submits (and if necessary, approves) the changes. For more information, see Importing Policies or Devices, page 10-12.

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.


Policy Objects Page

Use the Policy Objects page to define system defaults related to policy object creation.

Navigation Path

Select Tools > Security Manager Administration and select Policy Objects from the table of contents.

Related Topics

Understanding and Specifying Services and Service and Port List Objects, page 6-72

Chapter 6, "Managing Policy Objects"

Field Reference

Table 11-23 Policy Objects Page 

Element
Description

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, page 6-74.

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.


Rule Expiration Page

Use the Rule Expiration page to define the default values for policy rule expiration. When you create policies for some types of policy rules (such as access rules), you can set an expiration date for the rule, and Security Manager can notify you by e-mail of the approaching expiration date.

You must configure an SMTP server to enable e-mail notifications. For more information, see Configuring an SMTP Server and Default Addresses for E-Mail Notifications, page 1-21.

Navigation Path

Select Tools > Security Manager Administration and select Rule Expiration from the table of contents.

Field Reference

Table 11-24 Rule Expiration Page 

Element
Description

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.


Server Security Page

Use the Server Security page to open specific pages in the CiscoWorks Common Services application, where you can configure various security features on the Security Manager server. CiscoWorks Common Services controls the basic functions of the Security Manager server, including user access control and system security.

When you log in to Security Manager, your username and password are compared with the account information stored in the CiscoWorks or Cisco Secure Access Control Server (ACS) database, depending on which system you established at installation as your AAA provider. After the authentication of your credentials, you have access according to the role you have been assigned.

For more information on Security Manager roles and privileges, including descriptions of how Common Services roles translate to user functions in Security Manager, see the Installation Guide for Cisco Security Manager.

Navigation Path

Select Tools > Security Manager Administration and select Server Security from the table of contents.

Field Reference

Table 11-25 Server Security Page 

Element
Description

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.


Status Page

Use the Status page to select the providers that will provide status to users when they view their inventory status by selecting Tools > Inventory Status. The status is displayed on the Status tab in the Inventory Status window.

By default, Security Manager provides status on deployment to the devices, but you can add Performance Monitor servers if you use them to monitor your network.

Navigation Path

Select Tools > Security Manager Administration and select Status from the table of contents.

Related Topics

Configuring Status Providers, page 65-16

Inventory Status Window, page 65-18

Viewing Inventory Status, page 65-15

Field Reference

Table 11-26 Status Page 

Element
Description

Display Deployment Status

Whether to include the status of deployment jobs that include the device.

Providers table

The Performance Monitor servers that are registered with Security Manager. You can add up to five servers.

The provider name appears in the Inventory Status window on the Status tab for individual devices, indicating the server that provided the status. The short name is a nickname.

To add a Performance Monitor server to the list, click the Add (+) button and fill in the Add or Edit Status Provider Dialog Box.

To edit a server's properties, select it and click the Edit (pencil) button.

To delete a server, select it and click the Delete (trash can) button.

Use the Status cell to change whether Security Manager actively polls the server for status. Select Enabled to actively poll the server, or Disabled to suspend polling the server without having to delete the provider entry.

Save button

Saves your changes.

Reset button

Resets changes to the last saved values.


Add or Edit Status Provider Dialog Box

Use the Add or Edit Status Provider dialog box to register a Performance Monitor server with Security Manager. Security Manager can then poll the Performance Monitor servers for event status such as VPN tunnels, device connectivity, and CPU usage threshold. Users can view the status of their devices by selecting Tools > Inventory Status. For more information, see Configuring Status Providers, page 65-16.

Navigation Path

From the Tools > Security Manager Administration > Status page, click the Add (+) button beneath the providers table, or select a provider and click the Edit (pencil) button.

Field Reference

Table 11-27 Add or Edit Status Provider Dialog Box 

Element
Description

Provider name

The name of the service provider, for example, Performance Monitor. You can enter up to 128 characters. Valid characters are: 0-9; uppercase A-Z; lowercase a-z; and the following characters: - _ :. and space.

Server

The IP address or fully-qualified host name of the Performance Monitor server. The host name can be up to 128 characters.

Short Name

The short name for the provider name.

Port

The port number that Security Manager should use to communicate with the Performance Monitor server. The default is 443.

Poll Cycle

The number of minutes the firewall device will wait between polling Performance Monitor for new information. The default is 600 seconds (10 minutes). The minimum time is 60 seconds.

Username

The username for logging in to Performance Monitor.

Password

The password for logging in to Performance Monitor. In the Confirm field, enter the password again.

URN

The uniform resource name for Performance Monitor. URN is the name that identifies the resource on the Internet. URN is part of a URL, for example, /mcp/StatusServlet. The full URL could be:

https://:<server ip> :443/mcp/StatusServlet

where:

<server ip> is the IP address of Performance Monitor.

443 is the port number Performance Monitor listens to.

/mcp/StatusServlet is the URN of the Performance Monitor.

Status

Whether the server is enabled for providing status to Security Manager. If you select Disabled, the server is added to the status providers list, but Security Manager does not poll it for status.


Take Over User Session Page

Use the Take Over User Session page to take over another user's configuration session. A user with administrative privileges can take over the work of another user in non-Workflow mode. Taking over a session is useful when a user is working on devices and policies, causing the devices and policies to be locked, and another user needs access to the same devices and policies. However, when you take over another user's session, your current session is discarded, so make sure that you submit your changes before taking over a session.

The table shows all current configuration sessions, listing the user name and the state of the session, whether the user is currently logged in or logged out. Select the configuration session you want to take over and click Take over session. The session is transferred to you in its current state, including any saved changes the user made during the session.

If the selected user is logged in at the time you take over the session, the user receives a warning message, loses any unsaved changes in progress, and then is logged out.

For more information, see Taking Over Another User's Work, page 10-20.

Navigation Path

Select Tools > Security Manager Administration and select Take Over User Session from the table of contents.

Token Management Page

Use the Token Management page to identify the Token Management System (TMS) server to use for deploying configurations to Cisco IOS routers that use TMS as the communication protocol. Security Manager uses the settings on this page to contact the TMS server.

Security Manager uses FTP to deploy the delta configuration file to the TMS server, from which the configuration file can be downloaded and encrypted onto an eToken.

To use TMS with Cisco IOS routers, you must specify TMS as the transport protocol. You can do this for all routers on the Device Communication page (see Device Communication Page), or for a specific router in its device properties (see General Page, page 3-36). You must also configure the TMS server as an FTP server, otherwise deployment will fail.

Navigation Path

Select Tools > Security Manager Administration and select Token Management from the table of contents.

Related Topics

Deploying Configurations to a Token Management Server, page 8-41

Understanding Deployment Methods, page 8-8

Field Reference

Table 11-28 Token Management Page 

Element
Description

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.


VPN Policy Defaults Page

Use the VPN Policy Defaults page to view or assign the default VPN policies that Security Manager uses for each IPsec technology. Before you can select a policy as a default, you must create the policy as a shared policy, submit it to the database and have it approved. You cannot create policies from this page. For detailed information on how to configure these defaults, see Understanding and Configuring VPN Default Policies, page 21-12.

For each tab that relates to a VPN topology, the drop-down lists for each policy type list the existing shared policies that you can select. You can select a policy and click the View Content button to see the definition of that policy. In some cases, you are allowed to make changes, but you cannot save them.

Security Manager uses VPN policy defaults to simplify VPN configuration while ensuring that policy consistency is maintained. Security Manager provides factory default policies for mandatory policies, which provide values for settings that must be configured on the devices in your VPN topology for the VPN to work. Mandatory policies differ depending on the assigned IPsec technology. Factory default policies with their default configurations enable you to deploy to your devices immediately after creating the VPN topology. Default settings are not provided for optional policies. You might want to create shared policies to provide different default settings instead of using the factory default settings.

Navigation Path

Select Tools > Security Manager Administration and select VPN Policy Defaults from the table of contents.

Related Topics

Assigning Initial Policies (Defaults) to a New VPN Topology, page 21-58

Creating IPSec VPNs Using the Remote Access VPN Configuration Wizard (ASA and PIX 7.0+ Devices), page 26-24

Creating IPSec VPNs Using the Remote Access VPN Configuration Wizard (IOS and PIX 6.3 Devices), page 26-35

Field Reference

Table 11-29 VPN Policy Defaults Page 

Element
Description

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.

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.


Workflow Page

Use the Workflow page to select the workflow mode that Security Manager enforces and to define the default settings for activity and deployment job notifications and logging.

Before changing the workflow mode, read the following topics to understand how the modes differ and the effects of changing the modes:

Working in Workflow Mode, page 1-17

Working in Non-Workflow Mode, page 1-17

Comparing the Two Workflow Modes, page 1-18

Changing Workflow Modes, page 1-22

Navigation Path

Click Tools > Security Manager Administration and select Workflow from the table of contents.

Related Topics

Chapter 4, "Managing Activities"

Chapter 8, "Managing Deployment"

Field Reference

Table 11-30 Workflow Page 

Element
Description
Workflow Control

Enable Workflow

Whether to enable Workflow mode. When Workflow mode is enabled, you can select whether 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, page 4-2.

Require Deployment Approval

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

Email Notifications

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), page 4-15.

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, page 8-36.

Job Completion Notification

The e-mail address of the person who should receive notification when deployment jobs are completed. Users can override this address when creating a deployment job.

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.

Workflow History

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.

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.