STIGhubSTIGhub
STIGsRMF ControlsCompare

STIGhub

A free tool to search and browse the entire DISA STIG library. Saves up to 75% in security compliance research time.

Navigation

  • Browse STIGs
  • Search
  • RMF Controls
  • Compare Versions

Resources

  • About
  • Release Notes
  • VPAT
  • DISA STIG Library
STIGs updated 3 hours ago
Powered by Pylon
© 2026 Beacon Cloud Solutions, Inc. All rights reserved.
← Back to VMware vRealize Automation 7.x Lighttpd Security Technical Implementation Guide

V-240256

CAT II (Medium)

Lighttpd must not be configured to use mod_status.

Rule ID

SV-240256r879655_rule

STIG

VMware vRealize Automation 7.x Lighttpd Security Technical Implementation Guide

Version

V1R2

CCIs

CCI-001312

Discussion

Any application providing too much information in error logs and in administrative messages to the screen risks compromising the data and security of the application and system. The structure and content of error messages needs to be carefully considered by the organization and development team. Lighttpd must only generate error messages that provide information necessary for corrective actions without revealing sensitive or potentially harmful information in error logs and administrative messages. The mod_status module generates the status overview of the webserver. The information covers: uptime average throughput current throughput active connections and their state While this information is useful on a development system, production systems must not have mod_status enabled.

Check Content

At the command prompt, execute the following command:    

cat /opt/vmware/etc/lighttpd/lighttpd.conf | awk '/server\.modules/,/\)/'

If the "mod_status" module is listed, this is a finding.

Fix Text

Navigate to and open the /opt/vmware/etc/lighttpd/lighttpd.conf file

Navigate to the "server.modules" section.

In the "server.modules" section, delete the "mod_status" entry.