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 login 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.
Review the web server documentation and configuration to determine if web server modules are fully tested before implementation in the production environment. Review the web server for modules identified as test, debug, or backup and that cannot be reached through the hosted application. Review the web server to see if the web server or an external utility is in use to enforce the signing of modules before they are put into a production environment. If development and testing is taking place on the production web server or modules are put into production without being signed, this is a finding.
Configure the web server to enforce, internally or through an external utility, the review, testing and signing of modules before implementation into the production environment.