Title

Advanced Intrusion Detection Environment (AIDE) must verify the baseline SUSE operating system configuration at least weekly. (Cat II impact)

Discussion

Unauthorized changes to the baseline configuration could make the system vulnerable to various attacks or allow unauthorized access to the SUSE operating system. Changes to SUSE operating system configurations can have unintended side effects, some of which may be relevant to security. Detecting such changes and providing an automated response can help avoid unintended, negative consequences that could ultimately affect the security state of the SUSE operating system. The SUSE operating system's Information System Security Manager (ISSM)/Information System Security Officer (ISSO) and System Administrator (SAs) must be notified via email and/or monitoring system trap when there is an unauthorized modification of a configuration item.

Check Content

Verify the SUSE operating system checks the baseline configuration for unauthorized changes at least once weekly. Note: A file integrity tool other than Advanced Intrusion Detection Environment (AIDE) may be used, but the tool must be executed at least once per week. Check for a "crontab" that controls the execution of the file integrity application. For example, if AIDE is installed on the system, use the following command: # sudo crontab -l 0 0 * * 6 /usr/bin/aide --check | /bin/mail -s "$HOSTNAME - Daily AIDE integrity check run" root@example_server_name.mil If the file integrity application does not exist, or a "crontab" entry does not exist, check the cron directories for a script that runs the file integrity application: # ls -al /etc/cron.daily /etc/cron.weekly Inspect the file and ensure that the file integrity tool is being executed. If a file integrity tool is not configured in the crontab or in a script that runs at least weekly, this is a finding.

Fix Text

Configure the SUSE operating system to check the baseline configuration for unauthorized changes at least once weekly. Configure the file integrity tool to automatically run on the system at least weekly. The following example output is generic. It will set cron to run AIDE weekly, but other file integrity tools may be used: # sudo crontab -l 0 0 * * 6 /usr/sbin/aide --check | /bin/mail -s "$HOSTNAME - Daily AIDE integrity check run" root@example_server_name.mil Note: Per requirement SLES-12-010498, the "mailx" package must be installed on the system to enable email functionality.

Additional Identifiers

Rule ID: SV-217148r958794_rule

Vulnerability ID: V-217148

Group Title: SRG-OS-000363-GPOS-00150

Expert Comments

CCIs tied to check.

Controls tied to check. These are derived from the CCIs shown above.