Title

The file integrity tool must use FIPS 140-2 approved cryptographic hashes for validating file contents. (Cat III impact)

Discussion

File integrity tools often use cryptographic hashes for verifying that file contents have not been altered. These hashes must be FIPS 140-2 approved.

Check Content

If using AIDE, verify the configuration contains the sha256 or sha512 options for all monitored files and directories. Here is an example AIDE configuration fragment. SampleRule = p+i+l+n+u+g+s+m+c+acl+xattrs+sha256 /bin SampleRule If either the sha256 or sha512 option is not present, this is a finding. If using a different file integrity tool, check the configuration per tool documentation.

Fix Text

If using AIDE, edit the configuration and add the sha256 or sha512 option for all monitored files and directories. If using a different file integrity tool, configure FIPS 140-2 approved cryptographic hashes per the tool's documentation.

Additional Identifiers

Rule ID: SV-227047r603265_rule

Vulnerability ID: V-227047

Group Title: SRG-OS-000278

Expert Comments

CCIs tied to check.

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