Rule ID
SV-218767r1265529_rule
Version
V2R17
CCIs
The use of a DoW PKI certificate ensures clients the private website they are connecting to is legitimate, and is an essential part of the DoW defense-in-depth strategy.
Note: If the server being reviewed is hosting WSUS, this is not applicable. Note: If the server is providing OCSP, and not otherwise hosting any content, this requirement is not applicable. Follow the procedures below for each site hosted on the IIS 10.0 web server: Open the IIS 10.0 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 DoW PKI Root CA, DoW-approved external certificate authority (ECA), or DoW-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.
To add DoW Certificates to the Server, if not already present: Open the IIS 10.0 Manager. Click the Server name. Double-click "Server Certificates". Click "Import" under the "Actions" pane. Browse to the DoW certificate location, select it, and click "OK". Remove any non-DoW certificates if present. Follow the procedures below for each site hosted on the IIS 10.0 web server to bind the certificates to the site: 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".