Accenture MDR Quick Start Guide for Unix® OS

This quick start guide will help Accenture MDR customers configure Unix® Servers to send logs to the Log collection Platform (LCP).

This document includes the following topics:

Supported Versions

A list of supported versions is available in the Accenture MDR Supported Products List document (Accenture_MDR_Supported_Products_List.xlsx) which can be found in Accenture MDR Portal.

Port Requirements

Table 1-1: Port requirements for LCP communication.

Source

Destination

Port

Description

Unix/Linux/Solaris server

LCP

514 (UDP) or

601 (TCP)

Default port

 

 Configuring Red Hat Enterprise Linux, Debian Linux, Oracle Linux, SUSE Linux, Ubuntu Linux,Huawei EulerOS, Alma Linux, IBM PowerVM and CentOS operating systems

Red Hat Enterprise Linux, Debian Linux, Oracle Linux, SUSE Linux, Ubuntu Linux, Huawei EulerOS, IBM PowerVM and CentOS uses one of the following daemons for log forwarding:

  • syslogd

  • rsyslog

For configuring syslogd, See "Configuring syslog message forwarding by using syslogd"

For configuring rsyslog, See "Configuring syslog  message forwarding by using rsyslogd"

Additionally, you must configure iptables and auditd logging. 

For configuring iptables, See "Configuring logging for Linux iptables"

Installing auditd package for Ubuntu Linux, See "Installing auditd package for Ubuntu Linux"

 For configuring audit logging, See "Configuring syslog plugin for auditd"

Configuring SUSE Linux operating system

SUSE Linux 9 to 11 SP3 uses syslog-ng daemon for log forwarding.

For configuring syslog-ng, See "Configuring syslog message forwarding by using syslog-ng"

SUSE Linux 12 uses rsyslog daemon for log forwarding.

For configuring rsyslog, See "Configuring syslog  message forwarding by using rsyslogd"

Additionally, you must configure iptables logging.

For configuring iptables, See "Configuring logging for Linux iptables"

For configuring SUSE Linux 12 date format, See "Configuring event date format for SUSE Linux"

Configuring Solaris operating system

Solaris uses syslogd daemon for log forwarding.

For configuring syslogd, See "Configuring syslog message forwarding by using syslogd"

Additionally, you must configure iptables logging.

For configuring iptables, See "Configuring logging for Linux iptables"

Configuring IBM AIX operating system

IBM AIX uses syslogd daemon for log forwarding.

For configuring syslogd, See "Configuring syslog message forwarding by using syslogd"

Additionally, you must configure FTP to log FTP sessions and debug information.

For configuring FTP, Configuring FTP to log FTP sessions and debug information for IBM AIX

Configuring HP UX operating system

HP UX operating system uses syslogd daemon for log forwarding.

For configuring syslogd, See "Configuring syslog message forwarding by using syslogd"

Configuring Nokia IPSO operating system

For configuring syslog, See "Configuring syslog message forwarding for Nokia IPSO"

Configuring Macintosh operating system

Macintosh operating system uses syslogd daemon for log forwarding.

For configuring syslogd, See "Configuring syslog message forwarding by using syslogd"

Configuring Syslog Message Forwarding Using syslogd

To configure syslog message forwarding using syslogd:

  1. From a Unix server, login with root privileges.

  2. To stop syslogd, at the command prompt, type the following command as required:

HP-UX

/sbin/init.d/syslogd stop

IBM AIX

stopsrc -s syslogd

Solaris 8 and 9

/etc/init.d/syslog stop

  1. Use a text editor, such as vi, to open and edit the /etc/syslog.conf file.

Add the following line in the syslog.conf file: *.info  @IP_address_of_the_LCP

For example: *.info @192.0.2.1, where 192.0.2.1 is the IP address of the LCP.

4. Save and close the syslog.conf file.

5. To start or restart syslogd, type the following command as required:

HP-UX

/sbin/init.d/syslogd start

IBM AIX

startsrc -s syslogd

Solaris 8 and 9

/etc/init.d/syslog start

Solaris 10 and 11

svcadm restart svc:/system/system-log

Red Hat Linux 3-5,

Debian Linux 3 - 4.9

/etc/init.d/syslogd restart

Red Hat Linux 6,

Oracle Linux 5.0 - 6.5,

CentOS 5.0 - 6.5

/etc/init.d/rsyslog restart

Mac OS X

Run the terminal utility and then at the command prompt, type the following command to restart syslogd:

launchctl unload /System/Library/ LaunchDaemons/com.apple.syslogd.plist; sleep1;

launchctl load /System/Library/ LaunchDaemons/com.apple.syslogd.plist

Note: This command must be entered in one line, there is no carriage return or linefeed.

Configuring Syslog Message Forwarding Using rsyslogd (RHEL/Huawei EulerOS/Alma Linux/IBM PowerVM)

You can configure syslog message forwarding by using rsyslogd.

