STIGhubSTIGhub
STIGsRMF ControlsCompare

STIGhub

A free tool to search and browse the entire DISA STIG library. Saves up to 75% in security compliance research time.

Navigation

  • Browse STIGs
  • Search
  • RMF Controls
  • Compare Versions

Resources

  • About
  • Release Notes
  • VPAT
  • DISA STIG Library
STIGs updated 3 hours ago
Powered by Pylon
© 2026 Beacon Cloud Solutions, Inc. All rights reserved.
← Back to Oracle WebLogic Server 12c Security Technical Implementation Guide

V-235984

CAT II (Medium)

Oracle WebLogic must ensure authentication of both client and server during the entire session.

Rule ID

SV-235984r1043178_rule

STIG

Oracle WebLogic Server 12c Security Technical Implementation Guide

Version

V2R2

CCIs

CCI-001184

Discussion

This control focuses on communications protection at the session, versus packet level. At the application layer, session IDs are tokens generated by web applications to uniquely identify an application user's session. Web applications utilize session tokens or session IDs in order to establish application user identity. Proper use of session IDs addresses man-in-the-middle attacks, including session hijacking or insertion of false information into a session. Application servers must provide the capability to perform mutual authentication. Mutual authentication is when both the client and the server authenticate each other.

Check Content

1. Access AC
2. From 'Domain Structure', select 'Environment' -> 'Servers' 
3. From the list of servers, select one which needs check for Mutual Authentication configuration verification
4. From 'Configuration' tab -> 'General' tab, ensure 'Listen Port Enabled' checkbox is deselected
5. Ensure 'SSL Listen Port Enabled' checkbox is selected and a valid port number is in 'SSL Listen Port' field, e.g., 7002
6. From 'Configuration' tab -> 'SSL' tab, click 'Advanced' link
7. Ensure 'Two Way Client Cert Behavior' field value is set to 'Client Certs Requested And Enforced'
8. Repeat steps 3-7 for all servers requiring Mutual Authentication configuration checking

If any servers requiring Mutual Authentication do not have the 'SSL Listen Port Enabled' checkbox selected or the 'Two Way Client Cert Behavior' field value set to 'Client Certs Requested And Enforced', this is a finding.

Fix Text

1. Obtain the certificate(s) for the trusted certificate authority that signed the certificates for the client(s)
2. Access EM 
3. Select the domain from the navigation tree, and use the dropdown to select 'WebLogic Domain' -> 'Security' -> 'Keystore' 
4. Locate the desired keystore in which to load the client certificate(s), select and click 'Manage' button
5. From 'Manage Certificates' page, click 'Import'
6. Complete 'Certificate Type', 'Alias' and 'Certificate Source' fields and click 'OK'. Ensure the imported certificate(s) appears in the list.
7. Access AC
8. Utilize 'Change Center' to create a new change session
9. From 'Domain Structure', select 'Environment' -> 'Servers' 
10. From the list of servers, select one which needs Mutual Authentication set up
11. From 'Configuration' tab -> 'SSL' tab, click 'Advanced' link
12. Set 'Two Way Client Cert Behavior' field value is set to 'Client Certs Requested And Enforced'
13. Repeat steps 7-12 for all servers requiring SSL configuration
14. From 'Domain Structure', select 'Environment' -> 'Servers', click 'Control' tab
15. Select checkbox for all servers configured in previous steps and click 'Restart SSL'