Title

The IIS 8.5 private website have a server certificate issued by DoD PKI or DoD-approved PKI Certification Authorities (CAs). (Cat II impact)

Discussion

The use of a DoD PKI certificate ensures clients the private website they are connecting to is legitimate, and is an essential part of the DoD defense-in-depth strategy.

Check Content

Follow the procedures below for each site hosted on the IIS 8.5 web server: Open the IIS 8.5 Manager. Click the site name under review. Click “Bindings” in the “Action” Pane. Click the “HTTPS type” from the box. Click “Edit”. Click “View” and then review and verify the certificate path. If the list of CAs in the trust hierarchy does not lead to the DoD PKI Root CA, DoD-approved external certificate authority (ECA), or DoD-approved external partner, this is a finding. If HTTPS is not an available type under site bindings, this is a finding. If HTTPS is not an available type under site bindings, and the Web Server ONLY communicates directly with a load balancer/proxy server, with IP address and Domain Restrictions in place, this is not a finding. For systems with load balancers that perform SSL offloading, this is Not Applicable.

Fix Text

Follow the procedures below for each site hosted on the IIS 8.5 web server: Open the IIS 8.5 Manager. Click the Server name. Double-click “Server Certificates”. Click “Import” under the "Actions" pane. Browse to the DoD certificate location, select it, and click “OK”. Remove any non-DoD certificates if present. Click on the site needing the certificate. Select “Bindings” under the "Actions" pane. Click on the binding needing a certificate and select “Edit”, or add a site binding for HTTPS. Assign the certificate to the website by choosing it under the “SSL Certificate” drop-down and clicking “OK”.

Additional Identifiers

Rule ID: SV-214479r879798_rule

Vulnerability ID: V-214479

Group Title: SRG-APP-000427-WSR-000186

Expert Comments

CCIs tied to check.

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