From Red Hat Enterprise Linux 6 Security Technical Implementation Guide
Part of SRG-OS-999999
Associated with: CCI-000366
The hash on important files like system executables should match the information given by the RPM database. Executables with erroneous hashes could be a sign of nefarious activity on the system.
The following command will list which files on the system have file hashes different from what is expected by the RPM database: # rpm -Va | awk '$1 ~ /..5/ && $2 != "c"' If there is any output from the command for system binaries, verify that the changes were due to STIG application and have been documented with the ISSO. If there are changes to system binaries and they are not documented with the ISSO, this is a finding.
The RPM package management system can check the hashes of installed software packages, including many that are important to system security. Run the following command to list which files on the system have hashes that differ from what is expected by the RPM database: # rpm -Va | awk '$1 ~ /..5/ && $2 != "c"' If the file that has changed was not expected to, refresh from distribution media or online repositories. rpm -Uvh [affected_package] OR yum reinstall [affected_package]
Lavender hyperlinks in small type off to the right (of CSS
class id
, if you view the page source) point to
globally unique URIs for each document and item. Copy the
link location and paste anywhere you need to talk
unambiguously about these things.
You can obtain data about documents and items in other
formats. Simply provide an HTTP header Accept:
text/turtle
or
Accept: application/rdf+xml
.
Powered by sagemincer