Security Manager for Cisco Secure ACS allows you to monitor Cisco Secure Access Control System (ACS) devices in your environment. This module provides knowledge so you can proactively manage Cisco Secure ACS and identify issues before they become critical.

Security Manager for Cisco Secure ACS monitors syslog messages generated by Cisco Secure ACS devices and highlights events that may indicate configuration changes or attacks, so you can quickly take corrective or preventative action. For example, Security Manager for Cisco Secure ACS enables you to perform the following tasks:

• Detect device network configuration changes
• Monitor login attempts through a VPN and other remote network access points
• Identify possible attacks on the Cisco Secure ACS device or attached network
• Monitor authentication attempts by users, including wireless users
• Notify when system or threshold alarms occur

Security Manager for Cisco Secure ACS also collects events from logs and stores them in secure repositories so you can archive this data, create reports for management or auditing purposes, and analyze critical events to research issues. Security Manager for Cisco Secure ACS collects all log messages you configure your Cisco Secure ACS devices to send.

NetIQ often makes improvements to modules in direct response to suggestions from our customers. We thank you for your time and valuable input. We hope you continue to help us ensure our products meet all your needs. You can post feedback in the Security Manager forum on Qmunity, our community Web site that also includes product notifications, blogs, and the Security Manager user group.

This document outlines why you should install this module, lists installation requirements, and identifies known issues.

Return to Top

Supported Products

For the latest information about supported software versions and the availability of module updates, visit the Security Manager Supported Products page. If you encounter problems using this module with a later version of your application, contact NetIQ Technical Support.

This release supports the following products:

• Cisco Secure Access Control System 5.0
• Cisco Secure Access Control System 5.1
• Cisco Secure Access Control System 5.2

Return to Top

Why Install This Module?

Security Manager for Cisco Secure ACS provides support for received data from monitored Cisco Secure ACS devices. The volume and type of data that Security Manager for Cisco Secure ACS collects is determined by the configuration of the device and the policies you have created for the device.

Return to Top

System Requirements

The following table lists additional requirements for a Windows agent. For more information about agent requirements, see the Installation Guide for NetIQ Security Manager.

Category	Requirement
Processor	1.5 GHz Intel Pentium III or equivalent.
Memory	40 MB minimum. The amount of memory usage varies and depends on the environment, including event rate and other factors.
Operating System	All supported Windows agent platforms.
Software	Ensure you have Security Manager 6.5 or later installed. Ensure you have the latest version of the Security Manager Self-Monitoring module installed. This module is required for optimum functionality of the product.

Return to Top

Installing This Module

Install the module using the Module Installer utility. For more information about installing modules, see the User Guide for NetIQ Security Manager.

You can verify successful installation of the module in the Module Installer. After the installation completes, verify the Status column indicates the module is current and the module version listed in the Installed Version column is the same as the version in the Available Version column.

After you install the module, run the Configuration Wizard to configure Security Manager for Cisco Secure ACS. For more information about using the Configuration Wizard, see the User Guide for NetIQ Security Manager.

Return to Top

Configuring Cisco Secure ACS Devices for Remote Logging

After you install the module, you must configure all Cisco Secure ACS devices in your environment to send messages to a remote syslog server where the Windows agent computer can access the logs. Create and set a remote log target for ACS messages using the Cisco Secure ACS Web interface, configure Cisco Secure ACS logging categories to use your remote log target, create a remote log target for alarm messages, and then enable Cisco Secure ACS to send alarm notifications as syslog messages to the remote log target.

You can use any agent computer to monitor Cisco Secure ACS logs, including a central computer or a remote agent. For more information about creating remote log targets, see the Cisco Secure ACS product documentation.

Create a Remote Log Target for Cisco Secure ACS Messages

Before Security Manager can monitor your Cisco Secure ACS environment, you must first create a remote log target Cisco Secure ACS can use to store messages and Security Manager can use to collect ACS data.

To create and set the remote syslog server you want to use as a remote log target for ACS messages:

1. Start a Web browser on a computer with access to the Cisco Secure ACS device.
2. In the browser, open the Cisco Secure ACS Web interface.
3. In the left pane, expand System Administration > Configuration > Log Configuration > Remote Log Targets.
4. In the right pane, click Create.
5. In the Name and Description fields, specify the name and description you want to use for the new remote log target.
6. In the IP Address field, specify the IP address of the Security Manager agent or central computer you want to use to receive the syslog messages.

