SV-214799r991589: The Red Hat Enterprise Linux operating system must be configured so that the cryptographic hash of system files and commands matches vendor values. | Red Hat Enterprise Linux 7 STIG SCAP Benchmark

Loading benchmark…

Assessment Title

Rule Text

The Red Hat Enterprise Linux operating system must be configured so that the cryptographic hash of system files and commands matches vendor values.

Description

Discussion Text

Without cryptographic integrity protections, system command and files can be altered by unauthorized users without detection. Cryptographic mechanisms used for protecting the integrity of information include, for example, signed hash functions using asymmetric cryptography enabling distribution of the public key to verify the hash information while maintaining the confidentiality of the key used to generate the hash.

How this relates to the STIG checklist: STIG vs SCAP benchmark.

IA Controls

NIST SP 800-53

Not mappedCCI-001749SV-86479V-71855

References

DPMS Target Red Hat Enterprise Linux 7 DISA DPMS Target Red Hat Enterprise Linux 7 2899

Checks

DISA STIG (Manual Reference)

Verify the cryptographic hash of system files and commands match the vendor values.

Check the cryptographic hash of system files and commands with the following command:

Note: System configuration files (indicated by a "c" in the second column) are expected to change over time. Unusual modifications should be investigated through the system audit log.

# rpm -Va --noconfig | grep '^..5'

If there is any output from the command for system files or binaries, this is a finding.

SCC Automation Reference

The reconstructed evaluation script behind this rule's OVAL check(s) — every module a compound check combines, with this rule's own concrete values and DISA's SCC tool's real per-module mechanism curated from static teardown of SCC releases.

#!/bin/bash
# Reconstructed from oval:mil.disa.stig.rhel7:def:1340
# The Red Hat Enterprise Linux operating system must be configured so that the cryptographic hash of system files and commands matches vendor values.
# Per-module read mechanism curated from static teardown of DISA's SCC tool
# (SCAP Compliance Checker) -- see the SCC Automation Reference above.

# verify file md5 hashes
# rpmverifyfile_object (rpmverifyfile_test)
test_1() {
  ! ( rpm -V .* &>/dev/null )
}

if test_1; then
  echo "PASS"
else
  echo "FAIL"
fi

Assessment Script Powered by AISyntax-verified

A standalone Shell script to assess this control automatically. Review before running it in your environment.

Syntax-checked as valid Shell. Not executed here — running it for real needs the actual rhel_7 target this check assesses.

#!/bin/sh
# OVAL definition: oval:mil.disa.stig.rhel7:def:1340
if [ ! -x "$(command -v rpm)" ]; then echo "FAIL"; exit 1; fi
for file in /usr/{,local/}{bin,sbin,lib,lib64,libexec}/*; do \
  if [ -f "$file" ]; then \
    hash=$(stat -c %H "$file") && \
    pkg=$(rpm -qf "$file" 2>/dev/null) && \
    [ -z "$pkg" ] && echo "FAIL" && exit 1; \
  fi; \
done
echo "PASS"; exit 0

Remediation

Run the following command to determine which package owns the file:

# rpm -qf <filename>

The package can be reinstalled from a yum repository using the command:

# sudo yum reinstall <packagename>

Alternatively, the package can be reinstalled from trusted media using the command:

# sudo rpm -Uvh <packagename>