Information
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.
NOTE: Nessus has provided the target output to assist in reviewing the benchmark to ensure target compliance.
Solution
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.
Item Details
Category: CONFIGURATION MANAGEMENT, SYSTEM AND INFORMATION INTEGRITY
References: 800-53|CM-3(5), 800-53|SI-6a., 800-53|SI-6b., CAT|II, CCI|CCI-001744, CCI|CCI-002696, CCI|CCI-002699, Rule-ID|SV-217148r958794_rule, STIG-ID|SLES-12-010500, STIG-Legacy|SV-91847, STIG-Legacy|V-77151, Vuln-ID|V-217148
Control ID: fbeca184c59ce01013a19d4715f1c00dc13d3971ccaf878c4a5eb2e90eecca33