Details
Determining a safe state for failure and weighing that against a potential denial of service for users depends on what type of application the web server is hosting. For an application presenting publicly available information that is not critical, a safe state for failure might be to shut down for any type of failure, but for an application that presents critical and timely information, a shutdown might not be the best state for all failures.
Performing a proper risk analysis of the hosted applications and configuring the web server according to what actions to take for each failure condition will provide a known fail safe state for the web server.
Satisfies: SRG-APP-000225-WSR-000140, SRG-APP-000225-WSR-000074
NOTE: Nessus has not performed this check. Please review the benchmark to ensure target compliance.
Solution
Prepare documentation for disaster recovery methods for the Apache 2.4 web server in the event of the necessity for rollback.
Document and test the disaster recovery methods designed.
Supportive Information
The following resource is also helpful.
This security hardening control applies to the following category of controls within NIST 800-53: System and Communications Protection.This control applies to the following type of system Unix.
References
- 800-53|SC-24
- CAT|II
- CCI|CCI-001190
- Rule-ID|SV-214254r612240_rule
- STIG-ID|AS24-U1-000550
- STIG-Legacy|SV-102783
- STIG-Legacy|V-92695
- Vuln-ID|V-214254