69-9
User Guide for Cisco Security Manager 4.4
OL-28826-01
Chapter69 Using External Monitoring, Troubleshooting, and Diagnostic Tools
Launching Cisco Prime Security Manager
Step 3 In the SDM window, click the Monitoring button to display the Monitoring panel; click Logging in the
left pane to access the log-viewing options.
The Logging pane appears with Syslog tab displayed.
Step 4 To view the access rule that triggered a specific syslog message, select the message and click the Go to
Rule in CSM button above the table of log messages.
The Security Manager client window is activated and the Access Rules page appears with the rule
highlighted in the rules table. If the syslog entry was triggered by an access rule not referenced in the
current Security Manager activity, an error message appears.
Launching Cisco Prime Security Manager
The ASA CX is an Adaptive Security Appliance module that provides advanced ConteXt-aware security,
extending the ASA platform to provide in-depth “who-what-where-when-how” application visibility and
control.
These ASA CX devices are managed by the Cisco Prime Security Manager (PRSM) application—they
cannot be directly managed by Cisco Security Manager. However, Security Manager has been enhanced
to allow you to discover the presence of CX modules on ASA devices; to “cross launch” PRSM from the
Configuration Manager application; and to share Policy Object data between Security Manager and
PRSM (pronounced “prism”).
Note PRSM is a browser-based application; that is, it is launched and operates within a browser window.
Therefore, when you cross-launch PRSM from the Configuration Manager client, the host system��s
default browser is opened and PRSM initiated. However, some browsers have not been certified with
PRSM and you may need to change the default browser on the Security Manager client’s host system
prior to cross-launching PRSM. See “Browser Requirements” in the PRSM installation guide for more
information.
Before You Begin
In order to cross-launch PRSM, Security Manager must be aware of the presence of the CX modules.
This is accomplished through discovery of either new ASA CX devices, or of CX modules which have
been added to existing ASAs. This process is outlined in Detecting ASA CX Modules, page 69-10.
Related Topics
•Detecting ASA CX Modules, page 69-10
•Sharing Device Inventory and Policy Objects with PRSM, page 69-11
To monitor and manage your ASA CX devices, cross-launch PRSM:
Step 1 Select a previously discovered ASA CX device in Configuration Manager’s Device view—in either the
device-selector tree, or the table of devices in the content area.
Again, discovering ASA CX devices in Security Manager is described in Detecting ASA CX Modules,
page 69-10.