AIX7-00-002133 - AIX must be configured to use syslogd to log events by TCPD.

Warning! Audit Deprecated

This audit has been deprecated and will be removed in a future update.

View Next Audit Version

Information

Without auditing the enforcement of access restrictions against changes to the application configuration, it will be difficult to identify attempted attacks and an audit trail will not be available for forensic investigation for after-the-fact actions.

Enforcement actions are the methods or mechanisms used to prevent unauthorized changes to configuration settings. Enforcement action methods may be as simple as denying access to a file based on the application of file permissions (access restriction). Audit items may consist of lists of actions blocked by access restrictions or changes identified after the fact.

NOTE: Nessus has provided the target output to assist in reviewing the benchmark to ensure target compliance.

Solution

Configure the access restriction program to log every access attempt. Ensure the implementation instructions for TCP_WRAPPERS are followed, so system access attempts are logged into the system log files. If an alternate application is used, it must support this function. Edit the '/etc/syslog.conf' file by writing the following to the file.
auth.info /var/log/messages

# touch /var/log/messages
# refresh -s yslogd

See Also

https://dl.dod.cyber.mil/wp-content/uploads/stigs/zip/U_IBM_AIX_7-x_V2R5_STIG.zip

Item Details

References: CAT|II, CCI|CCI-001814, Rule-ID|SV-215314r508663_rule, STIG-ID|AIX7-00-002133, STIG-Legacy|SV-101631, STIG-Legacy|V-91533, Vuln-ID|V-215314

Plugin: Unix

Control ID: 29d7f95c951595715fca96c3c94e90d6afa8eb1a59332158f74d8a569e7ae6e4