Step 1. Configure your Log Sources
With Tripwire LogCenter, you can collect log messages from a wide variety of Log Sources (i.e. log-generating systems and devices).
The following topics explain how to configure some popular Log Sources to send log messages to a Manager of your choosing. In Step 5. Configure your Collectors, you will create the Collectors for your Log Sources.
Configuring a Blue Coat ProxySG Appliance
Configuring a Check Point Firewall
Configuring a Cisco Access Control Server (ACS)
Configuring a Cisco Adaptive Security Appliance (ASA)
Configuring a Cisco CATOS Switch
Configuring a Cisco IDS Sensor
Configuring a Cisco IOS Router
Configuring a Cisco PIX Firewall
Configuring a Fortinet Fortigate Firewall
Configuring an Internet Information Server (IIS)
Configuring a McAfee ePO Server
Configuring a Microsoft Windows System
Configuring a Microsoft IAS Server
Configuring a Microsoft ISA Server
Configuring a Microsoft SQL Server
Configuring an Nmap Security Scanner
Configuring an Oracle Database Server
Configuring a Snare Windows Server
Configuring a Syslog or Rsyslog Module
Configuring a Syslog-ng Module
Configuring a Tenable Nessus Vulnerability Scanner
Configuring a Tripwire VnE Manager
Configuring a VMware ESX Server
Configuring a VMware ESXi Server
|
Notes |
For the list of Log Sources available with this release, see: https://www.tripwire.com/products/tripwire-log-center/system-requirements/ To configure other Log Sources, contact Tripwire Support for assistance. If a Monitored Asset does not exist for the Log Source, TLC will automatically create the Asset when it begins receiving log messages from the Log Source if:
Otherwise, you will need to create a Monitored Asset for the Log Source (see Working with Monitored Assets). For more information about Auto-Discovery, see How does Auto-Discovery work?. |
|---|