The IIS 10.0 website must only accept client certificates issued by DOD PKI or DOD-approved PKI Certification Authorities (CAs).

Severity	Group ID	Group Title	Version	Rule ID	Date	STIG Version
medium	V-218767	SRG-APP-000427-WSR-000186	IIST-SI-000241	SV-218767r1067601_rule	2025-02-11	2

Description
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
Note: If the server being reviewed is hosting WSUS, this 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 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.

ℹ️ Check

Note: If the server being reviewed is hosting WSUS, this 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 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.

✔️ Fix
To add DOD 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 DOD certificate location, select it, and click "OK". Remove any non-DOD 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".

✔️ Fix

To add DOD 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 DOD certificate location, select it, and click "OK". Remove any non-DOD 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".