Supported Products
Why Install This Module?
System Requirements
Installing This Module
Upgrading This Module
Configuring the Agent
Configuring the NetScreen Firewall Device
Contact Information
Legal Notice
|
|
Event Manager for Firewalls allows you to monitor NetScreen firewall devices. By detecting, alerting on, and automatically responding to critical events in realtime, Event Manager for Firewalls helps indicate, correct, and prevent possible external intrusions, attacks, and configuration problems.
Event Manager for Firewalls monitors syslog messages generated by NetScreen firewall devices. Event Manager for Firewalls 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:
- Detect misconfigurations in your firewall environment
- Monitor failover between primary and standby firewalls
- Identify attacks, such as unusual port scans, and then respond with an alert
- Identify policy misuse
- Trace administrative access and actions
- Notify the Security Specialists notification group of serious issues
- Monitor your environment from a single console
Supported Products
This release supports the following products:
- NetScreen firewalls with ScreenOS 5.x
- NetScreen firewalls with ScreenOS 6.x
Return to Top
Why Install This Module?
Event Manager for Firewalls provides the following important new capabilities:
- Adds support for NetScreen ScreenOS 6.x
- Improves usability of rules and views
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.
Return to Top
System Requirements
The following table lists additional requirements for a Windows agent acting as the proxy agent for NetScreen firewall devices. 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 use for a Windows agent monitoring NetScreen Firewall could reach 256 MB or higher.
|
Operating System
|
All supported Windows agent platforms.
|
Software
|
- Ensure you have Security Manager 6.5 or later installed.
- A Windows agent can monitor one or more NetScreen firewalls. For more information about the number of instances one agent can support, see the NetIQ Security Manager Knowledge Base article NETIQKB51404 at www.netiq.com/support/sm/.
- If the NetScreen device and the agent are separated by a firewall, ensure the firewall allows syslog data through.
- Install each Windows agent on a subnet as physically close to the firewall as possible. Fewer network hops provide better performance.
- Install the Windows agent with NetScreen support on a separate computer from the database server or central computer.
|
Return to Top
Installing This Module
Complete the following steps to install this module in a new Security Manager 6.5 installation.
To install this module:
- Open the Module Installer. Under Event Manager for Firewalls, the Module Installer lists both a Legacy and a non-Legacy version of the NetScreen Firewall module.
- Select only the non-Legacy version of the module and click Install.
- Configure the new module using the Configuration Wizard. For more information about accessing the Configuration Wizard, see the User Guide for NetIQ Security Manager. For more information about how to enter information, click the question mark in the bottom left of the Configuration Wizard to expand a Help window to the right.
- Configure the Windows agent. For more information, see the Installation Guide for NetIQ Security Manager.
- Configure the NetScreen firewall device to communicate with the Windows agent. For more information, see Configuring the NetScreen Firewall Device.
Return to Top
Upgrading This Module
After you have upgraded your existing installation to Security Manager 6.5, complete either step 1 or step 2 in the following procedure to upgrade a previous version of this module.
To upgrade this module:
- If you have access to reconfigure the NetScreen firewall devices and have an extra computer on which to install a new Security Manager 6.5 Windows agent, complete the following steps:
- Install and configure a new Security Manager 6.5 Windows agent to receive syslog messages. For more information, see the Installation Guide for NetIQ Security Manager.
- Open the Module Installer. Under Event Manager for Firewalls, the Module Installer lists both a Legacy and a non-Legacy version of the NetScreen Firewall module.
- Select both the Legacy and non-Legacy versions of this module and click Install. If you do not install the Legacy version of NetScreen Firewall, two instances of Configure the module for NetScreen Firewall will appear in the Support for Firewalls section of the Configuration Wizard. You will then have to open each instance to see which one is Legacy. When you install both versions, Security Manager renames Configuration Wizard links, existing rule groups, and documentation so you can easily distinguish between legacy items and new items, minimizing confusion.
- When the modules are installed, open the Configuration Wizard.
- In the left pane, click Support for Firewalls.
- Click Configure the module for NetScreen Firewall.
- In the left pane, click Agents that monitor NetScreen Firewall.
- Add the new Security Manager 6.5 Windows agent you just installed.
- In the left pane, click NetScreen Firewall Devices.
- Add the NetScreen firewall devices from which you want the new Windows agent to receive data.
- Click Finish.
- Access the NetScreen firewall devices and reconfigure them to send data to the new Windows agent. For more information, see Configuring the NetScreen Firewall Device.
- Verify the new NetScreen Firewall computer groups are populated with data.
- Open the Configuration Wizard.
- In the left pane, click Support for Firewalls.
- Click Configure the module for NetScreen Firewall (Legacy).
- Remove all agents and devices, disabling the Legacy version of the module.
|
Warning
Ensure you have already reconfigured the NetScreen firewall devices to forward their syslog events to the new agent before you disable the Legacy version of the module, otherwise you will lose data.
|
- Click Finish.
- In the Schedule Configuration Changes window, select both checkboxes and click OK.
- If you do not have easy access to reconfigure NetScreen firewall devices or you do not have an extra computer on which to install a new Security Manager 6.5 Windows agent, complete the following steps:
|
Note
If you do not complete the following steps in a timely manner, it is possible some data collected will be stored as unrecognized syslog events in the log archive under source Generic Syslog.
|
- Open the Module Installer. Under Event Manager for Firewalls, the Module Installer lists both a Legacy and a non-Legacy version of the NetScreen Firewall module.
- Select both the Legacy and non-Legacy versions of this module and click Install. If you do not install the Legacy version of NetScreen Firewall, two instances of Configure the module for NetScreen Firewall will appear in the Support for Firewalls section of the Configuration Wizard. You will then have to open each instance to see which one is Legacy. When you install both versions, Security Manager renames Configuration Wizard links, existing rule groups, and documentation so you can easily distinguish between legacy items and new items, minimizing confusion.
- When the modules are installed, open the Configuration Wizard.
- In the left pane, click Support for Firewalls.
- Click Configure the module for NetScreen Firewall (Legacy).
- Take note of all settings:
- Agent domains and names
- Device names
- Monitoring settings
- Clear all entries, disabling the module.
- Click Finish.
- In the Schedule Configuration Changes window, ensure both checkboxes are cleared.
|
Warning
Selecting these options will result in data loss as the agents you have removed will stop receiving data from your NetScreen firewall devices.
|
- Click OK.
- Click Configure the module for NetScreen Firewall.
- Configure the non-Legacy version of NetScreen Firewall with the settings you recorded earlier from the Legacy version.
- Click Finish.
- In the Schedule Configuration Changes window, select both checkboxes and click OK. Selecting both options forces the Legacy module to empty all of its computer groups, causing the version 6.5 module to fill up its computer groups with all of the newly dropped agents and devices.
- If you want to configure additional NetScreen firewall devices in your installation, configure the Windows agent and then configure the NetScreen firewall device. For more information, see Configuring the Agent and Configuring the NetScreen Firewall Device.
Return to Top
Configuring the Agent
Add the name and IP address of the NetScreen firewall 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 the NetScreen Firewall Device
NetScreen firewalls require configuration before Event Manager or Log Manager can begin
monitoring or collecting data from them. Configure each NetScreen firewall device to forward
syslog messages to the Windows agent acting as the proxy agent.
To configure support for NetScreen:
- Configure the NetScreen firewall to send syslog messages to the Windows agent.
If you want to receive traffic messages on your Windows agent, turn on Syslog Traffic
Messaging.
You will receive a large number of messages with this option. Security Manager stores
them for log analysis, but does not report them as they occur.
- Configure the NetScreen firewall to report only the messages with the severity you want to
monitor. For example, debug messages should normally be disabled due to the high
number of messages created when debug messages are reported.
- On the NetScreen device, disable syslog VPN and enable Syslog.
- If your NetScreen syslog messages have a time stamp, ensure the time stamp has a year,
month, day, hour, minutes, and seconds in the format YYYY-MM-DD-hh-mm-ss.
|
Note
If your NetScreen syslog messages do not have a time stamp in the right format,
Security Manager uses the local time of the agent for the log message time.
|
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.
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.
Return to Top |