Use https://seceonhelp.freshdesk.com/support/login to access updated Knowledge Base Articles, Submit Technical Support Tickets and Review Status of submitted support tickets.

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

This guide helps you in configuring Redhat Linux and EventTracker to receive the events. You will find the detailed procedures required for monitoring Redhat Linux.

The configurations detailed in this guide are consistent with Seceon CCE and Redhat Linux.

Redhat Linux users, who wish to forward Events to EventTracker and monitor events using EventTracker.

  1. Overview

  2. Prerequisites

  3. Configuring Redhat Linux to forward logs to EventTracker - Seceon CCE

  4. Verification

Overview

Redhat Linux is an operating system based on Unix developed in 1992 by Sun Microsystems. EventTracker integrates with Redhat Linux via Syslog. It monitors events to provide insight on security and compliance events such as login, logout, login-failed events, the command executed, and privilege escalation.

Prerequisites

  1. Seceon CCE should be installed.

  2. Allow the Syslog UDP Port 514 in the firewall/network

Configuration Steps:

The following steps describe how to configure rsyslog on Red Hat Enterprise Linux 6 or 7 to receive logs from Deep Security.

  1. Log in as a root

  2. Execute: vi /etc/rsyslog.conf

  3. Uncomment the following lines near the top of the rsyslog.conf to change them from:
    #$ModLoad imudp
    #$UDPServerRun 514
    #$ModLoad imtcp
    #$InputTCPServerRun 514
    to
    $ModLoad imudp
    $UDPServerRun 514
    $ModLoad imtcp
    $InputTCPServerRun 514

  4. Add the following two lines of text to the end of the rsyslog.conf:

#Save Deep Security Manager logs to cce.log

Local7.* /var/log/Seceon/cce.log

Depending on your manager settings, you may need to replace Local7 with another value.

  1. Save the file and exit

  2. Create the /var/log/Seceon/cce.log file by typing touch /var/log/Seceon/cce.log

  3. Set the permissions on the CCE log so that Syslog can write to it

  4. Save the file and exit

  5. Restart syslog: service rsyslog restart

Verification Steps:

When Syslog is functioning, you will see logs populated in: /var/log/Seceon/cce.log

  • No labels