Details
The web server has several remote communications channels. Examples are user requests via http/https, communication to a backend database, or communication to authenticate users. The encryption used to communicate must match the data that is being retrieved or presented.
Methods of communication are http for publicly displayed information, https to encrypt when user data is being transmitted, VPN tunneling, or other encryption methods to a database.
NOTE: Nessus has provided the target output to assist in reviewing the benchmark to ensure target compliance.
Solution
1. Open every .conf file (e.g., ssl.conf) included in $DOMAIN_HOME/config/fmwconfig/components/OHS/
Note: Does not apply to admin.conf.
2a. Search for the ‘SSLEngine’ directive at the OHS server, virtual host, and/or directory configuration scopes.
2b. Set the ‘SSLEngine’ directive to ‘On’, add the directive if it does not exist.
3a. Search for the ‘SSLProtocol’ directive at the OHS server configuration, virtual host, and/or directory levels.
3b. Set the ‘SSLProtocol’ directive to ‘TLSv1.2 TLSv1.1’, add the directive if it does not exist.
4a. Search for the ‘SSLWallet’ directive at the OHS server configuration, virtual host, and/or directory levels.
4b. Set the ‘SSLWallet’ directive to the location (i.e., folder within $DOMAIN_HOME/config/fmwconfig/components/OHS/instances/
Supportive Information
The following resource is also helpful.
This security hardening control applies to the following category of controls within NIST 800-53: Access Control.This control applies to the following type of system Unix.
References
- 800-53|AC-17(2)
- CAT|II
- CCI|CCI-000068
- Rule-ID|SV-78627r2_rule
- STIG-ID|OH12-1X-000009
- Vuln-ID|V-64137