Log Correlation Engine 3.0 Client Guide May 5, 2009 (Revision 2)

Transcription

1 Log Correlation Engine 3.0 Client Guide May 5, 2009 (Revision 2) The newest version of this document is available at the following URL:

2 Table of Contents TABLE OF CONTENTS... 2 INTRODUCTION... 3 LOG CORRELATION ENGINE CLIENT OVERVIEW... 3 LCE CLIENT TYPES AND PLATFORMS... 4 QUICK START SUMMARY... 5 LOG CORRELATION ENGINE UNIX CLIENTS... 6 UPGRADING LCE CLIENTS FROM THUNDER CLIENTS... 6 INSTALLING THE LCE UNIX CLIENTS... 7 Installation Directories... 8 REMOVING THE LCE CLIENTS... 9 LCE UNIX CLIENT CONFIGURATION Log Correlation Engine Log Agent Log Correlation Engine OPSEC Client Tenable Network Monitor Client Tenable RDEP Monitor Client TNS NetFlow Monitor Client LCE UNIX CLIENT OPERATIONS Starting the LCE Unix Clients Halting the LCE Unix Clients Monitoring Log Correlation Engine Client Status LOG CORRELATION ENGINE WINDOWS CLIENT UPGRADING LCE CLIENTS FROM THUNDER CLIENTS INSTALLING THE WINDOWS CLIENT Installation Location Service Location USING THE LCE CLIENT ON VISTA AND WINDOWS REMOVING THE LCE WINDOWS CLIENT WINDOWS CLIENT CONFIGURATION LCE WINDOWS CLIENT OPERATIONS Starting the LCE Windows Client Halting the LCE Windows Client Remote Installation for Multiple Hosts FOR MORE INFORMATION ABOUT TENABLE NETWORK SECURITY APPENDIX 1: SAMPLE INSTALLATION OUTPUT APPENDIX 2: SAMPLE REMOVE OUTPUT APPENDIX 3: SAMPLE WINDOWS WMI CONFIGURATION FILE

3 Introduction This document describes the different clients that are available for Tenable Network Security s Log Correlation Engine 3.0. Please share your comments and suggestions with us by ing them to support@tenablesecurity.com. A working knowledge of Secure Shell, regular expressions and the Security Center operation and architecture is assumed. The reader should be familiar with general log formats from various operating systems, network devices and applications, as well as a basic understanding of Unix. This document is intended to be used with LCE installations for version 3.0 and higher. If you are using an older version of LCE (known as Thunder ), please refer to the LCE 2.0 Client Guide. Standards and Conventions Throughout the documentation, filenames, daemons and executables are indicated with a courier bold font such as gunzip, httpd and /etc/passwd. Command line options and keywords will also be printed with the courier bold font. Command line options may or may not include the command line prompt and output text from the results of the command. Often, the command being run will be boldfaced to indicate what the user typed. Below is an example running of the Unix pwd command. # pwd /opt/lce/ # Important notes and considerations are highlighted with this symbol and grey text boxes. Log Correlation Engine Client Overview The Log Correlation Engine (LCE) Clients are agents that are installed on systems whose logs, network traffic, performance and other types of protocols and technologies are to be monitored by forwarding the data securly to the LCE server. Once an LCE is installed and configured, one or more LCE clients can be used to send information back for normalization and correlation. This document details specific methods that LCE clients can be installed on systems to gather information and events from the following sources: Windows Event Logs Windows and Unix system and application logs Checkpoint OPSEC events Cisco RDEP events Netflow Sniffed TCP and UDP network sessions Sniffed SYSLOG messages in motion 3

4 Many of these agents are required to take advatage of the LCE s power. For example, to perform Blacklist correlation, the LCE clients that monitor network traffic via sniffing or netflow can be used to identify connections with known hostile IP addresses even if you don t have firewall or proxy logs. Running LCE Clients Directly on the LCE Server LCE clients can be run directly on the LCE server. They must be configured to connect to either the localhost ( ) or the external IP address of the LCE server. Multiple LCE client types (such as a and a Tenable NetFlow Monitor) can be run at the same time as well. See the section titled LCE Client Types and Platforms for a list of available clients. While using s to watch LCE log files, be extremely careful to avoid feedback loops. For example, choosing to tail the lce.log file would cause any log saved by the lced process to be grabbed by the, sent back to pced and repeated indefinitely. Running Multiple LCE Clients on One Host Remote systems can also run multiple LCE clients. All remote LCE clients must be configured with the same password that matches the one configured on the LCE server for the client s IP address. Only one entry is required in the lce.conf file on the LCE server. Maximum Number of LCE Clients A maximum of 8,192 individual LCE clients can be specified in the lce.conf file. If more are configured, the LCE server will produce an error informing the user of the limit. The LCE itself can be configured with the specific IP address of the remote LCE clients, or network CIDR blocks can be used. LCE Client Types and Platforms There are a number of different LCE client types available. All LCE clients report performance statistics (memory, disk space and CPU usage) on their host regardless of platform. Client Type Platforms Function Red Hat ES 3, ES 4, ES 5 FreeBSD 6 Fedora Core 6 Solaris SPARC (8,9,10) Monitors specific log files or directories for different operating systems. These clients will tail any number of log files and send the observed data to the LCE server for analysis. The Windows Log Agent also can monitor: Entries in the Windows event log USB device inserts and removals Entries in the event logs of remote Windows servers 4

5 Tenable RDEP Monitor Mac OS X Dragon Appliance MS Windows XP Professional, Windows Server 2003, Windows Server 2008, Windows Vista Red Hat ES 3, ES 4, ES 5 s are designed to send log data to the LCE. Log data is in ASCII text format and will never include binary files. The LCE Log Agents will check all data before sending, specifically omitting binary files such as.zip,.gz,.tar,.lzh,.bz2, etc. If a binary file is sent to the LCE, it has the potential to corrupt the database. This functionality is automatically performed by the LCE client software. Retrieves messages from one or more Cisco IDS devices using Cisco s Remote Data Exchange Protocol (RDEP) that can send events to the LCE for processing, or it can be configured to send IDS events directly to Security Center via SYSLOG. LCE OPSEC Client Red Hat ES 3, ES 4, ES 5 Based on Checkpoint s API for Linux, it monitors OPSEC compliant devices for new events. Tenable Netflow Monitor Tenable Network Monitor Red Hat ES 3, ES 4, ES 5 FreeBSD 6 Red Hat ES 3, ES 4, ES 5 FreeBSD 6 Debian 4 Receives NetFlow messages for logging to the LCE. Messages can be sent from multiple NetFlow sources to a single TNS_Netflow client. The client supports NetFlow version 5 and 9. Designed to monitor network traffic and send session information to the LCE server. Sniffs network traffic to identify TCP sessions as well as UDP, ICMP, and IGMP activity. It also has a very useful feature of sniffing live SYSLOG traffic in motion and sending it to the LCE as if the traffic were originally destined for it. This makes it very easy to centralize logs and not rely on forwaring of events from a different log server. Quick Start Summary As clients are added for monitoring by the Log Correlation Engine (LCE), the following process can be used to ensure installation success: 1. Install the client as per the instructions in the LCE Unix Clients Installation section or the LCE Windows Client Installation section. 2. Configure the clients with the IP address of the LCE server as well as a password. Do not start the client yet. See the appropriate section to Configure LCE Unix Clients or LCE Windows Clients. 5

