Search filters this STIG's checks locally. Separate terms must all match (use quotes for an exact phrase). A search you ran on the Search page carries over here.
Assessment Title
Rule Text
VAMI must not be configured to use "mod_status".
Description
Discussion Text
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.
VAMI 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.
VAMI 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.
New to STIG checklists? Read What is a STIG checklist? and CKL vs CKLB.