Event Manager for Imperva SecureSphere monitors events generated by Imperva SecureSphere devices in real-time and allows you to collect, evaluate, and present data reported by an Imperva SecureSphere device. By detecting, alerting on, and automatically responding to critical events, Event Manager for Imperva SecureSphere helps identify, correct, and prevent possible configuration problems and external intrusions or attacks.

Improvements are 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 provides configuration information.

Supported Products

This release supports Imperva SecureSphere device 6.00.2.x.

Return to Top

Why Install This Module?

With this release of Event Manager for Imperva SecureSphere, Security Manager now provides support for the Imperva SecureSphere Intrusion Prevention System.

Event Manager for Imperva SecureSphere monitors real-time events that the Imperva SecureSphere device sends to the Windows agent computer. This data includes any change or access event generated for a monitored database that matches the policy criteria configured on the Imperva SecureSphere device. The volume and type of data that Event Manager for Imperva SecureSphere collects is determined by the configuration of the device and the policies you have created on the device.

Event Manager for Imperva SecureSphere has the capability to monitor and alert on the following events:

• Schema changes to each monitored database
• Configuration changes to each monitored database
• Data read or changed from each monitored database
• Logon and logoff activity for each monitored database, including login failures

Return to Top

System Requirements

The following table lists additional requirements for a Windows agent acting as the proxy agent for Imperva SecureSphere. 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. Memory usage for a Windows agent monitoring Imperva SecureSphere could reach 256 MB or higher.
Operating System	All supported Windows agent platforms.
Software	Ensure you have Security Manager 6.5 or later installed. Ensure you install a separate Windows agent for each Imperva SecureSphere device you plan to monitor. If the Imperva SecureSphere device and the agent are separated by a firewall, ensure the firewall allows syslog data through. In addition, install the Windows agent on a subnet as physically close to the firewall as possible. Fewer network hops provide better performance. Install the Windows agent with Imperva SecureSphere support on a separate computer from the database server or central computer.

Return to Top

Installing This Module

Install this module using the Module Installer utility. If this is the first time you have installed the module, ensure you also add a license.

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. For more information about installing modules, see the Installation Guide for NetIQ Security Manager.

Return to Top

Configuring the Agent

Add the name and IP address of the Imperva SecureSphere device to the Hosts file on the Windows agent computer. For more information about the Hosts file, see the Windows documentation.

Return to Top

Configuring Event Manager for Imperva SecureSphere

You can configure this module with the Configuration Wizard. Specify the Windows agent computer to receive syslog data from the Imperva SecureSphere device, and specify the IP address or host name of the Imperva SecureSphere device. For more information about using the Configuration Wizard, see the User Guide for NetIQ Security Manager.

This module contains processing rules you can customize with the Development Console. Processing rules configure Security Manager to process events, alerts, and responses. Review processing rules that contain the word Customize to see if you want to customize them for your environment. You can perform a search for these rules in the Development Console, and then read the Knowledge Base for each rule. For more information about finding processing rules you can customize, see the Installation Guide for NetIQ Security Manager.

Return to Top

Configuring the Imperva SecureSphere Device

Set up the Imperva SecureSphere device in your environment and configure the appropriate policies, action sets, and action interfaces for your organization. Security Manager collects all data received from the Imperva SecureSphere device and archives the data for analysis and reporting, but the data that the Imperva SecureSphere device sends is determined by the set of policies you configure on the device. For more information about setting up the Imperva SecureSphere device and configuring appropriate policies and action sets, see the Imperva SecureSphere documentation.

Once you have set up and configured the Imperva SecureSphere device, complete the following required steps on the Imperva SecureSphere device. These steps ensure the Imperva SecureSphere device sends syslog data to the Windows agent in the required format so Security Manager logs events and responds with custom actions where appropriate.

To configure the Imperva SecureSphere device to work with Security Manager:

1. On the Imperva SecureSphere device, add the IP address of the Windows agent computer you specified in the Configuration Wizard, and configure the device to forward syslog events to the agent using port 514.
2. Create one or more new action sets for Security Manager syslog events. Ensure you select the option to log events to the system log (syslog) in each action set. Type the appropriate Security Manager syslog format string in the Message field. For more information about configuring custom action sets, see the Imperva SecureSphere documentation.