6 3. On the LCE server, edit the lce.conf file to add in the new parameters for the LCE client. Be sure to add in the correct remote IP address of the LCE client as well as the matching password. 4. Restart the LCE server. 5. Start the LCE client. 6. From the command prompt (Unix or DOS) run the command netstat an grep to display any network sessions on port This is the port used for communication to the LCE server. What to do if the Log Correlation Engine Client cannot Connect If the LCE client cannot connect, try the following: Check to see if there is a local firewall, network firewall or other network issue which would prevent connection from the LCE client to the LCE server. To test this, run a sniffer on the LCE server for port If no connections are observed from the system running the LCE client, something is blocking the connection. Running a sniffer on the system of the LCE client may also help determine if something is blocking. Verify that the passwords are correct. Both the LCE client and LCE server will log bad connection errors. Verify that the IP addresses of the LCE client and LCE server are correct. The client will not connect to the LCE server if it has the wrong IP address and the LCE server will not accept a random client unless it is specifically configured in the lce.conf file. Upgrade Considerations The LCE 3.0 clients are designed to work optimally with the LCE 3.0 server, but they will also function with the LCE 2.X server. However, some of the new features may not function with the older server. LCE 3.0 clients contain many new features since the 2.x releases. In an environment with a Thunder 2.x server and LCE 3.x clients, some of the new features (e.g., heartbeatfrequency, statistics-frequency) will be backward compatible. Some features, such as the new server-port directive, will not work unless the server is upgraded to LCE 3.x. Log Correlation Engine Unix Clients The LCE 3.0 Unix clients are shipped in a package format appropriate for the platform operating system and also includes system start up files. Upgrading LCE Clients from Thunder Clients If you were using the older Thunder clients, its is recommended that you do a fresh installation and save your old configuration files. You can use these as reference to configure the new configuration file that is provided in the release. To upgrade an existing LCE Unix Client, halt the running process, move the current configuration file to a safe place, install the new distribution and edit the new configuration using your old one as a reference. 6

7 Installing the LCE Unix Clients Users of the Log Correlation Engine Unix Client for Red Hat ES 3 must have libpcap installed. Starting with LCE release 3.0, all LCE clients are shipped with an installation package appropriate to the host Operating System (rpm, dpkg, pkgadd, etc). Each client comes with an example client configuration file (e.g., lce_client.conf for the ), the program binary, and is installed into the appropriate client directory, which will be created if it does not already exist. To install the LCE client, obtain the package for your OS platform and desired client and install as the root user on the target client system. The following table provides an installation example for each available LCE client on all supported platforms. Any special installation instructions are provided in a note following the example. LCE Client Type Installation Example Red Hat ES 3, ES 4, ES 5 Tenable RDEP Monitor LCE OPSEC Client Tenable NetFlow Monitor Tenable Network Monitor # rpm -ivh lce_client esx.i386.rpm # rpm -ivh TenableRdepMonitor esX.i386.rpm # rpm -ivh lce_opsec esx.i386.rpm # rpm -ivh TenableNetFlowMonitor esX.i386.rpm # rpm -ivh TenableNetworkMonitor esX.i386.rpm FreeBSD # pkg_add lce_client freebsd.tbz Add the following line to /etc/rc.conf.local or /etc/rc.conf to enable the LCE client service: lce_clientd_enable="yes" Tenable Network Monitor Tenable NetFlow Monitor # pkg_add TenableNetworkMonitor freebsd.tbz Add the following line to /etc/rc.conf.local or /etc/rc.conf to enable the Network Monitor service: tnmd_enable="yes" # pkg_add TenableNetFlowMonitor freebsd.tbz Add the following line to /etc/rc.conf.local or 7

8 /etc/rc.conf to enable the Netflow Monitor service: tfmd_enable="yes" Fedora Core # rpm ivh lce_client fc6.i386.rpm Solaris # gunzip -c lce_client sparc.pkg.tar.gz tar -xvf - Mac OS X # pkgadd -d. The following packages are available: 1 lce-client LCE Client (sparc) Select package(s) you wish to process (or 'all' to process all packages). (default: all) [?,??,q]: 1 Download lce_client osx.tar.gz to the client system and click on it to run the Mac Installer. Debian 4 Tenable Network Monitor # dpkg i TenableNetworkMonitor debian4-i386.deb Dragon Appliance # installpkg lce_client dragon-skw.tgz Depending on how the users system is configured, the upgrade may produce messages such as: /sbin/ldconfig: File /usr/lib/libcprts.so is too small, not checked. These are not errors, just informational messages. A successful installation is indicated by the return of the command prompt with no errors. See Appendix 1 for example output of several installations. Once the client is installed, it is recommended that you customize the provided configuration file for your environment. Please see the section LCE Unix Client Configuration for more information. Installation Directories 8

9 Client Software Installation Directory Red Hat ES 3, ES 4, ES 5 LCE OPSEC Client Tenable NetFlow Monitor Tenable Network Monitor Tenable RDEP Monitor /opt/lce_client /opt/lce_opsec /opt/netflow_monitor /opt/network_monitor /opt/rdep_monitor FreeBSD Tenable NetFlow Monitor Tenable Network Monitor /usr/local/lce_client /usr/local/netflow_monitor /usr/local/rdep_monitor Fedora Core /opt/lce_client Solaris /opt/lce_client Mac OS X /opt/lce_client Debian Tenable Network Monitor /opt/network_monitor Dragon Appliance /opt/lce_client Removing the LCE Clients To remove the LCE client, login as the root user, stop the client daemon (see the section Halting the LCE Unix Clients for directions) and run the appropriate commands for your client and platform as shown in the following table: LCE Client Type Removal Example Red Hat ES 3, ES 4, ES 5 9

10 Determine the name of the installed package: # rpm -qa grep lce_client lce_client esx.2 # Remove the installed package: # rpm -ev lce_client esx.2 Tenable RDEP Monitor Determine the name of the installed package: # rpm -qa grep TenableRdepMonitor TenableRdepMonitor esX.2 # Remove the installed package: # rpm -ev TenableRdepMonitor esX.2 LCE OPSEC Client Determine the name of the installed package: # rpm -qa grep lce_opsec lce_opsec esx.2 # Remove the installed package: # rpm -ev lce_opsec esx.2 Tenable NetFlow Monitor Determine the name of the installed package: # rpm -qa grep TenableNetFlowMonitor TenableNetFlowMonitor esX.2 # Remove the installed package: # rpm -ev TenableNetFlowMonitor esX.2 Tenable Network Monitor Determine the name of the installed package: # rpm -qa grep TenableNetworkMonitor TenableNetworkMonitor esX # Remove the installed package: # rpm -ev TenableNetworkMonitor esX FreeBSD Determine the name of the installed package: 10

