| Hostname | IP Address | Status | Assigned To | Last Scan | Actions |
|---|---|---|---|---|---|
| SCHR-P3-DP-001 | 164.231.170.44 | 2026-03-12 | |||
Finding DetailsEvaluate-STIG 1.2601.0 (Scan-IIS10_0_Site_Checks) found this to be NOT A FINDING on 03/05/2026 Site: Default Web Site ResultHash: 4DAFD73A73E142C404EAA5FA34EAB3F3718A717C ~~~~~ Mode is set to 'InProc' Comments |
|||||
Check Text
Note: If ASP.NET is not installed, 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 the "ASP.NET" section, select "Session State". Under "Session State" Mode Settings, verify the "In Process" mode is selected. If the "In Process" mode is selected, this is not a finding. Alternative method: Click the site name. Select "Configuration Editor" under the "Management" section. From the "Section:" drop-down list at the top of the configuration editor, locate "system.web/sessionState". Verify the "mode" reflects "InProc". If the "mode" is not set to "InProc", this is a finding. If the system being reviewed is part of a Web Farm, interview the System Administrator to ensure Session State Tracking is enabled via a SQL server, or other means. If Session State Tracking is enabled on the Web Farm, this is not a finding.
Fix Text
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 the ASP.NET section, select "Session State". Under "Session State" Mode Settings, select the "In Process" mode.
| Hostname | IP Address | Status | Assigned To | Last Scan | Actions |
|---|---|---|---|---|---|
| SCHR-P3-DP-001 | 164.231.170.44 | 2026-03-12 | |||
Finding DetailsEvaluate-STIG 1.2601.0 (Scan-IIS10_0_Site_Checks) found this to be OPEN on 03/05/2026 Site: Default Web Site ResultHash: 82833DC68D5FCB33EF4976B85E80237A71D613C3 ~~~~~ Both the OS and the web site are installed on C: Comments |
|||||
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. 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.
Fix Text
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. Change the Physical Path to the new partition and directory location.
| Hostname | IP Address | Status | Assigned To | Last Scan | Actions |
|---|---|---|---|---|---|
| SCHR-P3-DP-001 | 164.231.170.44 | 2026-03-12 | |||
Finding DetailsEvaluate-STIG 1.2601.0 (Scan-IIS10_0_Site_Checks) found this to be NOT A FINDING on 03/05/2026 Site: Default Web Site ResultHash: F2EA50F0C244BFF62634234D1860279E15690490 ~~~~~ MaxURL is set to '4096' Comments |
|||||
Check Text
Follow the procedures below for each site hosted on the IIS 10.0 web server: Open the IIS 10.0 Manager. Click on the site name. Double-click the "Request Filtering" icon. Click "Edit Feature Settings" in the "Actions" pane. If the "maxUrl" value is not set to "4096" or less, this is a finding.
Fix Text
Follow the procedures below for each site hosted on the IIS 10.0 web server: Click the site name under review. Double-click the "Request Filtering" icon. Click "Edit Feature Settings" in the "Actions" pane. Set the "maxURL" value to "4096" or less.
| Hostname | IP Address | Status | Assigned To | Last Scan | Actions |
|---|---|---|---|---|---|
| SCHR-P3-DP-001 | 164.231.170.44 | 2026-03-12 | |||
Finding DetailsEvaluate-STIG 1.2601.0 (Scan-IIS10_0_Site_Checks) found this to be NOT A FINDING on 03/05/2026 Site: Default Web Site ResultHash: 61B975D8C5C29BE38FE820498269486B83933521 ~~~~~ MaxAllowedContentLength is set to '30000000' Comments |
|||||
Check Text
Follow the procedures below for each site hosted on the IIS 10.0 web server: Open the IIS 10.0 Manager. Click on the site name. Double-click the "Request Filtering" icon. Click "Edit Feature Settings" in the "Actions" pane. If the "maxAllowedContentLength" value is not explicitly set to "2147483647" or less or a length documented and approved by the ISSO, this is a finding.
Fix Text
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 the "Request Filtering" icon. Click "Edit Feature Settings" in the "Actions" pane. Set the "maxAllowedContentLength" value to "2147483647" or less.
| Hostname | IP Address | Status | Assigned To | Last Scan | Actions |
|---|---|---|---|---|---|
| SCHR-P3-DP-001 | 164.231.170.44 | 2026-03-12 | |||
Finding DetailsEvaluate-STIG 1.2601.0 (Scan-IIS10_0_Site_Checks) found this to be NOT A FINDING on 03/05/2026 Site: Default Web Site ResultHash: 0B0E1D157A012760B8EF8577018C2CE9536125C3 ~~~~~ MaxQueryString is set to '2048' Comments |
|||||
Check Text
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 "Maximum Query String" value is not set to "2048" or less, this is a finding.
Fix Text
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 the "Request Filtering" icon. Click "Edit Feature Settings" in the "Actions" pane. Set the "Maximum Query String" value to "2048" or less.
| Hostname | IP Address | Status | Assigned To | Last Scan | Actions |
|---|---|---|---|---|---|
| SCHR-P3-DP-001 | 164.231.170.44 | 2026-03-12 | |||
Finding DetailsEvaluate-STIG 1.2601.0 (Scan-IIS10_0_Site_Checks) found this to be OPEN on 03/05/2026 Site: Default Web Site ResultHash: 545E96FB53E421DBB94A039FB5D6FBC26514D6A0 ~~~~~ AllowHighBitCharacters is Enabled Comments |
|||||
Check Text
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 high-bit characters" 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.
Fix Text
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 the "Request Filtering" icon. Click "Edit Feature Settings" in the "Actions" pane. Uncheck the "Allow high-bit characters" check box.
| Hostname | IP Address | Status | Assigned To | Last Scan | Actions |
|---|---|---|---|---|---|
| SCHR-P3-DP-001 | 164.231.170.44 | 2026-03-12 | |||
Finding DetailsEvaluate-STIG 1.2601.0 (Scan-IIS10_0_Site_Checks) found this to be NOT A FINDING on 03/05/2026 Site: Default Web Site ResultHash: ABDEB31F62077F38682F3B6A94057B49A3CFDE3A ~~~~~ AllowDoubleEscaping is Disabled Comments |
|||||
Check Text
Note: If the server being reviewed is hosting SharePoint, 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.
Fix Text
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 the "Request Filtering" icon. Click "Edit Feature Settings" in the "Actions" pane. Uncheck the "Allow double escaping" check box.
| Hostname | IP Address | Status | Assigned To | Last Scan | Actions |
|---|---|---|---|---|---|
| SCHR-P3-DP-001 | 164.231.170.44 | 2026-03-12 | |||
Finding DetailsEvaluate-STIG 1.2601.0 (Scan-IIS10_0_Site_Checks) found this to be OPEN on 03/05/2026 Site: Default Web Site ResultHash: B5726175B8459E9B878193D0B97D55FA98562ED9 ~~~~~ AllowUnlisted is Enabled Comments |
|||||
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. 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.
Fix Text
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 the "Request Filtering" icon. Click "Edit Feature Settings" in the "Actions" pane. Uncheck the "Allow unlisted file extensions" check box.
| Hostname | IP Address | Status | Assigned To | Last Scan | Actions |
|---|---|---|---|---|---|
| SCHR-P3-DP-001 | 164.231.170.44 | 2026-03-12 | |||
Finding DetailsEvaluate-STIG 1.2601.0 (Scan-IIS10_0_Site_Checks) found this to be NOT A FINDING on 03/05/2026 Site: Default Web Site ResultHash: 0F0103BE5E8235FF5226B744537FC12082EF2285 ~~~~~ Directory Browsing is Disabled Comments |
|||||
Check Text
Follow the procedures below for each site hosted on the IIS 10.0 web server: Click the Site. Double-click the "Directory Browsing" icon. If "Directory Browsing" is not installed, this is Not Applicable. Under the "Actions" pane, verify "Directory Browsing" is "Disabled". If "Directory Browsing" is not "Disabled", this is a finding.
Fix Text
Follow the procedures below for each site hosted on the IIS 10.0 web server: Open the IIS 10.0 Manager. Click the Site. Double-click the "Directory Browsing" icon. Under the "Actions" pane, click "Disabled".
| Hostname | IP Address | Status | Assigned To | Last Scan | Actions |
|---|---|---|---|---|---|
| SCHR-P3-DP-001 | 164.231.170.44 | 2026-03-12 | |||
Finding DetailsEvaluate-STIG 1.2601.0 (Scan-IIS10_0_Site_Checks) found this to be NOT A FINDING on 03/05/2026 Site: Default Web Site ResultHash: 8DD7CFE973D10647A1435F5B797FDBD4463D27D1 ~~~~~ Error Responses is configured to 'Detailed errors for local requests and custom error pages for remote requests' errorMode: DetailedLocalOnly Comments |
|||||
Check Text
Note: If this server is hosting WSUS, 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. Double-click the "Error Pages" icon. Click each error message and click "Edit Feature" setting from the "Actions" pane. If any error message is not set to "Detailed errors for local requests and custom error pages for remote requests" or "Custom error pages", this is a finding.
Fix Text
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 the "Error Pages" icon. Click each error message and click "Edit Feature" Setting from the "Actions" pane; set each error message to "Detailed errors for local requests and custom error pages for remote requests" or "Custom error pages".
| Hostname | IP Address | Status | Assigned To | Last Scan | Actions |
|---|---|---|---|---|---|
| SCHR-P3-DP-001 | 164.231.170.44 | 2026-03-12 | |||
Finding DetailsEvaluate-STIG 1.2601.0 (Scan-IIS10_0_Site_Checks) found this to be NOT A FINDING on 03/05/2026 Site: Default Web Site ResultHash: DA86857153490799139F10F11554C3FC6F2FE873 ~~~~~ Debug is set to 'False' Comments |
|||||
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. 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.
Fix Text
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 set the value for "Debug" to "False".
| Hostname | IP Address | Status | Assigned To | Last Scan | Actions |
|---|---|---|---|---|---|
| SCHR-P3-DP-001 | 164.231.170.44 | 2026-03-12 | |||
Finding DetailsEvaluate-STIG 1.2601.0 (Scan-IIS10_0_Site_Checks) found this to be NOT A FINDING on 03/05/2026 Site: Default Web Site ResultHash: 014F652F7321865AAC624F62B49DF31D1BF1CA97 ~~~~~ Idle Time-out is configured to '20' total minutes Comments |
|||||
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. 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.
Fix Text
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 set the value for "Idle Time-out" to something other than "0". "20" or less is recommended if the amount of RAM on the system is limited.
| Hostname | IP Address | Status | Assigned To | Last Scan | Actions |
|---|---|---|---|---|---|
| SCHR-P3-DP-001 | 164.231.170.44 | 2026-03-12 | |||
Finding DetailsEvaluate-STIG 1.2601.0 (Scan-IIS10_0_Site_Checks) found this to be NOT A FINDING on 03/05/2026 Site: Default Web Site ResultHash: CC80929894FE26706CBF815CB07276E9E7A98AC3 ~~~~~ Time-out is configured to '00:15:00' Comments |
|||||
Check Text
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. Select "Configuration Editor" under the "Management" section. From the "Section:" drop-down list at the top of the configuration editor, locate "system.web/sessionState". Verify the "timeout" is set to "00:15:00 or less”. If "timeout" is not set to "00:15:00 or less”, this is a finding.
Fix Text
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. Select "Configuration Editor" under the "Management" section. From the "Section:" drop-down list at the top of the configuration editor, locate "system.web/sessionState". Set the "timeout" to "00:15:00 or less”. In the "Actions" pane, click "Apply".
| Hostname | IP Address | Status | Assigned To | Last Scan | Actions |
|---|---|---|---|---|---|
| SCHR-P3-DP-001 | 164.231.170.44 | 2026-03-12 | |||
Finding DetailsEvaluate-STIG 1.2601.0 (Scan-IIS10_0_Site_Checks) found this to be NOT A FINDING on 03/05/2026 Site: Default Web Site ResultHash: 32AFF8CF36570A0DC084CA270EE023B4DED1D486 ~~~~~ There is nothing preventing an administrator from shutting down either the webservice or an individual IIS site in the event of an attack. Documentation exists describing how. Comments |
|||||
Check Text
Interview the System Administrator and Web Manager. Ask for documentation for the IIS 10.0 web server administration. Verify there are documented procedures for shutting down an IIS 10.0 website in the event of an attack. The procedure should, at a minimum, provide the following steps: Determine the respective website for the application at risk of an attack. Access the IIS 10.0 web server IIS 10.0 Manager. Select the respective website. In the "Actions" pane, under "Manage Website", click "Stop". If necessary, stop all websites. If necessary, stop the IIS 10.0 web server by selecting the web server in the IIS 10.0 Manager. In the "Actions" pane, under "Manage Server", click "Stop". If there are not documented procedures with, at a minimum, the mentioned steps for stopping a website, this is a finding.
Fix Text
Prepare documented procedures for shutting down an IIS 10.0 website in the event of an attack. The procedure should, at a minimum, provide the following steps: Determine the respective website for the application at risk of an attack. Access the IIS 10.0 web server IIS 10.0 Manager. Select the respective website. In the "Actions" pane, under "Manage Website", click "Stop". If necessary, stop all websites. If necessary, stop the IIS 10.0 web server by selecting the web server in the IIS 10.0 Manager. In the "Actions" pane, under "Manage Server", click "Stop".
| Hostname | IP Address | Status | Assigned To | Last Scan | Actions |
|---|---|---|---|---|---|
| SCHR-P3-DP-001 | 164.231.170.44 | 2026-03-12 | |||
Finding DetailsEvaluate-STIG 1.2601.0 (Scan-IIS10_0_Site_Checks) found this to be NOT A FINDING on 03/05/2026 Site: Default Web Site ResultHash: 6ADE9501D86E927416808AF0B186536D51A249DE ~~~~~ Logs are set to roll over Daily. Comments |
|||||
Check Text
Follow the procedures below for each site hosted on the IIS 10.0 web server: Access the IIS 10.0 web server IIS 10.0 Manager. Under "IIS" double-click on the "Logging" icon. In the "Logging" configuration box, determine the "Directory:" to which the "W3C" logging is being written. Confirm with the System Administrator that the designated log path is of sufficient size to maintain the logging. Under "Log File Rollover", verify "Do not create new log files" is not selected. Verify a schedule is configured to rollover log files on a regular basis. Consult with the System Administrator to determine if there is a documented process for moving the log files off of the IIS 10.0 web server to another logging device. If the designated logging path device is not of sufficient space to maintain all log files and there is not a schedule to rollover files on a regular basis, this is a finding.
Fix Text
Follow the procedures below for each site hosted on the IIS 10.0 web server: Under "IIS" double-click on the "Logging" icon. If necessary, in the "Logging" configuration box, redesignate a log path to a location able to house the logs. Under "Log File Rollover", deselect the "Do not create new log files" setting. Configure a schedule to rollover log files on a regular basis.
| Hostname | IP Address | Status | Assigned To | Last Scan | Actions |
|---|---|---|---|---|---|
| SCHR-P3-DP-001 | 164.231.170.44 | 2026-03-12 | |||
Finding DetailsEvaluate-STIG 1.2601.0 (Scan-IIS10_0_Site_Checks) found this to be NOT A FINDING on 03/05/2026 Site: Default Web Site ResultHash: D43BD30938BEE28D70E09D5B397315762DD4C2D3 ~~~~~ All ports are PPSM approved. Below are the current HTTP and HTTPS bindings: http (*:80:) Comments |
|||||
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 DOD 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.
Fix Text
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". Edit to change an existing binding and set the correct ports and protocol.
| Hostname | IP Address | Status | Assigned To | Last Scan | Actions |
|---|---|---|---|---|---|
| SCHR-P3-DP-001 | 164.231.170.44 | 2026-03-12 | |||
Finding DetailsEvaluate-STIG 1.2601.0 (Scan-IIS10_0_Site_Checks) found this to be OPEN on 03/05/2026 Site: Default Web Site ResultHash: 7B47C3FC645686A5BBF0E23296FB14E0C58713A2 ~~~~~ There are no HTTPS bindings on this site. Comments |
|||||
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 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 Text
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".
| Hostname | IP Address | Status | Assigned To | Last Scan | Actions |
|---|---|---|---|---|---|
| SCHR-P3-DP-001 | 164.231.170.44 | 2026-03-12 | |||
Finding DetailsEvaluate-STIG 1.2601.0 (Scan-IIS10_0_Site_Checks) found this to be NOT A FINDING on 03/05/2026 Site: Default Web Site ResultHash: 88428619BE4167554B71D4EBAEE30C7BD51B4A99 ~~~~~ KeepSessionIdSecure is set to 'True' Comments |
|||||
Check Text
Follow the procedures below for each site hosted on the IIS 10.0 web server: Access the IIS 10.0 Manager. Select the website being reviewed. Under "Management" section, double-click the "Configuration Editor" icon. From the "Section:" drop-down list, select "system.webServer/asp". Expand the "session" section. Verify the "keepSessionIdSecure" is set to "True". If the "keepSessionIdSecure" is not set to "True", this is a finding.
Fix Text
Follow the procedures below for each site hosted on the IIS 10.0 web server: Access the IIS 10.0 Manager. Select the website being reviewed. Under "Management" section, double-click the "Configuration Editor" icon. From the "Section:" drop-down list, select "system.webServer/asp". Expand the "session" section. Select "True" for the "keepSessionIdSecure" setting. Select "Apply" from the "Actions" pane.
| Hostname | IP Address | Status | Assigned To | Last Scan | Actions |
|---|---|---|---|---|---|
| SCHR-P3-DP-001 | 164.231.170.44 | 2026-03-12 | |||
Finding DetailsEvaluate-STIG 1.2601.0 (Scan-IIS10_0_Site_Checks) found this to be OPEN on 03/05/2026 Site: Default Web Site ResultHash: FE11E6C510BB860B5F598EF635D52AFCEA9CEE15 ~~~~~ RequireSSL is set to 'False' CompressionEnabled is set to 'False' Comments |
|||||
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. 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.
Fix Text
Follow the procedures below for each site hosted on the IIS 10.0 web server: Access the IIS 10.0 Manager. Under "Management" section, double-click the "Configuration Editor" icon. From the "Section:" drop-down list, select "system.web/httpCookies". Set the "require SSL" to "True". From the "Section:" drop-down list, select "system.web/sessionState". Set the "compressionEnabled" to "False". Select "Apply" from the "Actions" pane.
| Hostname | IP Address | Status | Assigned To | Last Scan | Actions |
|---|---|---|---|---|---|
| SCHR-P3-DP-001 | 164.231.170.44 | 2026-03-12 | |||
Finding DetailsEvaluate-STIG 1.2601.0 (Scan-IIS10_0_Site_Checks) found this to be NOT A FINDING on 03/05/2026 Site: Default Web Site ResultHash: 5335ED9BAD61DF8DC37184AF69529D1843D12936 ~~~~~ ApplicationPool: DefaultAppPool WebSiteUsage: Default Web Site Comments |
|||||
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. 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.
Fix Text
Open the IIS 10.0 Manager. Click the site name under review. Assign a unique application pool to each website.
| Hostname | IP Address | Status | Assigned To | Last Scan | Actions |
|---|---|---|---|---|---|
| SCHR-P3-DP-001 | 164.231.170.44 | 2026-03-12 | |||
Finding DetailsEvaluate-STIG 1.2601.0 (Scan-IIS10_0_Site_Checks) was unable to determine a Status but found the below configuration on 03/05/2026: Site: Default Web Site ResultHash: A56676E8EA3BFCF08B73F6A5B5A76450CBBE9579 ~~~~~ Application Pool: .NET v4.5 Request Limit: 0 Application Pool: .NET v4.5 Classic Request Limit: 0 Application Pool: DefaultAppPool Request Limit: 0 Comments |
|||||
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. 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.
Fix Text
Open the IIS 10.0 Manager. Click "Application Pools". Highlight an Application Pool and click "Advanced Settings" in the "Action" Pane. Scroll down to the "Recycling section" and set the value for "Request Limit" to greater than "0". Click "OK".
| Hostname | IP Address | Status | Assigned To | Last Scan | Actions |
|---|---|---|---|---|---|
| SCHR-P3-DP-001 | 164.231.170.44 | 2026-03-12 | |||
Finding DetailsEvaluate-STIG 1.2601.0 (Scan-IIS10_0_Site_Checks) found this to be NOT A FINDING on 03/05/2026 Site: Default Web Site ResultHash: 630A16ADFDB7CF1BE1A54B6AD5648CC5D3357FBA ~~~~~ Compliant AppPools: ----------------------------------- AppPool: .NET v4.5 Condition: time [Enabled=True; LogEnabled=True] AppPool: .NET v4.5 Classic Condition: time [Enabled=True; LogEnabled=True] AppPool: DefaultAppPool Condition: time [Enabled=True; LogEnabled=True] Comments |
|||||
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. 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".
Fix Text
Open the IIS 10.0 Manager. Click the "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, select at least one means to recycle the Application Pool (e.g., Regular Time Intervals, Scheduled Time). Click "Next". In the Recycling Events to Log window, select at minimum both the events that match the conditions from the previous step (e.g., Regular Time Intervals, Scheduled Time). Click "Finish".
| Hostname | IP Address | Status | Assigned To | Last Scan | Actions |
|---|---|---|---|---|---|
| SCHR-P3-DP-001 | 164.231.170.44 | 2026-03-12 | |||
Finding DetailsEvaluate-STIG 1.2601.0 (Scan-IIS10_0_Site_Checks) found this to be NOT A FINDING on 03/05/2026 Site: Default Web Site ResultHash: D20E64BF1B05FA68EEE046BE06AB34AE4CE8C3AF ~~~~~ Application Pool: .NET v4.5 Rapid Fail Protection: True Application Pool: .NET v4.5 Classic Rapid Fail Protection: True Application Pool: DefaultAppPool Rapid Fail Protection: True Comments |
|||||
Check Text
Note: If the IIS Application Pool is hosting Microsoft SharePoint, 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 "Enabled" is set to "True". If the "Rapid Fail Protection:Enabled" is not set to "True", this is a finding.
Fix Text
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 set the value for "Enabled" to "True". Click "OK".
| Hostname | IP Address | Status | Assigned To | Last Scan | Actions |
|---|---|---|---|---|---|
| SCHR-P3-DP-001 | 164.231.170.44 | 2026-03-12 | |||
Finding DetailsEvaluate-STIG 1.2601.0 (Scan-IIS10_0_Site_Checks) found this to be NOT A FINDING on 03/05/2026 Site: Default Web Site ResultHash: B30004B860C1C6BA9D64F62621C3F9D9CB69C162 ~~~~~ Application Pool: .NET v4.5 Failure Interval: 5 Application Pool: .NET v4.5 Classic Failure Interval: 5 Application Pool: DefaultAppPool Failure Interval: 5 Comments |
|||||
Check Text
Note: If the IIS Application Pool is hosting Microsoft SharePoint, 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.
Fix Text
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 set the value for "Failure Interval" to "5" or less. Click "OK".
| Hostname | IP Address | Status | Assigned To | Last Scan | Actions |
|---|---|---|---|---|---|
| SCHR-P3-DP-001 | 164.231.170.44 | 2026-03-12 | |||
Finding DetailsEvaluate-STIG 1.2601.0 (Scan-IIS10_0_Site_Checks) found this to be NOT APPLICABLE on 03/05/2026 Site: Default Web Site ResultHash: 6A077B4054A7B71BCF2A558FC6BFD199ED9070AA ~~~~~ CGI is not installed so this requirement is NA. Comments |
|||||
Check Text
Determine whether scripts are used on the web server for the target website. Common file extensions include, but are not limited to: .cgi, .pl, .vbs, .class, .c, .php, and .asp. All interactive programs must be placed in unique designated folders based on CGI or ASP script type. For modular and/or third-party applications, it is permissible to have script files in multiple folders. Open the IIS 10.0 Manager. Right-click the IIS 10.0 web site name and select "Explore". Search for the listed script extensions. Each script type must be in its unique designated folder. If scripts are not segregated from web content and in their own unique folders, this is a finding. If the website does not utilize CGI, this finding is Not Applicable.
Fix Text
All interactive programs must be placed in unique designated folders based on CGI or ASP script type. Open the IIS 10.0 Manager. Right-click the IIS 10.0 web server name and select "Explore". Search for the listed script extensions. Move each script type to its unique designated folder. Set the permissions to the scripts folders as follows: Administrators: FULL TrustedInstaller: FULL SYSTEM: FULL ApplicationPoolId:READ Custom Service Account: READ Users: READ ALL APPLICATION PACKAGES: READ
| Hostname | IP Address | Status | Assigned To | Last Scan | Actions |
|---|---|---|---|---|---|
| SCHR-P3-DP-001 | 164.231.170.44 | 2026-03-12 | |||
Finding DetailsEvaluate-STIG 1.2601.0 (Scan-IIS10_0_Site_Checks) found this to be NOT APPLICABLE on 03/05/2026 Site: Default Web Site ResultHash: 6A077B4054A7B71BCF2A558FC6BFD199ED9070AA ~~~~~ CGI is not installed so this requirement is NA. Comments |
|||||
Check Text
Determine whether scripts are used on the web server for the subject website. Common file extensions include, but are not limited to: .cgi, .pl, .vb, .class, .c, .php, and .asp. If the website does not utilize CGI, this finding is Not Applicable. All interactive programs must have restrictive permissions. Open the IIS 10.0 Manager. Right-click the IIS 10.0 web site name and select "Explore". Search for the listed script extensions. Review the permissions to the CGI scripts and verify only the permissions listed, or more restrictive permissions are assigned. Administrators: FULL Web Administrators: FULL TrustedInstaller: FULL ALL APPLICATION PACKAGES: Read ALL RESTRICTED APPLICATION PACKAGES: Read SYSTEM: FULL ApplicationPoolId: READ Custom Service Account: READ Users: READ If the permissions are less restrictive than listed above, this is a finding.
Fix Text
Determine whether scripts are used on the web server for the subject website. Common file extensions include, but are not limited to: .cgi, .pl, .vb, .class, .c, .php, and .asp. If the website does not utilize CGI, this finding is NA. All interactive programs must have restrictive permissions. Open the IIS 10.0 Manager. Right-click the IIS 10.0 web server name and select "Explore". Search for the listed script extensions. Set the permissions to the CGI scripts as follows: Administrators: FULL Web Administrators: FULL TrustedInstaller: FULL ALL APPLICATION PACKAGES: Read ALL RESTRICTED APPLICATION PACKAGES: Read SYSTEM: FULL ApplicationPoolId: READ Custom Service Account: READ Users: READ
| Hostname | IP Address | Status | Assigned To | Last Scan | Actions |
|---|---|---|---|---|---|
| SCHR-P3-DP-001 | 164.231.170.44 | 2026-03-12 | |||
Finding DetailsEvaluate-STIG 1.2601.0 (Scan-IIS10_0_Site_Checks) found this to be NOT APPLICABLE on 03/05/2026 Site: Default Web Site ResultHash: 6A077B4054A7B71BCF2A558FC6BFD199ED9070AA ~~~~~ CGI is not installed so this requirement is NA. Comments |
|||||
Check Text
If the website does not utilize CGI, this finding is Not Applicable. Open the IIS 10.0 Manager. Right-click the IIS 10.0 web site name and select "Explore". Search for the listed script extensions Search for the following files: *.bak, *.old, *.temp, *.tmp, *.backup, or “copy of...”. If files with these extensions are found, this is a finding.
Fix Text
Remove the backup files from the production web server.
| Hostname | IP Address | Status | Assigned To | Last Scan | Actions |
|---|---|---|---|---|---|
| SCHR-P3-DP-001 | 164.231.170.44 | 2026-03-12 | |||
Finding DetailsNo details recorded. Comments |
|||||
Check Text
Note: This requirement is only applicable for private DOD 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 DoD private website to display the required DoD banner page when authentication is required for user access.
| Hostname | IP Address | Status | Assigned To | Last Scan | Actions |
|---|---|---|---|---|---|
| SCHR-P3-DP-001 | 164.231.170.44 | 2026-03-12 | |||
Finding DetailsEvaluate-STIG 1.2601.0 (Scan-IIS10_0_Server_Checks) found this to be OPEN on 03/05/2026 ResultHash: 6A6094447CB8DE66FC6303CBDD8749BE276169CF ~~~~~ File is the only option selected. Comments |
|||||
Check Text
Note: If the server is hosting WSUS, this is Not Applicable. Open the IIS 10.0 Manager. Click the IIS 10.0 server name. Click the "Logging" icon. Under Log Event Destination, verify the "Both log file and ETW event" radio button is selected. If the "Both log file and ETW event" radio button is not selected, this is a finding.
Fix Text
Open the IIS 10.0 Manager. Click the IIS 10.0 server name. Click the "Logging" icon. Under Log Event Destination, select the "Both log file and ETW event" radio button. Under the "Actions" pane, click "Apply".
| Hostname | IP Address | Status | Assigned To | Last Scan | Actions |
|---|---|---|---|---|---|
| SCHR-P3-DP-001 | 164.231.170.44 | 2026-03-12 | |||
Finding DetailsEvaluate-STIG 1.2601.0 (Scan-IIS10_0_Server_Checks) found this to be OPEN on 03/05/2026 ResultHash: 7599E6F84AF0FE02631E378C3BDEFF3AC6CE19D6 ~~~~~ Log format is 'W3C' The 'Request Header >> Connection' custom field is NOT configured. The 'Request Header >> Warning' custom field is NOT configured. Comments |
|||||
Check Text
Note: If the server is hosting WSUS, this is Not Applicable. Access the IIS 10.0 web server IIS Manager. Click the IIS 10.0 web server name. Under "IIS", double-click the "Logging" icon. Verify the "Format:" under "Log File" is configured to "W3C". Select "Fields". Under "Custom Fields", verify the following fields have been configured: Request Header >> Connection. Request Header >> Warning. If any of the above fields are not selected, this is a finding.
Fix Text
Access the IIS 10.0 web server IIS Manager. Click the IIS 10.0 web server name. Under "IIS", double-click the "Logging" icon. Verify the "Format:" under "Log File" is configured to "W3C". Select "Fields". Under "Custom Fields", click "Add Field...". For each field being added, give a name unique to what the field is capturing. Click on the "Source Type" drop-down list and select "Request Header". Click the "Source" drop-down list, and select "Connection". Click "OK" to add. Click the "Source Type" drop-down list, and select "Request Header". Click the "Source" drop-down list, and select "Warning". Click "OK" to add. Click "Apply" under the "Actions" pane.
| Hostname | IP Address | Status | Assigned To | Last Scan | Actions |
|---|---|---|---|---|---|
| SCHR-P3-DP-001 | 164.231.170.44 | 2026-03-12 | |||
Finding DetailsEvaluate-STIG 1.2601.0 (Scan-IIS10_0_Server_Checks) found this to be OPEN on 03/05/2026 ResultHash: C3C26BB04CA1EEAB0A14FFB0A603274C530242F3 ~~~~~ Log format is 'W3C' User Agent, User Name, and Referrer are all logged. The 'Request Header >> Authorization' custom field is NOT configured. The 'Response Header >> Content-Type' custom field is NOT configured. Comments |
|||||
Check Text
Note: If the server is hosting WSUS, this is Not Applicable. Access the IIS 10.0 web server IIS Manager. Click the IIS 10.0 web server name. Under "IIS", double-click the "Logging" icon. Verify the "Format:" under "Log File" is configured to "W3C". Select "Fields". Under "Standard Fields", verify "User Agent", "User Name", and "Referrer" are selected. Under "Custom Fields", verify the following field has been configured: Request Header >> Authorization. Response Header >> Content-Type. If any of the above fields are not selected, this is a finding.
Fix Text
Access the IIS 10.0 web server IIS Manager. Click the IIS 10.0 web server name. Under "IIS", double-click the "Logging" icon. Verify the "Format:" under "Log File" is configured to "W3C". Select "Fields". Under "Standard Fields", select "User Agent", "User Name", and "Referrer". Under "Custom Fields", select the following fields: Click the "Source Type" drop-down list, and select "Request Header". Click on "Source" drop-down, list and select "Authorization". Click "OK" to add. Click the "Source" drop-down list, and select "Content-Type". Click the "Source Type" drop-down list, and select "Response Header". Click "OK" to add. Click "OK". Click "Apply" under the "Actions" pane.
| Hostname | IP Address | Status | Assigned To | Last Scan | Actions |
|---|---|---|---|---|---|
| SCHR-P3-DP-001 | 164.231.170.44 | 2026-03-12 | |||
Finding DetailsEvaluate-STIG 1.2601.0 (Scan-IIS10_0_Server_Checks) was unable to determine a Status but found the below configuration on 03/05/2026: ResultHash: 47C2704EC787A78914769229C4FEA868D5EB6FA8 ~~~~~ Path: C:\inetpub\logs\LogFiles OverallState: Less restrictive than Expected [finding] Compliance: Not Compliant Unexpected rules... --------------------- State: LessRestrictive Compliant: False Identity: CREATOR OWNER Type: Allow Basic: FullControl Expected: N/A Advanced: AppendData, ChangePermissions, CreateDirectories, CreateFiles, Delete, DeleteSubdirectoriesAndFiles, ExecuteFile, ListDirectory, ReadAttributes, ReadData, ReadExtendedAttributes, ReadPermissions, TakeOwnership, Traverse, WriteAttributes, WriteData, WriteExtendedAttributes Expected: Inherited: C:\inetpub\logs AppliesTo: Subfolders, Files Summary: Unexpected Rule: A rule with rights 'FullControl' was found on the system but was not defined in the expectation. State: LessRestrictive Compliant: False Identity: NT SERVICE\TrustedInstaller Type: Allow Basic: FullControl Expected: N/A Advanced: AppendData, ChangePermissions, CreateDirectories, CreateFiles, Delete, DeleteSubdirectoriesAndFiles, ExecuteFile, ListDirectory, ReadAttributes, ReadData, ReadExtendedAttributes, ReadPermissions, TakeOwnership, Traverse, WriteAttributes, WriteData, WriteExtendedAttributes Expected: Inherited: C:\inetpub\logs AppliesTo: This, Subfolders, Files Summary: Unexpected Rule: A rule with rights 'FullControl' was found on the system but was not defined in the expectation. --------------------- Comments |
|||||
Check Text
This check does not apply to service account IDs utilized by automated services necessary to process, manage, and store log files. Open the IIS 10.0 Manager. Click the IIS 10.0 web server name. Click the "Logging" icon. Click "Browse" and navigate to the directory where the log files are stored. Right-click the log file directory to review. Click "Properties". Click the "Security" tab. Verify log file access is restricted as follows. Otherwise, this is a finding. SYSTEM - Full Control, This folder, subfolders and files Administrators - Full Control, This folder, subfolders and files Note: A "Web Administrators", etc., type group that is an approved group of administrators is also allowed, and must be given "Full Control, This folder, subfolders and files" permissions.
Fix Text
Open the IIS 10.0 Manager. Click the IIS 10.0 web server name. Click the "Logging" icon. Click "Browse" and navigate to the directory where the log files are stored. Right-click the log file directory to review and click "Properties". Click the "Security" tab. Set the log file permissions for the appropriate group(s). Click "OK". Select "Apply" in the "Actions" pane.
| Hostname | IP Address | Status | Assigned To | Last Scan | Actions |
|---|---|---|---|---|---|
| SCHR-P3-DP-001 | 164.231.170.44 | 2026-03-12 | |||
Finding DetailsEvaluate-STIG 1.2601.0 (Scan-IIS10_0_Server_Checks) was unable to determine a Status but found the below configuration on 03/05/2026: ResultHash: 74E69E807F3DCC8CA324A8C5947BC62D9FE1A815 ~~~~~ Log Directory: %SystemDrive%\inetpub\logs\LogFiles Ensure the logs in the directory above are being backed up. Comments |
|||||
Check Text
The IIS 10.0 web server and website log files should be backed up by the system backup. To determine if log files are backed up by the system backup, determine the location of the web server log files and each website's log files. Open the IIS 10.0 Manager. Click the IIS 10.0 server name. Click the "Logging" icon. Under "Log File" >> "Directory" obtain the path of the log file. Once all locations are known, consult with the System Administrator to review the server's backup procedure and policy. Verify the paths of all log files are part of the system backup. Verify log files are backed up to an unrelated system or onto separate media on which the system the web server is running. If the paths of all log files are not part of the system backup and/or not backed up to a separate media, this is a finding.
Fix Text
Configure system backups to include the directory paths of all IIS 10.0 web server and website log files.
| Hostname | IP Address | Status | Assigned To | Last Scan | Actions |
|---|---|---|---|---|---|
| SCHR-P3-DP-001 | 164.231.170.44 | 2026-03-12 | |||
Finding DetailsNo details recorded. Comments |
|||||
Check Text
Interview the System Administrator about the role of the IIS 10.0 web server. If the IIS 10.0 web server is hosting an application, have the SA provide supporting documentation on how the application's user management is accomplished outside of the IIS 10.0 web server. If the IIS 10.0 web server is not hosting an application, this is Not Applicable. If the IIS web server is performing user management for hosted applications, this is a finding. If the IIS 10.0 web server is hosting an application and the SA cannot provide supporting documentation on how the application's user management is accomplished outside of the IIS 10.0 web server, this is a finding.
Fix Text
Reconfigure any hosted applications on the IIS 10.0 web server to perform user management outside the IIS 10.0 web server. Document how the hosted application user management is accomplished.
| Hostname | IP Address | Status | Assigned To | Last Scan | Actions |
|---|---|---|---|---|---|
| SCHR-P3-DP-001 | 164.231.170.44 | 2026-03-12 | |||
Finding DetailsEvaluate-STIG 1.2601.0 (Scan-IIS10_0_Server_Checks) was unable to determine a Status but found the below configuration on 03/05/2026: ResultHash: 909864146B7EF18AC7E6CCAEB573BFB88320271A ~~~~~ Software installed on this system: ActivID ActivClient x64 Axway Desktop Validator CRLAutoCache DoD Secure Host Baseline Server InstallRoot Microsoft Edge Microsoft NetBanner Microsoft Visual C++ 2015-2022 Redistributable (x64) - 14.38.33130 Microsoft Visual C++ 2015-2022 Redistributable (x86) - 14.38.33130 STIG Viewer 3 (Machine) Veritas Backup Exec Remote Agent for Windows WinZip 23.0 Comments |
|||||
Check Text
Click “Start”. Open Control Panel. Click “Programs”. Click “Programs and Features”. Review the installed programs. If any programs are installed other than those required for the IIS 10.0 web services, this is a finding. Note: If additional software is needed, supporting documentation must be signed by the ISSO.
Fix Text
Remove all unapproved programs and roles from the production IIS 10.0 web server.
| Hostname | IP Address | Status | Assigned To | Last Scan | Actions |
|---|---|---|---|---|---|
| SCHR-P3-DP-001 | 164.231.170.44 | 2026-03-12 | |||
Finding DetailsEvaluate-STIG 1.2601.0 (Scan-IIS10_0_Server_Checks) found this to be NOT A FINDING on 03/05/2026 ResultHash: 5ACA563509DF0C703A464BA6BDCBE01BACEB7FD1 ~~~~~ Application Request Routing Cache is not installed. Comments |
|||||
Check Text
Open the IIS 10.0 Manager. Under the "Connections" pane on the left side of the management console, select the IIS 10.0 web server. If, under the IIS installed features "Application Request Routing Cache" is not present, this is not a finding. If, under the IIS installed features "Application Request Routing Cache" is present, double-click the icon to open the feature. From the right "Actions" pane under "Proxy", select "Server Proxy Settings...". In the "Application Request Routing" settings window, verify whether "Enable proxy" is selected. If "Enable proxy" is selected under the "Application Request Routing" settings, this is a finding. If the server has been approved to be a Proxy server, this requirement is Not Applicable.
Fix Text
Open the IIS 10.0 Manager. Under the "Connections" pane on the left side of the management console, select the IIS 10.0 web server. Under the IIS installed features, if "Application Request Routing Cache" is present, double-click the icon to open the feature. From the right "Actions" pane, under "Proxy", select "Server Proxy Settings...". In the "Application Request Routing" settings window, remove the check from the "Enable proxy" check box. Click "Apply" in the "Actions" pane.
| Hostname | IP Address | Status | Assigned To | Last Scan | Actions |
|---|---|---|---|---|---|
| SCHR-P3-DP-001 | 164.231.170.44 | 2026-03-12 | |||
Finding DetailsEvaluate-STIG 1.2601.0 (Scan-IIS10_0_Server_Checks) was unable to determine a Status but found the below configuration on 03/05/2026: ResultHash: 18A38144AE758B632F13BB4CD7F8C15B7EA37790 ~~~~~ Local user accounts on this system: DefaultAccount DOD_Admin Visitor WDAGUtilityAccount X_Admin Comments |
|||||
Check Text
Access the IIS 10.0 web server. Access “Apps” menu. Under “Administrative Tools”, select “Computer Management”. In the left pane, expand "Local Users and Groups" and click "Users". Review the local users listed in the middle pane. If any local accounts are present and were created by features which have been uninstalled or are not used, this is a finding.
Fix Text
Access the IIS 10.0 web server. Access “Apps” menu. Under “Administrative Tools”, select “Computer Management”. In the left pane, expand "Local Users and Groups" and click "Users". Delete any local accounts which were created by features which have been uninstalled or are not used.
| Hostname | IP Address | Status | Assigned To | Last Scan | Actions |
|---|---|---|---|---|---|
| SCHR-P3-DP-001 | 164.231.170.44 | 2026-03-12 | |||
Finding DetailsEvaluate-STIG 1.2601.0 (Scan-IIS10_0_Server_Checks) was unable to determine a Status but found the below configuration on 03/05/2026: ResultHash: A651C464F3C53AD8D73A90109651B37A8084D1B7 ~~~~~ The following Windows features are installed: AzureArcSetup DeviceHealthAttestationService FileAndStorage-Services File-Services FS-FileServer NET-Framework-45-ASPNET NET-Framework-45-Core NET-Framework-45-Features NET-WCF-HTTP-Activation45 NET-WCF-Services45 NET-WCF-TCP-PortSharing45 PowerShell PowerShellRoot Storage-Services System-DataArchiver WAS WAS-Config-APIs WAS-Process-Model Web-App-Dev Web-Asp-Net45 Web-Common-Http Web-Default-Doc Web-Dir-Browsing Web-Filtering Web-Health Web-Http-Errors Web-Http-Logging Web-Http-Tracing Web-Includes Web-ISAPI-Ext Web-ISAPI-Filter Web-Mgmt-Console Web-Mgmt-Tools Web-Net-Ext45 Web-Performance Web-Security Web-Server Web-Stat-Compression Web-Static-Content Web-WebServer Windows-Defender WoW64-Support Comments |
|||||
Check Text
Consult with the System Administrator and review all of the IIS 10.0 and Operating System features installed. Determine if any features installed are no longer necessary for operation. If any utility programs, features, or modules are installed which are not necessary for operation, this is a finding. If any unnecessary Operating System features are installed, this is a finding.
Fix Text
Remove all utility programs, Operating System features, or modules installed that are not necessary for web server operation.
| Hostname | IP Address | Status | Assigned To | Last Scan | Actions |
|---|---|---|---|---|---|
| SCHR-P3-DP-001 | 164.231.170.44 | 2026-03-12 | |||
Finding DetailsEvaluate-STIG 1.2601.0 (Scan-IIS10_0_Server_Checks) found this to be OPEN on 03/05/2026 ResultHash: 47C2C311101A88836E6EF2E986BC87A38AC57B63 ~~~~~ The following invalid MIME types for OS shell program extensions are configured: .exe .dll .csh Comments |
|||||
Check Text
Note: If the server is hosting WSUS, this is not applicable. Open the IIS 10.0 Manager. Click the IIS 10.0 web server name. Under IIS, double-click the "MIME Types" icon. From the "Group by:" drop-down list, select "Content Type". From the list of extensions under "Application", verify MIME types for OS shell program extensions have been removed, to include at a minimum, the following extensions: .exe .dll .com .bat .csh If any OS shell MIME types are configured, this is a finding.
Fix Text
Open the IIS 10.0 Manager. Click the IIS 10.0 web server name. Under IIS, double-click the "MIME Types" icon. From the "Group by:" drop-down list, select "Content Type". From the list of extensions under "Application", remove MIME types for OS shell program extensions, to include at a minimum, the following extensions: .exe .dll .com .bat .csh Under the "Actions" pane, click "Apply".
| Hostname | IP Address | Status | Assigned To | Last Scan | Actions |
|---|---|---|---|---|---|
| SCHR-P3-DP-001 | 164.231.170.44 | 2026-03-12 | |||
Finding DetailsEvaluate-STIG 1.2601.0 (Scan-IIS10_0_Server_Checks) found this to be NOT A FINDING on 03/05/2026 ResultHash: 11E9E664D97AAF7C5FF4F4BDDCF9203D790D431E ~~~~~ WebDAV is not installed. Comments |
|||||
Check Text
Open the IIS 10.0 Manager. Click the IIS 10.0 web server name. Review the features listed under the “IIS" section. If the "WebDAV Authoring Rules" icon exists, this is a finding.
Fix Text
Access Server Manager on the IIS 10.0 web server. Click the IIS 10.0 web server name. Click on "Manage". Select "Add Roles and Features". Click "Next" in the "Before you begin" dialog box. Select "Role-based or feature-based installation" on the "Installation Type" dialog box and click "Next". Select the IIS 10.0 web server in the "Server Selection" dialog box. From the "Windows Features" dialog box, navigate to "World Wide Web Services" >> "Common HTTP Features". De-select "WebDAV Publishing", and click "Next" to complete removing the WebDAV Publishing feature from the IIS 10.0 web server.
| Hostname | IP Address | Status | Assigned To | Last Scan | Actions |
|---|---|---|---|---|---|
| SCHR-P3-DP-001 | 164.231.170.44 | 2026-03-12 | |||
Finding DetailsEvaluate-STIG 1.2601.0 (Scan-IIS10_0_Server_Checks) found this to be NOT A FINDING on 03/05/2026 ResultHash: 7C036395A18A2F6B324D665A6F665274B1C279AC ~~~~~ No .java or .jpp files were found on the system. Comments |
|||||
Check Text
Search the system for files with either .java or .jpp extensions. If files with .java or .jpp extensions are found, this is a finding.
Fix Text
Remove all files from the web server with both .java and .jpp extensions.
| Hostname | IP Address | Status | Assigned To | Last Scan | Actions |
|---|---|---|---|---|---|
| SCHR-P3-DP-001 | 164.231.170.44 | 2026-03-12 | |||
Finding DetailsNo details recorded. Comments |
|||||
Check Text
Review the IIS 10.0 web server configuration with the System Administrator. Determine if the IIS 10.0 web server hosts any applications. If the IIS 10.0 web server does not host any applications, this is Not Applicable. If the IIS 10.0 web server is hosting Exchange, this is Not Applicable. If the IIS 10.0 web server hosts applications, review the application's management functionality and authentication methods with the System Administrator to determine if the management of the application is accomplished with the same functions and authentication methods as the web server management. If the IIS 10.0 web server management and the application's management functionality is not separated, this is a finding.
Fix Text
Develop a method to manage the hosted applications, either by moving its management functions off of the IIS 10.0 web server or by accessing the application's management via a uniquely assigned IP address.
| Hostname | IP Address | Status | Assigned To | Last Scan | Actions |
|---|---|---|---|---|---|
| SCHR-P3-DP-001 | 164.231.170.44 | 2026-03-12 | |||
Finding DetailsEvaluate-STIG 1.2601.0 (Scan-IIS10_0_Server_Checks) found this to be NOT A FINDING on 03/05/2026 ResultHash: 82F8F3236DC4CEA119EF339FF044AF71A3B6F80F ~~~~~ Cookie Settings Mode is configured to 'UseCookies' Comments |
|||||
Check Text
Note: If ASP.NET is not installed, this is Not Applicable. Open the IIS 10.0 Manager. Click the IIS 10.0 web server name. Under "ASP.Net", double-click the "Session State" icon. Under "Cookie Settings", verify the "Mode" has "Use Cookies" selected from the drop-down list. If the "Cookie Settings" "Mode" is not set to "Use Cookies", this is a finding. Alternative method: Click the site name. Select "Configuration Editor" under the "Management" section. From the "Section:" drop-down list at the top of the configuration editor, locate "system.web/sessionState". Verify the "cookieless" is set to "UseCookies". If the "cookieless" is not set to "UseCookies", this is a finding. Note: If IIS 10.0 server/site is used only for system-to-system maintenance, does not allow users to connect to interface, and is restricted to specific system IPs, this is Not Applicable.
Fix Text
Open the IIS 10.0 Manager. Click the IIS 10.0 web server name. Under "ASP.Net", double-click the "Session State" icon. Under "Cookie Settings", select "Use Cookies” from the "Mode" drop-down list. Click "Apply" in the "Actions" pane.
| Hostname | IP Address | Status | Assigned To | Last Scan | Actions |
|---|---|---|---|---|---|
| SCHR-P3-DP-001 | 164.231.170.44 | 2026-03-12 | |||
Finding DetailsEvaluate-STIG 1.2601.0 (Scan-IIS10_0_Server_Checks) found this to be NOT A FINDING on 03/05/2026 ResultHash: 7533F9E6958FD6D045546A3732F63AFD8472E223 ~~~~~ Cookie Settings Mode is configured to 'UseCookies' Time-out is configured to '00:15:00' Comments |
|||||
Check Text
Note: If ASP.NET is not installed, this is Not Applicable. Open the IIS 10.0 Manager. Click the IIS 10.0 web server name. Under the "ASP.NET" section, select "Session State". Under "Cookie Settings", verify the "Use Cookies" mode is selected from the "Mode:" drop-down list. Under "Time-out (in minutes)", verify a maximum of 15 minutes is entered. If the "Use Cookies" mode is selected and Time-out (in minutes) is configured for "15 minutes" (or less), this is not a finding. Alternative method: Click the site name. Select "Configuration Editor" under the "Management" section. From the "Section:" drop-down list at the top of the configuration editor, locate "system.web/sessionState". Verify the "cookieless" is set to "UseCookies". If the "cookieless" is not set to "UseCookies", this is a finding. Note: If IIS 10.0 server/site is used only for system-to-system maintenance, does not allow users to connect to interface, and is restricted to specific system IPs, this is Not Applicable.
Fix Text
Open the IIS 10.0 Manager. Click the IIS 10.0 web server name. Under the "ASP.NET" section, select "Session State". Under "Cookie Settings", select the "Use Cookies" mode from the "Mode:" drop-down list. Under "Time-out (in minutes)", enter a value of "15 or less".
| Hostname | IP Address | Status | Assigned To | Last Scan | Actions |
|---|---|---|---|---|---|
| SCHR-P3-DP-001 | 164.231.170.44 | 2026-03-12 | |||
Finding DetailsNo details recorded. Comments |
|||||
Check Text
Interview the System Administrator for the IIS 10.0 web server. Ask for documentation on the disaster recovery methods tested and planned for the IIS 10.0 web server in the event of the necessity for rollback. If documentation for a disaster recovery has not been established, this is a finding.
Fix Text
Prepare documentation for disaster recovery methods for the IIS 10.0 web server in the event of the necessity for rollback. Document and test the disaster recovery methods designed.
| Hostname | IP Address | Status | Assigned To | Last Scan | Actions |
|---|---|---|---|---|---|
| SCHR-P3-DP-001 | 164.231.170.44 | 2026-03-12 | |||
Finding DetailsEvaluate-STIG 1.2601.0 (Scan-IIS10_0_Server_Checks) found this to be NOT A FINDING on 03/05/2026 ResultHash: 530DCB7F759E36FF01EB01CF5B0A9E37991A6046 ~~~~~ Validation method is configured to 'HMACSHA256' Encryption method is configured to 'Auto' Comments |
|||||
Check Text
Note: If ASP.NET is not installed, this is Not Applicable. Note: If the IIS 10.0 web server is hosting Exchange, this is Not Applicable. Open the IIS 10.0 Manager. Click the IIS 10.0 web server name. Double-click the "Machine Key" icon in the website Home Pane. Verify "HMACSHA256" or stronger encryption is selected for the Validation method and "Auto" is selected for the Encryption method. If "HMACSHA256" or stronger encryption is not selected for the Validation method and/or "Auto" is not selected for the Encryption method, this is a finding. If .NET is not installed, this is Not Applicable.
Fix Text
Open the IIS 10.0 Manager. Click the IIS 10.0 web server name. Double-click the "Machine Key" icon in the web server Home Pane. Set the Validation method to "HMACSHA256" or stronger. Set the Encryption method to "Auto". Click "Apply" in the "Actions" pane.
| Hostname | IP Address | Status | Assigned To | Last Scan | Actions |
|---|---|---|---|---|---|
| SCHR-P3-DP-001 | 164.231.170.44 | 2026-03-12 | |||
Finding DetailsEvaluate-STIG 1.2601.0 (Scan-IIS10_0_Server_Checks) found this to be NOT A FINDING on 03/05/2026 ResultHash: 5386A3B2F3411A770BCAD2C194ACBAEBD1970A52 ~~~~~ Directory Browsing is disabled. Comments |
|||||
Check Text
Open the IIS 10.0 Manager. Click the IIS 10.0 web server name. Double-click the "Directory Browsing" icon. Under the “Actions” pane verify "Directory Browsing" is disabled. If “Directory Browsing” is not disabled, this is a finding.
Fix Text
Open the IIS 10.0 Manager. Click the IIS 10.0 web server name. Double-click the "Directory Browsing" icon. Under the "Actions" pane click "Disabled". Under the "Actions" pane, click "Apply".
| Hostname | IP Address | Status | Assigned To | Last Scan | Actions |
|---|---|---|---|---|---|
| SCHR-P3-DP-001 | 164.231.170.44 | 2026-03-12 | |||
Finding DetailsEvaluate-STIG 1.2601.0 (Scan-IIS10_0_Server_Checks) found this to be NOT APPLICABLE on 03/05/2026 ResultHash: 4BD2B86D8CFC3DF2188407FE8BEF3C5953DFB07F ~~~~~ The ContentIndex\Catalogs key does not exist so this check is Not Applicable. Comments |
|||||
Check Text
Access the IIS 10.0 Web Server. Access an administrator command prompt and type "regedit <enter>" to access the server's registry. Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\ContentIndex\Catalogs\. If this key exists, then indexing is enabled. If the key does not exist, this check is Not Applicable. Review the Catalog keys to determine if directories other than web document directories are being indexed. If so, this is a finding.
Fix Text
Run MMC. Add the Indexing Service snap-in. Edit the indexed directories to only include web document directories.
| Hostname | IP Address | Status | Assigned To | Last Scan | Actions |
|---|---|---|---|---|---|
| SCHR-P3-DP-001 | 164.231.170.44 | 2026-03-12 | |||
Finding DetailsEvaluate-STIG 1.2601.0 (Scan-IIS10_0_Server_Checks) found this to be NOT A FINDING on 03/05/2026 ResultHash: 8DD7CFE973D10647A1435F5B797FDBD4463D27D1 ~~~~~ Error Responses is configured to 'Detailed errors for local requests and custom error pages for remote requests' errorMode: DetailedLocalOnly Comments |
|||||
Check Text
Note: If the server is hosting WSUS, this is Not Applicable. Open the IIS 10.0 Manager. Click the IIS 10.0 web server name. Double-click the "Error Pages" icon. Click any error message, and then click "Edit Feature Setting" from the "Actions" Pane. This will apply to all error messages. If the feature setting is not set to "Detailed errors for local requests and custom error pages for remote requests", or "Custom error pages" this is a finding.
Fix Text
Open the IIS 10.0 Manager. Click the IIS 10.0 web server name. Double-click the "Error Pages" icon. Click any error message, and then click "Edit Feature Setting" from the "Actions" Pane. This will apply to all error messages. Set Feature Setting to "Detailed errors for local requests and custom error pages for remote requests" or "Custom error pages".
| Hostname | IP Address | Status | Assigned To | Last Scan | Actions |
|---|---|---|---|---|---|
| SCHR-P3-DP-001 | 164.231.170.44 | 2026-03-12 | |||
Finding DetailsEvaluate-STIG 1.2601.0 (Scan-IIS10_0_Server_Checks) found this to be NOT APPLICABLE on 03/05/2026 ResultHash: 69339D5EDE3A1D594FB554D39E84CA77B3304C98 ~~~~~ The remote management feature of IIS is not installed so this check is Not Applicable. Comments |
|||||
Check Text
Note: This requirement applies to the Web Management Service. If the Web Management Service is not installed, this is Not Applicable. Open the IIS 10.0 Manager. Click the IIS 10.0 web server name. Under "Management", double-click "Management Service". If "Enable remote connections" is not selected, this is Not Applicable. If "Enable remote connections" is selected, review the entries under "IP Address Restrictions". Verify only known, secure IP ranges are configured as "Allow". If "IP Address Restrictions" are not configured or IP ranges configured to "Allow" are not restrictive enough to prevent connections from nonsecure zones, this is a finding.
Fix Text
Open the IIS 10.0 Manager. Click the IIS 10.0 web server name. Under "Management", double-click "Management Service". Stop the Web Management Service under the "Actions" pane. Configure only known, secure IP ranges as "Allow". Select "Apply" in "Actions" pane. Restart the Web Management Service under the "Actions" pane.