To configure syslog message forwarding by using rsyslogd

  1. From the UNIX computer, log in as an administrator.

  2. To stop rsyslogd, at a command prompt, type the following command:

    • (For SUSE Linux and Ubuntu Linux) service rsyslog stop

    • (For other Linux Distribution) /etc/init.d/rsyslog stop

    • (For Ubuntu Linux) /etc/rsyslog.d/50-default.conf

    • (For other Linux Distribution) /etc/rsyslog.conf 

  3. Use a text editor such as vi to open and edit the following file:

  4. Add one of the following line at the end of the rsyslog.conf file, as required: For TCP forwarding, add  *.info      @@<IP or Hostname of the collector:<port> For UDP forwarding, add  *.info @<IP or Hostname of the collector:<port> An example for TCP forwarding is as follows: *.*      @@192.0.2.1,where 192.0.2.1 is the IP address of the collector computer.  An example for UDP forwarding is as follows: *.* @192.0.2.1,where 192.0.2.1 is the IP address of the collector computer. 

    Note

    Port is optional. If not provided, then default port 514 will be used.

  5. Save and close the rsyslog.conf file.

  6. To restart rsyslogd, at a command prompt, type the following command: 

    • (For SUSE Linux and Ubuntu Linux) service rsyslog restart

    • (For other Linux Distribution) /etc/init.d/rsyslog restart

Configuring Syslog Message Forwarding Using syslog-ng

To configure syslog message forwarding using syslog-ng:

  1. From a Unix server, login with root privileges.

  2. Use a text editor, such as vi, to open and edit the following file: /etc/syslog-ng/syslog-ng.conf

  3. Add the following lines in the syslog-ng.conf file:

destination d_label_for_lcp { udp(lcp_ip_address port(preferred_port_number)); };

filter f_label_that_identifies_the_filter { facility(info..emerg) and not facility (mail,cron); };

log { source(src); filter(f_label_that_identifies_the_filter); destination(d_label_for_lcp); };

For example:

destination d_lcp { udp(192.0.2.1 port(514)); }; filter f_lcpfilter { facility(info..emerg) and not facility (mail,cron); }; log { source(src); filter(f_lcpfilter); destination(d_lcp); };

Where:

  • udp - Protocol configured.

  • 192.0.2.1 - IP address of the LCP.

  • 514 - Default port on which the LCP is configured to listen (preferred).

  • source (src) - default syslog-ng, "source src" should already be defined in the syslog-ng.conf file.

  • The filter parameter is optional.

 Note: To configure TCP protocol, follow steps 1-3 and use "tcp" instead of "udp". Also use "601" instead of "514", where 601 is the default TCP port. 

  1. Save and close the syslog-ng.conf file.

  2. To restart syslog-ng, at a command prompt, type the following command: service syslog restart

Configuring Logging for Linux iptables

 Linux iptables use the following options to set the logging format for events: 

  • -- log-level

  • -- log-prefix

  • -- log-tcp-sequence

  • -- log-tcp-options

  • -- log-ip-options

These options affect the data available in the Information Manager event in the following ways:

-- log-prefix

This option causes the logged event to have a custom string prepended to it. This string is populated into the event_desc field. If the string ACCEPT is included, the event is treated as a successful connection. Similarly, if either the string DROP, or DENIED appears, the event is treated as a denied connection. 

-- log-tcp-sequence

This option causes the TCP sequence value to populate an Information Manager option field.

-- log-tcp-options

 -- log-ip-options

These options populate the Information Manager option fields with additional data.

 

Sample iptables rule is as follows:

iptables -A INPUT -i eth0 -p tcp -s 192.0.2.1

--dport 22 -j LOG --log-prefix "IPT: SSH DENY "

--log-level info --log-tcp-sequence --log-tcp-options

--log-ip-options  

Sample logline:

 

Mar  6 10:44:12 rhel6 kernel: IPT: SSH DENY IN=eth0 OUT=
MAC=00:50:56:bc:6c:b6:00:0c:29:4e:c6:fa:08:00 SRC=
192.0.2.11 DST=192.0.2.140 LEN=52 TOS=
0x00 PREC=0x00 TTL=
64 ID=60501 DF PROTO=TCP SPT=53141 DPT=22 SEQ=363874770 ACK=
1873456494 WINDOW=2720 RES=0x00 ACK URGP=0 OPT
(0101080A2B611D0C7649D30E)

Configuring Syslog Plugin for auditd

 Note: If syslog plugin for auditd is not installed on the server, refer to the vendor repository for installation.

 To configure syslog plugin for auditd:

  1. From a Unix server, login with root privileges.

  2. To stop the audit process, at a command prompt, type the following command: /etc/init.d/auditd stop

  3. Use a text editor, such as vi, to open and edit the following file: /etc/audisp/plugins.d/syslog.conf

  4. Add the following line to the /etc/audisp/plugins.d/syslog.conf file: active = yes

  5. Save and close the /etc/audisp/plugins.d/syslog.conf file.

  6. To restart the audit process, at a command prompt, type the following command: /etc/init.d/auditd start

