WBLC-08-000223 - Oracle WebLogic must ensure authentication of both client and server during the entire session.
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. NOTE: Nessus has provided the target output to assist in reviewing the benchmark to ensure target compliance.
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'