USNS MONTFORD POINT - Findings

Showing 50 of 126 findings (filtered) View Documentation Status (90 tracked)

Vuln ID	Severity	Asset	STIG	Title	Doc Status
V-218750	CAT I	MONT-MB-002	Microsoft IIS 10.0 Site Security Technic...	Anonymous IIS 10.0 website access accounts must be...	-
Check Text Check the account used for anonymous access to the website. Follow the procedures below for each site hosted on the IIS 10.0 web server: Open the IIS 10.0 Manager. Double-click "Authentication" in the IIS section of the website’s Home Pane. If "Anonymous access" is disabled, this is Not a Finding. If "Anonymous access" is enabled, click "Anonymous Authentication". Click "Edit" in the "Actions" pane. If the "Specific user" radio button is enabled and an ID is specified in the adjacent control box, this is the ID being used for anonymous access. Note the account name. If nothing is tied to "Specific User", this is Not a Finding. Check privileged groups that may allow the anonymous account inappropriate membership: Open "Computer Management" on the machine. Expand "Local Users and Groups". Open "Groups". Review the members of any of the following privileged groups: Administrators Backup Operators Certificate Services (of any designation) Distributed COM Users Event Log Readers Network Configuration Operators Performance Log Users Performance Monitor Users Power Users Print Operators Remote Desktop Users Replicator Double-click each group and review its members. If the IUSR account or any account noted above used for anonymous access is a member of any group with privileged access, this is a finding. Fix Text Remove the Anonymous access account from all privileged accounts and all privileged groups. Finding Details Evaluate-STIG 1.2507.5 (Scan-IIS10_0_Site_Checks) found this to be NOT A FINDING on 10/23/2025 Site: Default Web Site ResultHash: 11B73503DAE06F01B5185CC126C80F8941A56D00 ~~~~~ Anonymous Authentication is Enabled and using the account 'IUSR' for authentication. IUSR is not a member of any privileged groups. Source: _Reviewed/MONT-MB-002/Checklist/MONT-MB-002_IIS10Site_Default_Web_Site_V2R12_20251023-152518.ckl Scan Date: 2026-01-14T12:57:33.098574 Technology Area: Web Review
V-218750	CAT I	MONT-MB-002	Microsoft IIS 10.0 Site Security Technic...	Anonymous IIS 10.0 website access accounts must be...	-
Check Text Check the account used for anonymous access to the website. Follow the procedures below for each site hosted on the IIS 10.0 web server: Open the IIS 10.0 Manager. Double-click "Authentication" in the IIS section of the website’s Home Pane. If "Anonymous access" is disabled, this is Not a Finding. If "Anonymous access" is enabled, click "Anonymous Authentication". Click "Edit" in the "Actions" pane. If the "Specific user" radio button is enabled and an ID is specified in the adjacent control box, this is the ID being used for anonymous access. Note the account name. If nothing is tied to "Specific User", this is Not a Finding. Check privileged groups that may allow the anonymous account inappropriate membership: Open "Computer Management" on the machine. Expand "Local Users and Groups". Open "Groups". Review the members of any of the following privileged groups: Administrators Backup Operators Certificate Services (of any designation) Distributed COM Users Event Log Readers Network Configuration Operators Performance Log Users Performance Monitor Users Power Users Print Operators Remote Desktop Users Replicator Double-click each group and review its members. If the IUSR account or any account noted above used for anonymous access is a member of any group with privileged access, this is a finding. Fix Text Remove the Anonymous access account from all privileged accounts and all privileged groups. Finding Details Evaluate-STIG 1.2507.5 (Scan-IIS10_0_Site_Checks) found this to be NOT A FINDING on 10/23/2025 Site: Exchange Back End ResultHash: 11B73503DAE06F01B5185CC126C80F8941A56D00 ~~~~~ Anonymous Authentication is Enabled and using the account 'IUSR' for authentication. IUSR is not a member of any privileged groups. Source: _Reviewed/MONT-MB-002/Checklist/MONT-MB-002_IIS10Site_Exchange_Back_End_V2R12_20251023-152602.ckl Scan Date: 2026-01-14T12:57:33.300070 Technology Area: Web Review
V-218750	CAT I	MONT-DP-001	Microsoft IIS 10.0 Site Security Technic...	Anonymous IIS 10.0 website access accounts must be...	-
Check Text Check the account used for anonymous access to the website. Follow the procedures below for each site hosted on the IIS 10.0 web server: Open the IIS 10.0 Manager. Double-click "Authentication" in the IIS section of the website’s Home Pane. If "Anonymous access" is disabled, this is Not a Finding. If "Anonymous access" is enabled, click "Anonymous Authentication". Click "Edit" in the "Actions" pane. If the "Specific user" radio button is enabled and an ID is specified in the adjacent control box, this is the ID being used for anonymous access. Note the account name. If nothing is tied to "Specific User", this is Not a Finding. Check privileged groups that may allow the anonymous account inappropriate membership: Open "Computer Management" on the machine. Expand "Local Users and Groups". Open "Groups". Review the members of any of the following privileged groups: Administrators Backup Operators Certificate Services (of any designation) Distributed COM Users Event Log Readers Network Configuration Operators Performance Log Users Performance Monitor Users Power Users Print Operators Remote Desktop Users Replicator Double-click each group and review its members. If the IUSR account or any account noted above used for anonymous access is a member of any group with privileged access, this is a finding. Fix Text Remove the Anonymous access account from all privileged accounts and all privileged groups. Finding Details Evaluate-STIG 1.2507.5 (Scan-IIS10_0_Site_Checks) found this to be NOT A FINDING on 10/23/2025 Site: Default Web Site ResultHash: 11B73503DAE06F01B5185CC126C80F8941A56D00 ~~~~~ Anonymous Authentication is Enabled and using the account 'IUSR' for authentication. IUSR is not a member of any privileged groups. Source: _Reviewed/MONT-DP-001/Checklist/MONT-DP-001_IIS10Site_Default_Web_Site_V2R12_20251023-143912.ckl Scan Date: 2026-01-14T12:57:35.375369 Technology Area: Web Review
V-218768	CAT I	MONT-MB-002	Microsoft IIS 10.0 Site Security Technic...	The IIS 10.0 private website must employ cryptogra...	Documented Pending Review
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. 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. Fix Text 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. Select the "Require SSL" setting. Select the "Client Certificates Required" setting. Click "Apply" in the "Actions" pane. 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". Click on the drop-down list for "sslFlags". Select the "Ssl128" check box. Click "Apply" in the "Actions" pane. Finding Details Evaluate-STIG 1.2507.5 (Scan-IIS10_0_Site_Checks) found this to be OPEN on 10/23/2025 Site: Default Web Site ResultHash: 20F984A5D3F505EAE457B229ADD97C44EF33D3DC ~~~~~ The following SSL flags are missing: SslRequireCert Source: _Reviewed/MONT-MB-002/Checklist/MONT-MB-002_IIS10Site_Default_Web_Site_V2R12_20251023-152518.ckl Scan Date: 2026-01-14T12:57:33.098574 Technology Area: Web Review
V-218768	CAT I	MONT-MB-002	Microsoft IIS 10.0 Site Security Technic...	The IIS 10.0 private website must employ cryptogra...	Documented Pending Review
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. 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. Fix Text 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. Select the "Require SSL" setting. Select the "Client Certificates Required" setting. Click "Apply" in the "Actions" pane. 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". Click on the drop-down list for "sslFlags". Select the "Ssl128" check box. Click "Apply" in the "Actions" pane. Finding Details Evaluate-STIG 1.2507.5 (Scan-IIS10_0_Site_Checks) found this to be OPEN on 10/23/2025 Site: Exchange Back End ResultHash: 20F984A5D3F505EAE457B229ADD97C44EF33D3DC ~~~~~ The following SSL flags are missing: SslRequireCert Source: _Reviewed/MONT-MB-002/Checklist/MONT-MB-002_IIS10Site_Exchange_Back_End_V2R12_20251023-152602.ckl Scan Date: 2026-01-14T12:57:33.300070 Technology Area: Web Review
V-218768	CAT I	MONT-DP-001	Microsoft IIS 10.0 Site Security Technic...	The IIS 10.0 private website must employ cryptogra...	Documented Pending Review
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. 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. Fix Text 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. Select the "Require SSL" setting. Select the "Client Certificates Required" setting. Click "Apply" in the "Actions" pane. 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". Click on the drop-down list for "sslFlags". Select the "Ssl128" check box. Click "Apply" in the "Actions" pane. Finding Details Evaluate-STIG 1.2507.5 (Scan-IIS10_0_Site_Checks) found this to be OPEN on 10/23/2025 Site: Default Web Site ResultHash: 6275DCDEF057117A4E22688BC519EA5B675A222E ~~~~~ The following SSL flags are missing: Ssl SslRequireCert Ssl128 Comments If the server is hosting WSUS, this is Not Applicable. Source: _Reviewed/MONT-DP-001/Checklist/MONT-DP-001_IIS10Site_Default_Web_Site_V2R12_20251023-143912.ckl Scan Date: 2026-01-14T12:57:35.375369 Technology Area: Web Review
V-218736	CAT II	MONT-MB-002	Microsoft IIS 10.0 Site Security Technic...	The IIS 10.0 website session state cookie settings...	-
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 "Cookie Settings", verify the "Use Cookies" mode is selected from the "Mode:" drop-down list. If the "Use Cookies" 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 "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 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 "Cookie Settings", select the "Use Cookies" from the "Mode:" drop-down list. Select "Apply" from the "Actions" pane. Finding Details Evaluate-STIG 1.2507.5 (Scan-IIS10_0_Site_Checks) found this to be NOT A FINDING on 10/23/2025 Site: Default Web Site ResultHash: 453FAD461534700007B4F585B0D2FD1A4236A4FD ~~~~~ Cookie Settings is set to 'UseCookies' Source: _Reviewed/MONT-MB-002/Checklist/MONT-MB-002_IIS10Site_Default_Web_Site_V2R12_20251023-152518.ckl Scan Date: 2026-01-14T12:57:33.098574 Technology Area: Web Review
V-218736	CAT II	MONT-MB-002	Microsoft IIS 10.0 Site Security Technic...	The IIS 10.0 website session state cookie settings...	-
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 "Cookie Settings", verify the "Use Cookies" mode is selected from the "Mode:" drop-down list. If the "Use Cookies" 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 "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 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 "Cookie Settings", select the "Use Cookies" from the "Mode:" drop-down list. Select "Apply" from the "Actions" pane. Finding Details Evaluate-STIG 1.2507.5 (Scan-IIS10_0_Site_Checks) found this to be NOT A FINDING on 10/23/2025 Site: Exchange Back End ResultHash: 453FAD461534700007B4F585B0D2FD1A4236A4FD ~~~~~ Cookie Settings is set to 'UseCookies' Source: _Reviewed/MONT-MB-002/Checklist/MONT-MB-002_IIS10Site_Exchange_Back_End_V2R12_20251023-152602.ckl Scan Date: 2026-01-14T12:57:33.300070 Technology Area: Web Review
V-218736	CAT II	MONT-DP-001	Microsoft IIS 10.0 Site Security Technic...	The IIS 10.0 website session state cookie settings...	-
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 "Cookie Settings", verify the "Use Cookies" mode is selected from the "Mode:" drop-down list. If the "Use Cookies" 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 "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 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 "Cookie Settings", select the "Use Cookies" from the "Mode:" drop-down list. Select "Apply" from the "Actions" pane. Finding Details Evaluate-STIG 1.2507.5 (Scan-IIS10_0_Site_Checks) found this to be NOT APPLICABLE on 10/23/2025 Site: Default Web Site ResultHash: 2DD143332C0C53AB5EB35B604B56FEEE445E829C ~~~~~ ASP.NET is not installed so this requirement is NA. Source: _Reviewed/MONT-DP-001/Checklist/MONT-DP-001_IIS10Site_Default_Web_Site_V2R12_20251023-143912.ckl Scan Date: 2026-01-14T12:57:35.375369 Technology Area: Web Review
V-218737	CAT II	MONT-MB-002	Microsoft IIS 10.0 Site Security Technic...	A private IIS 10.0 website must only accept Secure...	-
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 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. 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. Double-click the "SSL Settings" icon. Select "Require SSL" check box. Select "Apply" from the "Actions" pane. Finding Details Evaluate-STIG 1.2507.5 (Scan-IIS10_0_Site_Checks) found this to be NOT A FINDING on 10/23/2025 Site: Default Web Site ResultHash: 17B78AD55656672A7E76179F07EDCDD767389185 ~~~~~ Require SSL is enabled Source: _Reviewed/MONT-MB-002/Checklist/MONT-MB-002_IIS10Site_Default_Web_Site_V2R12_20251023-152518.ckl Scan Date: 2026-01-14T12:57:33.098574 Technology Area: Web Review
V-218737	CAT II	MONT-MB-002	Microsoft IIS 10.0 Site Security Technic...	A private IIS 10.0 website must only accept Secure...	-
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 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. 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. Double-click the "SSL Settings" icon. Select "Require SSL" check box. Select "Apply" from the "Actions" pane. Finding Details Evaluate-STIG 1.2507.5 (Scan-IIS10_0_Site_Checks) found this to be NOT A FINDING on 10/23/2025 Site: Exchange Back End ResultHash: 17B78AD55656672A7E76179F07EDCDD767389185 ~~~~~ Require SSL is enabled Source: _Reviewed/MONT-MB-002/Checklist/MONT-MB-002_IIS10Site_Exchange_Back_End_V2R12_20251023-152602.ckl Scan Date: 2026-01-14T12:57:33.300070 Technology Area: Web Review
V-218737	CAT II	MONT-DP-001	Microsoft IIS 10.0 Site Security Technic...	A private IIS 10.0 website must only accept Secure...	-
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 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. 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. Double-click the "SSL Settings" icon. Select "Require SSL" check box. Select "Apply" from the "Actions" pane. Finding Details Evaluate-STIG 1.2507.5 (Scan-IIS10_0_Site_Checks) was unable to determine a Status but found the below configuration on 10/23/2025: Site: Default Web Site ResultHash: 1F8B0BF251048DDF52481451B9AA669A5C254D2B ~~~~~ Require SSL is NOT enabled Comments Find out: If MECM applies to this: If the server is hosting WSUS, this is Not Applicable. Source: _Reviewed/MONT-DP-001/Checklist/MONT-DP-001_IIS10Site_Default_Web_Site_V2R12_20251023-143912.ckl Scan Date: 2026-01-14T12:57:35.375369 Technology Area: Web Review
V-218738	CAT II	MONT-MB-002	Microsoft IIS 10.0 Site Security Technic...	A public IIS 10.0 website must only accept Secure ...	-
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. 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. Fix Text Note: If the server being reviewed is a private IIS 10.0 web server, 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. Select "Require SSL" check box. Select "Apply" from the "Actions" pane. Finding Details Evaluate-STIG 1.2507.5 (Scan-IIS10_0_Site_Checks) found this to be NOT A FINDING on 10/23/2025 Site: Default Web Site ResultHash: 17B78AD55656672A7E76179F07EDCDD767389185 ~~~~~ Require SSL is enabled Source: _Reviewed/MONT-MB-002/Checklist/MONT-MB-002_IIS10Site_Default_Web_Site_V2R12_20251023-152518.ckl Scan Date: 2026-01-14T12:57:33.098574 Technology Area: Web Review
V-218738	CAT II	MONT-MB-002	Microsoft IIS 10.0 Site Security Technic...	A public IIS 10.0 website must only accept Secure ...	-
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. 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. Fix Text Note: If the server being reviewed is a private IIS 10.0 web server, 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. Select "Require SSL" check box. Select "Apply" from the "Actions" pane. Finding Details Evaluate-STIG 1.2507.5 (Scan-IIS10_0_Site_Checks) found this to be NOT A FINDING on 10/23/2025 Site: Exchange Back End ResultHash: 17B78AD55656672A7E76179F07EDCDD767389185 ~~~~~ Require SSL is enabled Source: _Reviewed/MONT-MB-002/Checklist/MONT-MB-002_IIS10Site_Exchange_Back_End_V2R12_20251023-152602.ckl Scan Date: 2026-01-14T12:57:33.300070 Technology Area: Web Review
V-218738	CAT II	MONT-DP-001	Microsoft IIS 10.0 Site Security Technic...	A public IIS 10.0 website must only accept Secure ...	-
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. 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. Fix Text Note: If the server being reviewed is a private IIS 10.0 web server, 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. Select "Require SSL" check box. Select "Apply" from the "Actions" pane. Finding Details Evaluate-STIG 1.2507.5 (Scan-IIS10_0_Site_Checks) was unable to determine a Status but found the below configuration on 10/23/2025: Site: Default Web Site ResultHash: 1F8B0BF251048DDF52481451B9AA669A5C254D2B ~~~~~ Require SSL is NOT enabled Comments If the server is hosting WSUS, this is Not Applicable. Source: _Reviewed/MONT-DP-001/Checklist/MONT-DP-001_IIS10Site_Default_Web_Site_V2R12_20251023-143912.ckl Scan Date: 2026-01-14T12:57:35.375369 Technology Area: Web Review
V-218739	CAT II	MONT-MB-002	Microsoft IIS 10.0 Site Security Technic...	Both the log file and Event Tracing for Windows (E...	-
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. 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. Note: "Microsoft-IIS-Logging/logs" must be enabled prior to configuring this setting. More configuration information is available at: https://blogs.intelink.gov/blogs/_disairrt/?p=1317 Fix Text Note: "Microsoft-IIS-Logging/logs" must be enabled prior to configuring this setting. 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. Click the "Logging" icon. Under Log Event Destination, select the "Both log file and ETW event" radio button. Select "Apply" from the "Actions" pane. Finding Details Evaluate-STIG 1.2507.5 (Scan-IIS10_0_Site_Checks) found this to be OPEN on 10/23/2025 Site: Default Web Site ResultHash: 0B44ED3D6039C1A0BDB60FE41477857D9DAB447E ~~~~~ 'File' is the only option selected. Source: _Reviewed/MONT-MB-002/Checklist/MONT-MB-002_IIS10Site_Default_Web_Site_V2R12_20251023-152518.ckl Scan Date: 2026-01-14T12:57:33.098574 Technology Area: Web Review
V-218739	CAT II	MONT-MB-002	Microsoft IIS 10.0 Site Security Technic...	Both the log file and Event Tracing for Windows (E...	-
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. 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. Note: "Microsoft-IIS-Logging/logs" must be enabled prior to configuring this setting. More configuration information is available at: https://blogs.intelink.gov/blogs/_disairrt/?p=1317 Fix Text Note: "Microsoft-IIS-Logging/logs" must be enabled prior to configuring this setting. 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. Click the "Logging" icon. Under Log Event Destination, select the "Both log file and ETW event" radio button. Select "Apply" from the "Actions" pane. Finding Details Evaluate-STIG 1.2507.5 (Scan-IIS10_0_Site_Checks) found this to be OPEN on 10/23/2025 Site: Exchange Back End ResultHash: 0B44ED3D6039C1A0BDB60FE41477857D9DAB447E ~~~~~ 'File' is the only option selected. Source: _Reviewed/MONT-MB-002/Checklist/MONT-MB-002_IIS10Site_Exchange_Back_End_V2R12_20251023-152602.ckl Scan Date: 2026-01-14T12:57:33.300070 Technology Area: Web Review
V-218739	CAT II	MONT-DP-001	Microsoft IIS 10.0 Site Security Technic...	Both the log file and Event Tracing for Windows (E...	-
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. 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. Note: "Microsoft-IIS-Logging/logs" must be enabled prior to configuring this setting. More configuration information is available at: https://blogs.intelink.gov/blogs/_disairrt/?p=1317 Fix Text Note: "Microsoft-IIS-Logging/logs" must be enabled prior to configuring this setting. 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. Click the "Logging" icon. Under Log Event Destination, select the "Both log file and ETW event" radio button. Select "Apply" from the "Actions" pane. Finding Details Evaluate-STIG 1.2507.5 (Scan-IIS10_0_Site_Checks) found this to be OPEN on 10/23/2025 Site: Default Web Site ResultHash: 0B44ED3D6039C1A0BDB60FE41477857D9DAB447E ~~~~~ 'File' is the only option selected. Comments If the server is hosting WSUS, this is Not Applicable. Source: _Reviewed/MONT-DP-001/Checklist/MONT-DP-001_IIS10Site_Default_Web_Site_V2R12_20251023-143912.ckl Scan Date: 2026-01-14T12:57:35.375369 Technology Area: Web Review
V-218740	CAT II	MONT-MB-002	Microsoft IIS 10.0 Site Security Technic...	An IIS 10.0 website behind a load balancer or prox...	-
Check Text Interview the System Administrator to review the configuration of the IIS 10.0 architecture and determine if inbound web traffic is passed through a proxy. If the IIS 10.0 is receiving inbound web traffic through a proxy, the audit logs must be reviewed to determine if correct source information is being passed through by the proxy server. 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. Click the "Logging" icon. Click "View log file". When log file is displayed, review source IP information in log entries and verify entries do not reflect the IP address of the proxy server. If the website is not behind a load balancer or proxy server, this is Not Applicable. If the log entries in the log file(s) reflect the IP address of the proxy server as the source, this is a finding. If provisions have been made to log the client IP via another field (i.e., utilizing X-Forwarded-For), this is not a finding. Fix Text Access the proxy server through which inbound web traffic is passed and configure settings to pass web traffic to the IIS 10.0 web server transparently. Finding Details If the website is not behind a load balancer or proxy server, this is Not Applicable. Source: _Reviewed/MONT-MB-002/Checklist/MONT-MB-002_IIS10Site_Default_Web_Site_V2R12_20251023-152518.ckl Scan Date: 2026-01-14T12:57:33.098574 Technology Area: Web Review
V-218740	CAT II	MONT-MB-002	Microsoft IIS 10.0 Site Security Technic...	An IIS 10.0 website behind a load balancer or prox...	-
Check Text Interview the System Administrator to review the configuration of the IIS 10.0 architecture and determine if inbound web traffic is passed through a proxy. If the IIS 10.0 is receiving inbound web traffic through a proxy, the audit logs must be reviewed to determine if correct source information is being passed through by the proxy server. 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. Click the "Logging" icon. Click "View log file". When log file is displayed, review source IP information in log entries and verify entries do not reflect the IP address of the proxy server. If the website is not behind a load balancer or proxy server, this is Not Applicable. If the log entries in the log file(s) reflect the IP address of the proxy server as the source, this is a finding. If provisions have been made to log the client IP via another field (i.e., utilizing X-Forwarded-For), this is not a finding. Fix Text Access the proxy server through which inbound web traffic is passed and configure settings to pass web traffic to the IIS 10.0 web server transparently. Comments If the website is not behind a load balancer or proxy server, this is Not Applicable. Source: _Reviewed/MONT-MB-002/Checklist/MONT-MB-002_IIS10Site_Exchange_Back_End_V2R12_20251023-152602.ckl Scan Date: 2026-01-14T12:57:33.300070 Technology Area: Web Review
V-218740	CAT II	MONT-DP-001	Microsoft IIS 10.0 Site Security Technic...	An IIS 10.0 website behind a load balancer or prox...	-
Check Text Interview the System Administrator to review the configuration of the IIS 10.0 architecture and determine if inbound web traffic is passed through a proxy. If the IIS 10.0 is receiving inbound web traffic through a proxy, the audit logs must be reviewed to determine if correct source information is being passed through by the proxy server. 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. Click the "Logging" icon. Click "View log file". When log file is displayed, review source IP information in log entries and verify entries do not reflect the IP address of the proxy server. If the website is not behind a load balancer or proxy server, this is Not Applicable. If the log entries in the log file(s) reflect the IP address of the proxy server as the source, this is a finding. If provisions have been made to log the client IP via another field (i.e., utilizing X-Forwarded-For), this is not a finding. Fix Text Access the proxy server through which inbound web traffic is passed and configure settings to pass web traffic to the IIS 10.0 web server transparently. Comments If the website is not behind a load balancer or proxy server, this is Not Applicable. Source: _Reviewed/MONT-DP-001/Checklist/MONT-DP-001_IIS10Site_Default_Web_Site_V2R12_20251023-143912.ckl Scan Date: 2026-01-14T12:57:35.375369 Technology Area: Web Review
V-218741	CAT II	MONT-MB-002	Microsoft IIS 10.0 Site Security Technic...	The IIS 10.0 website must produce log records that...	-
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: Select the website being reviewed. 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 are selected: Request Header >> Connection Request Header >> Warning If any of the above fields are not selected, this is a finding. Fix Text Follow the procedures below for each site hosted on the IIS 10.0 web server: Select the website being reviewed. Under "IIS", double-click the "Logging" icon. Configure the "Format:" under "Log File" to "W3C". Select "Fields". Under "Custom Fields", select the following fields: Request Header >> Connection Request Header >> Warning Click "OK". Select "Apply" from the "Actions" pane. Finding Details Evaluate-STIG 1.2507.5 (Scan-IIS10_0_Site_Checks) found this to be OPEN on 10/23/2025 Site: Default Web Site ResultHash: 7599E6F84AF0FE02631E378C3BDEFF3AC6CE19D6 ~~~~~ Log format is 'W3C' The 'Request Header >> Connection' custom field is NOT configured. The 'Request Header >> Warning' custom field is NOT configured. Source: _Reviewed/MONT-MB-002/Checklist/MONT-MB-002_IIS10Site_Default_Web_Site_V2R12_20251023-152518.ckl Scan Date: 2026-01-14T12:57:33.098574 Technology Area: Web Review
V-218741	CAT II	MONT-MB-002	Microsoft IIS 10.0 Site Security Technic...	The IIS 10.0 website must produce log records that...	-
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: Select the website being reviewed. 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 are selected: Request Header >> Connection Request Header >> Warning If any of the above fields are not selected, this is a finding. Fix Text Follow the procedures below for each site hosted on the IIS 10.0 web server: Select the website being reviewed. Under "IIS", double-click the "Logging" icon. Configure the "Format:" under "Log File" to "W3C". Select "Fields". Under "Custom Fields", select the following fields: Request Header >> Connection Request Header >> Warning Click "OK". Select "Apply" from the "Actions" pane. Finding Details Evaluate-STIG 1.2507.5 (Scan-IIS10_0_Site_Checks) found this to be OPEN on 10/23/2025 Site: Exchange Back End ResultHash: 7599E6F84AF0FE02631E378C3BDEFF3AC6CE19D6 ~~~~~ Log format is 'W3C' The 'Request Header >> Connection' custom field is NOT configured. The 'Request Header >> Warning' custom field is NOT configured. Source: _Reviewed/MONT-MB-002/Checklist/MONT-MB-002_IIS10Site_Exchange_Back_End_V2R12_20251023-152602.ckl Scan Date: 2026-01-14T12:57:33.300070 Technology Area: Web Review
V-218741	CAT II	MONT-DP-001	Microsoft IIS 10.0 Site Security Technic...	The IIS 10.0 website must produce log records that...	-
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: Select the website being reviewed. 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 are selected: Request Header >> Connection Request Header >> Warning If any of the above fields are not selected, this is a finding. Fix Text Follow the procedures below for each site hosted on the IIS 10.0 web server: Select the website being reviewed. Under "IIS", double-click the "Logging" icon. Configure the "Format:" under "Log File" to "W3C". Select "Fields". Under "Custom Fields", select the following fields: Request Header >> Connection Request Header >> Warning Click "OK". Select "Apply" from the "Actions" pane. Finding Details Evaluate-STIG 1.2507.5 (Scan-IIS10_0_Site_Checks) found this to be OPEN on 10/23/2025 Site: Default Web Site 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 If the server is hosting WSUS, this is Not Applicable. Source: _Reviewed/MONT-DP-001/Checklist/MONT-DP-001_IIS10Site_Default_Web_Site_V2R12_20251023-143912.ckl Scan Date: 2026-01-14T12:57:35.375369 Technology Area: Web Review
V-218742	CAT II	MONT-MB-002	Microsoft IIS 10.0 Site Security Technic...	The IIS 10.0 website must produce log records cont...	-
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: Access the IIS 10.0 web server IIS 10.0 Manager. 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 fields have been configured: Request Header >> Authorization Response Header >> Content-Type If any of the above fields are not selected, 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 web server IIS 10.0 Manager. Select the website being reviewed. Under "IIS", double-click the "Logging" icon. Configure the "Format:" under "Log File" to "W3C". Select "Fields". Under "Standard Fields", select "User Agent", "User Name", and "Referrer". Under "Custom Fields", select the following fields: Request Header >> Authorization Response Header >> Content-Type Click "OK". Select "Apply" from the "Actions" pane. Finding Details Evaluate-STIG 1.2507.5 (Scan-IIS10_0_Site_Checks) found this to be OPEN on 10/23/2025 Site: Default Web Site 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. Source: _Reviewed/MONT-MB-002/Checklist/MONT-MB-002_IIS10Site_Default_Web_Site_V2R12_20251023-152518.ckl Scan Date: 2026-01-14T12:57:33.098574 Technology Area: Web Review
V-218742	CAT II	MONT-MB-002	Microsoft IIS 10.0 Site Security Technic...	The IIS 10.0 website must produce log records cont...	-
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: Access the IIS 10.0 web server IIS 10.0 Manager. 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 fields have been configured: Request Header >> Authorization Response Header >> Content-Type If any of the above fields are not selected, 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 web server IIS 10.0 Manager. Select the website being reviewed. Under "IIS", double-click the "Logging" icon. Configure the "Format:" under "Log File" to "W3C". Select "Fields". Under "Standard Fields", select "User Agent", "User Name", and "Referrer". Under "Custom Fields", select the following fields: Request Header >> Authorization Response Header >> Content-Type Click "OK". Select "Apply" from the "Actions" pane. Finding Details Evaluate-STIG 1.2507.5 (Scan-IIS10_0_Site_Checks) found this to be OPEN on 10/23/2025 Site: Exchange Back End 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. Source: _Reviewed/MONT-MB-002/Checklist/MONT-MB-002_IIS10Site_Exchange_Back_End_V2R12_20251023-152602.ckl Scan Date: 2026-01-14T12:57:33.300070 Technology Area: Web Review
V-218742	CAT II	MONT-DP-001	Microsoft IIS 10.0 Site Security Technic...	The IIS 10.0 website must produce log records cont...	-
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: Access the IIS 10.0 web server IIS 10.0 Manager. 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 fields have been configured: Request Header >> Authorization Response Header >> Content-Type If any of the above fields are not selected, 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 web server IIS 10.0 Manager. Select the website being reviewed. Under "IIS", double-click the "Logging" icon. Configure the "Format:" under "Log File" to "W3C". Select "Fields". Under "Standard Fields", select "User Agent", "User Name", and "Referrer". Under "Custom Fields", select the following fields: Request Header >> Authorization Response Header >> Content-Type Click "OK". Select "Apply" from the "Actions" pane. Finding Details Evaluate-STIG 1.2507.5 (Scan-IIS10_0_Site_Checks) found this to be OPEN on 10/23/2025 Site: Default Web Site 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 If the server is hosting WSUS, this is Not Applicable. Source: _Reviewed/MONT-DP-001/Checklist/MONT-DP-001_IIS10Site_Default_Web_Site_V2R12_20251023-143912.ckl Scan Date: 2026-01-14T12:57:35.375369 Technology Area: Web Review
V-218743	CAT II	MONT-MB-002	Microsoft IIS 10.0 Site Security Technic...	The IIS 10.0 website must have Multipurpose Intern...	-
Check Text Note: If the server is hosting WSUS, this is not applicable. Follow the procedures below for each site hosted on the IIS 10.0 web server: Open the IIS 10.0 Manager. Click on the IIS 10.0 site. 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 Follow the procedures below for each site hosted on the IIS 10.0 web server: Open the IIS 10.0 Manager. Click on the IIS 10.0 site. 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 Select "Apply" from the "Actions" pane. Finding Details Evaluate-STIG 1.2507.5 (Scan-IIS10_0_Site_Checks) found this to be OPEN on 10/23/2025 Site: Default Web Site ResultHash: 655AA1250F9F447877A75E551AC19473E3E576A5 ~~~~~ WSUS Hosted: False The following invalid MIME types for OS shell program extensions are configured: .exe .dll .csh Source: _Reviewed/MONT-MB-002/Checklist/MONT-MB-002_IIS10Site_Default_Web_Site_V2R12_20251023-152518.ckl Scan Date: 2026-01-14T12:57:33.098574 Technology Area: Web Review
V-218743	CAT II	MONT-MB-002	Microsoft IIS 10.0 Site Security Technic...	The IIS 10.0 website must have Multipurpose Intern...	-
Check Text Note: If the server is hosting WSUS, this is not applicable. Follow the procedures below for each site hosted on the IIS 10.0 web server: Open the IIS 10.0 Manager. Click on the IIS 10.0 site. 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 Follow the procedures below for each site hosted on the IIS 10.0 web server: Open the IIS 10.0 Manager. Click on the IIS 10.0 site. 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 Select "Apply" from the "Actions" pane. Finding Details Evaluate-STIG 1.2507.5 (Scan-IIS10_0_Site_Checks) found this to be OPEN on 10/23/2025 Site: Exchange Back End ResultHash: 655AA1250F9F447877A75E551AC19473E3E576A5 ~~~~~ WSUS Hosted: False The following invalid MIME types for OS shell program extensions are configured: .exe .dll .csh Source: _Reviewed/MONT-MB-002/Checklist/MONT-MB-002_IIS10Site_Exchange_Back_End_V2R12_20251023-152602.ckl Scan Date: 2026-01-14T12:57:33.300070 Technology Area: Web Review
V-218743	CAT II	MONT-DP-001	Microsoft IIS 10.0 Site Security Technic...	The IIS 10.0 website must have Multipurpose Intern...	-
Check Text Note: If the server is hosting WSUS, this is not applicable. Follow the procedures below for each site hosted on the IIS 10.0 web server: Open the IIS 10.0 Manager. Click on the IIS 10.0 site. 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 Follow the procedures below for each site hosted on the IIS 10.0 web server: Open the IIS 10.0 Manager. Click on the IIS 10.0 site. 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 Select "Apply" from the "Actions" pane. Finding Details Evaluate-STIG 1.2507.5 (Scan-IIS10_0_Site_Checks) found this to be OPEN on 10/23/2025 Site: Default Web Site ResultHash: 655AA1250F9F447877A75E551AC19473E3E576A5 ~~~~~ WSUS Hosted: False The following invalid MIME types for OS shell program extensions are configured: .exe .dll .csh Comments If the server is hosting WSUS, this is Not Applicable. Source: _Reviewed/MONT-DP-001/Checklist/MONT-DP-001_IIS10Site_Default_Web_Site_V2R12_20251023-143912.ckl Scan Date: 2026-01-14T12:57:35.375369 Technology Area: Web Review
V-218744	CAT II	MONT-MB-002	Microsoft IIS 10.0 Site Security Technic...	Mappings to unused and vulnerable scripts on the I...	-
Check Text Note: If the server being reviewed is hosting SharePoint, 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. Fix Text Open the IIS 10.0 Manager. Click the site name under review. Double-click "Handler Mappings". Remove any script file extensions listed on the black list that are enabled. Select "Apply" from the "Actions" pane. Finding Details Evaluate-STIG 1.2507.5 (Scan-IIS10_0_Site_Checks) was unable to determine a Status but found the below configuration on 10/23/2025: Site: Default Web Site ResultHash: 8356F37642CEDEB903ECD7759F6B764F91491675 ~~~~~ Access Policy: Read,Script Enabled Handler Mappings: ----------------------------------- Name: xamlx-ISAPI-4.0_64bit Path: .xamlx State: Enabled PathType: Unspecified Handler: IsapiModule ReqAccess: Script Name: xamlx-ISAPI-4.0_32bit Path: .xamlx State: Enabled PathType: Unspecified Handler: IsapiModule ReqAccess: Script Name: xamlx-Integrated-4.0 Path: .xamlx State: Enabled PathType: Unspecified Handler: ManagedPipelineHandler ReqAccess: Script Name: rules-ISAPI-4.0_64bit Path: .rules State: Enabled PathType: Unspecified Handler: IsapiModule ReqAccess: Script Name: rules-ISAPI-4.0_32bit Path: .rules State: Enabled PathType: Unspecified Handler: IsapiModule ReqAccess: Script Name: rules-Integrated-4.0 Path: .rules State: Enabled PathType: Unspecified Handler: ManagedPipelineHandler ReqAccess: Script Name: xoml-ISAPI-4.0_64bit Path: .xoml State: Enabled PathType: Unspecified Handler: IsapiModule ReqAccess: Script Name: xoml-ISAPI-4.0_32bit Path: .xoml State: Enabled PathType: Unspecified Handler: IsapiModule ReqAccess: Script Name: xoml-Integrated-4.0 Path: .xoml State: Enabled PathType: Unspecified Handler: ManagedPipelineHandler ReqAccess: Script Name: svc-ISAPI-4.0_64bit Path: .svc State: Enabled PathType: Unspecified Handler: IsapiModule ReqAccess: Script Name: svc-ISAPI-4.0_32bit Path: .svc State: Enabled PathType: Unspecified Handler: IsapiModule ReqAccess: Script Name: svc-Integrated-4.0 Path: .svc State: Enabled PathType: Unspecified Handler: ManagedPipelineHandler ReqAccess: Script Name: AXD-ISAPI-4.0_64bit Path: .axd State: Enabled PathType: Unspecified Handler: IsapiModule ReqAccess: Script Name: PageHandlerFactory-ISAPI-4.0_64bit Path: .aspx State: Enabled PathType: Unspecified Handler: IsapiModule ReqAccess: Script Name: SimpleHandlerFactory-ISAPI-4.0_64bit Path: .ashx State: Enabled PathType: Unspecified Handler: IsapiModule ReqAccess: Script Name: WebServiceHandlerFactory-ISAPI-4.0_64bit Path: .asmx State: Enabled PathType: Unspecified Handler: IsapiModule ReqAccess: Script Name: HttpRemotingHandlerFactory-rem-ISAPI-4.0_64bit Path: .rem State: Enabled PathType: Unspecified Handler: IsapiModule ReqAccess: Script Name: HttpRemotingHandlerFactory-soap-ISAPI-4.0_64bit Path: .soap State: Enabled PathType: Unspecified Handler: IsapiModule ReqAccess: Script Name: aspq-ISAPI-4.0_64bit Path: .aspq State: Enabled PathType: Unspecified Handler: IsapiModule ReqAccess: Script Name: cshtm-ISAPI-4.0_64bit Path: .cshtm State: Enabled PathType: Unspecified Handler: IsapiModule ReqAccess: Script Name: cshtml-ISAPI-4.0_64bit Path: .cshtml State: Enabled PathType: Unspecified Handler: IsapiModule ReqAccess: Script Name: vbhtm-ISAPI-4.0_64bit Path: .vbhtm State: Enabled PathType: Unspecified Handler: IsapiModule ReqAccess: Script Name: vbhtml-ISAPI-4.0_64bit Path: .vbhtml State: Enabled PathType: Unspecified Handler: IsapiModule ReqAccess: Script Name: TraceHandler-Integrated-4.0 Path: trace.axd State: Enabled PathType: Unspecified Handler: ManagedPipelineHandler ReqAccess: Script Name: WebAdminHandler-Integrated-4.0 Path: WebAdmin.axd State: Enabled PathType: Unspecified Handler: ManagedPipelineHandler ReqAccess: Script Name: AssemblyResourceLoader-Integrated-4.0 Path: WebResource.axd State: Enabled PathType: Unspecified Handler: ManagedPipelineHandler ReqAccess: Script Name: PageHandlerFactory-Integrated-4.0 Path: .aspx State: Enabled PathType: Unspecified Handler: ManagedPipelineHandler ReqAccess: Script Name: SimpleHandlerFactory-Integrated-4.0 Path: .ashx State: Enabled PathType: Unspecified Handler: ManagedPipelineHandler ReqAccess: Script Name: WebServiceHandlerFactory-Integrated-4.0 Path: .asmx State: Enabled PathType: Unspecified Handler: ManagedPipelineHandler ReqAccess: Script Name: HttpRemotingHandlerFactory-rem-Integrated-4.0 Path: .rem State: Enabled PathType: Unspecified Handler: ManagedPipelineHandler ReqAccess: Script Name: HttpRemotingHandlerFactory-soap-Integrated-4.0 Path: .soap State: Enabled PathType: Unspecified Handler: ManagedPipelineHandler ReqAccess: Script Name: aspq-Integrated-4.0 Path: .aspq State: Enabled PathType: Unspecified Handler: ManagedPipelineHandler ReqAccess: Script Name: cshtm-Integrated-4.0 Path: .cshtm State: Enabled PathType: Unspecified Handler: ManagedPipelineHandler ReqAccess: Script Name: cshtml-Integrated-4.0 Path: .cshtml State: Enabled PathType: Unspecified Handler: ManagedPipelineHandler ReqAccess: Script Name: vbhtm-Integrated-4.0 Path: .vbhtm State: Enabled PathType: Unspecified Handler: ManagedPipelineHandler ReqAccess: Script Name: vbhtml-Integrated-4.0 Path: .vbhtml State: Enabled PathType: Unspecified Handler: ManagedPipelineHandler ReqAccess: Script Name: ScriptHandlerFactoryAppServices-Integrated-4.0 Path: _AppService.axd State: Enabled PathType: Unspecified Handler: ManagedPipelineHandler ReqAccess: Script Name: ScriptResourceIntegrated-4.0 Path: ScriptResource.axd State: Enabled PathType: Unspecified Handler: ManagedPipelineHandler ReqAccess: Script Name: AXD-ISAPI-4.0_32bit Path: .axd State: Enabled PathType: Unspecified Handler: IsapiModule ReqAccess: Script Name: PageHandlerFactory-ISAPI-4.0_32bit Path: .aspx State: Enabled PathType: Unspecified Handler: IsapiModule ReqAccess: Script Name: SimpleHandlerFactory-ISAPI-4.0_32bit Path: .ashx State: Enabled PathType: Unspecified Handler: IsapiModule ReqAccess: Script Name: WebServiceHandlerFactory-ISAPI-4.0_32bit Path: .asmx State: Enabled PathType: Unspecified Handler: IsapiModule ReqAccess: Script Name: HttpRemotingHandlerFactory-rem-ISAPI-4.0_32bit Path: .rem State: Enabled PathType: Unspecified Handler: IsapiModule ReqAccess: Script Name: HttpRemotingHandlerFactory-soap-ISAPI-4.0_32bit Path: .soap State: Enabled PathType: Unspecified Handler: IsapiModule ReqAccess: Script Name: aspq-ISAPI-4.0_32bit Path: .aspq State: Enabled PathType: Unspecified Handler: IsapiModule ReqAccess: Script Name: cshtm-ISAPI-4.0_32bit Path: .cshtm State: Enabled PathType: Unspecified Handler: IsapiModule ReqAccess: Script Name: cshtml-ISAPI-4.0_32bit Path: .cshtml State: Enabled PathType: Unspecified Handler: IsapiModule ReqAccess: Script Name: vbhtm-ISAPI-4.0_32bit Path: .vbhtm State: Enabled PathType: Unspecified Handler: IsapiModule ReqAccess: Script Name: vbhtml-ISAPI-4.0_32bit Path: .vbhtml State: Enabled PathType: Unspecified Handler: IsapiModule ReqAccess: Script Name: TRACEVerbHandler Path: * State: Enabled PathType: Unspecified Handler: ProtocolSupportModule ReqAccess: None Name: OPTIONSVerbHandler Path: * State: Enabled PathType: Unspecified Handler: ProtocolSupportModule ReqAccess: None Name: ExtensionlessUrlHandler-ISAPI-4.0_32bit Path: . State: Enabled PathType: Unspecified Handler: IsapiModule ReqAccess: Script Name: ExtensionlessUrlHandler-ISAPI-4.0_64bit Path: . State: Enabled PathType: Unspecified Handler: IsapiModule ReqAccess: Script Name: ExtensionlessUrlHandler-Integrated-4.0 Path: . State: Enabled PathType: Unspecified Handler: ManagedPipelineHandler ReqAccess: Script Name: StaticFile Path: State: Enabled PathType: File or Folder Handler: StaticFileModule,DefaultDocumentModule,DirectoryListingModule ReqAccess: Read Disabled Handler Mappings: ----------------------------------- Name: ISAPI-dll Path: *.dll State: Disabled PathType: File Handler: IsapiModule ReqAccess: Execute Comments Documentation: For Handler Mappings, the ISSO must document and approve all allowable file extensions the website allows (white list) and denies (black list). Source: _Reviewed/MONT-MB-002/Checklist/MONT-MB-002_IIS10Site_Default_Web_Site_V2R12_20251023-152518.ckl Scan Date: 2026-01-14T12:57:33.098574 Technology Area: Web Review
V-218744	CAT II	MONT-MB-002	Microsoft IIS 10.0 Site Security Technic...	Mappings to unused and vulnerable scripts on the I...	-
Check Text Note: If the server being reviewed is hosting SharePoint, 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. Fix Text Open the IIS 10.0 Manager. Click the site name under review. Double-click "Handler Mappings". Remove any script file extensions listed on the black list that are enabled. Select "Apply" from the "Actions" pane. Finding Details Evaluate-STIG 1.2507.5 (Scan-IIS10_0_Site_Checks) was unable to determine a Status but found the below configuration on 10/23/2025: Site: Exchange Back End ResultHash: 8356F37642CEDEB903ECD7759F6B764F91491675 ~~~~~ Access Policy: Read,Script Enabled Handler Mappings: ----------------------------------- Name: xamlx-ISAPI-4.0_64bit Path: .xamlx State: Enabled PathType: Unspecified Handler: IsapiModule ReqAccess: Script Name: xamlx-ISAPI-4.0_32bit Path: .xamlx State: Enabled PathType: Unspecified Handler: IsapiModule ReqAccess: Script Name: xamlx-Integrated-4.0 Path: .xamlx State: Enabled PathType: Unspecified Handler: ManagedPipelineHandler ReqAccess: Script Name: rules-ISAPI-4.0_64bit Path: .rules State: Enabled PathType: Unspecified Handler: IsapiModule ReqAccess: Script Name: rules-ISAPI-4.0_32bit Path: .rules State: Enabled PathType: Unspecified Handler: IsapiModule ReqAccess: Script Name: rules-Integrated-4.0 Path: .rules State: Enabled PathType: Unspecified Handler: ManagedPipelineHandler ReqAccess: Script Name: xoml-ISAPI-4.0_64bit Path: .xoml State: Enabled PathType: Unspecified Handler: IsapiModule ReqAccess: Script Name: xoml-ISAPI-4.0_32bit Path: .xoml State: Enabled PathType: Unspecified Handler: IsapiModule ReqAccess: Script Name: xoml-Integrated-4.0 Path: .xoml State: Enabled PathType: Unspecified Handler: ManagedPipelineHandler ReqAccess: Script Name: svc-ISAPI-4.0_64bit Path: .svc State: Enabled PathType: Unspecified Handler: IsapiModule ReqAccess: Script Name: svc-ISAPI-4.0_32bit Path: .svc State: Enabled PathType: Unspecified Handler: IsapiModule ReqAccess: Script Name: svc-Integrated-4.0 Path: .svc State: Enabled PathType: Unspecified Handler: ManagedPipelineHandler ReqAccess: Script Name: AXD-ISAPI-4.0_64bit Path: .axd State: Enabled PathType: Unspecified Handler: IsapiModule ReqAccess: Script Name: PageHandlerFactory-ISAPI-4.0_64bit Path: .aspx State: Enabled PathType: Unspecified Handler: IsapiModule ReqAccess: Script Name: SimpleHandlerFactory-ISAPI-4.0_64bit Path: .ashx State: Enabled PathType: Unspecified Handler: IsapiModule ReqAccess: Script Name: WebServiceHandlerFactory-ISAPI-4.0_64bit Path: .asmx State: Enabled PathType: Unspecified Handler: IsapiModule ReqAccess: Script Name: HttpRemotingHandlerFactory-rem-ISAPI-4.0_64bit Path: .rem State: Enabled PathType: Unspecified Handler: IsapiModule ReqAccess: Script Name: HttpRemotingHandlerFactory-soap-ISAPI-4.0_64bit Path: .soap State: Enabled PathType: Unspecified Handler: IsapiModule ReqAccess: Script Name: aspq-ISAPI-4.0_64bit Path: .aspq State: Enabled PathType: Unspecified Handler: IsapiModule ReqAccess: Script Name: cshtm-ISAPI-4.0_64bit Path: .cshtm State: Enabled PathType: Unspecified Handler: IsapiModule ReqAccess: Script Name: cshtml-ISAPI-4.0_64bit Path: .cshtml State: Enabled PathType: Unspecified Handler: IsapiModule ReqAccess: Script Name: vbhtm-ISAPI-4.0_64bit Path: .vbhtm State: Enabled PathType: Unspecified Handler: IsapiModule ReqAccess: Script Name: vbhtml-ISAPI-4.0_64bit Path: .vbhtml State: Enabled PathType: Unspecified Handler: IsapiModule ReqAccess: Script Name: TraceHandler-Integrated-4.0 Path: trace.axd State: Enabled PathType: Unspecified Handler: ManagedPipelineHandler ReqAccess: Script Name: WebAdminHandler-Integrated-4.0 Path: WebAdmin.axd State: Enabled PathType: Unspecified Handler: ManagedPipelineHandler ReqAccess: Script Name: AssemblyResourceLoader-Integrated-4.0 Path: WebResource.axd State: Enabled PathType: Unspecified Handler: ManagedPipelineHandler ReqAccess: Script Name: PageHandlerFactory-Integrated-4.0 Path: .aspx State: Enabled PathType: Unspecified Handler: ManagedPipelineHandler ReqAccess: Script Name: SimpleHandlerFactory-Integrated-4.0 Path: .ashx State: Enabled PathType: Unspecified Handler: ManagedPipelineHandler ReqAccess: Script Name: WebServiceHandlerFactory-Integrated-4.0 Path: .asmx State: Enabled PathType: Unspecified Handler: ManagedPipelineHandler ReqAccess: Script Name: HttpRemotingHandlerFactory-rem-Integrated-4.0 Path: .rem State: Enabled PathType: Unspecified Handler: ManagedPipelineHandler ReqAccess: Script Name: HttpRemotingHandlerFactory-soap-Integrated-4.0 Path: .soap State: Enabled PathType: Unspecified Handler: ManagedPipelineHandler ReqAccess: Script Name: aspq-Integrated-4.0 Path: .aspq State: Enabled PathType: Unspecified Handler: ManagedPipelineHandler ReqAccess: Script Name: cshtm-Integrated-4.0 Path: .cshtm State: Enabled PathType: Unspecified Handler: ManagedPipelineHandler ReqAccess: Script Name: cshtml-Integrated-4.0 Path: .cshtml State: Enabled PathType: Unspecified Handler: ManagedPipelineHandler ReqAccess: Script Name: vbhtm-Integrated-4.0 Path: .vbhtm State: Enabled PathType: Unspecified Handler: ManagedPipelineHandler ReqAccess: Script Name: vbhtml-Integrated-4.0 Path: .vbhtml State: Enabled PathType: Unspecified Handler: ManagedPipelineHandler ReqAccess: Script Name: ScriptHandlerFactoryAppServices-Integrated-4.0 Path: _AppService.axd State: Enabled PathType: Unspecified Handler: ManagedPipelineHandler ReqAccess: Script Name: ScriptResourceIntegrated-4.0 Path: ScriptResource.axd State: Enabled PathType: Unspecified Handler: ManagedPipelineHandler ReqAccess: Script Name: AXD-ISAPI-4.0_32bit Path: .axd State: Enabled PathType: Unspecified Handler: IsapiModule ReqAccess: Script Name: PageHandlerFactory-ISAPI-4.0_32bit Path: .aspx State: Enabled PathType: Unspecified Handler: IsapiModule ReqAccess: Script Name: SimpleHandlerFactory-ISAPI-4.0_32bit Path: .ashx State: Enabled PathType: Unspecified Handler: IsapiModule ReqAccess: Script Name: WebServiceHandlerFactory-ISAPI-4.0_32bit Path: .asmx State: Enabled PathType: Unspecified Handler: IsapiModule ReqAccess: Script Name: HttpRemotingHandlerFactory-rem-ISAPI-4.0_32bit Path: .rem State: Enabled PathType: Unspecified Handler: IsapiModule ReqAccess: Script Name: HttpRemotingHandlerFactory-soap-ISAPI-4.0_32bit Path: .soap State: Enabled PathType: Unspecified Handler: IsapiModule ReqAccess: Script Name: aspq-ISAPI-4.0_32bit Path: .aspq State: Enabled PathType: Unspecified Handler: IsapiModule ReqAccess: Script Name: cshtm-ISAPI-4.0_32bit Path: .cshtm State: Enabled PathType: Unspecified Handler: IsapiModule ReqAccess: Script Name: cshtml-ISAPI-4.0_32bit Path: .cshtml State: Enabled PathType: Unspecified Handler: IsapiModule ReqAccess: Script Name: vbhtm-ISAPI-4.0_32bit Path: .vbhtm State: Enabled PathType: Unspecified Handler: IsapiModule ReqAccess: Script Name: vbhtml-ISAPI-4.0_32bit Path: .vbhtml State: Enabled PathType: Unspecified Handler: IsapiModule ReqAccess: Script Name: TRACEVerbHandler Path: * State: Enabled PathType: Unspecified Handler: ProtocolSupportModule ReqAccess: None Name: OPTIONSVerbHandler Path: * State: Enabled PathType: Unspecified Handler: ProtocolSupportModule ReqAccess: None Name: ExtensionlessUrlHandler-ISAPI-4.0_32bit Path: . State: Enabled PathType: Unspecified Handler: IsapiModule ReqAccess: Script Name: ExtensionlessUrlHandler-ISAPI-4.0_64bit Path: . State: Enabled PathType: Unspecified Handler: IsapiModule ReqAccess: Script Name: ExtensionlessUrlHandler-Integrated-4.0 Path: . State: Enabled PathType: Unspecified Handler: ManagedPipelineHandler ReqAccess: Script Name: StaticFile Path: State: Enabled PathType: File or Folder Handler: StaticFileModule,DefaultDocumentModule,DirectoryListingModule ReqAccess: Read Disabled Handler Mappings: ----------------------------------- Name: ISAPI-dll Path: *.dll State: Disabled PathType: File Handler: IsapiModule ReqAccess: Execute Comments Documentation: For Handler Mappings, the ISSO must document and approve all allowable scripts the website allows (white list) and denies (black list). Source: _Reviewed/MONT-MB-002/Checklist/MONT-MB-002_IIS10Site_Exchange_Back_End_V2R12_20251023-152602.ckl Scan Date: 2026-01-14T12:57:33.300070 Technology Area: Web Review
V-218744	CAT II	MONT-DP-001	Microsoft IIS 10.0 Site Security Technic...	Mappings to unused and vulnerable scripts on the I...	-
Check Text Note: If the server being reviewed is hosting SharePoint, 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. Fix Text Open the IIS 10.0 Manager. Click the site name under review. Double-click "Handler Mappings". Remove any script file extensions listed on the black list that are enabled. Select "Apply" from the "Actions" pane. Finding Details Evaluate-STIG 1.2507.5 (Scan-IIS10_0_Site_Checks) was unable to determine a Status but found the below configuration on 10/23/2025: Site: Default Web Site ResultHash: 964A425E614B45D739FF9628D93B9C7268F1E643 ~~~~~ Access Policy: Read,Script Enabled Handler Mappings: ----------------------------------- Name: TRACEVerbHandler Path: * State: Enabled PathType: Unspecified Handler: ProtocolSupportModule ReqAccess: None Name: OPTIONSVerbHandler Path: * State: Enabled PathType: Unspecified Handler: ProtocolSupportModule ReqAccess: None Name: StaticFile Path: * State: Enabled PathType: File or Folder Handler: StaticFileModule,DefaultDocumentModule,DirectoryListingModule ReqAccess: Read Disabled Handler Mappings: ----------------------------------- Name: ISAPI-dll Path: *.dll State: Disabled PathType: File Handler: IsapiModule ReqAccess: Execute Comments documentation Source: _Reviewed/MONT-DP-001/Checklist/MONT-DP-001_IIS10Site_Default_Web_Site_V2R12_20251023-143912.ckl Scan Date: 2026-01-14T12:57:35.375369 Technology Area: Web Review
V-218745	CAT II	MONT-MB-002	Microsoft IIS 10.0 Site Security Technic...	The IIS 10.0 website must have resource mappings s...	-
Check Text Note: If the server being reviewed is hosting SharePoint, 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. 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 to review. Double-click Request Filtering->File Name Extensions Tab->Deny File Name Extension. Add any script file extensions listed on the black list that are not listed. Select "Apply" from the "Actions" pane. Finding Details Evaluate-STIG 1.2507.5 (Scan-IIS10_0_Site_Checks) was unable to determine a Status but found the below configuration on 10/23/2025: Site: Default Web Site ResultHash: 2F23BA53ABD5080AF448F9773A244BEC788276EC ~~~~~ Denied file extensions: ----------------------------------- FileExtension: .asax Allowed: False FileExtension: .ascx Allowed: False FileExtension: .master Allowed: False FileExtension: .skin Allowed: False FileExtension: .browser Allowed: False FileExtension: .sitemap Allowed: False FileExtension: .config Allowed: False FileExtension: .cs Allowed: False FileExtension: .csproj Allowed: False FileExtension: .vb Allowed: False FileExtension: .vbproj Allowed: False FileExtension: .webinfo Allowed: False FileExtension: .licx Allowed: False FileExtension: .resx Allowed: False FileExtension: .resources Allowed: False FileExtension: .mdb Allowed: False FileExtension: .vjsproj Allowed: False FileExtension: .java Allowed: False FileExtension: .jsl Allowed: False FileExtension: .ldb Allowed: False FileExtension: .dsdgm Allowed: False FileExtension: .ssdgm Allowed: False FileExtension: .lsad Allowed: False FileExtension: .ssmap Allowed: False FileExtension: .cd Allowed: False FileExtension: .dsprototype Allowed: False FileExtension: .lsaprototype Allowed: False FileExtension: .sdm Allowed: False FileExtension: .sdmDocument Allowed: False FileExtension: .mdf Allowed: False FileExtension: .ldf Allowed: False FileExtension: .ad Allowed: False FileExtension: .dd Allowed: False FileExtension: .ldd Allowed: False FileExtension: .sd Allowed: False FileExtension: .adprototype Allowed: False FileExtension: .lddprototype Allowed: False FileExtension: .exclude Allowed: False FileExtension: .refresh Allowed: False FileExtension: .compiled Allowed: False FileExtension: .msgx Allowed: False FileExtension: .vsdisco Allowed: False FileExtension: .rules Allowed: False Allowed file extensions: ----------------------------------- None Comments None are allowed. Source: _Reviewed/MONT-MB-002/Checklist/MONT-MB-002_IIS10Site_Default_Web_Site_V2R12_20251023-152518.ckl Scan Date: 2026-01-14T12:57:33.098574 Technology Area: Web Review
V-218745	CAT II	MONT-MB-002	Microsoft IIS 10.0 Site Security Technic...	The IIS 10.0 website must have resource mappings s...	-
Check Text Note: If the server being reviewed is hosting SharePoint, 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. 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 to review. Double-click Request Filtering->File Name Extensions Tab->Deny File Name Extension. Add any script file extensions listed on the black list that are not listed. Select "Apply" from the "Actions" pane. Finding Details Evaluate-STIG 1.2507.5 (Scan-IIS10_0_Site_Checks) was unable to determine a Status but found the below configuration on 10/23/2025: Site: Exchange Back End ResultHash: 2F23BA53ABD5080AF448F9773A244BEC788276EC ~~~~~ Denied file extensions: ----------------------------------- FileExtension: .asax Allowed: False FileExtension: .ascx Allowed: False FileExtension: .master Allowed: False FileExtension: .skin Allowed: False FileExtension: .browser Allowed: False FileExtension: .sitemap Allowed: False FileExtension: .config Allowed: False FileExtension: .cs Allowed: False FileExtension: .csproj Allowed: False FileExtension: .vb Allowed: False FileExtension: .vbproj Allowed: False FileExtension: .webinfo Allowed: False FileExtension: .licx Allowed: False FileExtension: .resx Allowed: False FileExtension: .resources Allowed: False FileExtension: .mdb Allowed: False FileExtension: .vjsproj Allowed: False FileExtension: .java Allowed: False FileExtension: .jsl Allowed: False FileExtension: .ldb Allowed: False FileExtension: .dsdgm Allowed: False FileExtension: .ssdgm Allowed: False FileExtension: .lsad Allowed: False FileExtension: .ssmap Allowed: False FileExtension: .cd Allowed: False FileExtension: .dsprototype Allowed: False FileExtension: .lsaprototype Allowed: False FileExtension: .sdm Allowed: False FileExtension: .sdmDocument Allowed: False FileExtension: .mdf Allowed: False FileExtension: .ldf Allowed: False FileExtension: .ad Allowed: False FileExtension: .dd Allowed: False FileExtension: .ldd Allowed: False FileExtension: .sd Allowed: False FileExtension: .adprototype Allowed: False FileExtension: .lddprototype Allowed: False FileExtension: .exclude Allowed: False FileExtension: .refresh Allowed: False FileExtension: .compiled Allowed: False FileExtension: .msgx Allowed: False FileExtension: .vsdisco Allowed: False FileExtension: .rules Allowed: False Allowed file extensions: ----------------------------------- None Comments None are allowed, do we still need documentation? Source: _Reviewed/MONT-MB-002/Checklist/MONT-MB-002_IIS10Site_Exchange_Back_End_V2R12_20251023-152602.ckl Scan Date: 2026-01-14T12:57:33.300070 Technology Area: Web Review
V-218745	CAT II	MONT-DP-001	Microsoft IIS 10.0 Site Security Technic...	The IIS 10.0 website must have resource mappings s...	-
Check Text Note: If the server being reviewed is hosting SharePoint, 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. 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 to review. Double-click Request Filtering->File Name Extensions Tab->Deny File Name Extension. Add any script file extensions listed on the black list that are not listed. Select "Apply" from the "Actions" pane. Finding Details Evaluate-STIG 1.2507.5 (Scan-IIS10_0_Site_Checks) was unable to determine a Status but found the below configuration on 10/23/2025: Site: Default Web Site ResultHash: AFF99CDFF730E9E82458BBFE44EC307E573D7F90 ~~~~~ Denied file extensions: ----------------------------------- None Allowed file extensions: ----------------------------------- None Comments documentation Source: _Reviewed/MONT-DP-001/Checklist/MONT-DP-001_IIS10Site_Default_Web_Site_V2R12_20251023-143912.ckl Scan Date: 2026-01-14T12:57:35.375369 Technology Area: Web Review
V-218748	CAT II	MONT-MB-002	Microsoft IIS 10.0 Site Security Technic...	Each IIS 10.0 website must be assigned a default h...	Documented Pending Review
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. 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. Note: If this IIS 10.0 installation is supporting Microsoft Exchange, and not otherwise hosting any content, this requirement is Not Applicable. Fix 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. Right-click on the site name under review. Select "Edit Bindings". Assign hostname entries and unique IP addresses to port 80 for HTTP and port 443 for HTTPS. Other approved and documented ports may be used. Click "OK". Select "Apply" from the "Actions" pane. Finding Details Evaluate-STIG 1.2507.5 (Scan-IIS10_0_Site_Checks) was unable to determine a Status but found the below configuration on 10/23/2025: Site: Default Web Site ResultHash: C4AC55E057470F8E3BE8026C2E97039D7E1B552C ~~~~~ Exchange service detected. If this server only hosts Microsoft Exchange, mark this check as NA. Service: MSExchangeServiceHost Status: Running Source: _Reviewed/MONT-MB-002/Checklist/MONT-MB-002_IIS10Site_Default_Web_Site_V2R12_20251023-152518.ckl Scan Date: 2026-01-14T12:57:33.098574 Technology Area: Web Review
V-218748	CAT II	MONT-MB-002	Microsoft IIS 10.0 Site Security Technic...	Each IIS 10.0 website must be assigned a default h...	Documented Pending Review
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. 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. Note: If this IIS 10.0 installation is supporting Microsoft Exchange, and not otherwise hosting any content, this requirement is Not Applicable. Fix 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. Right-click on the site name under review. Select "Edit Bindings". Assign hostname entries and unique IP addresses to port 80 for HTTP and port 443 for HTTPS. Other approved and documented ports may be used. Click "OK". Select "Apply" from the "Actions" pane. Finding Details Evaluate-STIG 1.2507.5 (Scan-IIS10_0_Site_Checks) was unable to determine a Status but found the below configuration on 10/23/2025: Site: Exchange Back End ResultHash: C4AC55E057470F8E3BE8026C2E97039D7E1B552C ~~~~~ Exchange service detected. If this server only hosts Microsoft Exchange, mark this check as NA. Service: MSExchangeServiceHost Status: Running Source: _Reviewed/MONT-MB-002/Checklist/MONT-MB-002_IIS10Site_Exchange_Back_End_V2R12_20251023-152602.ckl Scan Date: 2026-01-14T12:57:33.300070 Technology Area: Web Review
V-218748	CAT II	MONT-DP-001	Microsoft IIS 10.0 Site Security Technic...	Each IIS 10.0 website must be assigned a default h...	Documented Pending Review
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. 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. Note: If this IIS 10.0 installation is supporting Microsoft Exchange, and not otherwise hosting any content, this requirement is Not Applicable. Fix 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. Right-click on the site name under review. Select "Edit Bindings". Assign hostname entries and unique IP addresses to port 80 for HTTP and port 443 for HTTPS. Other approved and documented ports may be used. Click "OK". Select "Apply" from the "Actions" pane. Finding Details Evaluate-STIG 1.2507.5 (Scan-IIS10_0_Site_Checks) found this to be OPEN on 10/23/2025 Site: Default Web Site ResultHash: 8E8482E042BD27CE6D91B327DB52B5325B740854 ~~~~~ The site is NOT bound to a specific host header on port 80 Source: _Reviewed/MONT-DP-001/Checklist/MONT-DP-001_IIS10Site_Default_Web_Site_V2R12_20251023-143912.ckl Scan Date: 2026-01-14T12:57:35.375369 Technology Area: Web Review
V-218749	CAT II	MONT-MB-002	Microsoft IIS 10.0 Site Security Technic...	A private IIS 10.0 website authentication mechanis...	Documented Pending Review
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 certificate handling is performed at the Proxy/Load Balancer, 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 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. 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. Fix Text 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. Select "Apply" from the "Actions" pane. Finding Details Evaluate-STIG 1.2507.5 (Scan-IIS10_0_Site_Checks) found this to be OPEN on 10/23/2025 Site: Default Web Site ResultHash: C9147AB75E3FE047BDF3394C860E38FD3A03A4FC ~~~~~ Client Certificates is NOT set to 'Require' Confirm if this this is a public server. If so, mark this finding as Not Applicable. Source: _Reviewed/MONT-MB-002/Checklist/MONT-MB-002_IIS10Site_Default_Web_Site_V2R12_20251023-152518.ckl Scan Date: 2026-01-14T12:57:33.098574 Technology Area: Web Review
V-218749	CAT II	MONT-MB-002	Microsoft IIS 10.0 Site Security Technic...	A private IIS 10.0 website authentication mechanis...	Documented Pending Review
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 certificate handling is performed at the Proxy/Load Balancer, 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 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. 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. Fix Text 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. Select "Apply" from the "Actions" pane. Finding Details Evaluate-STIG 1.2507.5 (Scan-IIS10_0_Site_Checks) found this to be OPEN on 10/23/2025 Site: Exchange Back End ResultHash: C9147AB75E3FE047BDF3394C860E38FD3A03A4FC ~~~~~ Client Certificates is NOT set to 'Require' Confirm if this this is a public server. If so, mark this finding as Not Applicable. Source: _Reviewed/MONT-MB-002/Checklist/MONT-MB-002_IIS10Site_Exchange_Back_End_V2R12_20251023-152602.ckl Scan Date: 2026-01-14T12:57:33.300070 Technology Area: Web Review
V-218749	CAT II	MONT-DP-001	Microsoft IIS 10.0 Site Security Technic...	A private IIS 10.0 website authentication mechanis...	Documented Pending Review
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 certificate handling is performed at the Proxy/Load Balancer, 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 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. 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. Fix Text 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. Select "Apply" from the "Actions" pane. Finding Details Evaluate-STIG 1.2507.5 (Scan-IIS10_0_Site_Checks) found this to be OPEN on 10/23/2025 Site: Default Web Site ResultHash: C9147AB75E3FE047BDF3394C860E38FD3A03A4FC ~~~~~ Client Certificates is NOT set to 'Require' Confirm if this this is a public server. If so, mark this finding as Not Applicable. Comments If the server is hosting WSUS, this is Not Applicable. Source: _Reviewed/MONT-DP-001/Checklist/MONT-DP-001_IIS10Site_Default_Web_Site_V2R12_20251023-143912.ckl Scan Date: 2026-01-14T12:57:35.375369 Technology Area: Web Review
V-218751	CAT II	MONT-MB-002	Microsoft IIS 10.0 Site Security Technic...	The IIS 10.0 website must generate unique session ...	-
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. Finding Details Evaluate-STIG 1.2507.5 (Scan-IIS10_0_Site_Checks) found this to be NOT A FINDING on 10/23/2025 Site: Default Web Site ResultHash: 4DAFD73A73E142C404EAA5FA34EAB3F3718A717C ~~~~~ Mode is set to 'InProc' Source: _Reviewed/MONT-MB-002/Checklist/MONT-MB-002_IIS10Site_Default_Web_Site_V2R12_20251023-152518.ckl Scan Date: 2026-01-14T12:57:33.098574 Technology Area: Web Review
V-218751	CAT II	MONT-MB-002	Microsoft IIS 10.0 Site Security Technic...	The IIS 10.0 website must generate unique session ...	-
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. Finding Details Evaluate-STIG 1.2507.5 (Scan-IIS10_0_Site_Checks) found this to be NOT A FINDING on 10/23/2025 Site: Exchange Back End ResultHash: 4DAFD73A73E142C404EAA5FA34EAB3F3718A717C ~~~~~ Mode is set to 'InProc' Source: _Reviewed/MONT-MB-002/Checklist/MONT-MB-002_IIS10Site_Exchange_Back_End_V2R12_20251023-152602.ckl Scan Date: 2026-01-14T12:57:33.300070 Technology Area: Web Review
V-218751	CAT II	MONT-DP-001	Microsoft IIS 10.0 Site Security Technic...	The IIS 10.0 website must generate unique session ...	-
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. Finding Details Evaluate-STIG 1.2507.5 (Scan-IIS10_0_Site_Checks) found this to be NOT APPLICABLE on 10/23/2025 Site: Default Web Site ResultHash: 2DD143332C0C53AB5EB35B604B56FEEE445E829C ~~~~~ ASP.NET is not installed so this requirement is NA. Source: _Reviewed/MONT-DP-001/Checklist/MONT-DP-001_IIS10Site_Default_Web_Site_V2R12_20251023-143912.ckl Scan Date: 2026-01-14T12:57:35.375369 Technology Area: Web Review
V-218752	CAT II	MONT-MB-002	Microsoft IIS 10.0 Site Security Technic...	The IIS 10.0 website document directory must be in...	-
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. Finding Details Evaluate-STIG 1.2507.5 (Scan-IIS10_0_Site_Checks) was unable to determine a Status but found the below configuration on 10/23/2025: Site: Default Web Site ResultHash: C4AC55E057470F8E3BE8026C2E97039D7E1B552C ~~~~~ Exchange service detected. If this server only hosts Microsoft Exchange, mark this check as NA. Service: MSExchangeServiceHost Status: Running Source: _Reviewed/MONT-MB-002/Checklist/MONT-MB-002_IIS10Site_Default_Web_Site_V2R12_20251023-152518.ckl Scan Date: 2026-01-14T12:57:33.098574 Technology Area: Web Review
V-218752	CAT II	MONT-MB-002	Microsoft IIS 10.0 Site Security Technic...	The IIS 10.0 website document directory must be in...	-
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. Finding Details Evaluate-STIG 1.2507.5 (Scan-IIS10_0_Site_Checks) was unable to determine a Status but found the below configuration on 10/23/2025: Site: Exchange Back End ResultHash: C4AC55E057470F8E3BE8026C2E97039D7E1B552C ~~~~~ Exchange service detected. If this server only hosts Microsoft Exchange, mark this check as NA. Service: MSExchangeServiceHost Status: Running Source: _Reviewed/MONT-MB-002/Checklist/MONT-MB-002_IIS10Site_Exchange_Back_End_V2R12_20251023-152602.ckl Scan Date: 2026-01-14T12:57:33.300070 Technology Area: Web Review
V-218752	CAT II	MONT-DP-001	Microsoft IIS 10.0 Site Security Technic...	The IIS 10.0 website document directory must be in...	-
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. Finding Details Evaluate-STIG 1.2507.5 (Scan-IIS10_0_Site_Checks) found this to be OPEN on 10/23/2025 Site: Default Web Site ResultHash: 82833DC68D5FCB33EF4976B85E80237A71D613C3 ~~~~~ Both the OS and the web site are installed on C: Comments If the server is hosting WSUS, this is Not Applicable. Source: _Reviewed/MONT-DP-001/Checklist/MONT-DP-001_IIS10Site_Default_Web_Site_V2R12_20251023-143912.ckl Scan Date: 2026-01-14T12:57:35.375369 Technology Area: Web Review
V-218753	CAT II	MONT-MB-002	Microsoft IIS 10.0 Site Security Technic...	The IIS 10.0 website must be configured to limit t...	-
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. Finding Details Evaluate-STIG 1.2507.5 (Scan-IIS10_0_Site_Checks) found this to be NOT A FINDING on 10/23/2025 Site: Default Web Site ResultHash: F2EA50F0C244BFF62634234D1860279E15690490 ~~~~~ MaxURL is set to '4096' Source: _Reviewed/MONT-MB-002/Checklist/MONT-MB-002_IIS10Site_Default_Web_Site_V2R12_20251023-152518.ckl Scan Date: 2026-01-14T12:57:33.098574 Technology Area: Web Review
V-218753	CAT II	MONT-MB-002	Microsoft IIS 10.0 Site Security Technic...	The IIS 10.0 website must be configured to limit t...	-
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. Finding Details Evaluate-STIG 1.2507.5 (Scan-IIS10_0_Site_Checks) found this to be NOT A FINDING on 10/23/2025 Site: Exchange Back End ResultHash: F2EA50F0C244BFF62634234D1860279E15690490 ~~~~~ MaxURL is set to '4096' Source: _Reviewed/MONT-MB-002/Checklist/MONT-MB-002_IIS10Site_Exchange_Back_End_V2R12_20251023-152602.ckl Scan Date: 2026-01-14T12:57:33.300070 Technology Area: Web Review

Page 1 of 3

Check Text

Fix Text

Finding Details

Check Text

Fix Text

Finding Details

Check Text

Fix Text

Finding Details

Check Text

Fix Text

Finding Details

Check Text

Fix Text

Finding Details

Check Text

Fix Text

Finding Details

Comments

Check Text

Fix Text

Finding Details

Check Text

Fix Text

Finding Details

Check Text

Fix Text

Finding Details

Check Text

Fix Text

Finding Details

Check Text

Fix Text

Finding Details

Check Text

Fix Text

Finding Details

Comments

Check Text

Fix Text

Finding Details

Check Text

Fix Text

Finding Details

Check Text

Fix Text

Finding Details

Comments

Check Text

Fix Text

Finding Details

Check Text

Fix Text

Finding Details

Check Text

Fix Text

Finding Details

Comments

Check Text

Fix Text

Finding Details

Check Text

Fix Text

Comments

Check Text

Fix Text

Comments

Check Text

Fix Text

Finding Details

Check Text

Fix Text

Finding Details

Check Text

Fix Text

Finding Details

Comments

Check Text

Fix Text

Finding Details