Details

A file integrity baseline is a collection of file metadata which is to evaluate the integrity of the system. A minimal baseline must contain metadata for all device files, setuid files, setgid files, system libraries, system binaries, and system configuration files. The minimal metadata must consist of the mode, owner, group owner, and modification times. For regular files, metadata must also include file size and a cryptographic hash of the file’s contents.

NOTE: Nessus has not performed this check. Please review the benchmark to ensure target compliance.

Solution

Create a file integrity baseline, including cryptographic hashes, for the system.

# find / -depth -print | tee Baseline

Open the above file and either manually execute md5sum, csum, or the chksum command on each file. Alternatively, write a script to perform the above. NOTE: For security purposes, ‘md5sum’ is preferred over ‘chksum’. The md5sum command can be loaded from the Linux Tool Kit for AIX.
Alternatively, OpenSSL can be used to create hashes.
#openssl dgst -md5 < file >

Supportive Information

The following resource is also helpful.

• https://iasecontent.disa.mil/stigs/zip/U_AIX_6-1_V1R14_STIG.zip

This security hardening control applies to the following category of controls within NIST 800-53: Configuration Management.This control applies to the following type of system Unix.

References

• 800-53|CM-2
• CAT|II
• CCI|CCI-000293
• Group-ID|V-11941
• Rule-ID|SV-38784r1_rule
• STIG-ID|GEN000140
• Vuln-ID|V-11941

Source

• Tenable.com/audits