Note The agent or central computer must have a syslog provider installed.

7. If you want to configure advanced syslog settings, complete the following steps:
1. Expand the Use Advanced Syslog Options section.
2. In the Port field, specify the port number you want the remote syslog server to use to receive ACS messages.
3. In the Facility Code field, specify the facility value of each syslog message you want to send to the remote syslog server. The facility value forms part of the priority of a syslog message. Valid options are LOCAL0, LOCAL1, LOCAL2, LOCAL3, LOCAL4, LOCAL5, LOCAL6, or LOCAL7.
4. In the Maximum Length field, specify the maximum length of each syslog message you want to send to the remote syslog server. You cannot specify a value greater than 1024 characters.
8. Click Submit.

Configure Logging Categories for Cisco Secure ACS Messages

After you create a new remote log target for ACS messages, use the Cisco Secure ACS Web interface to configure each Cisco Secure ACS logging category to use the new remote log target. The logging category of a message describes the content of the message. For example, Cisco Secure ACS includes the preconfigured Administrative and Operational Audit logging category, which indicates that the message relates to ACS configuration changes, events that occurred while an administrator accessed the system, and any operations requested by an administrator.

If you installed Cisco Secure ACS in a distributed deployment, you can configure logging categories globally or on a per-instance basis. For more information about configuring logging categories on a per-instance basis, see the Cisco Secure ACS product documentation.

To configure global logging categories to use a specific remote log target:

1. In the left pane of the Cisco Secure ACS Web interface, expand System Administration > Configuration > Log Configuration > Logging Categories > Global.
2. In the right pane, select a logging category.
3. Click Edit.
4. If you want to modify the log severity for the selected logging category, click the dropdown menu and select the severity level you want to use. Possible options are FATAL, ERROR, WARN, INFO, or DEBUG.

Note Audit or accounting categories only use one log severity level, NOTICE. You cannot modify the log severity for audit or accounting logging categories.

5. Click the Remote Syslog Target tab.
6. In the Available Targets list, select the remote log target you want to use.
7. Click the right arrow to move the selected target to the Selected Targets list.
8. Click Submit.
9. Repeat Steps 2 through 8 for each logging category.

Create a Remote Log Target for Alarm Messages

In addition to standard Cisco Secure ACS messages, you can also enable remote syslog monitoring of Cisco Secure ACS alarm messages. To enable alarm message logging, you must create a remote log target for alarm messages. For more information about enabling alarm and threshold message logging, see the Cisco Secure ACS product documentation.

To create and set the remote syslog server you want to use as a remote log target for alarm messages:

1. In the left pane of the Cisco Secure ACS Web interface, click Monitoring and Reports > Launch Monitoring & Report Viewer.
2. In the left pane, expand Monitoring Configuration > System Configuration > Alarm Syslog Targets.
3. In the right pane, click Add.
4. In the Name and Description fields, specify the name and description you want to use for the new remote alarm log target.
5. In the IP Address field, specify the IP address of the remote syslog server.
6. If you want to configure advanced syslog settings, complete the following steps:
1. Expand the Use Advanced Syslog Options section.
2. In the Port field, specify the port number you want the remote syslog server to use to receive alarm messages.
3. In the Facility Code field, specify the facility value of each alarm message you want to send to the remote syslog server. The facility value forms part of the priority of a syslog message. Possible options are LOCAL0, LOCAL1, LOCAL2, LOCAL3, LOCAL4, LOCAL5, LOCAL6, or LOCAL7.
7. Click Submit.

Enable System and Threshold Alarm Logging

After you create a remote log target for alarm messages, enable alarm logging in Cisco Secure ACS. Enable logging for system alarm messages and separately for each configured threshold alarm message in your ACS environment.

To enable Cisco Secure ACS to send system and threshold alarm messages to the remote log target:

1. In the left pane of the Monitoring & Report Viewer, expand Monitoring Configuration > System Configuration > System Alarm Settings.
2. In the right pane, select Send Syslog Message.
3. Click Submit.
4. In the left pane, expand Monitoring and Reports > Alarms > Thresholds.
5. In the right pane, select a threshold alarm you want to send alarm messages.
6. Click Edit.
7. In the Notification tab, select Send Syslog Message.
8. In the Severity dropdown menu, select the severity level you want to assign to each threshold alarm message. Possible options are Critical, Warning, or Info.
9. Click Submit.
10. Repeat Steps 5 through 9 for each threshold alarm.

