What changed in Microsoft IIS 10.0 Site STIG V2R17V2R17 changes

Check text

Note: If the server being reviewed is a public IIS 10.0 web server, this is Not Applicable. Note: If the server is hosting SharePoint, this is Not Applicable. Note: If the server is hosting WSUS, this is Not Applicable. Note: If the server is hosting Office Online Server (OOS), this is Not Applicable. Note: If SSL is installed on load balancer/proxy server through which traffic is routed to the IIS 10.0 server, and the IIS 10.0 server receives traffic from the load balancer/proxy server, the SSL requirement must be met on the load balancer/proxy server and is Not Applicable in this STIG. 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. Double-click the "SSL Settings" icon. Verify "Require SSL" check box is selected. If the "Require SSL" check box is not selected, this is a finding.

V-218737 in V2R17

Check text

Note: If the server being reviewed is a private IIS 10.0 web server, this is Not Applicable. Note: If the server being reviewed is a public IIS 10.0 web server not requiring authentication, this is Not Applicable. Note: If the server being reviewed is hosting SharePoint, this is Not Applicable. Note: If the server being reviewed is hosting WSUS, this is Not Applicable. Note: If the server being reviewed is hosting Simple Certificate Enrollment Services (SCEP), this is Not Applicable. Note: If the server being reviewed is hosting Network Device Enrollment Services (NDES), this is Not Applicable. Note: If the server is hosting Office Online Server (OOS), 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. Double-click the "SSL Settings" icon. Verify "Require SSL" check box is selected. If the "Require SSL" check box is not selected, this is a finding.

V-218738 in V2R17

Check text

Note: If the server being reviewed is hosting SharePoint, this is not applicable. Note: If the server is hosting Office Online Server (OOS), this is Not Applicable. For Handler Mappings, the ISSO must document and approve all allowable scripts the website allows (whitelist) and denies (blacklist). The whitelist and blacklist will be compared to the Handler Mappings in IIS 10.0. Handler Mappings at the site level take precedence over Handler Mappings at the server level. Open the IIS 10.0 Manager. Click the site name under review. Double-click "Handler Mappings". If any script file extensions from the blacklist are enabled, this is a finding.

V-218744 in V2R17

Check text

Note: If the server being reviewed is hosting SharePoint, this is Not Applicable. Note: If the server is hosting Office Online Server (OOS), this is Not Applicable. For Request Filtering, the ISSO must document and approve all allowable scripts the website allows (white list) and denies (black list). The white list and black list will be compared to the Request Filtering in IIS 10.0. Request Filtering at the site level take precedence over Request Filtering at the server level. 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 to review. Double-click Request Filtering->File Name Extensions Tab. If any script file extensions from the black list are not denied, this is a finding.

V-218745 in V2R17

Check text

Note: If any of the following is true, this requirement is Not Applicable: - The server being reviewed is hosting SharePoint. - The server being reviewed is hosting WSUS. - This IIS 10.0 installation is supporting Microsoft Exchange and not otherwise hosting any content. - The server being reviewed is hosting Office Online Server (OOS). Follow the procedures below for each site hosted on the IIS 10.0 web server: Open the IIS 10.0 Manager. Right-click on the site name under review. Select "Edit Bindings". Verify there are hostname entries and unique IP addresses assigned to port 80 for HTTP and port 443 for HTTPS. Other approved and documented ports may be used. If both hostname entries and unique IP addresses are not configured to port 80 for HTTP and port 443 for HTTPS (or other approved and documented port), this is a finding. Note: If certificate handling is performed at the Proxy/Load Balancer, this is not a finding. Note: If HTTP/Port 80 is not being used, and is not configured as above, this is not a finding.

V-218748 in V2R17

Check text

Note: If any of the following is true, this requirement is Not Applicable: - Authentication is offloaded to an external enterprise authentication mechanism that is performing certificate handling. - The server being reviewed is a public IIS 10.0 web server. - The server being reviewed is hosting SharePoint. - The server being reviewed is hosting WSUS. - Certificate handling is performed at the Proxy/Load Balancer. - The server being reviewed is hosting Simple Certificate Enrollment Services (SCEP). - The server being reviewed is hosting Network Device Enrollment Services (NDES). - The server is providing OCSP and not otherwise hosting any content. - The server being reviewed is hosting Office Online Server (OOS). Follow the procedures below for each site hosted on the IIS 10.0 web server: Open the IIS 10.0 Manager. Double-click the "SSL Settings" icon. Verify the "Clients Certificate Required" check box is selected. If the "Clients Certificate Required" check box is not selected, this is a finding.

Discussion

