|Finding ID||Version||Rule ID||IA Controls||Severity|
|Making certain that the web server has not been updated by an unauthorized user is always a concern. Adding patches, functions, and modules that are untested and not part of the baseline opens the possibility for security risks. The web server must offer, and not hinder, a method that allows for the quick and easy reinstallation of a verified and patched baseline to guarantee the production web server is up-to-date and has not been modified to add functionality or expose security risks. When the web server does not offer a method to roll back to a clean baseline, external methods, such as a baseline snapshot or virtualizing the web server, can be used.|
|Apache Server 2.4 UNIX Site Security Technical Implementation Guide||2022-12-14|
|Check Text ( C-15502r277208_chk )|
| Interview the System Administrator for the Apache web server. |
Ask for documentation on the disaster recovery methods tested and planned for the Apache web server in the event of the necessity for rollback.
If documentation for a disaster recovery has not been established, this is a finding.
|Fix Text (F-15500r277209_fix)|
| Prepare documentation for disaster recovery methods for the Apache web server in the event of the necessity for rollback. |
Document and test the disaster recovery methods designed.