Configuring FTP to Log FTP Sessions and Debug Information for IBM AIX

 To configure FTP to log FTP sessions and debug information for IBM AIX:

  1. On an AIX server, at the Unix prompt, login with root privileges.

  2. Use an editor, such as vi, to open and edit the following file: /etc/inetd.conf

  3. Configure the FTP daemon with -l and -d parameters. A sample configuration is as follows: ftp stream tcp nowait root /usr/sbin/ftpd -l -d

  4. Save and close the inetd.conf file.

  5. Stop and restart the FTP subserver by typing the following commands:

  • stopsrc -t ftp

  • startsrc -t ftp

Configuring Syslog Message Forwarding for Nokia IPSO

To configure syslog message forwarding for Nokia IPSO:

  1. Login to the Nokia Network Voyager Web console with root privileges.

  2. Click System Configuration > System Logging.

  3. Under Remote system logging, in the Add new remote IP address to log to field, enter the IP address of the LCP.

  4. Click Apply. The IP address of the LCP should appear in the list.

  5. From the Log at or above severity list, select Info.

  6. Click Apply and then Save.

Configuring Event Date Format for SUSE Linux

To configure event date format for SUSE Linux:

  1. From a SUSE Linux server, login with root privileges.

  2. To stop rsyslogd, at a command prompt, type the command: service rsyslog stop-

  3. Use a text editor, such as vi, to open and edit the following file: /etc/rsyslog.conf

  4. Add the following line to the /etc/rsyslog.conf file: $ActionFileDefaultTemplate RSYSLOG_TraditionalFileFormat

  5. Save and close the /etc/rsyslog.conf file.

  6. To restart rsyslog, at a command prompt, type the command: service rsyslog start

 

Installing auditd package for Ubuntu Linux

To install auditd package for Ubuntu Linux

  1. From the UNIX computer, log in as an Administrator.

  2. To install the auditd package, at a command prompt, type the following command: sudo apt-get install auditd

  3. To check the status of auditd service, at a command prompt, type the following command: sudo service auditd status

  4. To start or stop the auditd service, at a command prompt, type the following command: sudo service auditd start/stop

 

LCP Configuration Parameters

Table 1-2: The Unix OS event collector (Syslog -3252) properties to be configured by Accenture are given in the table.

Property

Default Value

Description

Protocol                      

UDP

The default protocol for syslog.

The collector can also accept logs in TCP.

Note: While TCP offers guaranteed delivery of log packets, it places a larger overhead on the LCP. To balance TCP for reliability over UDP for speed/simplicity, contact the  Accenture Security Onboarding team.

IP  Address

Unix OS Interface IP address

Logging device IP address mentioned in the Pre-Installation Questionnaire (PIQ).

Note: If the device sends logs using multiple interfaces, contact the Accenture Security Onboarding team.

Signatures    

ipmon, audispd:, named, httpd:, login:, dhclient, sshd, su, LOGIN, pam_unix, xinetd, kernel, useradd, adduser, userdel, gdm, rpc.statd, usermod, init:, reboot:, ftpd, last message repeated, shutdown:, Firewall[, passwd, shadow, in.telnetd, audit:, SuSEfirewall2:, auditd, gnome-keyring-daemon, vsftpd:, chage, groupdel, groupadd, groupmod, vsftpd[, login[, unix_chkpwd, chpasswd, gdm-session-worker, pam_sss, systemd, multipathd

Accenture Security recommended signatures processed by the Unix event collector.

Port Number    

514

The default port for UDP. For TCP, the default port is 601.

Note: The LCP can be configured to listen on a non-standard port, please advise the Accenture Security Onboarding team if this is a requirement.

 

Legal Notice

Copyright © 2021 Accenture. All rights reserved.

Accenture, the Accenture Logo, and DeepSight Intelligence are trademarks or registered trademarks of Accenture in the U.S. and other countries. Other names may be trademarks of their respective owners.

The product described in this document is distributed under licenses restricting its use, copying, distribution, and decompilation/reverse engineering. No part of this document may be reproduced in any form by any means without prior written authorization of Accenture and its licensors, if any.

THE DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID. ACCENTURE SHALL NOT BE LIABLE FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES IN CONNECTION WITH THE FURNISHING, PERFORMANCE, OR USE OF THIS DOCUMENTATION. THE INFORMATION CONTAINED IN THIS DOCUMENTATION IS SUBJECT TO CHANGE WITHOUT NOTICE.

The Licensed Software and Documentation are deemed to be commercial computer software as defined in FAR 12.212 and subject to restricted rights as defined in FAR Section 52.227-19 "Commercial Computer Software - Restricted Rights" and DFARS 227.7202, et seq. "Commercial Computer Software and Commercial Computer Software Documentation," as applicable, and any successor regulations, whether delivered by Accenture as on premises or hosted services. Any use, modification, reproduction release, performance, display or disclosure of the Licensed Software and Documentation by the U.S. Government shall be solely in accordance with the terms of this Agreement.