A DODDoW private website must use PKI as an authentication mechanism for web users. Information systems residing behind web servers requiring authorization based on individual identity must use the identity provided by certificate-based authentication to support access control decisions. Not using client certificates allows an attacker unauthenticated access to private websites. Satisfies: SRG-APP-000172-WSR-000104, SRG-APP-000224-WSR-000135, SRG-APP-000427-WSR-000186

V-218749 in V2R17

Check text

Note: If this server is hosting WSUS, this requirement is not applicable. Note: If this IIS 10.0 installation is supporting Microsoft Exchange, and not otherwise hosting any content, this requirement is not applicable. Note: If this server is hosting the SharePoint Web Services site, this requirement is not applicable. Note: If the server is hosting Office Online Server (OOS), 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 the "Advanced Settings" from the "Actions" pane. Review the Physical Path. If the Path is on the same partition as the OS, this is a finding.

V-218752 in V2R17

Check text

Note: If the server being reviewed is hosting SharePoint, this is Not Applicable. Note: If the server is hosting Office Online Server (OOS), 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. Double-click the "Request Filtering" icon. Click "Edit Feature Settings" in the "Actions" pane. If the "Allow double escaping" check box is checked, this is a finding.

V-218757 in V2R17

Check text

Note: If the server being reviewed is hosting SharePoint, this is Not Applicable. Note: If the server being reviewed is hosting Network Device Enrollment Services (NDES), this is Not Applicable. Note: If the server being reviewed is hosting Azure DevOps (ADO), this is Not Applicable. Note: If the server is hosting Office Online Server (OOS), 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. Double-click the "Request Filtering" icon. Click "Edit Feature Settings" in the "Actions" pane. If the "Allow unlisted file name extensions" check box is checked, this is a finding. Note: If this IIS 10.0 installation is supporting Microsoft Exchange, and not otherwise hosting any content, this requirement is Not Applicable. Note: If this IIS 10.0 installation is supporting Splunk, this requirement is Not Applicable. Note: If this IIS 10.0 installation is supporting WSUS, this requirement is Not Applicable.

V-218758 in V2R17

Check text

Note: If the server being reviewed is hosting SharePoint, this is Not Applicable. Note: If the ".NET feature" is not installed, this check is Not Applicable. Note: If the server is hosting Office Online Server (OOS), 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. Double-click ".NET Compilation". Scroll down to the "Behavior" section and verify the value for "Debug" is set to "False". If the "Debug" value is not set to "False", this is a finding.

V-218761 in V2R17

Check text

Note: If the IIS 10.0 installation is supporting Microsoft Exchange, WSUS, or SharePoint and is not otherwise hosting any content, this requirement is not applicable. Note: If the server is hosting Office Online Server (OOS), 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 Application Pools. Highlight an Application Pool to review and click "Advanced Settings" in the "Actions" pane. Scroll down to the "Process Model" section and verify the value for "Idle Time-out" is not "0". If the "Idle Time-out" is set to "0", this is a finding.

V-218762 in V2R17

Check text

Note: If the server is providing OCSP, and not otherwise hosting any content, this requirement is not applicable. Review the website to determine if HTTP and HTTPs (e.g., 80 and 443) are used in accordance with those ports and services registered and approved for use by the DODDoW PPSM. Any variation in PPS will be documented, registered, and approved by the PPSM. 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. In the "Action" Pane, click "Bindings". Review the ports and protocols. If unknown ports or protocols are used, then this is a finding.

Discussion

Web servers provide numerous processes, features, and functionalities that use TCP/IP ports. Some of these processes may be deemed unnecessary or too unsecure to run on a production system. The web server must provide the capability to disable or deactivate network-related services deemed to be non-essential to the server mission, too unsecure, or prohibited by the PPSM CAL and vulnerability assessments. Failure to comply with DoDDoW ports, protocols, and services (PPS) requirements can result in compromise of enclave boundary protections and/or functionality of the AIS. The ISSM will ensure web servers are configured to use only authorized PPS in accordance with the Network Infrastructure STIG, DoD Instruction 8551.1, PPSM, and the associated PPS Assurance Category Assignments List.

V-218766 in V2R17

Title

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

Check text

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 DODDoW PKI Root CA, DODDoW-approved external certificate authority (ECA), or DODDoW-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 text

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

Discussion

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

V-218767 in V2R17

Check text

