UCF STIG Viewer Logo

The systems access control program must log each system access attempt.


Overview

Finding ID Version Rule ID IA Controls Severity
V-941 GEN006600 SV-63571r2_rule Medium
Description
If access attempts are not logged, then multiple attempts to log on to the system by an unauthorized user may go undetected.
STIG Date
Oracle Linux 5 Security Technical Implementation Guide 2020-02-25

Details

Check Text ( C-52233r2_chk )
The tcp_wrappers package is provided with the RHEL distribution. Other access control programs may be available but will need to be checked manually. Depending on what system is used for log processing either /etc/syslog.conf or /etc/rsyslog.conf will be the logging configuration file.

Normally, tcpd logs to the mail facility in "/etc/syslog.conf" or “/etc/rsyslog.conf”. Determine if syslog or rsyslog is configured to log events by tcpd.

Procedure:

# more /etc/syslog.conf

Or:

# more /etc/rsyslog.conf

Look for entries similar to the following:

mail.debug /var/adm/maillog
mail.none /var/adm/maillog
mail.* /var/log/mail
authpriv.info /var/log/messages

The above entries would indicate mail alerts are being logged.

If no entries for mail exist, then tcpd is not logging this is a finding.

If an alternate access control program is used and it does not provide logging of access attempts, this is a finding.
Fix Text (F-54181r1_fix)
Configure the access restriction program to log every access attempt. Ensure the implementation instructions for tcp_wrappers are followed so system access attempts are recorded to the system log files. If an alternate application is used, it must support this function.