Security Manager for VMware ESXi |
Release Notes |
Date Published: September 2011 |
Configuring ESX and ESXi for Remote Logging |
Security Manager for VMware ESXi allows you to monitor VMware ESX and ESXi systems. This module provides knowledge so you can proactively manage ESX and ESXi systems and identify issues before they become critical. By detecting and alerting on critical events in real time, Security Manager for VMware ESXi helps indicate and prevent possible intrusions, attacks, and configuration problems. This module increases the security, availability, and performance of ESX and ESXi systems. Security Manager for VMware ESXi monitors syslog messages generated by ESX and ESXi systems, including the following:
Security Manager for VMware ESXi highlights events that may indicate configuration changes or attacks, so you can quickly take corrective or preventative action. For example, Security Manager for VMware ESXi enables you to perform the following tasks:
Security Manager for VMware ESXi also collects events from logs and stores them in secure repositories so you can archive the data, create reports for management or auditing purposes, and analyze critical events to research issues. Security Manager for VMware ESXi collects all log messages you configure the ESX or ESXi system 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 any installation requirements, and identifies any known issues. Supported ProductsThis release supports the following products:
Why Install This Module?Security Manager for VMware ESXi provides support for data received from monitored VMware ESX or ESXi systems. The volume and type of data that Security Manager for VMware ESXi collects is determined by the configuration of the ESX or ESXi system and the policies you have created on the ESX or ESXi system. System RequirementsThe following table lists additional requirements for a Windows agent. 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 Installation 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 VMware ESXi. For more information about using the Configuration Wizard, see the User Guide for NetIQ Security Manager. Configuring ESX and ESXi for Remote LoggingAfter you install the module, you must configure the ESX or ESXi system to log events to a remote host where Security Manager for VMware ESXi can access them. To configure ESX or ESXi remote logging:
ESX and ESXi Event Fields Used by Security ManagerSecurity Manager for VMware ESXi collects various fields from the data received from the ESX and ESXi systems. 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 ESX and ESXi 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 processing rules, see the Programming Guide for NetIQ Security Manager.
Contact InformationOur 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. 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. 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. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||