UCF STIG Viewer Logo

OHS must provide the capability to immediately disconnect or disable remote access to the hosted applications.


Overview

Finding ID Version Rule ID IA Controls Severity
V-64501 OH12-1X-000034 SV-78991r1_rule Medium
Description
During an attack on the web server or any of the hosted applications, the system administrator may need to disconnect or disable access by users to stop the attack. The web server must provide a capability to disconnect users to a hosted application without compromising other hosted applications unless deemed necessary to stop the attack. Methods to disconnect or disable connections are to stop the application service for a specified hosted application, stop the web server, or block all connections through web server access list. The web server capabilities used to disconnect or disable users from connecting to hosted applications and the web server must be documented to make certain that, during an attack, the proper action is taken to conserve connectivity to any other hosted application if possible and to make certain log data is conserved for later forensic analysis.
STIG Date
Oracle HTTP Server 12.1.3 Security Technical Implementation Guide 2020-06-12

Details

Check Text ( C-65253r1_chk )
1. Open $DOMAIN_HOME/config/fmwconfig/components/OHS//httpd.conf and every .conf file (e.g., ssl.conf) included in it with an editor.

2. Search for the "", "", or "" directive serving the application/content under attack at the OHS server, virtual host, or directory configuration scope.

3. If the "", "", or "" directive serving the application/content under attack does not contain the appropriate "Order", "Deny", and "Allow" directives to prohibit access, this is a finding.
Fix Text (F-70431r1_fix)
1. Open $DOMAIN_HOME/config/fmwconfig/components/OHS//httpd.conf and every .conf file (e.g., ssl.conf) included in it with an editor.

2. Search for the "", "", or "" directive serving the application/content under attack at the OHS server, virtual host, or directory configuration scope.

3. Set the "Order" directive to "allow,deny", add the directive if it does not exist.

4. Comment out any "Allow" directives to prohibit access to the application/content under attack if it exists.

5. Set "Deny" directives to "from all" to prohibit access to the application/content under attack, add the directive if it does not exist.

6. Issue a "nmSoftRestart(serverName='componentName',serverType='OHS') from the WLST shell prompt.