Return to Top

Configuring the Module

Configure Security Manager for Cisco Secure ACS using the Configuration Wizard. First use the Configuration Wizard to specify the Security Manager agent or agents you want to use to remotely monitor your Cisco Secure ACS environment, then specify the Cisco Secure ACS devices you want to monitor. Click Finish when you have specified the agents you want to use and devices you want to monitor.

For more information about using the Configuration Wizard, see the User Guide for NetIQ Security Manager.

Return to Top

Cisco Secure ACS Event Fields Used by Security Manager

Security Manager for Cisco Secure ACS collects various fields from the data received from monitored Cisco Secure ACS devices. The following table lists the Cisco Secure ACS data fields most commonly used by Security Manager and maps those fields to the corresponding names and values used for real-time alerting, log archival, and Forensic Analysis. You can use these fields to create processing rules or Forensic Analysis queries tailored to your specific environment. For more information about creating processing rules, see the Programming Guide for NetIQ Security Manager.

Real-Time Parameter Name/Number	Log Archive Field Name	Forensic Analysis Column Name
$Message	message	Message
$Computer	analyzer.node.name	Network Node
N/A	analyzer.node.address.address	Network Node Address
EventNumber	classification.name	Native Classification
EventType	N/A	N/A
N/A	analyzer.model	Platform
1	target.node.name	Target Node
2	rule name	Rule/Signature Name
3	source.node.name	Source Node
4	source.service.port	Source Port
5	classification.origin	Source Name
6	source.interface.type	Source Interface Type
7	Bytes Sent	Bytes Out
8	target.object.type	Target Object Type
9	action	Action
10	userfield_string_010	Packets Out
11	target.node.address.mac	Target MAC
12	session name	Session Name
13	common.category	Data Category
14	Bytes Received	Bytes In
15	target.service.port	Target Port
16	target.service.protocol	Target Protocol
17	source.interface	Source Interface
18	target.object.value.modified	Modified Data
19	source.user.userid.name	Source User
20	status.code	Status Code
21	target.object.name	Target Object Name
22	assessment.impact.severity	Severity
23	userfield_string_006	Port Type
24	userfield_string_007	ID Group
25	userfield_string_008	Session Duration
26	userfield_string_009	Packets In
27	userfield_string_002	Reason
28	userfield_string_003	Device Name
29	source.service.protocol	Source Protocol
30	userfield_string_004	Config Version
31	userfield_string_005	Privilege Level
32	source.node.address.mac	Source MAC
33	event.sequence.id	Event Sequence ID
34	status	Status
35	target.user.userid.name	Target User
36	target.process.name	Target Process
37	userfield_string_001	Message Class
38	status.description	Status Description
39	source.node.address.address	Source Address
40	target.node.address.address	Target Address
41	common.classification	Event Classification
42	common.classification.type	Event Classification Subtype

Return to Top

Contact Information

Our goal is to provide documentation that meets your needs. If you have suggestions for improvements, please email Documentation-Feedback@netiq.com. We value your input and look forward to hearing from you.

For detailed contact information, see the Support Contact Information Web site.

For interactive conversations with your peers and NetIQ experts, become an active member of Qmunity, our community Web site that offers product forums, product notifications, blogs, and product user groups.

Return to Top

Legal Notice

THIS DOCUMENT AND THE SOFTWARE DESCRIBED IN THIS DOCUMENT ARE FURNISHED UNDER AND ARE SUBJECT TO THE TERMS OF A LICENSE AGREEMENT OR A NON-DISCLOSURE AGREEMENT. EXCEPT AS EXPRESSLY SET FORTH IN SUCH LICENSE AGREEMENT OR NON-DISCLOSURE AGREEMENT, NETIQ CORPORATION PROVIDES THIS DOCUMENT AND THE SOFTWARE DESCRIBED IN THIS DOCUMENT "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. SOME STATES DO NOT ALLOW DISCLAIMERS OF EXPRESS OR IMPLIED WARRANTIES IN CERTAIN TRANSACTIONS; THEREFORE, THIS STATEMENT MAY NOT APPLY TO YOU.

This document and the software described in this document may not be lent, sold, or given away without the prior written permission of NetIQ Corporation, except as otherwise permitted by law. Except as expressly set forth in such license agreement or non-disclosure agreement, no part of this document or the software described in this document may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, electronic, mechanical, or otherwise, without the prior written consent of NetIQ Corporation. Some companies, names, and data in this document are used for illustration purposes and may not represent real companies, individuals, or data.

