All web server files must be verified for their integrity (e.g., checksums and hashes) before becoming part of the production web server.

From Web Server Security Requirements Guide

Part of SRG-APP-000131-WSR-000051

Associated with: CCI-001749

SV-70237r2_rule All web server files must be verified for their integrity (e.g., checksums and hashes) before becoming part of the production web server.

Vulnerability discussion

Being able to verify that a patch, upgrade, certificate, etc., being added to the web server is unchanged from the producer of the file is essential for file validation and non-repudiation of the information. The web server or hosting system must have a mechanism to verify that files, before installation, are valid.Examples of validation methods are sha1 and md5 hashes and checksums.

Check content

Review the web server documentation and deployment configuration to determine if the web server validates files before the files are implemented into the running configuration. If the web server does not meet this requirement and an external facility is not available for use, this is a finding.

Fix text

Configure the web server to verify object integrity before becoming part of the production web server or utilize an external tool designed to meet this requirement.

Pro Tips

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