Title

Google Search Appliance must ensure authentication of both client and server during the entire session. An example of this is SSL Mutual Authentication. (Cat II impact)

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 addressed man-in-the-middle attacks including session hijacking or insertion of false information into a session. This control is only implemented where deemed necessary by the organization (e.g., sessions in service-oriented architectures providing web-based services).

Check Content

Open the GSA Web Admin Console at https:<your GSA IP or hostname>:8443. Login to the GSA management interface. Navigate to "Administration", select "SSL Settings". If "Enable Server Certificate Authentication" is checked, this is not a finding.

Fix Text

Open the GSA Web Admin Console at https:<your GSA IP or hostname>:8443. Login to the GSA management interface. Navigate to "Administration", select "SSL Settings". Enable the option "Enable Server Certificate Authentication".

Additional Identifiers

Rule ID: SV-75243r1_rule

Vulnerability ID: V-60791

Group Title: SRG-APP-000219

Expert Comments

CCIs tied to check.

Controls tied to check. These are derived from the CCIs shown above.