This document could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein. These changes may be incorporated in new editions of this document. NetIQ Corporation may make improvements in or changes to the software described in this document at any time.

© 2011 NetIQ Corporation. All rights reserved.

U.S. Government Restricted Rights: If the software and documentation are being acquired by or on behalf of the U.S. Government or by a U.S. Government prime contractor or subcontractor (at any tier), in accordance with 48 C.F.R. 227.7202-4 (for Department of Defense (DOD) acquisitions) and 48 C.F.R. 2.101 and 12.212 (for non-DOD acquisitions), the government's rights in the software and documentation, including its rights to use, modify, reproduce, release, perform, display or disclose the software or documentation, will be subject in all respects to the commercial license rights and restrictions provided in the license agreement.

Check Point, FireWall-1, VPN-1, Provider-1, and SiteManager-1 are trademarks or registered trademarks of Check Point Software Technologies Ltd.

ActiveAudit, ActiveView, Aegis, AppManager, Change Administrator, Change Guardian, Compliance Suite, the cube logo design, Directory and Resource Administrator, Directory Security Administrator, Domain Migration Administrator, Exchange Administrator, File Security Administrator, Group Policy Administrator, Group Policy Guardian, Group Policy Suite, IntelliPolicy, Knowledge Scripts, NetConnect, NetIQ, the NetIQ logo, PSAudit, PSDetect, PSPasswordManager, PSSecure, Secure Configuration Manager, Security Administration Suite, Security Manager, Server Consolidator, VigilEnt, and Vivinet are trademarks or registered trademarks of NetIQ Corporation or its subsidiaries in the USA. All other company and product names mentioned are used only for identification purposes and may be trademarks or registered trademarks of their respective companies.

For purposes of clarity, any module, adapter or other similar material ("Module") is licensed under the terms and conditions of the End User License Agreement for the applicable version of the NetIQ product or software to which it relates or interoperates with, and by accessing, copying or using a Module you agree to be bound by such terms. If you do not agree to the terms of the End User License Agreement you are not authorized to use, access or copy a Module and you must destroy all copies of the Module and contact NetIQ for further instructions.

This product claims FIPS compliance by use of one or more of the Microsoft cryptographic components listed below. These components were certified by Microsoft and obtained FIPS certificates via the CMVP.

893 Windows Vista Enhanced Cryptographic Provider (RSAENH)

894 Windows Vista Enhanced DSS and Diffie-Hellman Cryptographic Provider (DSSENH)

989 Windows XP Enhanced Cryptographic Provider (RSAENH)

990 Windows XP Enhanced DSS and Diffie-Hellman Cryptographic Provider (DSSENH)

997 Microsoft Windows XP Kernel Mode Cryptographic Module (FIPS.SYS)

1000 Microsoft Windows Vista Kernel Mode Security Support Provider Interface (ksecdd.sys)

1001 Microsoft Windows Vista Cryptographic Primitives Library (bcrypt.dll)

1002 Windows Vista Enhanced Cryptographic Provider (RSAENH)

1003 Windows Vista Enhanced DSS and Diffie-Hellman Cryptographic Provider (DSSENH)

1006 Windows Server 2008 Code Integrity (ci.dll)

1007 Microsoft Windows Server 2008 Kernel Mode Security Support Provider Interface (ksecdd.sys)

1008 Microsoft Windows Server 2008

1009 Windows Server 2008 Enhanced DSS and Diffie-Hellman Cryptographic Provider (DSSENH)

1010 Windows Server 2008 Enhanced Cryptographic Provider

1012 Windows Server 2003 Enhanced Cryptographic Provider (RSAENH)

This product may also claim FIPS compliance by use of one or more of the Open SSL cryptographic components listed below. These components were certified by the Open Source Software Institute and obtained the FIPS certificates as indicated.

918 - OpenSSL FIPS Object Module v1.1.2 - 02/29/2008 140-2 L1

1051 - OpenSSL FIPS Object Module v 1.2 - 11/17/2008 140-2 L1

1111 - OpenSSL FIPS Runtime Module v 1.2 - 4/03/2009 140-2 L1

Note: Windows FIPS algorithms used in this product may have only been tested when the FIPS mode bit was set. While the modules have valid certificates at the time of this product release, it is the user's responsibility to validate the current module status.

Return to Top