4.1.15 Ensure system administrator actions (sudolog) are collected

Information

Monitor the sudo log file. If the system has been properly configured to disable the use of the su command and force all administrators to have to log in first and then use sudo to execute privileged commands, then all administrator commands will be logged to /var/log/sudo.log . Any time a command is executed, an audit event will be triggered as the /var/log/sudo.log file will be opened for write and the executed administration command will be written to the log.

Rationale:

Changes in /var/log/sudo.log indicate that an administrator has executed a command or the log file itself has been tampered with. Administrators will want to correlate the events written to the audit trail with the records written to /var/log/sudo.log to verify if unauthorized commands have been executed.

Solution

Edit or create a file in the /etc/audit/rules.d/ directory ending in .rules and add the following line:

-w <Path to sudo logfile> -p wa -k actions

Example: vi /etc/audit/rules.d/actions.rules
and add the following line:

-w /var/log/sudo.log -p wa -k actions

Additional Information:

The system must be configured with su disabled (See Item 5.6 Ensure access to the su command is restricted) to force all command execution through sudo. This will not be effective on the console, as administrators can log in as root.

Reloading the auditd config to set active settings requires the auditd service to be restarted, and may require a system reboot.

See Also

https://workbench.cisecurity.org/files/2971

Item Details

Category: AUDIT AND ACCOUNTABILITY

References: 800-53|AU-3, CSCv6|5.1, CSCv7|4.9

Plugin: Unix

Control ID: bb8832b245cc876433d8af17c77a7afed8944e76fc36a4c5c22de19731d85c54