Notes: - If SSL is installed on load balancer/proxy server through which traffic is routed to the IIS 10.0 server, and the IIS 10.0 server receives traffic from the load balancer/proxy server, the SSL requirement must be met on the load balancer/proxy server. In this case, this requirement is not applicable. - If this is a public-facing web server, this requirement is not applicable. - If this server is hosting WSUS, this requirement is not applicable. - If the server being reviewed is hosting SharePoint, this is not applicable. - If the server being reviewed is hosting Simple Certificate Enrollment Services (SCEP), this is not applicable. - If the server being reviewed is hosting Network Device Enrollment Services (NDES), this is not applicable. - If the server is providing OCSP, and not otherwise hosting any content, this requirement is not applicable. - If the server is providing CRL, and not otherwise hosting any content, this requirement is not applicable. - The server being reviewed is hosting Office Online Server (OOS). Follow the procedures below for each site hosted on the IIS 10.0 web server: Open the IIS 10.0 Manager. Double-click the "SSL Settings" icon under the "IIS" section. Verify "Require SSL" is checked. Verify "Client Certificates Required" is selected. Click the site under review. Select "Configuration Editor" under the "Management" section. From the "Section:" drop-down list at the top of the configuration editor, locate "system.webServer/security/access". The value for "sslFlags" set must include "ssl128". If the "Require SSL" is not selected, this is a finding. If the "Client Certificates Required" is not selected, this is a finding. Note: "Client Certificates Required" can be considered Not Applicable in a Single Sign On (SSO) scenario where client certificates are no longer processed locally. If the "sslFlags" is not set to "ssl128", this is a finding.

V-218768 in V2R17

Check text

Note: If the server being reviewed is a public IIS 10.0 web server, this is not applicable. Note: If the server being reviewed is hosting SharePoint, this is not applicable. Note: If the server being reviewed is hosting WSUS, this is not applicable. Note: If SSL is installed on load balancer/proxy server through which traffic is routed to the IIS 10.0 server, and the IIS 10.0 server receives traffic from the load balancer/proxy server, the SSL requirement must be met on the load balancer/proxy server. Note: If the server is providing OCSP, and not otherwise hosting any content, this requirement is not applicable. Note: If the server is hosting Office Online Server (OOS), this is Not Applicable. Follow the procedures below for each site hosted on the IIS 10.0 web server: Access the IIS 10.0 Manager. Under the "Management" section, double-click the "Configuration Editor" icon. From the "Section:" drop-down list, select "system.web/httpCookies". Verify the "require SSL" is set to "True". From the "Section:" drop-down list, select "system.web/sessionState". Verify the "compressionEnabled" is set to "False". If both the "system.web/httpCookies:require SSL" is set to "True" and the "system.web/sessionState:compressionEnabled" is set to "False", this is not a finding.

V-218770 in V2R17

Check text

Note: If the IIS Application Pool is hosting Microsoft SharePoint, this is not applicable. Note: If the IIS 10.0 installation is supporting Microsoft Exchange and is not otherwise hosting any content, this requirement is not applicable. Note: If the server is hosting Office Online Server (OOS), this is Not Applicable. Open the IIS 10.0 Manager. Click "Application Pools". In the list of Application Pools, right-click any Application Pool, and select View Applications. Remove the filter using the prompt. Compare the Site and Application Pool columns. If any Application Pools are being used for more than one Site, this is a finding.

V-218771 in V2R17

Check text

Note: If the IIS Application Pool is hosting Microsoft SharePoint, this is Not Applicable. Note: If this server is hosting WSUS, this requirement is Not Applicable. Note: If this IIS 10.0 installation is supporting Microsoft Exchange, and not otherwise hosting any content, this requirement is Not Applicable. Note: If the server is hosting Office Online Server (OOS), this is Not Applicable. Open the IIS 10.0 Manager. Perform for each Application Pool. Click "Application Pools". Highlight an Application Pool and click "Advanced Settings" in the "Action" Pane. Scroll down to the "Recycling section" and verify the value for "Request Limit" is set to a value other than "0". If the "Request Limit" is set to a value of "0", this is a finding. If the system must require "Request Limit" to be set to "0", it is documented and approved by the ISSO, this is not a finding.

V-218772 in V2R17

Check text

Note: If the IIS Application Pool is hosting Microsoft SharePoint, this is Not Applicable. Note: If the IIS Application Pool is hosting Microsoft Exchange and not otherwise hosting any content, this is Not Applicable. Note: If this server is hosting WSUS, this requirement is Not Applicable. Note: If the server is hosting Office Online Server (OOS), this is Not Applicable. Open the IIS 10.0 Manager. Expand "Application Pools". Perform the following for each Application Pool: Highlight an Application Pool and click "Recycling" in the "Actions" pane. In the Recycling Conditions window, verify at least one condition is checked as desired by the organization (e.g., Regular Time Intervals, Scheduled Time). If no conditions are checked, this is a finding. Click "Next". In the Recycling Events to Log window, verify at minimum the Recycling Events are selected that correspond to the conditions defined in the previous step (e.g., Regular Time Intervals, Scheduled Time). If no events are selected, this is a finding. Click "Cancel".