11 # pkg_info grep lce lce_client TNS Log Correlation Engine tail client # Remove the installed package: # pkg_delete lce_client Delete the following line from /etc/rc.conf.local or /etc/rc.conf to remove the LCE client service: lce_clientd_enable="yes" Tenable Network Monitor Determine the name of the installed package: # pkg_info grep network network_monitor TNS Log Correlation Engine tail client # Remove the installed package: # pkg_delete network_monitor Delete the following line from /etc/rc.conf.local or /etc/rc.conf to remove the LCE client service: tnmd_enable="yes" Tenable NetFlow Monitor Determine the name of the installed package: # pkg_info grep netflow netflow_monitor TNS Log Correlation Engine tail client # Remove the installed package: # pkg_delete netflow_monitor Delete the following line from /etc/rc.conf.local or /etc/rc.conf to remove the LCE client service: tfmd_enable="yes" Fedora Core Determine the name of the installed package: # rpm -qa grep lce_client lce_client fc8.2 11

12 Remove the installed package: # rpm -ev lce_client fc8.2 Solaris Determine the name of the installed package: # pkginfo grep lce security lce-client LCE Client # Remove the installed package: # pkgrm lce-client Mac OS X To remove the LCE client on a Mac, you can either use a third party de-installation program or run the following commands from the command line prompt: # rm /opt/lce_client/lce_clientd # rm r /System/Library/StartupItems/LCEClient Debian 4 Tenable Network Monitor Determine the name of the installed package: # dpkg l grep tnm ii tnm Tenable Network Monitor. This program sniffs # Remove the installed package: # dpkg -r tnm Dragon Appliance # removepkg lce_client dragon-skw.tgz LCE Unix Client Configuration The example configuration file has limited logging enabled and should be customized for the local applications and operating system. This section describes how to configure the LCE Unix clients. The configuration files for each of the clients on the supported operating systems are listed in the table below: 12

13 Client Software Configuration File Red Hat ES 3, ES 4, ES 5 LCE OPSEC Client Tenable NetFlow Monitor Tenable Network Monitor Tenable RDEP Monitor /opt/lce_client/lce_client.conf /opt/lce_opsec/lce_opsec.conf /opt/netflow_monitor/tfm.conf /opt/network_monitor/tnm.conf /opt/rdep_monitor/trm.conf FreeBSD Tenable Log Agent Tenable NetFlow Monitor Tenable Network Monitor /usr/local/lce_client/lce_client.conf /usr/local/netflow_monitor/tfm.conf /usr/local/rdep_monitor/trm.conf Fedora Core /opt/lce_client/lce_client.conf Solaris /opt/lce_client/lce_client.conf Mac OS X /opt/lce_client/lce_client.conf Debian Tenable Network Monitor /opt/network_monitor/tnm.conf Dragon Appliance /opt/lce_client/lce_client.conf If changes are to be made to an existing configuration file and the client is already running, make the changes, halt the client and then restart it. See Halting the LCE Unix Client. Log Correlation Engine Log Agent LCE Unix Log Agents can be used to monitor log files which contain events received from other devices. For example, a Unix server could be configured to receive SYSLOG events from a nearby router. The and LCE server would parse all events as if they originally came from the Unix server. If there were IP address information in the SYSLOG message, then the LCE server would assign the source and destination events accordingly. 13