Use the following syslog strings to assign the syslog format to the action sets you want to send to Security Manager:

Note Ensure you type each string on a single line, using only a tab delimiter between parameters in the string. Do not use spaces.

LAImpervaLogOnly             
AlertNumber=${Alert.dn}            
CreateTime=${Alert.createTime}                
Description=${Alert.description}               
Username=${Alert.username}  
AlertType=${Alert.alertType}                
ServerGroup=${Alert.serverGroupName}            
Severity=${Alert.severity}           
Action=${Alert.immediateAction}                
Service=${Alert.serviceName}   
Application=${Alert.applicationName}   
SourceIP=${Event.sourceInfo.sourceIp}                
SourcePort=${Event.sourceInfo.sourcePort}                
Protocol=${Event.sourceInfo.ipProtocol}             
ServerIP=${Event.destInfo.serverIp}                
ServerPort=${Event.destInfo.serverPort}                
RuleName=${Rule.parent.displayName}

ImpervaWarning             
AlertNumber=${Alert.dn}            
CreateTime=${Alert.createTime}                
Description=${Alert.description}               
Username=${Alert.username}  
AlertType=${Alert.alertType}                
ServerGroup=${Alert.serverGroupName}            
Severity=${Alert.severity}           
Action=${Alert.immediateAction}                
Service=${Alert.serviceName}   
Application=${Alert.applicationName}   
SourceIP=${Event.sourceInfo.sourceIp}                
SourcePort=${Event.sourceInfo.sourcePort}                
Protocol=${Event.sourceInfo.ipProtocol}              
ServerIP=${Event.destInfo.serverIp}                
ServerPort=${Event.destInfo.serverPort}                
RuleName=${Rule.parent.displayName}

ImpervaError             
AlertNumber=${Alert.dn}            
CreateTime=${Alert.createTime}                
Description=${Alert.description}               
Username=${Alert.username}  
AlertType=${Alert.alertType}                
ServerGroup=${Alert.serverGroupName}            
Severity=${Alert.severity}           
Action=${Alert.immediateAction}                
Service=${Alert.serviceName}   
Application=${Alert.applicationName}   
SourceIP=${Event.sourceInfo.sourceIp}                
SourcePort=${Event.sourceInfo.sourcePort}                
Protocol=${Event.sourceInfo.ipProtocol}              
ServerIP=${Event.destInfo.serverIp}                
ServerPort=${Event.destInfo.serverPort}                
RuleName=${Rule.parent.displayName}

ImpervaCritical             
AlertNumber=${Alert.dn}            
CreateTime=${Alert.createTime}                
Description=${Alert.description}               
Username=${Alert.username}  
AlertType=${Alert.alertType}                
ServerGroup=${Alert.serverGroupName}            
Severity=${Alert.severity}           
Action=${Alert.immediateAction}                
Service=${Alert.serviceName}   
Application=${Alert.applicationName}   
SourceIP=${Event.sourceInfo.sourceIp}                
SourcePort=${Event.sourceInfo.sourcePort}                
Protocol=${Event.sourceInfo.ipProtocol}              
ServerIP=${Event.destInfo.serverIp}                
ServerPort=${Event.destInfo.serverPort}                
RuleName=${Rule.parent.displayName}

ImpervaSecurityBreach             
AlertNumber=${Alert.dn}            
CreateTime=${Alert.createTime}                
Description=${Alert.description}               
Username=${Alert.username}  
AlertType=${Alert.alertType}                
ServerGroup=${Alert.serverGroupName}            
Severity=${Alert.severity}           
Action=${Alert.immediateAction}                
Service=${Alert.serviceName}   
Application=${Alert.applicationName}   
SourceIP=${Event.sourceInfo.sourceIp}                
SourcePort=${Event.sourceInfo.sourcePort}               
Protocol=${Event.sourceInfo.ipProtocol}              
ServerIP=${Event.destInfo.serverIp}                
ServerPort=${Event.destInfo.serverPort}                
RuleName=${Rule.parent.displayName}

3. Review each security and system event policy configured on the Imperva SecureSphere device and apply the appropriate custom action set to the policy. For more information about configuring policies and applying action sets on the Imperva SecureSphere device, see the Imperva SecureSphere documentation.

Return to Top

Contact Information

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.

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.

© 2009 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.

Return to Top