Log Manager for TippingPoint

Release Notes

Date Published: May 2009

 
 

 

Log Manager for TippingPoint allows you to collect, evaluate, and present data reported by a TippingPoint device.

Supported Products

This release supports the following products:

  • TippingPoint Security Management System version 2.5.1

Return to Top

Why Install This Module?

With this release of Log Manager for TippingPoint, Security Manager now provides support for the TippingPoint Intrusion Prevention System.

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 TippingPoint. 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 TippingPoint 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 instances of TippingPoint. 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 TippingPoint and the Windows agent are separated by a firewall, ensure the firewall allows syslog data through.
  • Install the Windows agent with TippingPoint 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:

  1. Open the Module Installer. Under Log Manager for IDS, the Module Installer lists both a Legacy and a non-Legacy version of the TippingPoint module.
  2. Select only the non-Legacy version of the module and click Install.
  3. 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.
  4. Configure the Windows agent. For more information, see the Installation Guide for NetIQ Security Manager.
  5. Configure the TippingPoint device to communicate with the Windows agent. For more information, see Configuring TippingPoint.

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:

  1. If you have access to reconfigure the TippingPoint devices and have an extra computer on which to install a new Security Manager 6.5 Windows agent, complete the following steps:
    1. 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.
    2. Open the Module Installer. Under Log Manager for IDS, the Module Installer lists both a Legacy and a non-Legacy version of the TippingPoint module.
    3. Select both the Legacy and non-Legacy versions of this module and click Install. If you do not install the Legacy version of TippingPoint, two instances of Configure the module for TippingPoint will appear in the Support for IDS 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.
    4. When the modules are installed, open the Configuration Wizard.
    5. In the left pane, click Support for IDS.
    6. Click Configure the module for TippingPoint.
    7. In the left pane, click Agents that monitor TippingPoint.
    8. Add the new Security Manager 6.5 Windows agent you just installed.
    9. In the left pane, click TippingPoint Devices.
    10. Add the TippingPoint devices from which you want the new Windows agent to receive data.
    11. Click Finish.
    12. Access the TippingPoint devices and reconfigure them to send data to the new Windows agent. For more information, see Configuring TippingPoint.
    13. Verify the new TippingPoint computer groups are populated with data.
    14. Open the Configuration Wizard.
    15. In the left pane, click Support for IDS.
    16. Click Configure the module for TippingPoint (Legacy).
    17. Remove all agents and devices, disabling the Legacy version of the module.
    18. Warning
      Ensure you have already reconfigured the TippingPoint devices to forward their syslog events to the new agent before you disable the Legacy version of the module, otherwise you will lose data.

    19. Click Finish.
    20. In the Schedule Configuration Changes window, select both checkboxes and click OK.
  2. If you do not have easy access to reconfigure TippingPoint 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:
  3. 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.

    1. Open the Module Installer. Under Log Manager for IDS, the Module Installer lists both a Legacy and a non-Legacy version of the TippingPoint module.
    2. Select both the Legacy and non-Legacy versions of this module and click Install. If you do not install the Legacy version of TippingPoint, two instances of Configure the module for TippingPoint will appear in the Support for IDS 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.
    3. When the modules are installed, open the Configuration Wizard.
    4. In the left pane, click Support for IDS.
    5. Click Configure the module for TippingPoint (Legacy).
    6. Take note of all settings:
      • Agent domains and names
      • Device names
      • Monitoring settings
    7. Clear all entries, disabling the module.
    8. Click Finish.
    9. In the Schedule Configuration Changes window, ensure both checkboxes are cleared.
    10. Warning
      Selecting these options will result in data loss as the agents you have removed will stop receiving data from your TippingPoint devices.

    11. Click OK.
    12. Click Configure the module for TippingPoint.
    13. Configure the non-Legacy version of TippingPoint with the settings you recorded earlier from the Legacy version.
    14. Click Finish.
    15. 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.
    16. If you want to configure additional TippingPoint devices in your installation, configure the Windows agent and then configure the TippingPoint device. For more information, see Configuring TippingPoint.

Return to Top

Configuring TippingPoint

Ensure you have configured TippingPoint to forward syslog events to a designated Windows agent using port 514. For more information about forwarding events, see the TippingPoint 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.

Return to Top

Legal Notice

Return to Top