The SUSE operating system must use a separate file system for the system audit data path.

From SLES 12 Security Technical Implementation Guide

Associated with: CCI-000366

SV-91967r2_rule The SUSE operating system must use a separate file system for the system audit data path.

Vulnerability discussion

The use of separate file systems for different paths can protect the system from failures resulting from a file system becoming full or failing.

Check content

Verify that the SUSE operating system has a separate file system/partition for the system audit data path. Check that a file system/partition has been created for the system audit data path with the following command: Note: "/var/log/audit" is used as the example as it is a common location. #grep /var/log/audit /etc/fstab UUID=3645951a /var/log/audit ext4 defaults 1 2 If a separate entry for the system audit data path (in this example the "/var/log/audit" path) does not exist, ask the System Administrator if the system audit logs are being written to a different file system/partition on the system and then grep for that file system/partition. If a separate file system/partition does not exist for the system audit data path, this is a finding.

Fix text

Migrate the SUSE operating system audit data path onto a separate file system.

Pro Tips

Lavender hyperlinks in small type off to the right (of CSS class id, if you view the page source) point to globally unique URIs for each document and item. Copy the link location and paste anywhere you need to talk unambiguously about these things.

You can obtain data about documents and items in other formats. Simply provide an HTTP header Accept: text/turtle or Accept: application/rdf+xml.