The file integrity tool must use FIPS 140-2 approved cryptographic hashes for validating file contents.

Overview

Finding ID	Version	Rule ID	IA Controls	Severity
V-227955	GEN006575	SV-227955r603266_rule		Low

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

STIG	Date
Solaris 10 X86 Security Technical Implementation Guide	2022-09-07

Details

Check Text ( C-30117r490291_chk )
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 (F-30105r490292_fix)
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.