Details
To minimize exposure of private assets to unnecessary risk by attackers, public web servers must be isolated from internal systems. Public web servers are by nature more vulnerable to attack from publically based sources, such as the public Internet. Once compromised, a public web server might be used as a base for further attack on private resources, unless additional layers of protection are implemented. Public web servers must be located in a DoD DMZ Extension, if hosted on the NIPRNet, with carefully controlled access. Failure to isolate resources in this way increase risk that private assets are exposed to attacks from public sources.
NOTE: Nessus has not performed this check. Please review the benchmark to ensure target compliance.
Solution
Logically relocate the public web server to be isolated from internal systems. In addition, ensure the public web server does not have trusted connections with assets outside the confines of the demilitarized zone (DMZ) other than application and/or database servers that are a part of the same system as the web server.
Supportive Information
The following resource is also helpful.
This control applies to the following type of system Unix.
References
- CAT|II
- Rule-ID|SV-32932r2_rule
- STIG-ID|WA060_A22
- Vuln-ID|V-2242