V-218775 in V2R17

Check text

Note: If the IIS Application Pool is hosting Microsoft SharePoint, this is Not Applicable. Note: If this IIS 10.0 installation is supporting Microsoft Exchange, and not otherwise hosting any content, this requirement is Not Applicable. Note: If the server is hosting Office Online Server (OOS), this is Not Applicable. Open the IIS 10.0 Manager. Click "Application Pools". Perform the following for each Application Pool: Highlight an Application Pool to review and click "Advanced Settings" in the "Actions" pane. Scroll down to the "Rapid Fail Protection" section and verify the value for "Enabled" is set to "True". If the "Rapid Fail Protection:Enabled" is not set to "True", this is a finding.

V-218777 in V2R17

Check text

Note: If the IIS Application Pool is hosting Microsoft SharePoint, this is Not Applicable. Note: If the server is hosting Office Online Server (OOS), this is Not Applicable. If this IIS 10.0 installation is supporting Microsoft Exchange, and not otherwise hosting any content, this requirement is Not Applicable. Open the IIS 10.0 Manager. Click "Application Pools". Perform the following for each Application Pool: Highlight an Application Pool to review and click "Advanced Settings" in the "Actions" pane. Scroll down to the "Rapid Fail Protection" section and verify the value for "Failure Interval" is set to "5". If the "Failure Interval" is not set to "5" or less, this is a finding.

V-218778 in V2R17

Title

The required DoDW banner page must be displayed to authenticated users accessing a DoDW private website.

Check text

Note: This requirement is only applicable for private DODDoW websites. Note: If the server being reviewed is hosting WSUS, this is not applicable. If a banner is required, the following banner page must be in place: "You are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only. By using this IS (which includes any device attached to this IS), you consent to the following conditions: -The USG routinely intercepts and monitors communications on this IS for purposes including, but not limited to, penetration testing, COMSEC monitoring, network operations and defense, personnel misconduct (PM), law enforcement (LE), and counterintelligence (CI) investigations. - At any time, the USG may inspect and seize data stored on this IS. - Communications using, or data stored on, this IS are not private, are subject to routine monitoring, interception, and search, and may be disclosed or used for any USG-authorized purpose. - This IS includes security measures (e.g., authentication and access controls) to protect USG interests—not for your personal benefit or privacy. - Notwithstanding the above, using this IS does not constitute consent to PM, LE or CI investigative searching or monitoring of the content of privileged communications, or work product, related to personal representation or services by attorneys, psychotherapists, or clergy, and their assistants. Such communications and work product are private and confidential. See User Agreement for details." OR If your system cannot meet the character limits to store this amount of text in the banner, the following is another option for the warning banner: "I've read & consent to terms in IS user agreem't." NOTE: While DoDI 8500.01 does not contain a copy of the banner to be used, it does point to the RMF Knowledge Service for a copy of the required text. It is also noted that the banner is to be displayed only once when the individual enters the site and not for each page. If the access-controlled website does not display this banner page before entry, this is a finding.

Fix text

Configure a DoDW private website to display the required DoDW banner page when authentication is required for user access.

Discussion

A consent banner will be in place to inform prospective entrants the website they are about to enter is a DoDDoW website and their activity is subject to monitoring. The document, DoDI 8500.01, establishes the policy on the use of DoDDoW information systems. It requires the use of a standard Notice and Consent Banner and standard text to be included in user agreements. The requirement for the banner is for websites with security and access controls. These are restricted and not publicly accessible. If the website does not require authentication/authorization for use, then the banner does not need to be present. A manual check of the document root directory for a banner page file (such as banner.html) or navigation to the website via a browser can be used to confirm the information provided from interviewing the web staff.

V-218782 in V2R17

Check text

Note: If the server is hosting WSUS, this is not applicable. Open Registry Editor. Navigate to "HKLM1System1CurrentControlSet1Services1HTTP1Parameters". Verify "DisableServerHeader" is set to "1" or "2". If REG_DWORD DisableServerHeader is not set to "1" or "2", this is a finding. If the system administrator (SA) can show that Server Version information has been removed via other means, such as using a rewrite outbound rule, this is not a finding.

Fix text

Navigate to "HKLM1System1CurrentControlSet1Services1HTTP1Parameters". Create REG_DWORD "DisableServerHeader" and set it to "1" or "2". Note: This can be performed multiple ways; this is an example.

V-278953 in V2R17