Event Manager for Cisco Firewalls
Date Published: November 2010
Event Manager for Cisco Firewalls allows you to monitor Cisco PIX, ASA, and FWSM firewalls. This module provides embedded knowledge so you can proactively manage Cisco firewalls and identify issues before they become critical. By detecting, alerting on, and automatically responding to critical events in real-time, Event Manager for Cisco Firewalls helps indicate, correct, and prevent possible external intrusions, attacks, and configuration problems. This module increases the security, availability, and performance of Cisco firewalls.
Event Manager for Cisco Firewalls monitors syslog messages generated by Cisco firewalls. Event Manager for Cisco Firewalls also highlights events that may indicate configuration changes or external attacks, so you can quickly take corrective or preventive actions. For example, Event Manager for Firewalls enables you to perform the following tasks:
This module for the Security Manager product includes usability improvements and resolves several previous issues. Many of these improvements were made 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 any installation requirements, and identifies any known issues.
This release supports the following products:
Why Install This Module?
Event Manager for Cisco Firewalls provides support for received data that contains Internet Protocol version 6 (IPv6) addresses. For more information about how Security Manager supports IPv6, see the Security Manager 6.5 documentation.
After you install this release, Event Manager for Cisco Firewalls enables you to create real-time processing rules on any events collected from your Cisco firewall devices, in addition to storing those events in the log archive. If you want to generate additional real-time alerts on Cisco firewall events, create new rules based on those events.
The following table lists additional requirements for a Windows agent acting as the agent for Cisco firewalls. For more information about agent requirements, see the Installation Guide for NetIQ Security Manager.
Installing This Module
Complete the following steps to install this module in a new Security Manager 6.5 installation.
To install this module:
Upgrading This Module
If you have an existing Security Manager 6.5 installation and have already replaced your Legacy version of the Cisco Firewalls module, you can upgrade the module as usual using the Module Installer. However, if you have an existing Security Manager installation, but did not yet upgrade to Security Manager 6.5, use the following procedure to upgrade the module from the old Legacy version. Upgrade your existing installation to Security Manager 6.5, and then complete either step 1 or step 2 in the following procedure to upgrade the module.
To upgrade this module from the Legacy version:
Configuring the Agent
To configure the Windows agent, add the name and IP address of the Cisco firewall device to the Hosts file on the Windows agent computer. For more information about the Hosts file, see the Windows documentation.
Configuring Cisco Firewall Devices
You can configure one or more Cisco firewall devices to communicate effectively with the Windows agent computer.
To configure a Cisco firewall device:
Creating Custom Processing Rules
NetIQ recommends you create your own custom processing rule group outside of the processing rule group installed with the module and then create custom processing rules for your environment. You can copy the predefined rules included in the module processing rule group to your custom processing rule group or create new rules within your custom processing rule group.
If you create or modify processing rules within the module processing rule group, the next time you install an updated version of the module, Security Manager may remove your customized rules. If you use your custom processing rule group to create or modify rules, Security Manager does not remove your customized rules when you install a new version of the module.
NetIQ Corporation strives to ensure our products provide quality solutions for your enterprise software needs. The following issues are currently being researched. If you need further assistance with any issue, please contact Technical Support.
Device ID Cannot Have Three Characters
Due to limitations in regular expression parsing for this release, the device ID can have less than three characters or more than three characters, but not exactly three characters.
Incorrect Address or Interface Name
If an interface name on the firewall includes a colon or space, events will not be properly interpreted.
Excluded Account Names May Break Processing Rules
A known issue exists where adding certain account names or regular expressions on the Cisco Firewall Excluded Accounts page in the Configuration Wizard breaks associated module processing rules, and Security Manager does not generate alerts for matching events. If you enter any account names or regular expressions containing the characters or, and, or not, the module parser treats those characters as Boolean operators and does not recognize them as part of an account name. For example, entering Administrator or Anderson in the excluded accounts list would break the "Successful Login" and "User accessed configuration mode" rules in this module. If you add any regular expressions or account names containing or, and, or not to the excluded accounts list in the Configuration Wizard, you must also edit those names in the Development Console to enable the associated rules to function.
To ensure excluded account names do not break associated processing rules:
Configuration Wizard Allows Unsupported Characters
The Configuration Wizard allows entry of duplicate user account names and account names that conflict with the naming guidelines for Cisco and Microsoft Windows. Rules may not function correctly if you enter user account names:
Please contact us with your questions and comments. We 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 user groups.
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.
© 2010 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.
ActiveAgent, ActiveAnalytics, ActiveAudit, ActiveReporting, ADcheck, Aegis, AppAnalyzer, AppManager, the cube logo design, Change Administrator, Change Guardian, Compliance Suite, 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, Knowing is Everything, Knowledge Scripts, Mission Critical Software for E-Business, MP3check, NetConnect, NetIQ, the NetIQ logo, the NetIQ Partner Network design, Patch Manager, PSAudit, PSDetect, PSPasswordManager, PSSecure, Risk and Compliance Center, Secure Configuration Manager, Security Administration Suite, Security Analyzer, Security Manager, Server Consolidator, VigilEnt, Vivinet, Vulnerability Manager, Work Smarter, and XMP are trademarks or registered trademarks of NetIQ Corporation or its subsidiaries in the United States and other jurisdictions. 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.