Security Manager for Mantra |
|
Release Notes |
Date Published: May 2011 |
|
Configuring Security Manager for Mantra |
Security Manager for Mantra monitors events generated by Mantra devices in real-time. By detecting, alerting on, and automatically responding to critical events, Security Manager for Mantra helps identify, correct, and prevent possible configuration problems and external intrusions or attacks. Security Manager for Mantra collects data from the Mantra device and stores the data in secure repositories so you can archive it, create reports for management or auditing purposes, and analyze critical events to research issues. Security Manager for Mantra collects all syslog data you configure the Mantra device to send to the Windows agent. 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 identifies any known issues. Supported ProductsThis release supports Mantra 6.0.2, 7.0 and 7.6. Why Install This Module?Security Manager for Mantra monitors real-time events that the Mantra device sends to the Windows agent computer and archives all data received from the device. This data includes any change or access event generated for a monitored file, file share, or database that matches the policy criteria configured on the Mantra device. The volume and type of data that Security Manager for Mantra collects is determined by the configuration of the device and the policies you have created on the device. Security Manager for Mantra has the capability to monitor, alert and archive on the following events:
You can use the data Security Manager collects to produce various reports. For example, you can report on the largest number of failed logins to monitored databases from a given source. System RequirementsThe following table lists additional requirements for a Windows agent computer monitoring Mantra. For more information about agent requirements, see the Installation Guide for NetIQ Security Manager.
Installing This ModuleInstall 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. For more information about installing modules, see the Installation Guide for NetIQ Security Manager. After you install this module, ensure you follow the steps below to configure the Windows agent computer you want to monitor your Mantra device and the Mantra device being monitored. With the agent and Mantra device configured, use the Configuration Wizard to configure the Security Manager for Mantra module. Configuring the AgentAdd the name and IP address of the Mantra device to the Hosts file on the Windows agent computer. For more information about the Hosts file, see the Windows documentation. Configuring the Mantra DeviceSet up the Mantra device in your environment and configure the appropriate policies and custom actions for your organization. Security Manager collects all data received from the Mantra device and archives the data for analysis and reporting, but the data that the Mantra device sends is determined by the set of policies you configure on the device. For more information about setting up the Mantra device and configuring appropriate policies and actions, see the Mantra documentation. Once you have set up the Mantra device and configured policies and actions, complete the following required steps on the Mantra device. These steps ensure the Mantra 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 Mantra device to work with Security Manager:
To assign custom actions, perform the following steps: enable configure terminal
For example, the following command assigns the tzaction name SecurityManagerAlertCritical format-syslog "MantraSMCritical:$datetime| $server.type|$policy|$server.application|$server.info|$location.clientip| $location.clientport|$location.serverip|$location.serverport|$operation.file| $operation.sql|$user.serveruser|$user.hostuser|$content.table|$content.column| $content.filepath|$content.filename|$eventid|$session.source|$session.sourcename| $command.text|$size.rows|$Response.Status|$session.programname|$session.id"
Use the following syslog strings to assign the syslog format to the actions you want to send to Security Manager: Configuring Security Manager for MantraAfter configuring the Windows agent and monitored Mantra device, configure this module using the Configuration Wizard. Open the Configuration Wizard from the Security Manager Control Center, then click Support for Databases > Configure the module for Mantra. In the Configuration Wizard, specify the Windows agent computer you want to receive syslog data from the Mantra device and specify the IP address or host name of the Mantra device. For more information about using the Configuration Wizard to configure the Security Manager for Mantra module, see the Configuration Wizard Help. You can verify successful configuration of your environment by logging onto a Windows agent computer you specified in the Configuration Wizard for monitoring Mantra devices, opening a command prompt, and typing the following command:
netstat -ano -p UDP In the list of active connections, look for an open port used for syslog communication. The default port is 514. Creating Custom Processing RulesNetIQ 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. Mantra Event Fields Used by Security ManagerSecurity Manager for Mantra collects various fields from the data received from monitored Mantra devices. Security Manager stores some of those fields in the log archive and uses some fields for generating real-time alerts or in Forensic Analysis queries. The following table lists the Mantra 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.
Known IssuesNetIQ 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.
Upgrading Requires Updated Version of Previously Installed Log Manager for Mantra ModuleThe Security Manager for Mantra module replaces the Event Manager for Mantra and Log Manager for Mantra modules. However, if you upgrade from Log Manager for Mantra to the Security Manager for Mantra module, you must also use the Module Installer to install the latest version of the Log Manager for Mantra module, available on the NetIQ AutoSync Server. In the Module Installer, the name of the Log Manager for Mantra module is "Log Manager for Mantra (Obsolete)," located in the "zzz Obsolete Modules - Only select if already installed" category. If you did not previously install the Log Manager for Mantra or Event Manager for Mantra modules, you need to install only the Security Manager for Mantra module. (DOC300057) Top-Level Log Manager for Databases Processing Rule Group Displayed After UpgradeAfter you upgrade from the Log Manager for Mantra module to the Security Manager for Mantra module, the Development Console displays not only the new top-level Support for Databases processing rule group and Support for Mantra sub-processing rule group but also the previous top-level Log Manager for Databases processing rule group. The Log Manager for Databases processing rule group is only a "container" processing rule group that includes no rules of its own. You can delete the unneeded processing rule group by right-clicking Log Manager for Databases and selecting Delete. (ENG299313) Superseded Release Notes Not Removed on UpgradeThe Security Manager for Mantra module replaces the Event Manager for Mantra and Log Manager for Mantra modules. However, a known issue exists where Security Manager cannot remove old release notes files when installing updated modules. Release notes are installed by default in the \Program Files\NetIQ Security Manager\OnePoint\Documentation\Release Notes\Module Release Notes folder on the central computer, but may have been moved or copied to a different location in your environment. After upgrading this module, you should manually delete any superseded release notes in the default folder or in other folders. Contact InformationPlease 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. Legal NoticeTHIS 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. 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. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||