STIGQter: STIG Summary: Tri-Lab Operating System Stack (TOSS) 5 Security Technical Implementation Guide Version: 1 Release: 1 Benchmark Date: 26 Mar 2026:

TOSS 5 must use a file integrity tool that is configured to use FIPS 140-3-approved cryptographic hashes for validating file contents and directories.

DISA Rule

SV-282742r1201206_rule

Vulnerability Number

V-282742

Group Title

SRG-OS-000480-GPOS-00227

Rule Version

TOSS-05-000371

Severity

CAT II

CCI(s)

• CCI-000366 - Implement the security configuration settings.
• CCI-002450 - Implement organization-defined types of cryptography for each specified cryptography use.

Weight

10

Fix Recommendation

Configure the file integrity tool to use FIPS 140-3 cryptographic hashes for validating file and directory contents.

If AIDE is installed, ensure the "sha512" rule is present on all uncommented file and directory selection lists. Exclude any log files or files expected to change frequently to reduce unnecessary notifications.

Check Contents

Verify AIDE is configured to use FIPS 140-3 file hashing using the following command:

$ grep sha512 /etc/aide.conf

All=p+i+n+u+g+s+m+S+sha512+acl+xattrs+selinux

If the "sha512" rule is not being used on all uncommented selection lines in the "/etc/aide.conf" file, or another file integrity tool is not using 140-3-approved cryptographic hashes for validating file contents and directories, this is a finding.

Vulnerability Number

V-282742

Documentable

False

Rule Version

TOSS-05-000371

Severity Override Guidance

Verify AIDE is configured to use FIPS 140-3 file hashing using the following command:

$ grep sha512 /etc/aide.conf

All=p+i+n+u+g+s+m+S+sha512+acl+xattrs+selinux

If the "sha512" rule is not being used on all uncommented selection lines in the "/etc/aide.conf" file, or another file integrity tool is not using 140-3-approved cryptographic hashes for validating file contents and directories, this is a finding.

Check Content Reference

M

Target Key

5738