14 To configure the lce.conf file, enter in a list of files or directories to be monitored. You will also need to include the relevant IP address and shared secret key of the LCE server in the lce-server section. An example lce_client.conf configuration file is shown below: options { # LCE client log messages are written to a file named according to # the date in the directory specified below. log-directory./ # The files specified below are tailed. tail-file /var/log/messages tail-file /var/log/secure # All files in directories specified with the tail-dir option will # be tailed. # This can also be limited to files matching a certain pattern. # tail-dir /var/log/*.log # tail-dir /security_logs/* # When a directory is monitored, the LCE client periodically re- # scans the directory to determine if any new files have been added. # The next option determines the number of seconds between each # scan. scan-frequency 60 # When the following line is uncommented, debugging is enabled in # the client. # client-debug # The following section defines the IP at which the LCE server is # located, as well as the authentication required to log in. Only 1 # LCE server is currently supported. For example, use the following # to configure an LCE server at (localhost) using the # password "s3kret" lce-server { client-auth auth-secret-key s3kret } # The LCE server can be configured to listen on a user-specified # port. The setting below should match the server setting, which is # by default. server-port # The heartbeat-frequency option defines the number of seconds # between each pair of client heartbeat messages that are sent to # the server. heartbeat-frequency 300 # The LCE client provides the option of periodically sending a log # file containing performance statistics to the LCE server. The # following option determines the number of minutes between each # performance statistics report. When the next line # is commented out or removed, performance reporting is disabled. statistics-frequency 60 14

15 } Two types of log directives can be used. The tail-file directive specifies a specific file to follow. The tail-dir directive specifies all files in a specific directory to be followed. This is invoked by specifying the path, followed by an asterisk. For example, the above configuration could be simplified to: options { tail-dir /var/log/* tail-dir /var/log/httpd/* } lce-server { client-auth auth-secret-key tenable } This would cause all new files or any existing files with new content in the /var/log and /var/log/httpd directories to be tailed by the. Note that only regular text files are looked at in a specified directory not special files or sub-directories. Comments can be entered into the configuration file with lines starting with the # character. Once the configuration file is updated, check the client log to ensure it is operating properly and to validate that configuration directives were configured correctly. lce_client.conf The following table describes the configuration options available in the lce_client.conf configuration file: Option log-directory tail-file tail-dir scan-frequency client-debug Description Directory where logs are stored. If the logdirectory keyword is commented out, then the client install directory will be used. Otherwise ISO9000 compliant log files will be saved in the specified directory. Specifies which log(s) are to be tailed for monitoring by the. Configuration file allows multiple tail-file options. Specifies a directory or directories in which the will tail all regular text files. Frequency with which the will re-scan the taildir directory to determine if new files have been added. Set debug mode on or off. 15

16 lce-server server-port heartbeat-frequency statistics-frequency Directs the to the IP address of the LCE, and specifies the password used to connect. Note: Each client can only connect to one server, and will connect to the first server specified if multiple lce-server directives exist. The port the LCE listens to as designated by the lce-server directive. The can be configured to send a heartbeat message to the LCE. This message indicates that the client is still alive and performing normally. The frequency with which the sends a log entry containing performance statistics to the LCE. The following is an example of the heartbeat message sent from the to the LCE: # LCE Client Heartbeat Hostname: holodeckvista.lab.tenablesecurity.com IP: Revision: LCE Client Performance Reporting When the sends performance statistics to the LCE server, the exact information sent depends on the operating system (e.g., swap and cache data is not available on all platforms). The performance report is sent to the LCE server. The various performance logs are normalized to the lce event type for easy analysis. TASL scripts are available to monitor the performance of various systems and generate an alert when low resources are detected. When viewed using the Raw Syslog Events tool, the data appears similar to the following: LCE-Client-Statistics [Config280VM1, , Network Monitor 3.0] Network Statistics Udp: 1171 packets received 184 packets to unknown port received. 0 packet receive errors 1210 packets sent Memory Load: / kilobytes main memory used (92.61%), with kilobytes free (7.39%) 208/ kilobytes swap memory used (0.01%), with kilobytes free (99.99%) kilobytes of data cached Disk Load: 3.6G/4.3G (46%) disk storage used on LCE filesystem (54% free) 16

17 CPU load average: 0.33, 0.25, 0.14 Log Correlation Engine OPSEC Client To configure the LCE OPSEC Client, edit the lce_opsec.conf file with a text editor. A script which pulls a cryptographic key from the desired OSPEC source is also required. The opsec_pull_cert script is bundled with OPSEC SDK and can be found at the following link: This script will be used in the event that authenticated connections are required from the Checkpoint firewall. The OPSEC API supports a variety of features for connecting to OPSEC enabled devices. These options are defined with examples throughout the lce_opsec.conf file. The file also includes two keywords for specifying the location of the LCE server IP and the shared secret. The following is an example of the lce_opsec.conf configuration file: # Messages generated during runtime will be stored in a dated file # of the format YYYYMon.log in the following directory. LOG_DIR="/opt/lce_opsec/" # DEBUG_MODE={yes YES no NO} DEBUG_MODE="no" # This option defines the location of the FW1 management station. # Only 1 station is currently supported. # FW1_SERVER=<IP address of FW1-Management Station> FW1_SERVER=" " # FW1_PORT=<Port number for LEA connections> FW1_PORT="50001" # FW1_LOGFILE=<Name of FW1-Logfilename> FW1_LOGFILE="fws.log" # FW1_OUTPUT=<files logs> FW1_OUTPUT="logs" # FW1_TYPE=<NG ng 2000> FW1_TYPE="NG" # FW1_MODE=<audit AUDIT normal NORMAL> FW1_MODE="NORMAL" # This option defines the number of seconds between each pair of client # heartbeat messages that are sent to the server. HEARTBEAT_FREQUENCY="300" # The LCE client provides the option of periodically sending a log file # containing performance statistics to the LCE server. The following option # determines the number of minutes between each performance statistics # report. When the next line is commented out or removed, performance 17

18 # reporting is disabled. STATISTICS_FREQUENCY="60" # ONLINE_MODE=<yes YES no NO> ONLINE_MODE="no" # RESOLVE_MODE=<yes YES no NO> RESOLVE_MODE="no" # SHOW_FIELDNAMES=<yes YES no NO> SHOW_FIELDNAMES="yes" # RECORD_SEPARATOR=<char> RECORD_SEPARATOR=" " # DATEFORMAT=<CP UNIX STD> # CP = " 3Feb :15:16" # UNIX = " " # STD = " :15:16" DATEFORMAT="STD" # # FW1-Authentication settings # # AUTHENTICATES={yes YES no NO} AUTHENTICATED="no" # OPSEC_CERTIFICATE=<Path and Name of Opsec Certificate> OPSEC_CERTIFICATE="opsec.p12" # OPSEC_CLIENT_DN=<DN of Opsec-Client> OPSEC_CLIENT_DN="CN=LEA-Client,O=fw1-ng.fellhauer-web.de..n77jpa" # OPSEC_SERVER_DN=<DN of Opsec-Server> OPSEC_SERVER_DN="cn=cp_mgmt,o=fw1-ng.fellhauer-web.de..n77jpa" # This option defines the location and authentication settings of the # Log Correlation Engine. Only 1 server is currently supported. LCE_SERVER=" " LCE_PASSWORD="tenable" LCE_PORT="31300 While running, the user should observe a network connection between the lce_opsec client and the Checkpoint firewall on port 50001, as well as a network connection between the lce_opsec client and the LCE server on port lce_opsec.conf The following table describes the configuration options available in the lce_opsec.conf configuration file: Option Description 18

19 LOG_DIR DEBUG_MODE FW1_SERVER FW1_PORT FW1_LOGFILE FW1_OUTPUT Log message storage point. Set debug mode on or off. Location of the FireWall-1 management station. Listening port of the FireWall-1 management station as defined in the FW1_SERVER directive. Name of the FireWall-1 log file. Specify if the FireWall-1 log file output is files or logs. FW1_TYPE Specify the FireWall-1 type NG, ng or FW1_MODE HEARTBEAT_FREQUENCY STATISTICS_FREQUENCY ONLINE_MODE RESOLVE_MODE SHOW_FIELDNAMES RECORD_SEPARATOR DATEFORMAT AUTHENTICATED OPSEC_CERTIFICATE OPSEC_CLIENT_DN OPSEC_SERVER_DN LCE_SERVER LCE_PASSWORD LCE_PORT Specify the FireWall-1 mode; AUDIT or NORMAL The LCE OPSEC client can be configured to send a heartbeat message to the LCE. This message indicates that the client is still alive and performing normally. The frequency with which the LCE OPSEC client sends a log entry containing performance statistics to the LCE. Specify the online mode; yes or no (Not case sensitive). Specify the resolve mode; yes or no (Not case sensitive). Specify if field names should be displayed; yes or no (Not case sensitive). Specify the character that acts as the record separator. Specify the log file date format; CP, UNIX or STD. Specify the FireWall-1 authentication settings; yes or no (Not case sensitive). The path and name of the OPSEC certificate file. The OPSEC Client Distinguished Name. The OPSEC Server Distinguished Name. The IP address of the LCE server. The password required to authenticate to the LCE server. The remote port of the LCE server designated in the LCE_SERVER directive. FW-1 Log Grabber 19

20 Although Tenable provides a native LCE OPSEC Client, the client can be utilized to monitor logs generated by the open source FW-1 Log Grabber project. The open source tool is located at: To use this tool, add a client to your Linux server which is also running Log Grabber. Configure the lce.conf file of the client to monitor the log file generated by the Log Grabber program. At the LCE server, ensure that the firewall_checkpoint_loggrabber.prm library has been enabled. This library is used to process the Firewall log events generated by the Log Grabber tool. Linux Binary Compatibility Depending on your specific Linux kernel, when starting, the lce_opsec client may complain about not being able to locate the libelf.so.0 library. If this is the case, please run the following command: # ln -s /usr/lib/libelf.so.1 /usr/lib/libelf.so.0 ldconfig # This will ensure that the lce_opsec client has proper access to the required system libraries. Firewall Connectivity Configuration of unauthenticated connections Configuration of FW-1 server: Modify $FWDIR/conf/fwopsec.conf and define the port to be used for unauthenticated lea connections: lea_server port Bounce FW-1 in order to activate changes # cpstop; cpstart Configuration of FW-1 policy: Add a rule to the policy to allow the port defined above from the lce_opsec-client machine to the FW-1 management server. Install the policy. Configuration of lce_opsec-client: Edit the FW1_PORT configuration file parameter to specify the port you defined on your FW-1 server. (This example 50001) Configuration of authenticated connections Configuration of FW-1 server: 20

21 Modify $FWDIR/conf/fwopsec.conf and define the port to be used for authenticated lea connections as well as the authentication algorithm. The default algorithm for authenticated connections is SSLCA: lea_server auth_port lea_server auth_type sslca cpstop; cpstart (if settings above are in place than bouncing the FW-1 Management Server is not necessary) Configuration of FW-1 policy: Create a new Opsec Application Object with the following details: o Name: e.g. thunder (thunder is an example Object name) o Vendor: User Defined o Server Entities: None o Client Entities: LEA Initialize Secure Internal Communication (SIC) for recently created Opsec Application Object and enter (and remember) the initial password. Write down the DN of the recently created Opsec Application Object. This is your Client Distinguished Name, which you need later on. Open the object of your FW-1 management server and write down the DN of that object. This is the Server Distinguished Name, which you will need later on. Add a rule to the policy to allow the port defined above as well as port 18210/TCP (FW1_ica_pull) in order to allow pulling of PKCS#12 certificate from the lce_opsecclient machine to the FW-1 management server. The port 18210/TCP can be shut down after the communication between lce_opsec-client and the FW-1 management server has been established successfully. The pulling of the certificate will be accomplished with the opsec_pull_cert script. Install the policy. Configuration of lce_opsec-client: Execute the command opsec_pull_cert as follows and copy the resulting PKCS#12 file (default: opsec.p12) to your lce_opsec-client directory. (The opsec_pull_cert can be accessed at the following address: ates.html opsec_pull_cert \ -h <IP of FW-1 Management Server> \ -n <Name of Opsec Application Object> \ -p <Password you entered before in policy> Example: #./opsec_pull_cert -h host -n object-name -p activation-key #./opsec_pull_cert -h n c001_lea -p abc123 The full entity sic name is: 21

22 CN=c001_lea,O=cpmodule..gysidy Certificate was created successfully and written to "opsec.p12". The following options will need to be updated within the lce_opsec.conf: Edit the FW1_PORT configuration file parameter to specify the port you defined on your FW-1 server. (This example uses port ) Edit the AUTHENTICATED="yes" option within the lce_opsec.conf file. Edit the OPSEC_CERTIFICATE configuration file parameter according to the name of the PKCS#12 file which you created before using the opsec_pull_cert command. (The example above uses opsec.p12) Edit the OPSEC_CLIENT_DN configuration file parameter according to the Client DN that you have written down before. Edit the OPSEC_SERVER_DN configuration file parameter according to the Server DN that you have written down before. Reading Live or Past Log Entries The LCE OPSEC Client can operate in online and offline modes. In the online mode it will report events as they occur, i.e. real-time. In the offline mode the client will read all of the events that are currently in the log and forward them onto the LCE server. If the user wants to see past log entries, then they should use the offline mode. If they want to see real-time entries, then they should use the online mode. Some examples of invocation: (The following is configurable within the lce_opsec.conf as well)./lce_opsec --online./lce_opsec --offline Tenable Network Monitor Client The Tenable Network Monitor (TNM) is designed to monitor network traffic and send session information to the LCE server. It can also sniff SYSLOG messages sent from one point to another and treat them as if they were originally sent directly to the LCE. The following is an example of the tnm.conf congfiguration file: options { # Network Monitor log messages are stored in files named according # to the date in the following directory. log-directory "./"; # The heartbeat-frequency option defines the number of seconds # between each pair of client heartbeat messages that are sent to # the server. heartbeat-frequency "300"; # The network monitor provides the option of periodically sending a # log file containing performance statistics to the LCE server. The 22

23 # following option determines the number of minutes between each # performance statistics report. When the next line is commented # out or removed, performance reporting is disabled. statistics-frequency "60"; # This section defines the IP address and authentication password # for connections to the Log Correlation Engine server. In the # example, the server is located at (localhost), where a # password of "tenable" has been set for the client. Only one LCE # server is currently supported. lce-server { client-auth auth-secret-key "tenable"; } # The LCE server can be configured to listen on a user-specified # port. The setting below should match the server setting, which is # by default. server-port "31300"; # The network monitor will report traffic from only the interfaces # listed below. #interface "eth0"; interface "vxn0"; # Traffic containing syslog messages is forwarded to the LCE server # for the hosts matching the filtering criteria in the final # section. The following specifies the protocol/port pairs for which # all traffic will be processed as syslog messages. # These settings should match the syslog or syslog-ng configuration. monitor-syslog-port "udp/514"; monitor-syslog-port "tcp/1468"; } # When the below option is set to yes, only syslog messages are # reported, and all all other traffic is ignored. syslog-only "no"; # The following section defines the networks on which syslog will be # monitored. The network monitor will report syslog messages received at the # above specified ports for any IP address matching the filter criteria. include-networks { " /32"; " "; } exclude-networks { } tnm.conf The following table describes the configuration options available in the tnm.conf configuration file: 23

24 Option log-directory heartbeat-frequency statistics-frequency lce-server server-port interface monitor-syslog-port syslog-only include-networks exclude-networks Description Directory where LCE client logs are stored. If the logdirectory keyword is commented out, then the client install directory will be used. Otherwise ISO9000 compliant log files will be saved in the specified directory. The Tenable Network Monitor can be configured to send a "heartbeat" message to the LCE. This message indicates that the client is still alive and performing normally. The frequency with which the Tenable Network Monitor sends a log entry containing performance statistics to the LCE. Directs the Tenable Network Monitor to the IP address of the LCE, and specifies the password used to connect. The port the LCE listens to as designated by the lce-server directive. The network interface(s) that the Tenable Network Monitor will report traffic from. The protocol/port designation that is used to forward syslog messages to the LCE server. Directive to only report syslog messages; yes or no. Specify which networks are to be included in monitoring activity. Designate specific networks that should be excluded from monitoring activity. Functionality The tnm tool will report on TCP sessions it sees. For example, if there is an FTP session, it will report when the session starts and when it is completed. If the session has no activity for a certain amount of time, tnm will time out the session and log it as complete. For UDP and ICMP protocols, tnm will log the individual packets. When sending network traffic activity to the LCE, care should be taken when choosing the traffic source to monitor. The amount of network logs generated while monitoring a busy T3, 100 Mb or even Gigabit link can vastly outweigh the total amount of firewall, web log and IDS logs. However, monitoring activity on key servers, key protocols or even known malicious IP addresses is extremely useful. When used to aggregate SYSLOG messages from another set of servers, make sure to specify the correct destination IP addresses for the syslog messages. Otherwise, the Tenable Network Monitor may ignore SYSLOG messages you actually want gathered. 24

25 Tenable also reccomends deploying the TNM directly in front of or on any SYSLOG gathering servers. The advantage of this is to work with the logs directly as they arrive from their source servers. SYSLOG servers that forward messages often add additional data in front of the log which increases the overall log size. Also, logs that are forwarded often include source names for systems they may not be resolvable via DNS, making it harder to understand which system generated a log file. Using the TNM to sniff logs in motion preserves the source IP address of the original log. Comand Line Options The tnm binary has several command line options which are printed out when it is invoked without any options. Here is a list of the current options: usage:./tnm [ -v ] [ -r <pcap file> ] [ -t <TCP timeout> ] [ expression ] The v option turns on increased verbosity. The r option specifies a TCPDUMP binary file which can be used to send older logs to the LCE. The t option specifies the amount of time of inactivity to be used by tnm before considering a TCP session dead. And lastly, the last part of the command line allows for specification of a specific packet filter. Command line filtering options must be enclosed in quotation marks. For example, the following command line can be used to run tnm and log all network data except for UDP packets and ports 80 and #./tnm "not proto 17 and not port 80 and not port 6346" & The tnm is usually started via the network_monitor RC script in the system startup directory (for example, /etc/rc.d/init.d on Red Hat Linux systems). To change the default packet filter in the start up script, edit this script and go to the following entry on or about line 21: $NETWORK_MONITOR_DIR/$NETWORK_MONITOR_BIN &> /dev/null & To modify this default setting, add your filter statement after the command statement such as this: $NETWORK_MONITOR_DIR/$NETWORK_MONITOR_BIN tcp or icmp or udp port 514 &> /dev/null This particular statement matches on any TCP or ICMP traffic and also collects any UDP based SYSLOG traffic. Performance Considerations When running the TNM, you should consider how much data you are collecting and what you are doing with the data. If you are not doing anything with a certain set of data and you do not have a requirement to collect it, you can increase the performance of your LCE and the total volume of logs you can store at one time by not collecting it. Consider these strategies when collecting logs: 25

26 Ignoring UDP traffic in general, or at least UDP protocols to your basic services can save you many records. For example, ignoring DNS lookups to your DNS servers will save you logging these events which are repetitious. If you have very good logs from your , web and other types of servers, consider ignoring port 80, port 443, port 25 and so on to these servers. If you have a long term requirement to store logs but not necessarily network traffic, consider deploying a single LCE for log aggregation and then add a secondary LCE to gather network traffic. You might be able to store your logs much longer than your network traffic. With two LCEs, the Security Center can also query both of these and unify their results. Tenable RDEP Monitor Client Cisco s line of intrusion detection appliances makes use of a protocol known as RDEP. The Tenable RDEP Monitor (TRM) client is designed to connect into a Cisco IDS appliance and retrieve new events for processing by the LCE. Since the Security Center does not support the RDEP protocol, this client can also be used to create SYSLOG messages which can be read by the Security Center. The trm.conf file has several configuration options as shown in the following example: options { # This section defines the login information for the LCE server. Only # one LCE server is currently supported. lce-server ; lce-password "tenable"; # The LCE server can be configured to listen on a user-specified port. # The setting below should match the server setting, which is by # default. server-port 31300; # The heartbeat-frequency option defines the number of seconds between # each pair of client heartbeat messages that are sent to the server. heartbeat-frequency 300; # The LCE client provides the option of periodically sending a log file # containing performance statistics to the LCE server. The following # option determines the number of minutes between each performance # statistics report. When the next line is commented out or removed, # performance reporting is disabled. statistics-frequency 60; # run forever #daemonize; # print parsed events to standard error debug; # only parse and forward the latest events latest-events-only; # The next option sets the amount of time in seconds between each # interval at which the IDS device is checked for new events. This 26

27 # option is only meaningful if daemonize is set above. poll-interval 300; # In addition to the Log Correlation Engine, events downloaded from the # RDEP device can also be forwarded to up to 8 syslog servers. The # syslog-server keyword defines the address at which each is located. # syslog-server ; # The following section sets configuration information for an RDEP # server. Multiple servers can be added by providing an RDEP-server {} # block for each. RDEP-server { address ; port "443"; use-ssl; user "cisco"; password "Att@ck!"; # subscription based retrieval retrieval-method subscribe; event-types { evalert; } alert-severities { # or all # informational # low; medium; high; } } } trm.conf The following table describes the configuration options available in the trm.conf configuration file: Option lce-server lce-password server-port heartbeat-frequency Description Specifies which LCE server this client will send events to. An LCE server is not required to use this tool. Specifies the password for the LCE server, if used. Specifies the port that the LCE server listens on. Determines how often the TRM client sends a "heartbeat" message to the LCE to indicate that the client is still alive and 27

28 performing normally. statistics-frequency daemonize debug latest-events-only Determines how often the TRM client sends performance statistics to the LCE server Specifies tha the trm client is to run in the background as a daemon, if uncommented. Prints out a variety of status messages to the command line, if enabled. It is recommended that this be enabled when connecting to the remote Cisco IDS sensors for the first time. Causes the trm binary to skip to the most recent event and then only report new events. Tenable recommends that the trm be configured to skip forward to the last event by enabling this option. poll-interval syslog-server RDEP-server Specifies how often (in seconds) the trm shall attempt to connect to the remote Cisco IDS sensors. Tenable recommends five minute intervals on busy or heavily loaded Cisco IDS sensors. However, smaller time intervals such as 30 seconds will provide more fidelity in event logging. If SYSLOG event forwarding is desired, the IP address of this server (most likely the IP of the Security Center) can be specified with this keyword. This section specifies a single Cisco IDS sensor to aggregate events from. Multiple RDEP-server entries can be specified in a single trm.conf file. This particular construct specifics the IP address, account, and password for the trm to log into the sensor. In addition, there are some default parameters such as which port, the type of encryption (the use-ssl keyword), and the event-type keyword which specify how the events are to be retrieved. Last, the alert-severity keyword is used to specify what type of IDS events from the Cisco sensor are to be retrieved. Sending Events to the Security Center Specifying the IP address of the Security Center with the syslog-server keyword will send new IDS events from one or more Cisco sensors to the Security Center. TNS NetFlow Monitor Client The Tenable NetFlow Monitor (TFM) client takes advantage of the ability in most modern routers to use the NetFlow protocol to send network session statistics to remote collectors for processing and reporting. This enables you to monitor network traffic without having to install a sniffer on a hub or switched span port. The following is an example tfm.conf configuration file: 28

29 options { # Log messages will be stored in a file named according to date in # the following directory. log-directory "./"; # This section defines the login information for the LCE server. # Only one server is currently supported. lce-server { client-auth auth-secret-key "tenable"; } # The LCE server can be configured to listen on a user-specified # port. The setting below should match the server setting, which is # by default. server-port 31300; netflow-server-port 9995; # The heartbeat-frequency option defines the number of seconds # between each pair of client heartbeat log messages that are sent # to the server. heartbeat-frequency 300; # The LCE client provides the option of periodically sending a log # file containing performance statistics to the LCE server. The # following option determines the number of minutes between each # performance statistics report. When the next line # is commented out or removed, performance reporting is disabled. statistics-frequency 60; # The netflow agent implements a white list of matching IP # elements including IP protocol, IP address and port numbers. # If multiple elements are specified, then only sessions matching # at least one variable in each element will be matched. In the # below example, only UDP and TCP sessions would be logged from # with a source port of 1024 and a destination port # of 53. If multiple destination or source ports were required # for matching, they could be entered in on other lines. Only # one include-filter can be used per netflow agent. # Example #1. include-filter { proto 6; } exclude-filter { port 20; port 21; # port 22; # port 25; port 80; port 53; port 110; port 123; port 161; 29

30 } port 143; port 443; port 1434; port 1863; port 5050; port 5190; port 8200; # Example #2 - logging all ftp, web, smtp and dns traffic # include-filter { # port 21; # port 25; # port 53; # port 80; # } } # Example #3 - logging all ftp, web, smtp and dns traffic from # /8 # include-filter { # cidr / ; # port 21; # port 25; # port 53; # port 80; # } tfm.conf The following table describes the configuration options available in the tfm.conf configuration file: Option log-directory lce-server server-port netflow-server-port Description Directory where LCE client logs are stored. If the logdirectory keyword is commented out, then the client install directory will be used. Otherwise ISO9000 compliant log files will be saved in the specified directory. Directs the TFM client to the IP address of the LCE, and specifies the password used to connect. Note: Each client can only connect to one server, and will connect to the first server specified if multiple lce-server directives exist. The port the LCE listens to as designated by the lce-server directive. Specifies the NetFlow port to monitor. The netflow-serverport keyword should not change unless you have specifically modified the configuration of your networking devices to report NetFlow data on non-standard ports. 30

31 heartbeat-frequency statistics-frequency include-filter exclude-filter The TFM client can be configured to send a heartbeat message to the LCE. This message indicates that the client is still alive and performing normally. The frequency with which the LCE client sends a log entry containing performance statistics to the LCE. The filtering section is used to limit the amount of data logged. Unlike the TNM which has command line filtering courtesy of the libcap packet capture library, TFM filtering is specified inside the tfm.conf file. Filtering is accomplished by specifying one or more protocol, network or port combinations. In the provided tfm.conf file, several examples are given which look for generic matches. The filtering logic works such that any reported NetFlow session must match at least one of the specified filters in each section. Negative filtering can also be used. Consider the following section from a tfm.conf file: include-filter { proto 6; } exclude-filter { port 20; port 21; port 22; port 25; port 80; port 53; port 110; port 123; port 161; port 143; port 443; port 1434; port 1863; port 5050; port 5190; port 8200; } In this example, the tfm would look for all TCP traffic, but would also ignore any sessions occurring on the ports listed in the exclude filter. Tenable NetFlow Monitor Event Types These are the event types that the Tenable NetFlow Monitor can currently generate: TFM-TCP_Session_Whole TFM-TCP_Session_Partial TFM-UDP_Activity 31

32 Usage TFM-TCP_Session_Whole_1MB TFM-TCP_Session_Whole_10MB TFM-TCP_Session_Whole_100MB TFM-TCP_Session_Whole_1000MB TFM-TCP_Session_Whole_Long TFM-TCP_Session_Partial_Long Once the tfm.conf file is configured correctly, simply invoke the tfm binary from the command line. Traffic from NetFlow version 9 will produce records that will have a trailing 0. This will be seen in Security Center when viewing log data from the LCE. An example of these records is shown below: Tue Jul 18 13:30:27 - TFM-TCP_Session_Partial[46 0]: :5190 -> : Tue Jul 18 13:30:39 - TFM-TCP_Session_Partial[9492 0]: : > : Tue Jul 18 13:31:05 - TFM-TCP_Session_Partial[0 757]: :4136 -> : LCE Unix Client Operations This section describes the administrative functions of the LCE Unix clients including starting, halting and monitoring. Starting the LCE Unix Clients As noted earlier in this document, the LCE 3.0 package includes start-up scripts that are installed in the system start-up directory (usually /etc/init.d) on the respective platform. The provided start-up scripts are designed to check if the LCE client is already running and will not start a second instance. Although it is possible to manually start the LCE client without using the provided script, it is not recommended to do so as it could result in multiple instances of the LCE client daemon running. If there are errors in the configuration file, they will be displayed in the LCE Client log, which is under the appropriate client directory (/opt/lce_client for the, /opt/network_monitor for the Tenable Network Monitor client, etc) in the format of YEARMon.log. At the LCE server, using the netstat an grep command will list all of the established LCE client connections. At any time, the version of the LCE client can be determined by running it with the -v option, as follows: #./lce_clientd -v LCE Client

33 # Below is a table that displays how to start the client software on the various platforms: Client Software Starting Methods Red Hat ES 3, ES 4, ES 5 LCE OPSEC Client Tenable NetFlow Monitor Tenable Network Monitor Tenable RDEP Monitor # service lce_client start or # /etc/init.d/lce_client start # service lce_opsec start or # /etc/init.d/lce_opsec start # service netflow_monitor start or # /etc/init.d/netflow_monitor start # service network_monitor start or # /etc/init.d/network_monitor start # service rdep_monitor start or # /etc/init.d/rdep_monitor start FreeBSD TNS NetworkMonitor TNS NetFlowMonitor # /usr/local/etc/rc.d/lce_client start # /usr/local/etc/rc.d/network_monitor start # /usr/local/etc/rc.d/netflow_monitor start Fedora Core # /etc/init.d/lce_client start Solaris # /etc/init.d/lce_client start Mac OS X # SystemStarter start LCEClient Debian Tenable Network Monitor # /etc/init.d/network_monitor start Dragon Appliance 33

34 # /etc/rc.d/rc.lce_client start Halting the LCE Unix Clients LCE client software can be halted using any one of three methods; Use the kill command to cause the process of the lce_client program to stop running, use the service command or use the init.d script. The following table demonstrates how to halt the various client software: Client Software Halting Methods Red Hat ES 3, ES 4, ES 5 LCE OPSEC Client Tenable NetFlow Monitor Tenable Network Monitor Tenable RDEP Monitor # service lce_client stop or # /etc/init.d/lce_client stop # service lce_opsec stop or # /etc/init.d/lce_opsec stop # service netflow_monitor stop or # /etc/init.d/netflow_monitor stop # service network_monitor stop or # /etc/init.d/network_monitor stop # service rdep_monitor stop or # /etc/init.d/rdep_monitor stop FreeBSD Tenable Network Monitor Tenable NetFlow Monitor # /usr/local/etc/rc.d/lce_client stop # /usr/local/etc/rc.d/network_monitor stop # /usr/local/etc/rc.d/netflow_monitor stop Fedora Core # /etc/init.d/lce_client stop Solaris # /etc/init.d/lce_client stop Mac OS X 34

35 # SystemStarter stop LCEClient Debian Tenable Network Monitor # /etc/init.d/network_monitor stop Dragon Appliance # /etc/rc.d/rc.lce_client stop Monitoring Log Correlation Engine Client Status While running, the lced process will keep track of LCE client status in a file named client.status which is located in the /opt/lce/admin/log directory. Below is an example listing: # pwd /opt/lce/admin/log # cat client.status Client[ ]: HeartBeatTime[Jul 07, 08 13:43] : Logged in Alive Client[ ]: Not logged in Client[ ]: Not logged in Client[ ]: Not logged in Client[ ]: HeartBeatTime[Jul 07, 08 13:44] : Logged in Alive Client[ ]: Not logged in Client[ ]: HeartBeatTime[Jul 07, 08 13:44] : Logged in Alive Client[ ]: Not logged in Client[ ]: HeartBeatTime[Jul 07, 08 13:43] : Logged in Alive # For each configured LCE client, the IP address specified in the lce.conf file will be displayed as well as if it has logged in, the time of the last heartbeat and if the client is considered alive or dead. The tail-f command is not effective on this log file since it is completely rewritten each time the lced process detects a change in a client s status. The following are possible status messages and their descriptions: Message Not logged in Logged in Dead Logged in Alive Description The client has not logged in at all yet, or has been shutdown gracefully. The client has logged in before but, for some reason, has not sent in any data. This could be an indication of an issue on the client side. The client is working and sending data when it needs to. 35

36 Log Correlation Engine Client Reconnection Attempts The LCE client will attempt to reconnect every minute until it can re-establish a connection with the server if the following conditions occur: The lced process stops The network connection between the client and the server breaks The client is removed from the server s configuration file (this requires a restart of the service to take affect) Log Correlation Engine Windows Client The Log Correlation Engine Windows Log Agent client monitors events as well as specific log files or directories for new logs. Platform LCE Client Type Install File Name and Utility MS Windows XP Professional, Windows Server 2003, Windows Server 2008, Windows Vista Tenable LCE Client v3.0.1.msi Windows Installer Upgrading LCE Clients from Thunder Clients If you were using a version of the LCE Windows Log Agent client prior to LCE 3.0 (previously referred to as the Thunder client), you must remove the old client before installing the new version. If you attempt to intall the new client without removing the old one, a window will be displayed reminding you to remove the old client as follows: Installing the Windows Client The LCE Windows Log Agent client installs by clicking on the.msi distribution file which will launch the InstallShield Wizard. A license agreement will be displayed that the user must agree to before installation can commence. The user will be asked to choose if the application is to be shared or not, as shown in the following screen: 36

37 Installation Location The next screen allows the user to change the default installation location: 37

38 If you wish to use the default location, simply click on Next and a screen will be displayed to begin the installation by clicking on Install. After a few minutes, the InstallShield Wizard will display a screen indicating that the installation is complete. Service Location Once installation is complete, a new Windows Service named the Tenable LCE Client will be added that can be viewed through the Control Panel / Administrative Tools / Services window as shown below: Using the LCE Client on Vista and Windows 2008 The latest OS releases from Microsoft contain a new security layer called User Account Control (UAC). The LCE Windows client needs administrative privileges to operate. This may be accomplished using one of the following two methods: 1. Disable UAC on the machine. This will cause the system to behave in a manner similar to XP in that all applications started by an administrator account will have administrative privileges. To accomplish this, click on Control Panel and then User Accounts and select admin. The following screen will be displayed: 38

39 From this screen, select Turn User Account Control on or off. The following screen will be displayed: 39

40 Make sure the box in front of Use User Account Control (UAC) to help your computer is not checked. 2. Run both the installer and the application as an administrator with UAC enabled. The following steps describe how to run the installer as an administrator: Login with an account with administrative rights. Open a command prompt as administrator. From the Start button, click on Run and enter cmd in the dialog box. Use the cd command to change directory to the location where the msi file is located. Run the following command (substituting the actual name of the.msi file): msiexec /i " Tenable LCE Client v3.0.1.msi" The following steps describe how to run the application as an administrator: Right click on the LCEConfig shortcut on the desktop. Select Properties from the pull-down menu. Choose the Shortcut tab from the dialog box. Click the Advanced button. Check Run as Administrator. Click OK on the Advanced properties panel. Click OK on the Shortcut properties panel. To run the LCE Windows client program, this shortcut must always be used. Removing the LCE Windows Client To remove the LCE Windows Log Agent client, under the Control Panel open Add or Remove Programs. Select Tenable LCE Client and then click on the Change/Remove button. This will open the InstallShield Wizard. Follow the directions in this wizard to completely remove the LCE client. Windows Client Configuration To configure the LCE Windows Log Agent client launch the LCE Configuration tool located at C\Program Files\Tenable\LCEClient\LCEConfig. This tool allows configuration of LCE server connectivity as well as configuration of the Windows event logs, file logs and directories which should be monitored. An example startup screen for the LCE Windows Client Configuration tool is shown below: General 40

41 By default, the client is configured to connect to with a password of password. This must be modified to the IP address of the LCE server, and the password configured on the LCE server for this particular LCE Windows Log Agent client. When configuring the client, the default screen also includes the following three paramaters: Heartbeats Send new events only this causes the client to monitor the Windows event log from the very moment it starts. It ignores all events that were previously in the event log. For testing purposes, it may be useful to send all of the events currently in the event log by unchecking this box. Poll every some number of seconds this causes the client to poll the local system to see if any USB or disk drives were removed or added since the last polling. If any changes were detected, the client will send a log which results in a Windows-LCE_Client_Detected_Attached_Drive or a Windows- LCE_Client_Detected_Removed_Drive event. Send performance data every some number of seconds this specifies how often the performance data is sent to the LCE. The Heartbeats tab of the LCE Client Configuration tool allows you to set how often a heartbeat message will be sent to the LCE server indicating that the client is still alive and functioning normally, as shown in the screen below: 41

42 The following is an example of the heartbeat message sent from the LCE Windows Log Agent client to the LCE: LCE Client Heartbeat Hostname: ga2k3ten IP: Revision: Windows LCE Client v Local Event Logs The LCE Windows Log Agent client can also be configured to send any combination of event logs which are available. The Local Event Logs tab displays a list of available event log sources to send to the LCE server. By default, the security, application and system logs will be present, but other applications may add their own log file sources. An example of the Local Event Logs tab is shown below: 42

43 Remote Events Logs The Remote Event Logs tab can be used to configure forwarding of Windows events from remote hosts using WMI. Because the LCE Client uses WMI to collect events from remote hosts, firewall connectivity must be configured to enable WMI communications. WMI connectivity can be tested with WMI tools including Microsoft s WMI CIM Studio, available at: 48DB-8CC5-F2ABDC3ED314&displaylang=en 43

44 To add a host, click on the New button and fill in the information in the following screen: Versions prior to of the LCE client include the WMI namespace field. This requirement has been removed in LCE Client

45 This will create an XML file called lce_wmi_config.xml, located in the LCE client folder (usually C:\Program Files\Tenable\LCEClient). Each time you add a new host, it will be appended to the lce_wmi_config.xml file. To add a list of hosts from a file, use the Add hosts from file.. button to select an XML formatted file with multiple hosts. For example, a user could individually add each remote host in the LCE client on one system and manually copy the XML file to another system and use the Add hosts from file button to import it to that system s LCE log Agent client. See Appendix 3 for an example of the lce_wmi_config.xml file. If the system where the LCE client is running is part of a workgroup, the client service needs to run as an administrator account in order to receive events from remote hosts. By default, the LCE client is configured to log on and run as the Local System account. To change this to log on as an administrator account, go to the Services utility under Administrative Tools, right-click on the Tenable LCE Client service, select Properties and then select the Log On tab. An example screen capture is shown below: Restart the LCE client service for the setting to take effect. Log Files The Log Files tab in the LCE Client Configuration tool allows you to select which log files you wish to send to the LCE server. It can be directed to tail specific log files or all of the log files in a given directory. When tailing a log file, the LCE Windows Log Agent client will continuously check the file for any new data written to it. When tailing an entire directory of log files, the LCE Windows Log Agent client will tail all of the files present in that directory, including new files. To add a specific log file to tail, click on the Add log file tab and select which log file you want to have tailed. To tail an entire directory of log files, click on the 45

46 Add log folder tab and select the log file folder you wish to tail. An example screen capture showing the LCE Windows Log Agent client configured to tail both a specific log file and a log folder is shown below: If you choose to add a log folder, a dialog box will be displayed allowing you to to specify which log files you wish to include or exclude. If you do not wish to include or exclude any specific log files in this folder, simply close this box and the log files for the entire folder will be tailed. A sample of this dialog box is shown below: LCE Windows Client Operations This section describes the administrative functions of the LCE Windows Log Agent client, including starting, halting and monitoring. 46