Title

SharePoint must ensure authentication of both client and server during the entire session. An example of this is SSL Mutual Authentication. (Cat I 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 addresses 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

Review the SharePoint server configuration to ensure SSL Mutual authentication of both client and server during the entire session. Navigate to Central Administration. Under “System Settings”, click “Configure Alternate Access mappings”. Review the “Public URL for zone” column values. If any URL does not begin with “https”, this is a finding.

Fix Text

Configure the SharePoint server to ensure SSL Mutual authentication of both client and server during the entire session. Open IIS Manager. In the Connections pane, expand "Sites". Click the "Web Application" site. In the Actions pane, click "Bindings". In the Site Bindings window, click "Add". In the Add Site Binding window, change "Type" to "https", and select the site's SSL certificate. Click "OK". Remove all bindings that do not use https. Click "Close".

Additional Identifiers

Rule ID: SV-223257r612235_rule

Vulnerability ID: V-223257

Group Title: SRG-APP-000219

Expert Comments

CCIs tied to check.

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