|Finding ID||Version||Rule ID||IA Controls||Severity|
|In the case of a production web server, areas for content development and testing will not exist, as this type of content is only permissible on a development website. The process of developing on a functional production website entails a degree of trial and error and repeated testing. This process is often accomplished in an environment where debugging, sequencing, and formatting of content are the main goals. The opportunity for a malicious user to obtain files that reveal business logic and logon schemes is high in this situation. The existence of such immature content on a web server represents a significant security risk that is totally avoidable. The web server must enforce, internally or through an external utility, the signing of modules before they are implemented into a production environment. By signing modules, the author guarantees that the module has been reviewed and tested before production implementation.|
|Apache Server 2.4 UNIX Server Security Technical Implementation Guide||2020-09-25|
|Check Text ( C-15452r276974_chk )|
| Enter the following command: |
This will provide a list of the loaded modules. Validate that all displayed modules are required for operations.
If any module is not required for operation, this is a finding.
NOTE: The following modules are needed for basic web function and do not need to be reviewed:
For a complete list of signed Apache Modules, review https://httpd.apache.org/docs/2.4/mod/.
|Fix Text (F-15450r276975_fix)|
|Remove any unsigned modules.|