From c3adcf2ce4732eef31660a3fa643eebbbd032e55 Mon Sep 17 00:00:00 2001 From: Eric Jenkins Date: Fri, 29 May 2020 15:28:31 -0400 Subject: [PATCH] Update PowerSTIG to successfully parse/apply Microsoft IIS 10 Server/Site STIG - V1R1 (#641) * added IIS 10.0 Server * updated IIS 10 site stig * updated based on tests * updated based on tests * updated log file --- CHANGELOG.md | 3 +- source/Module/Common/Functions.XccdfXml.ps1 | 10 + .../Convert/IISLoggingRule.Convert.psm1 | 2 +- .../Convert/MimeTypeRule.Convert.psm1 | 2 +- .../Convert/PermissionRule.Convert.psm1 | 2 +- .../WebConfigurationPropertyRule.Convert.psm1 | 5 +- ...U_MS_IIS_10-0_Server_V1R1_Manual-xccdf.log | 3 + ...U_MS_IIS_10-0_Server_V1R1_Manual-xccdf.xml | 919 ++++++++++ .../U_MS_IIS_10-0_Site_V1R1_Manual-xccdf.log | 3 + .../U_MS_IIS_10-0_Site_V1R1_Manual-xccdf.xml | 1272 ++++++++++++++ .../IISServer-10.0-1.1.org.default.xml | 11 + .../StigData/Processed/IISServer-10.0-1.1.xml | 1484 +++++++++++++++++ .../IISSite-10.0-1.1.org.default.xml | 29 + .../StigData/Processed/IISSite-10.0-1.1.xml | 1355 +++++++++++++++ 14 files changed, 5094 insertions(+), 6 deletions(-) create mode 100644 source/StigData/Archive/Web Server/U_MS_IIS_10-0_Server_V1R1_Manual-xccdf.log create mode 100644 source/StigData/Archive/Web Server/U_MS_IIS_10-0_Server_V1R1_Manual-xccdf.xml create mode 100644 source/StigData/Archive/Web Server/U_MS_IIS_10-0_Site_V1R1_Manual-xccdf.log create mode 100644 source/StigData/Archive/Web Server/U_MS_IIS_10-0_Site_V1R1_Manual-xccdf.xml create mode 100644 source/StigData/Processed/IISServer-10.0-1.1.org.default.xml create mode 100644 source/StigData/Processed/IISServer-10.0-1.1.xml create mode 100644 source/StigData/Processed/IISSite-10.0-1.1.org.default.xml create mode 100644 source/StigData/Processed/IISSite-10.0-1.1.xml diff --git a/CHANGELOG.md b/CHANGELOG.md index 7055fd32c..d9e1d8b25 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -2,10 +2,11 @@ ## [Unreleased] +* Update PowerSTIG to successfully parse Microsoft IIS Server/Site 10.0 STIG STIG V1R1: [#632](https://github.com/microsoft/PowerStig/issues/632) * Update PowerSTIG to successfully parse Microsoft Visio 2013 STIG V1R4: [#629](https://github.com/microsoft/PowerStig/issues/629) * Update PowerSTIG to successfully parse/apply Windows Defender Antivirus STIG - V1R8: [#625](https://github.com/microsoft/PowerStig/issues/625) * Update PowerSTIG to successfully parse Microsoft SQL Server 2012 Database STIG V1R20: [#618](https://github.com/microsoft/PowerStig/issues/618) -* Update PowerSTIG to successfully parse/apply Microsoft IIS Server/Site STIG - Ver 1, Rel10: [#622](https://github.com/microsoft/PowerStig/issues/622) +* Update PowerSTIG to successfully parse/apply Microsoft IIS Server/Site 8.5 STIG - Ver 1, Rel10: [#622](https://github.com/microsoft/PowerStig/issues/622) * Update PowerSTIG to use Azure Pipelines and DSC Community based build logic: [#600](https://github.com/microsoft/PowerStig/issues/600) * Update PowerSTIG to parse/convert the Vmware Vsphere 6.5 STIG V1R3: [#604](https://github.com/microsoft/PowerStig/issues/604) * Fixed [#616](https://github.com/microsoft/PowerStig/issues/616): Unable to Import PowerSTIG 4.4.0 Due to cyclic dependency Error diff --git a/source/Module/Common/Functions.XccdfXml.ps1 b/source/Module/Common/Functions.XccdfXml.ps1 index b991ea36d..2af584033 100644 --- a/source/Module/Common/Functions.XccdfXml.ps1 +++ b/source/Module/Common/Functions.XccdfXml.ps1 @@ -406,6 +406,16 @@ function Split-BenchmarkId $returnId = 'IISSite_8.5' continue } + {$PSItem -match "IIS_10-0_Site"} + { + $returnId = 'IISSite_10.0' + continue + } + {$PSItem -match "IIS_10-0_Server"} + { + $returnId = 'IISServer_10.0' + continue + } {$PSItem -match "Domain_Name_System"} { # The Windows Server 2012 and 2012 R2 STIGs are combined, so return the 2012R2 diff --git a/source/Module/Rule.IISLogging/Convert/IISLoggingRule.Convert.psm1 b/source/Module/Rule.IISLogging/Convert/IISLoggingRule.Convert.psm1 index c7cfccd4b..3e8f5ecbf 100644 --- a/source/Module/Rule.IISLogging/Convert/IISLoggingRule.Convert.psm1 +++ b/source/Module/Rule.IISLogging/Convert/IISLoggingRule.Convert.psm1 @@ -195,7 +195,7 @@ class IisLoggingRuleConvert : IisLoggingRule if ( $CheckContent -Match 'Logging' -and - $CheckContent -Match 'IIS 8\.5' -and + $CheckContent -Match 'IIS 8\.5|IIS 10\.0' -and $CheckContent -NotMatch 'review source IP' -and $CheckContent -NotMatch 'verify only authorized groups' -and $CheckContent -NotMatch 'Confirm|Consult with the System Administrator' -and diff --git a/source/Module/Rule.MimeType/Convert/MimeTypeRule.Convert.psm1 b/source/Module/Rule.MimeType/Convert/MimeTypeRule.Convert.psm1 index 6c113e3de..2131593e1 100644 --- a/source/Module/Rule.MimeType/Convert/MimeTypeRule.Convert.psm1 +++ b/source/Module/Rule.MimeType/Convert/MimeTypeRule.Convert.psm1 @@ -154,7 +154,7 @@ class MimeTypeRuleConvert : MimeTypeRule if ( $CheckContent -Match 'MIME Types' -and - $CheckContent -Match 'IIS 8\.5' + $CheckContent -Match 'IIS 8\.5|IIS 10\.0' ) { return $true diff --git a/source/Module/Rule.Permission/Convert/PermissionRule.Convert.psm1 b/source/Module/Rule.Permission/Convert/PermissionRule.Convert.psm1 index 9ce607158..941e3c378 100644 --- a/source/Module/Rule.Permission/Convert/PermissionRule.Convert.psm1 +++ b/source/Module/Rule.Permission/Convert/PermissionRule.Convert.psm1 @@ -163,7 +163,7 @@ class PermissionRuleConvert : PermissionRule $CheckContent -NotMatch 'Windows Registry Editor' -and $CheckContent -NotMatch '(ID|id)s? .* (A|a)uditors?,? (SA|sa)s?,? .* (W|w)eb (A|a)dministrators? .* access to log files?' -and $CheckContent -NotMatch '\n*\.NET Trust Level' -and - $CheckContent -NotMatch 'IIS 8\.5 web' -and + $CheckContent -NotMatch 'IIS 8\.5 web|IIS 10\.0 web' -and $CheckContent -cNotmatch 'SELECT' -and $CheckContent -NotMatch 'SQL Server' -and $CheckContent -NotMatch 'user\srights\sand\spermissions' -and diff --git a/source/Module/Rule.WebConfigurationProperty/Convert/WebConfigurationPropertyRule.Convert.psm1 b/source/Module/Rule.WebConfigurationProperty/Convert/WebConfigurationPropertyRule.Convert.psm1 index 0e69c6fe8..28ff8b8ae 100644 --- a/source/Module/Rule.WebConfigurationProperty/Convert/WebConfigurationPropertyRule.Convert.psm1 +++ b/source/Module/Rule.WebConfigurationProperty/Convert/WebConfigurationPropertyRule.Convert.psm1 @@ -148,7 +148,7 @@ class WebConfigurationPropertyRuleConvert : WebConfigurationPropertyRule ( $CheckContent -Match '\.NET Trust Level' -or ( - $CheckContent -Match 'IIS 8\.5 web|IIS 10\.0' -and + $CheckContent -Match 'IIS 8\.5 web|IIS 10\.0 web' -and $CheckContent -NotMatch 'document' ) -and ( @@ -171,7 +171,8 @@ class WebConfigurationPropertyRuleConvert : WebConfigurationPropertyRule $CheckContent -NotMatch 'Authorization Rules' -and $CheckContent -NotMatch 'regedit ' -and $CheckContent -NotMatch 'Enable proxy' -and - $CheckContent -NotMatch 'SSL Settings' + $CheckContent -NotMatch 'SSL Settings' -and + $CheckContent -NotMatch 'Strict-Transport-Security' ) ) { diff --git a/source/StigData/Archive/Web Server/U_MS_IIS_10-0_Server_V1R1_Manual-xccdf.log b/source/StigData/Archive/Web Server/U_MS_IIS_10-0_Server_V1R1_Manual-xccdf.log new file mode 100644 index 000000000..bd41f3634 --- /dev/null +++ b/source/StigData/Archive/Web Server/U_MS_IIS_10-0_Server_V1R1_Manual-xccdf.log @@ -0,0 +1,3 @@ +V-100115::This check does not apply to service account IDs utilized by automated services necessary to process, manage, and store log files::If an account associated with roles other than auditors +V-100177::*::HardCodedRule(RegistryRule)@{DscResource = 'Registry'; Ensure = 'Present'; Key = 'HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.1\Server'; ValueData = 1; ValueName = 'DisabledByDefault'; ValueType = 'DWORD'}HardCodedRule(RegistryRule)@{DscResource = 'Registry'; Ensure = 'Present'; Key = 'HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2\Server'; ValueData = 0; ValueName = 'DisabledByDefault'; ValueType = 'DWORD'}HardCodedRule(RegistryRule)@{DscResource = 'Registry'; Ensure = 'Present'; Key = 'HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.0\Server'; ValueData = 1; ValueName = 'DisabledByDefault'; ValueType = 'DWORD'}HardCodedRule(RegistryRule)@{DscResource = 'Registry'; Ensure = 'Present'; Key = 'HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\SSL 2.0\Server'; ValueData = 1; ValueName = 'DisabledByDefault'; ValueType = 'DWORD'}HardCodedRule(RegistryRule)@{DscResource = 'Registry'; Ensure = 'Present'; Key = 'HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\SSL 3.0\Server'; ValueData = 1; ValueName = 'DisabledByDefault'; ValueType = 'DWORD'}HardCodedRule(RegistryRule)@{DscResource = 'Registry'; Ensure = 'Present'; Key = 'HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.0\Server'; ValueData = 0; ValueName = 'Enabled'; ValueType = 'DWORD'}HardCodedRule(RegistryRule)@{DscResource = 'Registry'; Ensure = 'Present'; Key = 'HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\SSL 2.0\Server'; ValueData = 0; ValueName = 'Enabled'; ValueType = 'DWORD'}HardCodedRule(RegistryRule)@{DscResource = 'Registry'; Ensure = 'Present'; Key = 'HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\SSL 3.0\Server'; ValueData = 0; ValueName = 'Enabled'; ValueType = 'DWORD'}HardCodedRule(RegistryRule)@{DscResource = 'Registry'; Ensure = 'Present'; Key = 'HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.1\Server'; ValueData = 0; ValueName = 'Enabled'; ValueType = 'DWORD'} +V-100163::CREATOR OWNER: Full Control, Subfolders and files only::CREATOR OWNER: Full Control - Subfolders and files only diff --git a/source/StigData/Archive/Web Server/U_MS_IIS_10-0_Server_V1R1_Manual-xccdf.xml b/source/StigData/Archive/Web Server/U_MS_IIS_10-0_Server_V1R1_Manual-xccdf.xml new file mode 100644 index 000000000..26dedbaa8 --- /dev/null +++ b/source/StigData/Archive/Web Server/U_MS_IIS_10-0_Server_V1R1_Manual-xccdf.xml @@ -0,0 +1,919 @@ +acceptedMicrosoft IIS 10.0 Server Security Technical Implementation GuideThis Security Technical Implementation Guide is published as a tool to improve the security of Department of Defense (DoD) information systems. The requirements are derived from the National Institute of Standards and Technology (NIST) 800-53 and related documents. Comments or proposed revisions to this document should be sent via email to the following address: disa.stig_spt@mail.mil.DISASTIG.DOD.MILRelease: 1 Benchmark Date: 20 Mar 20201I - Mission Critical Classified<ProfileDescription></ProfileDescription>I - Mission Critical Public<ProfileDescription></ProfileDescription>I - Mission Critical Sensitive<ProfileDescription></ProfileDescription>II - Mission Support Classified<ProfileDescription></ProfileDescription>II - Mission Support Public<ProfileDescription></ProfileDescription>II - Mission Support Sensitive<ProfileDescription></ProfileDescription>III - Administrative Classified<ProfileDescription></ProfileDescription>III - Administrative Public<ProfileDescription></ProfileDescription>III - Administrative Sensitive<ProfileDescription></ProfileDescription>SRG-APP-000015-WSR-000014<GroupDescription></GroupDescription>IIST-SV-000100The IIS 10.0 web server remote authors or content providers must only use secure encrypted logons and connections to upload web server content.<VulnDiscussion>Logging onto a web server remotely using an unencrypted protocol or service when performing updates and maintenance is a major risk. Data, such as user account, is transmitted in plaintext and can easily be compromised. When performing remote administrative tasks, a protocol or service that encrypts the communication channel must be used. + +An alternative to remote administration of the web server is to perform web server administration locally at the console. Local administration at the console implies physical access to the server.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target IIS 10.0 ServerDISADPMS TargetIIS 10.0 Server3535CCI-001453Ensure the web server administration is only performed over a secure path.If web administration is performed at the console, this check is NA. + +If web administration is performed remotely the following checks will apply: + +If administration of the server is performed remotely, it will only be performed securely by system administrators. + +If website administration or web application administration has been delegated, those users will be documented and approved by the ISSO. + +Remote administration must be in compliance with any requirements contained within the Windows Server STIGs, and any applicable Network STIGs. + +Remote administration of any kind will be restricted to documented and authorized personnel. + +All users performing remote administration must be authenticated. + +All remote sessions will be encrypted and utilize FIPS 140-2-approved protocols. + +FIPS 140-2-approved TLS versions include TLS V1.1 or greater. + +Review with site management how remote administration is configured on the website, if applicable. + +If remote management meets the criteria listed above, this is not a finding. + +If remote management is utilized and does not meet the criteria listed above, this is a finding.SRG-APP-000092-WSR-000055<GroupDescription></GroupDescription>IIST-SV-000102The enhanced logging for the IIS 10.0 web server must be enabled and capture all user and web server events.<VulnDiscussion>Log files are a critical component to the successful management of an IS used within the DoD. By generating log files with useful information, web administrators can leverage them in the event of a disaster, malicious attack, or other site specific needs. + +Ascertaining the correct order of the events that occurred is important during forensic analysis. Events that appear harmless by themselves might be flagged as a potential threat when properly viewed in sequence. By also establishing the event date and time, an event can be properly viewed with an enterprise tool to fully see a possible threat in its entirety. + +Without sufficient information establishing when the log event occurred, investigation into the cause of event is severely hindered. Log record content that may be necessary to satisfy the requirement of this control includes, but is not limited to, time stamps, source and destination IP addresses, user/process identifiers, event descriptions, application-specific events, success/fail indications, file names involved, access control, or flow control rules invoked. + +Satisfies: SRG-APP-000092-WSR-000055, SRG-APP-000093-WSR-000053, SRG-APP-000095-WSR-000056, SRG-APP-000096-WSR-000057, SRG-APP-000097-WSR-000058, SRG-APP-000097-WSR-000059</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target IIS 10.0 ServerDISADPMS TargetIIS 10.0 Server3535CCI-000130CCI-000131CCI-000132CCI-000133CCI-001462CCI-001464Open the IIS 10.0 Manager. + +Click the IIS 10.0 web server name. + +Click the "Logging" icon. + +Under Format select "W3C". + +Select the following fields: Date, Time, Client IP Address, User Name, Method, URI Query, Protocol Status, and Referrer. + +Under the "Actions" pane, click "Apply".Open the IIS 10.0 Manager. + +Click the IIS 10.0 web server name. + +Click the "Logging" icon. + +Under Format select "W3C". + +Click "Select Fields", verify at a minimum the following fields are checked: Date, Time, Client IP Address, User Name, Method, URI Query, Protocol Status, and Referrer. + +If not, this is a finding.SRG-APP-000092-WSR-000055<GroupDescription></GroupDescription>IIST-SV-000103Both the log file and Event Tracing for Windows (ETW) for the IIS 10.0 web server must be enabled.<VulnDiscussion>Internet Information Services (IIS) on Windows Server 2012 provides basic logging capabilities. However, because IIS takes some time to flush logs to disk, administrators do not have access to logging information in real-time. In addition, text-based log files can be difficult and time-consuming to process. + +In IIS 10.0, the administrator has the option of sending logging information to Event Tracing for Windows (ETW). This option gives the administrator the ability to use standard query tools, or create custom tools, for viewing real-time logging information in ETW. This provides a significant advantage over parsing text-based log files that are not updated in real time. + +Satisfies: SRG-APP-000092-WSR-000055, SRG-APP-000108-WSR-000166, SRG-APP-000358-WSR-000063</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target IIS 10.0 ServerDISADPMS TargetIIS 10.0 Server3535CCI-000139CCI-001464CCI-001851Open the IIS 10.0 Manager. + +Click the IIS 10.0 server name. + +Click the "Logging" icon. + +Under Log Event Destination, select the "Both log file and ETW event" radio button. + +Under the "Actions" pane, click "Apply".Open the IIS 10.0 Manager. + +Click the IIS 10.0 server name. + +Click the "Logging" icon. + +Under Log Event Destination, verify the "Both log file and ETW event" radio button is selected. + +If the "Both log file and ETW event" radio button is not selected, this is a finding.SRG-APP-000098-WSR-000060<GroupDescription></GroupDescription>IIST-SV-000109An IIS 10.0 web server behind a load balancer or proxy server must produce log records containing the source client IP and destination information.<VulnDiscussion>Web server logging capability is critical for accurate forensic analysis. Without sufficient and accurate information, a correct replay of the events cannot be determined. + +Ascertaining the correct source (e.g., source IP), of the events is important during forensic analysis. Correctly determining the source of events will add information to the overall reconstruction of the loggable event. By determining the source of the event correctly, analysis of the enterprise can be undertaken to determine if events tied to the source occurred in other areas within the enterprise. + +A web server behind a load balancer or proxy server, when not configured correctly, will record the load balancer or proxy server as the source of every loggable event. When looking at the information forensically, this information is not helpful in the investigation of events. The web server must record with each event the client source of the event.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target IIS 10.0 ServerDISADPMS TargetIIS 10.0 Server3535CCI-000133Access 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.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 web server 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 this procedure for web server and each website: + +Open the IIS 10.0 Manager. + +Click the IIS 10.0 web server name. + +Click the "Logging" icon. + +Click on "View log files" under the "Actions" pane. + +When the log file is displayed, review source IP information in log entries and verify the 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.SRG-APP-000099-WSR-000061<GroupDescription></GroupDescription>IIST-SV-000110The IIS 10.0 web server must produce log records that contain sufficient information to establish the outcome (success or failure) of IIS 10.0 web server events.<VulnDiscussion>Web server logging capability is critical for accurate forensic analysis. Without sufficient and accurate information, a correct replay of the events cannot be determined. + +Ascertaining the success or failure of an event is important during forensic analysis. Correctly determining the outcome will add information to the overall reconstruction of the loggable event. By determining the success or failure of the event correctly, analysis of the enterprise can be undertaken to determine if events tied to the event occurred in other areas within the enterprise. + +Without sufficient information establishing the success or failure of the logged event, investigation into the cause of event is severely hindered. The success or failure also provides a means to measure the impact of an event and help authorized personnel determine the appropriate response. Log record content that may be necessary to satisfy the requirement of this control includes, but is not limited to, time stamps, source and destination IP addresses, user/process identifiers, event descriptions, application-specific events, success/fail indications, file names involved, access control, or flow control rules invoked.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target IIS 10.0 ServerDISADPMS TargetIIS 10.0 Server3535CCI-000134Access the IIS 10.0 web server IIS Manager. +Click the IIS 10.0 web server name. +Under "IIS", double-click the "Logging" icon. +Verify the "Format:" under "Log File" is configured to "W3C". +Select the "Fields" button. +Under "Custom Fields", click the "Add Field..." button. +For each field being added, give a name unique to what the field is capturing. +Click on the "Source Type" drop-down list and select "Request Header". +Click on the "Source" drop-down list and select "Connection". +Click "OK" to add. + +Click on the "Source Type" drop-down list and select "Request Header". +Click on the "Source" drop-down list and select "Warning". +Click "OK" to add. +Click "Apply" under the "Actions" pane.Access the IIS 10.0 web server IIS Manager. +Click the IIS 10.0 web server name. +Under "IIS", double-click the "Logging" icon. +Verify the "Format:" under "Log File" is configured to "W3C". +Select the "Fields" button. +Under "Custom Fields", verify the following fields have been configured: +Request Header >> Connection +Request Header >> Warning +If any of the above fields are not selected, this is a finding.SRG-APP-000100-WSR-000064<GroupDescription></GroupDescription>IIST-SV-000111The IIS 10.0 web server must produce log records containing sufficient information to establish the identity of any user/subject or process associated with an event.<VulnDiscussion>Web server logging capability is critical for accurate forensic analysis. Without sufficient and accurate information, a correct replay of the events cannot be determined. + +Determining user accounts, processes running on behalf of the user, and running process identifiers also enable a better understanding of the overall event. User tool identification is also helpful to determine if events are related to overall user access or specific client tools. + +Log record content that may be necessary to satisfy the requirement of this control includes: time stamps, source and destination addresses, user/process identifiers, event descriptions, success/fail indications, file names involved, and access control or flow control rules invoked.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target IIS 10.0 ServerDISADPMS TargetIIS 10.0 Server3535CCI-001487Access the IIS 10.0 web server IIS Manager. +Click the IIS 10.0 web server name. +Under "IIS", double-click the "Logging" icon. +Verify the "Format:" under "Log File" is configured to "W3C". +Select the "Fields" button. +Under "Standard Fields", select "User Agent", "User Name", and "Referrer". +Under "Custom Fields", select the following fields: +Click on the "Source Type" drop-down list and select "Request Header". +Click on the "Source" drop-down list and select "Authorization". +Click "OK" to add. + +Click on the "Source" drop-down list and select "Content-Type". +Click on the "Source Type" drop-down list and select "Response Header". +Click "OK" to add. +Click "OK". +Click "Apply" under the "Actions" pane.Access the IIS 10.0 web server IIS Manager. +Click the IIS 10.0 web server name. +Under "IIS", double-click the "Logging" icon. +Verify the "Format:" under "Log File" is configured to "W3C". +Select the "Fields" button. +Under "Standard Fields", verify "User Agent", "User Name", and "Referrer" are selected. +Under "Custom Fields", verify the following field has been configured: +Request Header >> Authorization +Response Header >> Content-Type +If any of the above fields are not selected, this is a finding.SRG-APP-000120-WSR-000070<GroupDescription></GroupDescription>IIST-SV-000115The log information from the IIS 10.0 web server must be protected from unauthorized modification or deletion.<VulnDiscussion>A major tool in exploring the website use, attempted use, unusual conditions, and problems are the access and error logs. In the event of a security incident, these logs can provide the System Administrator (SA) and the web manager with valuable information. Failure to protect log files could enable an attacker to modify the log file data or falsify events to mask an attacker's activity. + +Satisfies: SRG-APP-000120-WSR-000070, SRG-APP-000118-WSR-000068, SRG-APP-000118-WSR-000069</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target IIS 10.0 ServerDISADPMS TargetIIS 10.0 Server3535CCI-000164Open the IIS 10.0 Manager. + +Click the IIS 10.0 web server name. + +Click the "Logging" icon. + +Click "Browse" and navigate to the directory where the log files are stored. + +Right-click the log file name to review and click "Properties". + +Click the "Security" tab. + +Set the log file permissions for the appropriate group(s). + +Click "OK". + +Select "Apply" in the "Actions" pane.This check does not apply to service account IDs utilized by automated services necessary to process, manage, and store log files. +Open the IIS 10.0 Manager. +Click the IIS 10.0 web server name. +Click the "Logging" icon. +Click "Browse" and navigate to the directory where the log files are stored. +Right-click the log file name to review. +Click "Properties". +Click the "Security" tab. +Verify log file access is restricted as follows. Otherwise, this is a finding. +SYSTEM - Full Control +Administrators - Full ControlSRG-APP-000125-WSR-000071<GroupDescription></GroupDescription>IIST-SV-000116The log data and records from the IIS 10.0 web server must be backed up onto a different system or media.<VulnDiscussion>Protection of log data includes ensuring log data is not accidentally lost or deleted. Backing up log records to an unrelated system, or onto separate media than the system on which the web server is running, helps to ensure the log records will be retained in the event of a catastrophic system failure.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target IIS 10.0 ServerDISADPMS TargetIIS 10.0 Server3535CCI-001348Configure system backups to include the directory paths of all IIS 10.0 web server and website log files.The IIS 10.0 web server and website log files should be backed up by the system backup. + +To determine if log files are backed up by the system backup, determine the location of the web server log files and each website's log files. + +Open the IIS 10.0 Manager. + +Click the IIS 10.0 server name. + +Click the "Logging" icon. + +Under "Log File" >> "Directory" obtain the path of the log file. + +Once all locations are known, consult with the System Administrator to review the server's backup procedure and policy. + +Verify the paths of all log files are part of the system backup. +Verify log files are backed up to an unrelated system or onto separate media on which the system the web server is running. + +If the paths of all log files are not part of the system backup and/or not backed up to a separate media, this is a finding.SRG-APP-000141-WSR-000015<GroupDescription></GroupDescription>IIST-SV-000117The IIS 10.0 web server must not perform user management for hosted applications.<VulnDiscussion>User management and authentication can be an essential part of any application hosted by the web server. Along with authenticating users, the user management function must perform several other tasks enterprise-wide, such as password complexity, locking users after a configurable number of failed logons, and management of temporary and emergency accounts. + +The web server contains a minimal user management function, but the web server user management function does not offer enterprise-wide user management, and user management is not the primary function of the web server. User management for the hosted applications should be done through a facility built for enterprise-wide user management, such as LDAP and Active Directory.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target IIS 10.0 ServerDISADPMS TargetIIS 10.0 Server3535CCI-000381Reconfigure any hosted applications on the IIS 10.0 web server to perform user management outside the IIS 10.0 web server. + +Document how the hosted application user management is accomplished.Interview the System Administrator about the role of the IIS 10.0 web server. + +If the IIS 10.0 web server is hosting an application, have the SA provide supporting documentation on how the application's user management is accomplished outside of the IIS 10.0 web server. + +If the IIS 10.0 web server is not hosting an application, this is Not Applicable. + +If the IIS web server is performing user management for hosted applications, this is a finding. + +If the IIS 10.0 web server is hosting an application and the SA cannot provide supporting documentation on how the application's user management is accomplished outside of the IIS 10.0 web server, this is a finding.SRG-APP-000141-WSR-000075<GroupDescription></GroupDescription>IIST-SV-000118The IIS 10.0 web server must only contain functions necessary for operation.<VulnDiscussion>A web server can provide many features, services, and processes. Some of these may be deemed unnecessary or too unsecure to run on a production DoD system. + +The web server must provide the capability to disable, uninstall, or deactivate functionality and services deemed non-essential to the web server mission or that adversely impact server performance.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target IIS 10.0 ServerDISADPMS TargetIIS 10.0 Server3535CCI-000381Remove all unapproved programs and roles from the production IIS 10.0 web server.Click “Start”. + +Open Control Panel. + +Click “Programs”. + +Click “Programs and Features”. + +Review the installed programs. If any programs are installed other than those required for the IIS 10.0 web services, this is a finding. + +Note: If additional software is needed, supporting documentation must be signed by the ISSO.SRG-APP-000141-WSR-000076<GroupDescription></GroupDescription>IIST-SV-000119The IIS 10.0 web server must not be both a website server and a proxy server.<VulnDiscussion>A web server should be primarily a web server or a proxy server but not both, for the same reasons that other multi-use servers are not recommended. Scanning for web servers that also proxy requests into an otherwise protected network is a common attack, making the attack anonymous.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target IIS 10.0 ServerDISADPMS TargetIIS 10.0 Server3535CCI-000381Open the IIS 10.0 Manager. + +Under the "Connections" pane on the left side of the management console, select the IIS 10.0 web server. + +Under the IIS installed features, "Application Request Routing Cache" is present, double-click the icon to open the feature. + +From the right "Actions" pane, under "Proxy", select "Server Proxy Settings...". + +In the "Application Request Routing" settings window, remove the check from the "Enable proxy" check box. + +Click "Apply" in the "Actions" pane.Open the IIS 10.0 Manager. + +Under the "Connections" pane on the left side of the management console, select the IIS 10.0 web server. + +If, under the IIS installed features, "Application Request Routing Cache" is not present, this is not a finding. + +If, under the IIS installed features, "Application Request Routing Cache" is present, double-click the icon to open the feature. + +From the right "Actions" pane, under "Proxy", select "Server Proxy Settings...". + +In the "Application Request Routing" settings window, verify whether "Enable proxy" is selected. + +If “Enable proxy" is selected under the "Application Request Routing" settings, this is a finding.SRG-APP-000141-WSR-000077<GroupDescription></GroupDescription>IIST-SV-000120All IIS 10.0 web server sample code, example applications, and tutorials must be removed from a production IIS 10.0 server.<VulnDiscussion>Web server documentation, sample code, example applications, and tutorials may be an exploitable threat to a web server. A production web server may only contain components that are operationally necessary (i.e., compiled code, scripts, web content, etc.). Delete all directories containing samples and any scripts used to execute the samples.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target IIS 10.0 ServerDISADPMS TargetIIS 10.0 Server3535CCI-000381Remove any executable sample code, example applications, or tutorials which are not explicitly used by a production website.Navigate to the following folders: + +inetpub\ +Program Files\Common Files\System\msadc +Program Files (x86)\Common Files\System\msadc + +If the folder or sub-folders contain any executable sample code, example applications, or tutorials which are not explicitly used by a production website, this is a finding.SRG-APP-000141-WSR-000078<GroupDescription></GroupDescription>IIST-SV-000121The accounts created by uninstalled features (i.e., tools, utilities, specific, etc.) must be deleted from the IIS 10.0 server.<VulnDiscussion>Accounts used for web server features such as documentation, sample code, example applications, tutorials, utilities, and services created when the feature is not installed, become an exploitable threat to a web server. + +These accounts become inactive, are not monitored through regular use, and passwords for the accounts are not created or updated. An attacker, through very little effort, can use these accounts to gain access to the web server and begin investigating ways to elevate the account privileges. + +The accounts used for web server features not installed must not be created and must be deleted when these features are uninstalled.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target IIS 10.0 ServerDISADPMS TargetIIS 10.0 Server3535CCI-000381Access the IIS 10.0 web server. + +Access “Apps” menu. Under “Administrative Tools”, select “Computer Management”. + +In the left pane, expand "Local Users and Groups" and click "Users". + +Delete any local accounts which were created by features which have been uninstalled or are not used.Access the IIS 10.0 web server. + +Access “Apps” menu. Under “Administrative Tools”, select “Computer Management”. + +In the left pane, expand "Local Users and Groups" and click "Users". + +Review the local users listed in the middle pane. + +If any local accounts are present and were created by features which have been uninstalled or are not used, this is a finding.SRG-APP-000141-WSR-000080<GroupDescription></GroupDescription>IIST-SV-000123The IIS 10.0 web server must be reviewed on a regular basis to remove any Operating System features, utility programs, plug-ins, and modules not necessary for operation.<VulnDiscussion>Just as running unneeded services and protocols is a danger to the web server at the lower levels of the OSI model, running unneeded utilities and programs is a danger at the application layer of the OSI model. Office suites, development tools, and graphic editors are examples of such troublesome programs. + +Individual productivity tools have no legitimate place or use on an enterprise production web server and are prone to security risks. The web server installation process must provide options allowing the installer to choose which utility programs, services, and modules are to be installed or removed. By having a process for installation and removal, the web server is guaranteed to be in a more stable and secure state than if these services and programs were installed and removed manually.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target IIS 10.0 ServerDISADPMS TargetIIS 10.0 Server3535CCI-000381Remove all utility programs, Operating System features, or modules installed that are not necessary for web server operation.Consult with the System Administrator and review all of the IIS 10.0 and Operating System features installed. + +Determine if any features installed are no longer necessary for operation. + +If any utility programs, features, or modules are installed which are not necessary for operation, this is a finding. + +If any unnecessary Operating System features are installed, this is a finding.SRG-APP-000141-WSR-000081<GroupDescription></GroupDescription>IIST-SV-000124The IIS 10.0 web server must have Multipurpose Internet Mail Extensions (MIME) that invoke OS shell programs disabled.<VulnDiscussion>Controlling what a user of a hosted application can access is part of the security posture of the web server. Any time a user can access more functionality than is needed for the operation of the hosted application poses a security issue. A user with too much access can view information that is not needed for the user's job role, or the user could use the function in an unintentional manner. + +A MIME tells the web server the type of program, various file types, and extensions and what external utilities or programs are needed to execute the file type. + +A shell is a program that serves as the basic interface between the user and the operating system to ensure hosted application users do not have access to these programs. Shell programs may execute shell escapes and can perform unauthorized activities that could damage the security posture of the web server.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target IIS 10.0 ServerDISADPMS TargetIIS 10.0 Server3535CCI-000381Open the IIS 10.0 Manager. + +Click the IIS 10.0 web server name. + +Under IIS, double-click the "MIME Types" icon. + +From the "Group by:" drop-down list, select "Content Type". + +From the list of extensions under "Application", remove MIME types for OS shell program extensions, to include at a minimum, the following extensions: + +.exe +.dll +.com +.bat +.csh + +Under the "Actions" pane, click "Apply".Open the IIS 10.0 Manager. + +Click the IIS 10.0 web server name. + +Under IIS, double-click the "MIME Types" icon. + +From the "Group by:" drop-down list, select "Content Type". + +From the list of extensions under "Application", verify MIME types for OS shell program extensions have been removed, to include at a minimum, the following extensions: + +.exe +.dll +.com +.bat +.csh + +If any OS shell MIME types are configured, this is a finding.SRG-APP-000141-WSR-000085<GroupDescription></GroupDescription>IIST-SV-000125The IIS 10.0 web server must have Web Distributed Authoring and Versioning (WebDAV) disabled.<VulnDiscussion>A web server can be installed with functionality that by its nature is not secure. Web Distributed Authoring (WebDAV) is an extension to the HTTP protocol which, when developed, was meant to allow users to create, change, and move documents on a server, typically a web server or web share. Allowing this functionality, development, and deployment is much easier for web authors. + +WebDAV is not widely used and has serious security concerns because it may allow clients to modify unauthorized files on the web server.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target IIS 10.0 ServerDISADPMS TargetIIS 10.0 Server3535CCI-000381Access Server Manager on the IIS 10.0 web server. + +Click the IIS 10.0 web server name. + +Click on "Manage". + +Select "Add Roles and Features". + +Click "Next" in the "Before you begin" dialog box. + +Select "Role-based or feature-based installation" on the "Installation Type" dialog box and click "Next". + +Select the IIS 10.0 web server in the "Server Selection" dialog box. + +From the "Windows Features" dialog box, navigate to "World Wide Web Services" >> "Common HTTP Features". + +De-select "WebDAV Publishing", and click "Next" to complete removing the WebDAV Publishing feature from the IIS 10.0 web server.Open the IIS 10.0 Manager. + +Click the IIS 10.0 web server name. + +Review the features listed under the “IIS" section. + +If the "WebDAV Authoring Rules" icon exists, this is a finding.SRG-APP-000175-WSR-000095<GroupDescription></GroupDescription>IIST-SV-000129The IIS 10.0 web server must perform RFC 5280-compliant certification path validation.<VulnDiscussion>This check verifies the server certificate is actually a DoD-issued certificate used by the organization being reviewed. This is used to verify the authenticity of the website to the user. If the certificate is not issued by the DoD or if the certificate has expired, then there is no assurance the use of the certificate is valid, and therefore; the entire purpose of using a certificate is compromised.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target IIS 10.0 ServerDISADPMS TargetIIS 10.0 Server3535CCI-000185Open the IIS 10.0 Manager. + +Click the IIS 10.0 web server name. + +Double-click the "Server Certificate" icon. + +Import a valid DoD certificate and remove any non-DoD certificates.Open the IIS 10.0 Manager. + +Click the IIS 10.0 web server name. + +Double-click the "Server Certificate" icon. + +Double-click each certificate and verify the certificate path is to a DoD root CA. + +If the “Issued By” field of the PKI certificate being used by the IIS 10.0 server/site does not indicate the issuing Certificate Authority (CA) is part of the DoD PKI or an approved ECA, this is a finding.SRG-APP-000206-WSR-000128<GroupDescription></GroupDescription>IIST-SV-000130Java software installed on a production IIS 10.0 web server must be limited to .class files and the Java Virtual Machine.<VulnDiscussion>Mobile code in hosted applications allows the developer to add functionality and displays to hosted applications that are fluid, as opposed to a static web page. The data presentation becomes more appealing to the user, is easier to analyze, and is less complicated to navigate through the hosted application and data. + +Some mobile code technologies in use in today's applications are: Java, JavaScript, ActiveX, PDF, Postscript, Shockwave movies, Flash animations, and VBScript. The DoD has created policies that define the usage of mobile code on DoD systems. The usage restrictions and implementation guidance apply to both the selection and use of mobile code installed on organizational servers and mobile code downloaded and executed on individual workstations. + +Source code for a Java program is often stored in files with either .java or .jpp file extensions. From the .java and .jpp files the Java compiler produces a binary file with an extension of .class. The .java or .jpp file could therefore reveal sensitive information regarding an application's logic and permissions to resources on the server.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target IIS 10.0 ServerDISADPMS TargetIIS 10.0 Server3535CCI-001166Remove all files from the web server with both .java and .jpp extensions.Search the system for files with either .java or .jpp extensions. + +If files with .java or .jpp extensions are found, this is a finding.SRG-APP-000211-WSR-000030<GroupDescription></GroupDescription>IIST-SV-000131IIS 10.0 Web server accounts accessing the directory tree, the shell, or other operating system functions and utilities must only be administrative accounts.<VulnDiscussion>As a rule, accounts on a web server are to be kept to a minimum. Only administrators, web managers, developers, auditors, and web authors require accounts on the machine hosting the web server. This is in addition to the anonymous web user account. The resources to which these accounts have access must also be closely monitored and controlled. Only the SA needs access to all the system’s capabilities, while the web administrator and associated staff require access and control of the web content and web server configuration files. The anonymous web user account must not have access to system resources as that account could then control the server.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target IIS 10.0 ServerDISADPMS TargetIIS 10.0 Server3535CCI-001082Ensure non-administrators are not allowed access to the directory tree, the shell, or other operating system functions and utilities. + +All non-administrator access to shell scripts and operating system functions must be mission essential and documented.Obtain a list of the user accounts with access to the system, including all local and domain accounts. + +Review the privileges to the web server for each account. + +Verify with the system administrator or the ISSO that all privileged accounts are mission essential and documented. + +Verify with the system administrator or the ISSO that all non-administrator access to shell scripts and operating system functions are mission essential and documented. + +If undocumented privileged accounts are found, this is a finding. + +If undocumented non-administrator access to shell scripts and operating system functions are found, this is a finding. + +If this IIS 10 installation is supporting Microsoft Exchange, and not otherwise hosting any content, this requirement is Not Applicable.SRG-APP-000211-WSR-000129<GroupDescription></GroupDescription>IIST-SV-000132The IIS 10.0 web server must separate the hosted applications from hosted web server management functionality.<VulnDiscussion>The separation of user functionality from web server management can be accomplished by moving management functions to a separate IP address or port. To further separate the management functions, separate authentication methods and certificates should be used. + +By moving the management functionality, the possibility of accidental discovery of the management functions by non-privileged users during hosted application use is minimized.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target IIS 10.0 ServerDISADPMS TargetIIS 10.0 Server3535CCI-001082Develop a method to manage the hosted applications, either by moving its management functions off of the IIS 10.0 web server or by accessing the application's management via a uniquely assigned IP address.Review the IIS 10.0 web server configuration with the System Administrator. + +Determine if the IIS 10.0 web server hosts any applications. + +If the IIS 10.0 web server does not host any applications, this is Not Applicable. + +If the IIS 10.0 web server hosts applications, review the application's management functionality and authentication methods with the System Administrator to determine if the management of the application is accomplished with the same functions and authentication methods as the web server management. + +If the IIS 10.0 web server management and the application's management functionality is not separated, this is a finding.SRG-APP-000223-WSR-000011<GroupDescription></GroupDescription>IIST-SV-000134The IIS 10.0 web server must use cookies to track session state.<VulnDiscussion>Cookies are used to exchange data between the web server and the client. Cookies, such as a session cookie, may contain session information and user credentials used to maintain a persistent connection between the user and the hosted application since HTTP/HTTPS is a stateless protocol. + +Using URI will embed the session ID as a query string in the Uniform Resource Identifier (URI) request and then the URI is redirected to the originally requested URL. The changed URI request is used for the duration of the session, so no cookie is necessary. + +By requiring expired session IDs to be regenerated while using URI, potential attackers have less time to capture a cookie and gain access to the Web server content. + +Satisfies: SRG-APP-000223-WSR-000011, SRG-APP-000220-WSR-000201</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target IIS 10.0 ServerDISADPMS TargetIIS 10.0 Server3535CCI-001664Open the IIS 10.0 Manager. + +Click the IIS 10.0 web server name. + +Under "ASP.Net", double-click the "Session State" icon. + +Under "Cookie Settings", select "Use Cookies” from the "Mode" drop-down list. + +Click "Apply" in the "Actions" pane.Open the IIS 10.0 Manager. +Click the IIS 10.0 web server name. +Under "ASP.Net", double-click the "Session State" icon. +Under "Cookie Settings", verify the "Mode" has "Use Cookies" selected from the drop-down list. +If the "Cookie Settings" "Mode" is not set to "Use Cookies", this is a finding. + +Alternative method: + +Click the site name. +Select "Configuration Editor" under the "Management" section. +From the "Section:" drop-down list at the top of the configuration editor, locate "system.web/sessionState". +Verify the "cookieless" is set to "UseCookies". +If the "cookieless" is not set to "UseCookies", this is a finding. + +Note: If IIS 10.0 server/site is used only for system-to-system maintenance, does not allow users to connect to interface, and is restricted to specific system IPs, this is Not Applicable.SRG-APP-000223-WSR-000145<GroupDescription></GroupDescription>IIST-SV-000135The IIS 10.0 web server must accept only system-generated session identifiers.<VulnDiscussion>ASP.NET provides a session state, which is available as the HttpSessionState class, as a method of storing session-specific information that is visible only within the session. ASP.NET session state identifies requests from the same browser during a limited time window as a session and provides the ability to persist variable values for the duration of that session. + +When using the URI mode for cookie settings under session state, IIS will reject and reissue session IDs that do not have active sessions. Configuring IIS to expire session IDs and regenerate tokens gives a potential attacker less time to capture a cookie and gain access to server content.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target IIS 10.0 ServerDISADPMS TargetIIS 10.0 Server3535CCI-001664Open the IIS 10.0 Manager. + +Click the IIS 10.0 web server name. + +Under the "ASP.NET" section, select "Session State". + +Under "Cookie Settings", select the "Use Cookies" mode from the "Mode:" drop-down list. + +Under “Time-out (in minutes), enter a value of “20 or less”.Open the IIS 10.0 Manager. +Click the IIS 10.0 web server name. +Under the "ASP.NET" section, select "Session State". +Under "Cookie Settings", verify the "Use Cookies" mode is selected from the "Mode:" drop-down list. +Under Time-out (in minutes), verify “20 minutes or less” is selected. +If the "Use Cookies” mode is selected and Time-out (in minutes) is configured for “20 minutes or less”, this is not a finding. + +Alternative method: + +Click the site name. +Select "Configuration Editor" under the "Management" section. +From the "Section:" drop-down list at the top of the configuration editor, locate "system.web/sessionState". +Verify the "cookieless" is set to "UseCookies". +If the "cookieless" is not set to "UseCookies", this is a finding. + +Note: If IIS 10.0 server/site is used only for system-to-system maintenance, does not allow users to connect to interface, and is restricted to specific system IPs, this is Not Applicable.SRG-APP-000225-WSR-000074<GroupDescription></GroupDescription>IIST-SV-000136The IIS 10.0 web server must augment re-creation to a stable and known baseline.<VulnDiscussion>Making certain that the web server has not been updated by an unauthorized user is always a concern. Adding patches, functions, and modules that are untested and not part of the baseline opens the possibility for security risks. The web server must offer, and not hinder, a method that allows for the quick and easy reinstallation of a verified and patched baseline to guarantee the production web server is up-to-date and has not been modified to add functionality or expose security risks. + +When the web server does not offer a method to roll back to a clean baseline, external methods, such as a baseline snapshot or virtualizing the web server, can be used.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target IIS 10.0 ServerDISADPMS TargetIIS 10.0 Server3535CCI-001190Prepare documentation for disaster recovery methods for the IIS 10.0 web server in the event of the necessity for rollback. + +Document and test the disaster recovery methods designed.Interview the System Administrator for the IIS 10.0 web server. + +Ask for documentation on the disaster recovery methods tested and planned for the IIS 10.0 web server in the event of the necessity for rollback. + +If documentation for a disaster recovery has not been established, this is a finding.SRG-APP-000231-WSR-000144<GroupDescription></GroupDescription>IIST-SV-000137The production IIS 10.0 web server must utilize SHA2 encryption for the Machine Key.<VulnDiscussion>The Machine Key element of the ASP.NET web.config specifies the algorithm and keys that ASP.NET will use for encryption. The Machine Key feature can be managed to specify hashing and encryption settings for application services such as view state, forms authentication, membership and roles, and anonymous identification. Ensuring a strong encryption method can mitigate the risk of data tampering in crucial functional areas such as forms authentication cookies, or view state.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target IIS 10.0 ServerDISADPMS TargetIIS 10.0 Server3535CCI-001199Open the IIS 10.0 Manager. + +Click the IIS 10.0 web server name. + +Double-click the "Machine Key" icon in the web server Home Pane. + +Set the Validation method to "HMACSHA256" or stronger. +Set the Encryption method to "Auto". + +Click "Apply" in the "Actions" pane.Open the IIS 10.0 Manager. + +Click the IIS 10.0 web server name. + +Double-click the "Machine Key" icon in the website Home Pane. + +Verify "HMACSHA256" or stronger encryption is selected for the Validation method and "Auto" is selected for the Encryption method. + +If "HMACSHA256" or stronger encryption is not selected for the Validation method and/or "Auto" is not selected for the Encryption method, this is a finding. + +If .NET is not installed, this is Not Applicable.SRG-APP-000251-WSR-000157<GroupDescription></GroupDescription>IIST-SV-000138Directory Browsing on the IIS 10.0 web server must be disabled.<VulnDiscussion>Directory browsing allows the contents of a directory to be displayed upon request from a web client. If directory browsing is enabled for a directory in IIS, users could receive a web page listing the contents of the directory. If directory browsing is enabled, the risk of inadvertently disclosing sensitive content is increased.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target IIS 10.0 ServerDISADPMS TargetIIS 10.0 Server3535CCI-001310Open the IIS 10.0 Manager. + +Click the IIS 10.0 web server name. + +Double-click the "Directory Browsing" icon. + +Under the "Actions" pane click "Disabled". + +Under the "Actions" pane, click "Apply".Open the IIS 10.0 Manager. + +Click the IIS 10.0 web server name. + +Double-click the "Directory Browsing" icon. + +Under the “Actions” pane verify "Directory Browsing" is disabled. + +If “Directory Browsing” is not disabled, this is a finding.SRG-APP-000266-WSR-000142<GroupDescription></GroupDescription>IIST-SV-000139The IIS 10.0 web server indexing must only index web content.<VulnDiscussion>The indexing service can be used to facilitate a search function for websites. Enabling indexing may facilitate a directory traversal exploit and reveal unwanted information to a malicious user. Indexing must be limited to web document directories only.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target IIS 10.0 ServerDISADPMS TargetIIS 10.0 Server3535CCI-001312Run MMC. + +Add the Indexing Service snap-in. + +Edit the indexed directories to only include web document directories.Access the IIS 10.0 Web Server. + +Access an administrator command prompt and type "regedit <enter>" to access the server's registry. + +Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\ContentIndex\Catalogs\. + +If this key exists, then indexing is enabled. + +If the key does not exist, this check is Not Applicable. + +Review the Catalog keys to determine if directories other than web document directories are being indexed. + +If so, this is a finding.SRG-APP-000266-WSR-000159<GroupDescription></GroupDescription>IIST-SV-000140Warning and error messages displayed to clients must be modified to minimize the identity of the IIS 10.0 web server, patches, loaded modules, and directory paths.<VulnDiscussion>HTTP error pages contain information that could enable an attacker to gain access to an information system. Failure to prevent the sending of HTTP error pages with full information to remote requesters exposes internal configuration information to potential attackers.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target IIS 10.0 ServerDISADPMS TargetIIS 10.0 Server3535CCI-001312Open the IIS 10.0 Manager. + +Click the IIS 10.0 web server name. + +Double-click the "Error Pages" icon. + +Click any error message, and then click "Edit Feature Setting" from the "Actions" Pane. This will apply to all error messages. + +Set Feature Setting to “Detailed errors for local requests and custom error pages for remote requests”.Open the IIS 10.0 Manager. + +Click the IIS 10.0 web server name. + +Double-click the "Error Pages" icon. + +Click any error message, and then click "Edit Feature Setting" from the "Actions" Pane. This will apply to all error messages. + +If the feature setting is not set to “Detailed errors for local requests and custom error pages for remote requests”, this is a finding.SRG-APP-000315-WSR-000003<GroupDescription></GroupDescription>IIST-SV-000141Remote access to the IIS 10.0 web server must follow access policy or work in conjunction with enterprise tools designed to enforce policy requirements.<VulnDiscussion>Logging into a web server remotely using an unencrypted protocol or service when performing updates and maintenance is a major risk. Data, such as user account, is transmitted in plaintext and can easily be compromised. When performing remote administrative tasks, a protocol or service that encrypts the communication channel must be used.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target IIS 10.0 ServerDISADPMS TargetIIS 10.0 Server3535CCI-002314Ensure the web server administration is only performed over a secure path.If web administration is performed at the console, this check is Not Applicable. + +If web administration is performed remotely the following checks will apply. + +If administration of the server is performed remotely, it will only be performed securely by system administrators. + +If website administration or web application administration has been delegated, those users will be documented and approved by the ISSO. + +Remote administration must be in compliance with any requirements contained within the Windows Server STIGs, and any applicable network STIGs. + +Remote administration of any kind will be restricted to documented and authorized personnel. + +All users performing remote administration must be authenticated. + +All remote sessions will be encrypted and utilize FIPS 140-2-approved protocols. + +FIPS 140-2-approved TLS versions include TLS V1.1 or greater. + +Review with site management how remote administration, if applicable, is configured on the website. + +If remote management meets the criteria listed above, this is not a finding. + +If remote management is utilized and does not meet the criteria listed above, this is a finding.SRG-APP-000315-WSR-000004<GroupDescription></GroupDescription>IIST-SV-000142The IIS 10.0 web server must restrict inbound connections from non-secure zones.<VulnDiscussion>Remote access to the web server is any access that communicates through an external, non-organization-controlled network. Remote access can be used to access hosted applications or to perform management functions. + +A web server can be accessed remotely and must be capable of restricting access from what the DoD defines as non-secure zones. Non-secure zones are defined as any IP, subnet, or region defined as a threat to the organization. The non-secure zones must be defined for public web servers logically located in a DMZ, as well as private web servers with perimeter protection devices. By restricting access from non-secure zones through internal web server access lists, the web server can stop or slow denial of service (DoS) attacks on the web server.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target IIS 10.0 ServerDISADPMS TargetIIS 10.0 Server3535CCI-002314Open the IIS 10.0 Manager. + +Click the IIS 10.0 web server name. + +Under "Management", double-click "Management Service". + +Stop the Web Management Service under the "Actions" pane. + +Configure only known, secure IP ranges as "Allow". + +Select "Apply" in "Actions" pane. + +Restart the Web Management Service under the "Actions" pane.Note: This requirement applies to the Web Management Service. If the Web Management Service is not installed, this is Not Applicable. + +Open the IIS 10.0 Manager. + +Click the IIS 10.0 web server name. + +Under "Management", double-click "Management Service". + +If "Enable remote connections" is not selected, this is Not Applicable. + +If "Enable remote connections" is selected, review the entries under "IP Address Restrictions". + +Verify only known, secure IP ranges are configured as "Allow". + +If "IP Address Restrictions" are not configured or IP ranges configured to "Allow" are not restrictive enough to prevent connections from nonsecure zones, this is a finding.SRG-APP-000316-WSR-000170<GroupDescription></GroupDescription>IIST-SV-000143The IIS 10.0 web server must provide the capability to immediately disconnect or disable remote access to the hosted applications.<VulnDiscussion>During an attack on the web server or any of the hosted applications, the system administrator may need to disconnect or disable access by users to stop the attack. + +The web server must provide a capability to disconnect users to a hosted application without compromising other hosted applications unless deemed necessary to stop the attack. Methods to disconnect or disable connections are to stop the application service for a specified hosted application, stop the web server, or block all connections through web server access list. + +The web server capabilities used to disconnect or disable users from connecting to hosted applications and the web server must be documented to make certain that, during an attack, the proper action is taken to conserve connectivity to any other hosted application if possible and to make certain log data is conserved for later forensic analysis.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target IIS 10.0 ServerDISADPMS TargetIIS 10.0 Server3535CCI-002322Prepare documented procedures for shutting down an IIS 10.0 website in the event of an attack. + +The procedure should, at a minimum, provide the following steps: + +Determine the respective website for the application at risk of an attack. + +Access the IIS 10.0 web server IIS Manager. + +Select the respective website. + +In the "Actions" pane, under "Manage Website", click "Stop". + +If necessary, stop all websites. + +If necessary, stop the IIS 10.0 web server by selecting the web server in the IIS Manager. + +In the "Actions" pane, under "Manage Server", click "Stop".Interview the System Administrator and Web Manager. + +Ask for documentation for the IIS 10.0 web server administration. + +Verify there are documented procedures for shutting down an IIS 10.0 website in the event of an attack. The procedure should, at a minimum, provide the following steps: + +Determine the respective website for the application at risk of an attack. + +Access the IIS 10.0 web server IIS Manager. + +Select the respective website. + +In the "Actions" pane, under "Manage Website", click "Stop". + +If necessary, stop all websites. + +If necessary, stop the IIS 10.0 web server by selecting the web server in the IIS Manager. + +In the "Actions" pane, under "Manage Server", click "Stop". + +If the web server is not capable or cannot be configured to disconnect or disable remote access to the hosted applications when necessary, this is a finding.SRG-APP-000340-WSR-000029<GroupDescription></GroupDescription>IIST-SV-000144IIS 10.0 web server system files must conform to minimum file permission requirements.<VulnDiscussion>This check verifies the key web server system configuration files are owned by the SA or the web administrator controlled account. These same files that control the configuration of the web server, and thus its behavior, must also be accessible by the account running the web service. If these files are altered by a malicious user, the web server would no longer be under the control of its managers and owners; properties in the web server configuration could be altered to compromise the entire server platform.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target IIS 10.0 ServerDISADPMS TargetIIS 10.0 Server3535CCI-002235Open Explorer and navigate to the inetpub directory. + +Right-click "inetpub" and select "Properties". + +Click the "Security" tab. + +Set the following permissions: + +SYSTEM: Full control +Administrators: Full control +TrustedInstaller: Full control +ALL APPLICATION PACKAGES (built-in security group): Read and execute +Users: Read and execute, list folder contents +CREATOR OWNER: special permissions to subkeysOpen Explorer and navigate to the inetpub directory. + +Right-click "inetpub" and select "Properties". + +Click the "Security" tab. + +Verify the permissions for the following users; if the permissions are less restrictive, this is a finding. + +System: Full control +Administrators: Full control +TrustedInstaller: Full control +ALL APPLICATION PACKAGES (built-in security group): Read and execute +ALL RESTRICTED APPLICATION PACKAGES (built-in security group): Read and execute +Users: Read and execute, list folder contents +CREATOR OWNER: Full Control, Subfolders and files onlySRG-APP-000357-WSR-000150<GroupDescription></GroupDescription>IIST-SV-000145The IIS 10.0 web server must use a logging mechanism configured to allocate log record storage capacity large enough to accommodate the logging requirements of the IIS 10.0 web server.<VulnDiscussion>To ensure the logging mechanism used by the web server has sufficient storage capacity in which to write the logs, the logging mechanism must be able to allocate log record storage capacity. + +The task of allocating log record storage capacity is usually performed during initial installation of the logging mechanism. The system administrator will usually coordinate the allocation of physical drive space with the web server administrator along with the physical location of the partition and disk. Refer to NIST SP 800-92 for specific requirements on log rotation and storage dependent on the impact of the web server.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target IIS 10.0 ServerDISADPMS TargetIIS 10.0 Server3535CCI-001849Open the IIS 10.0 Manager. + +Click the IIS 10.0 web server name. + +Under "IIS" double-click on the "Logging" icon. + +If necessary, in the "Logging" configuration box, re-designate a log path to a location able to house the logs. + +Under "Log File Rollover", de-select the "Do not create new log files" setting. + +Configure a schedule to rollover log files on a regular basis.Open the IIS 10.0 Manager. + +Click the IIS 10.0 web server name. + +Under "IIS" double-click the "Logging" icon. + +In the "Logging" configuration box, determine the "Directory:" to which the "W3C" logging is being written. + +Confirm with the System Administrator that the designated log path is of sufficient size to maintain the logging. + +Under "Log File Rollover", verify "Do not create new log files" is not selected. + +Verify a schedule is configured to rollover log files on a regular basis. + +Consult with the System Administrator to determine if there is a documented process for moving the log files off of the IIS 10.0 web server to another logging device. + +If the designated logging path device is not of sufficient space to maintain all log files, and there is not a schedule to rollover files on a regular basis, this is a finding.SRG-APP-000380-WSR-000072<GroupDescription></GroupDescription>IIST-SV-000147Access to web administration tools must be restricted to the web manager and the web managers designees.<VulnDiscussion>A web server can be modified through parameter modification, patch installation, upgrades to the web server or modules, and security parameter changes. With each of these changes, there is the potential for an adverse effect such as a DoS, web server instability, or hosted application instability. + +To limit changes to the web server and limit exposure to any adverse effects from the changes, files such as the web server application files, libraries, and configuration files must have permissions and ownership set properly to only allow privileged users access. + +The key web service administrative and configuration tools must only be accessible by the web server staff. All users granted this authority will be documented and approved by the ISSO. Access to the IIS Manager will be limited to authorized users and administrators. + +Satisfies: SRG-APP-000380-WSR-000072, SRG-APP-000435-WSR-000147, SRG-APP-000033-WSR-000169</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target IIS 10.0 ServerDISADPMS TargetIIS 10.0 Server3535CCI-000213CCI-001813CCI-002385Restrict access to the web administration tool to only the web manager and the web manager’s designees.Right-click "InetMgr.exe", then click "Properties" from the "Context" menu. + +Select the "Security" tab. + +Review the groups and user names. + +The following accounts may have Full control privileges: + +TrustedInstaller +Web Managers +Web Manager designees +CREATOR OWNER: Full Control, Subfolders and files only + +The following accounts may have read and execute, or read permissions: + +Non Web Manager Administrators +ALL APPLICATION PACKAGES (built-in security group) +ALL RESTRICTED APPLICATION PACKAGES (built-in security group) +SYSTEM +Users + +Specific users may be granted read and execute and read permissions. + +Compare the local documentation authorizing specific users, against the users observed when reviewing the groups and users. + +If any other access is observed, this is a finding.SRG-APP-000383-WSR-000175<GroupDescription></GroupDescription>IIST-SV-000148The IIS 10.0 web server must not be running on a system providing any other role.<VulnDiscussion>Web servers provide numerous processes, features, and functionalities that utilize TCP/IP ports. Some of these processes may be deemed unnecessary or too unsecure to run on a production system. + +The web server must provide the capability to disable or deactivate network-related services deemed non-essential to the server mission, are too unsecure, or are prohibited by the PPSM CAL and vulnerability assessments.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target IIS 10.0 ServerDISADPMS TargetIIS 10.0 Server3535CCI-001762Remove all unapproved programs and roles from the production web server.Review programs installed on the OS. + +Open Control Panel. + +Open Programs and Features. + +The following programs may be installed without any additional documentation: + +Administration Pack for IIS +IIS Search Engine Optimization Toolkit +Microsoft .NET Framework version 3.5 SP1 or greater +Microsoft Web Platform Installer version 3.x or greater +Virtual Machine Additions + +Review the installed programs, if any programs are installed other than those listed above, this is a finding. + +Note: If additional software is needed and has supporting documentation signed by the ISSO, this is not a finding.SRG-APP-000383-WSR-000175<GroupDescription></GroupDescription>IIST-SV-000149The Internet Printing Protocol (IPP) must be disabled on the IIS 10.0 web server.<VulnDiscussion>The use of IPP on an IIS web server allows client access to shared printers. This privileged access could allow remote code execution by increasing the web servers attack surface. Additionally, since IPP does not support SSL, it is considered a risk and will not be deployed.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target IIS 10.0 ServerDISADPMS TargetIIS 10.0 Server3535CCI-001762Click “Start”, click “Administrative Tools”, and then click “Server Manager”. + +Expand the roles node, right-click “Print Services”, and then select “Remove Roles Services”. + +If the Internet Printing option is checked, clear the check box, click “Next”, and then click “Remove” to complete the wizard.If the Print Services role and the Internet Printing role are not installed, this check is Not Applicable. + +Navigate to the following directory: + +%windir%\web\printers + +If this folder exists, this is a finding. + +Determine whether Internet Printing is enabled: + +Click “Start”, click “Administrative Tools”, and then click “Server Manager”. + +Expand the roles node, right-click “Print Services”, and then select “Remove Roles Services”. + +If the Internet Printing option is enabled, this is a finding.SRG-APP-000435-WSR-000148<GroupDescription></GroupDescription>IIST-SV-000151The IIS 10.0 web server must be tuned to handle the operational requirements of the hosted application.<VulnDiscussion>A Denial of Service (DoS) can occur when the web server is overwhelmed and can no longer respond to additional requests. A web server not properly tuned may become overwhelmed and cause a DoS condition even with expected traffic from users. To avoid a DoS, the web server must be tuned to handle the expected traffic for the hosted applications.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target IIS 10.0 ServerDISADPMS TargetIIS 10.0 Server3535CCI-002385Access the IIS 10.0 web server registry. + +Verify the following keys are present and configured. The required setting depends upon the requirements of the application. These settings must be explicitly configured to show a conscientious tuning has been made. + +Navigate to HKLM\SYSTEM\CurrentControlSet\Services\HTTP\Parameters\ + +Configure the following registry keys to levels to accommodate the hosted applications. + +"URIEnableCache" +"UriMaxUriBytes" +"UriScavengerPeriod"If the IIS 10.0 web server is not hosting any applications, this is Not Applicable. + +If the IIS 10.0 web server is hosting applications, consult with the System Administrator to determine risk analysis performed when the application was written and deployed to the IIS 10.0 web server. + +Obtain documentation on the configuration. + +Verify, at a minimum, the following tuning settings in the registry. + +Access the IIS 10.0 web server registry. + +Verify the following keys are present and configured. The required setting depends upon the requirements of the application. + +Recommended settings are not provided as these settings must be explicitly configured to show a conscientious tuning has been made. + +Navigate to HKLM\SYSTEM\CurrentControlSet\Services\HTTP\Parameters\ +"URIEnableCache" +"UriMaxUriBytes" +"UriScavengerPeriod" + +If explicit settings are not configured for "URIEnableCache", "UriMaxUriBytes" and "UriScavengerPeriod", this is a finding.SRG-APP-000439-WSR-000152<GroupDescription></GroupDescription>IIST-SV-000152IIS 10.0 web server session IDs must be sent to the client using TLS.<VulnDiscussion>The HTTP protocol is a stateless protocol. To maintain a session, a session identifier is used. The session identifier is a piece of data used to identify a session and a user. If the session identifier is compromised by an attacker, the session can be hijacked. By encrypting the session identifier, the identifier becomes more difficult for an attacker to hijack, decrypt, and use before the session has expired.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target IIS 10.0 ServerDISADPMS TargetIIS 10.0 Server3535CCI-002418Open the IIS 10.0 Manager. + +Click the IIS 10.0 web server name. + +Under "Management" section, double-click the "Configuration Editor" icon. + +From the "Section:" drop-down list, select "system.webServer/asp". + +Expand the "session" section. + +Select "True" for the "keepSessionIdSecure" setting. + +Select "Apply" from the "Actions" pane.Open the IIS 10.0 Manager. + +Click the IIS 10.0 web server name. + +Under the "Management" section, double-click the "Configuration Editor" icon. + +From the "Section:" drop-down list, select "system.webServer/asp". + +Expand the "session" section. + +Verify the "keepSessionIdSecure" is set to "True". + +If the "keepSessionIdSecure" is not set to "True", this is a finding.SRG-APP-000439-WSR-000156<GroupDescription></GroupDescription>IIST-SV-000153An IIS 10.0 web server must maintain the confidentiality of controlled information during transmission through the use of an approved Transport Layer Security (TLS) version.<VulnDiscussion>TLS encryption is a required security setting for a private web server. Encryption of private information is essential to ensuring data confidentiality. If private information is not encrypted, it can be intercepted and easily read by an unauthorized party. A private web server must use a FIPS 140-2-approved TLS version, and all non-FIPS-approved SSL versions must be disabled. + +FIPS 140-2-approved TLS versions include TLS V1.1 or greater. NIST SP 800-52 specifies the preferred configurations for government systems.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target IIS 10.0 ServerDISADPMS TargetIIS 10.0 Server3535CCI-002418Access the IIS 10.0 Web Server. + +Access an administrator command prompt and type "regedit <enter>" to access the server's registry. + +Navigate to the following registry paths and configure the "DisabledByDefault" REG_DWORD with the appropriate values: + +HKLM\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2\Server + +With a REG_DWORD value of "0" for "DisabledByDefault" + +HKLM\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.0\Server + +HKLM\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.1\Server + +HKLM\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\SSL 2.0\Server + +HKLM\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\SSL 3.0\Server + +With a REG_DWORD value of "1" for "DisabledByDefault" + +With a REG_DWORD value of "0" for "Enabled"Access the IIS 10.0 Web Server. + +Access an administrator command prompt and type "regedit <enter>" to access the server's registry. + +Navigate to: +HKLM\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2\Server + +Verify a REG_DWORD value of "0" for "DisabledByDefault" + +Navigate to: +HKLM\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.0\Server + +HKLM\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.1\Server + +HKLM\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\SSL 2.0\Server + +HKLM\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\SSL 3.0\Server + +Verify a REG_DWORD value of "1" for "DisabledByDefault" +Verify a REG_DWORD value of "0" for "Enabled" + +If any of the respective registry paths do not exist or are configured with the wrong value, this is a finding.SRG-APP-000439-WSR-000156<GroupDescription></GroupDescription>IIST-SV-000154The IIS 10.0 web server must maintain the confidentiality of controlled information during transmission through the use of an approved Transport Layer Security (TLS) version.<VulnDiscussion>TLS is a required transmission protocol for a web server hosting controlled information. The use of TLS provides confidentiality of data in transit between the web server and client. FIPS 140-2-approved TLS versions must be enabled and non-FIPS-approved SSL versions must be disabled. + +NIST SP 800-52 defines the approved TLS versions for government applications.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target IIS 10.0 ServerDISADPMS TargetIIS 10.0 Server3535CCI-002418Configure the web server to use an approved TLS version according to NIST SP 800-52 and to disable all non-approved versions.Review the web server documentation and deployed configuration to determine which version of TLS is being used. + +If the TLS version is not TLS 1.2 or higher, according to NIST SP 800-52, or if non-FIPS-approved algorithms are enabled, this is a finding.SRG-APP-000516-WSR-000079<GroupDescription></GroupDescription>IIST-SV-000156All accounts installed with the IIS 10.0 web server software and tools must have passwords assigned and default passwords changed.<VulnDiscussion>During installation of the web server software, accounts are created for the web server to operate properly. The accounts installed can have either no password installed or a default password, which will be known and documented by the vendor and the user community. + +The first things an attacker will try when presented with a logon screen are the default user identifiers with default passwords. Installed applications may also install accounts with no password, making the logon even easier. Once the web server is installed, the passwords for any created accounts should be changed and documented. The new passwords must meet the requirements for all passwords, i.e., upper/lower characters, numbers, special characters, time until change, reuse policy, etc. + +Service accounts or system accounts that have no logon capability do not need to have passwords set or changed.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target IIS 10.0 ServerDISADPMS TargetIIS 10.0 Server3535CCI-000366Access the IIS 10.0 web server. + +Access the "Apps" menu. Under Administrative Tools, select Computer Management. + +In left pane, expand "Local Users and Groups" and click on "Users". + +Change passwords for any local accounts present that are used by IIS 10.0, then verify with System Administrator default passwords have been changed. + +Develop an internal process for changing passwords on a regular basis.Access the IIS 10.0 web server. + +Access the "Apps" menu. Under "Administrative Tools", select "Computer Management". + +In left pane, expand "Local Users and Groups" and click "Users". + +Review the local users listed in the middle pane. + +If any local accounts are present and used by IIS 10.0, verify with System Administrator that default passwords have been changed. + +If passwords have not been changed from the default, this is a finding.SRG-APP-000516-WSR-000174<GroupDescription></GroupDescription>IIST-SV-000158Unspecified file extensions on a production IIS 10.0 web server must be removed.<VulnDiscussion>By allowing unspecified file extensions to execute, the web servers attack surface is significantly increased. This increased risk can be reduced by only allowing specific ISAPI extensions or CGI extensions to run on the web server.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target IIS 10.0 ServerDISADPMS TargetIIS 10.0 Server3535CCI-000366Open the IIS 10.0 Manager. + +Click the IIS 10.0 web server name. + +Double-click the "ISAPI and CGI restrictions" icon. + +Click "Edit Feature Settings". + +Remove the check from the "Allow unspecified CGI modules" and the "Allow unspecified ISAPI modules" check boxes. + +Click "OK".Open the IIS 10.0 Manager. + +Click the IIS 10.0 web server name. + +Double-click the "ISAPI and CGI restrictions" icon. + +Click “Edit Feature Settings". + +Verify the "Allow unspecified CGI modules" and the "Allow unspecified ISAPI modules" check boxes are NOT checked. + +If either or both of the "Allow unspecified CGI modules" and the "Allow unspecified ISAPI modules" check boxes are checked, this is a finding.SRG-APP-000516-WSR-000174<GroupDescription></GroupDescription>IIST-SV-000159The IIS 10.0 web server must have a global authorization rule configured to restrict access.<VulnDiscussion>Authorization rules can be configured at the server, website, folder (including Virtual Directories), or file level. It is recommended that URL Authorization be configured to only grant access to the necessary security principals. Configuring a global Authorization rule that restricts access ensures inheritance of the settings down through the hierarchy of web directories. This will ensure access to current and future content is only granted to the appropriate principals, mitigating risk of unauthorized access.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target IIS 10.0 ServerDISADPMS TargetIIS 10.0 Server3535CCI-000366Open the IIS 10.0 Manager. + +Click the IIS 10.0 web server name. + +Double-click the "Authorization Rules" icon. + +Remove all users other than "Administrator".Open the IIS 10.0 Manager. + +Click the IIS 10.0 web server name. + +Double-click the ".NET Authorization Rules" icon. + +If any user other than "Administrator" is listed, this is a finding. + +If .NET is not installed, this is Not Applicable.SRG-APP-000001-WSR-000001<GroupDescription></GroupDescription>IIST-SV-000200The IIS 10.0 websites MaxConnections setting must be configured to limit the number of allowed simultaneous session requests.<VulnDiscussion>Resource exhaustion can occur when an unlimited number of concurrent requests are allowed on a website, facilitating a Denial of Service (DoS) attack. Mitigating this kind of attack will include limiting the number of concurrent HTTP/HTTPS requests per IP address and may include, where feasible, limiting parameter values associated with keepalive (i.e., a parameter used to limit the amount of time a connection may be inactive).</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target IIS 10.0 ServerDISADPMS TargetIIS 10.0 Server3535CCI-000054Access the IIS 10.0 IIS Manager. + +Click the IIS 10.0 server. + +Select "Configuration Editor" under the "Management" section. + +From the "Section:" drop-down list at the top of the configuration editor, locate "system.applicationHost/sites". + +Expand "siteDefaults". +Expand "limits". + +Set the "maxconnections" parameter to a value greater than zero.Access the IIS 10.0 IIS Manager. + +Click the IIS 10.0 server. + +Select "Configuration Editor" under the "Management" section. + +From the "Section:" drop-down list at the top of the configuration editor, locate "system.applicationHost/sites". + +Expand "siteDefaults". +Expand "limits". + +Review the results and verify the value is greater than zero for the "maxconnections" parameter. + +If the maxconnections parameter is set to zero, this is a finding.SRG-APP-000516-WSR-000174<GroupDescription></GroupDescription>IIST-SV-000205The IIS 10.0 web server must enable HTTP Strict Transport Security (HSTS).<VulnDiscussion>HTTP Strict Transport Security (HSTS) ensures browsers always connect to a website over TLS. HSTS exists to remove the need for redirection configurations. HSTS relies on the browser, web server, and a public "Whitelist". If the browser does not support HSTS, it will be ignored.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target IIS 10.0 ServerDISADPMS TargetIIS 10.0 Server3535CCI-000366Access the IIS 10.0 Web Server. + +Access an administrative command prompt and type the following commands, substituting proper domain name: + +%systemroot%\system32\inetsrv\appcmd.exe set config -section:system.applicationHost/sites "/[name='Contoso'].hsts.enabled:True" /commit:apphost +%systemroot%\system32\inetsrv\appcmd.exe set config -section:system.applicationHost/sites "/[name='Contoso'].hsts.max-age:480" /commit:apphost +%systemroot%\system32\inetsrv\appcmd.exe set config -section:system.applicationHost/sites "/[name='Contoso'].hsts.includeSubDomains:True" /commit:apphost +%systemroot%\system32\inetsrv\appcmd.exe set config -section:system.applicationHost/sites "/[name='Contoso'].hsts.redirectHttpToHttps:True" /commit:apphostAccess the IIS 10.0 Web Server. + +Open IIS Manager. + +In the "Connections" pane, select the server name. + +In the "Features View" pane, open "HTTP Response Headers". + +Verify an entry exists named "Strict-Transport-Security". + +Open "Strict-Transport-Security" and verify the value box contains a value greater than 0. + +Click "OK". + +If HSTS has not been enabled, this is a finding. +The recommended max age is 8 minutes (480 seconds) or greater. Any value greater than 0 is not a finding. +If the version of Windows Server does not natively support HSTS, this is not a finding. diff --git a/source/StigData/Archive/Web Server/U_MS_IIS_10-0_Site_V1R1_Manual-xccdf.log b/source/StigData/Archive/Web Server/U_MS_IIS_10-0_Site_V1R1_Manual-xccdf.log new file mode 100644 index 000000000..52cdaafd4 --- /dev/null +++ b/source/StigData/Archive/Web Server/U_MS_IIS_10-0_Site_V1R1_Manual-xccdf.log @@ -0,0 +1,3 @@ +V-100191::System Administrator::"" +V-100223::System Administrator::"" +V-100229::If the "maxAllowedContentLength" value is not explicitly set to "30000000" or less or a length documented and approved by the ISSO, this is a finding.::If the "maxAllowedContentLength" value is not explicitly set to "30000000" or less or a length approved by the ISSO, this is a finding. diff --git a/source/StigData/Archive/Web Server/U_MS_IIS_10-0_Site_V1R1_Manual-xccdf.xml b/source/StigData/Archive/Web Server/U_MS_IIS_10-0_Site_V1R1_Manual-xccdf.xml new file mode 100644 index 000000000..7f7d4a153 --- /dev/null +++ b/source/StigData/Archive/Web Server/U_MS_IIS_10-0_Site_V1R1_Manual-xccdf.xml @@ -0,0 +1,1272 @@ +acceptedMicrosoft IIS 10.0 Site Security Technical Implementation GuideThis Security Technical Implementation Guide is published as a tool to improve the security of Department of Defense (DoD) information systems. The requirements are derived from the National Institute of Standards and Technology (NIST) 800-53 and related documents. Comments or proposed revisions to this document should be sent via email to the following address: disa.stig_spt@mail.mil.DISASTIG.DOD.MILRelease: 1 Benchmark Date: 20 Mar 20201I - Mission Critical Classified<ProfileDescription></ProfileDescription>I - Mission Critical Public<ProfileDescription></ProfileDescription>I - Mission Critical Sensitive<ProfileDescription></ProfileDescription>II - Mission Support Classified<ProfileDescription></ProfileDescription>II - Mission Support Public<ProfileDescription></ProfileDescription>II - Mission Support Sensitive<ProfileDescription></ProfileDescription>III - Administrative Classified<ProfileDescription></ProfileDescription>III - Administrative Public<ProfileDescription></ProfileDescription>III - Administrative Sensitive<ProfileDescription></ProfileDescription>SRG-APP-000001-WSR-000002<GroupDescription></GroupDescription>IIST-SI-000201The IIS 10.0 website session state must be enabled.<VulnDiscussion>When the session information is stored on the client, the session ID, along with the user authorization and identity information, is sent along with each client request and is either stored in a cookie, embedded in the uniform resource locator (URL), or placed in a hidden field on the displayed form. Each of these offers advantages and disadvantages. The biggest disadvantage to all three is the hijacking of a session along with all of the user's credentials. + +When the user authorization and identity information is stored on the server in a protected and encrypted database, the communication between the client and web server will only send the session identifier, and the server can then retrieve user credentials for the session when needed. If, during transmission, the session were to be hijacked, the user's credentials would not be compromised. + +ASP.NET provides a session state, which is available as the HttpSessionState class, as a method of storing session-specific information that is visible only within the session. ASP.NET session state identifies requests from the same browser during a limited time window as a session, and provides the ability to persist variable values for the duration of that session.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target IIS 10.0 SiteDISADPMS TargetIIS 10.0 Site3537CCI-000054Follow 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. + +Select "Apply" from the "Actions" pane.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 "Session State Mode Settings" is set to "In Process", 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.SRG-APP-000001-WSR-000002<GroupDescription></GroupDescription>IIST-SI-000202The IIS 10.0 website session state cookie settings must be configured to Use Cookies mode.<VulnDiscussion>When the session information is stored on the client, the session ID, along with the user authorization and identity information, is sent along with each client request and is stored in either a cookie, embedded in the uniform resource locator (URL), or placed in a hidden field on the displayed form. Each of these offers advantages and disadvantages. The biggest disadvantage to all three is the hijacking of a session along with all of the user's credentials. + +When the user authorization and identity information is stored on the server in a protected and encrypted database, the communication between the client and website will only send the session identifier, and the server can then retrieve user credentials for the session when needed. If, during transmission, the session were to be hijacked, the user's credentials would not be compromised. + +ASP.NET provides a session state, which is available as the HttpSessionState class, as a method of storing session-specific information visible only within the session. ASP.NET session state identifies requests from the same browser during a limited time window as a session and provides the ability to persist variable values for the duration of that session. + +When using the URI mode for cookie settings under session state, IIS will reject and reissue session IDs that do not have active sessions. Configuring IIS to expire session IDs and regenerate tokens gives a potential attacker less time to capture a cookie and gain access to server content.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target IIS 10.0 SiteDISADPMS TargetIIS 10.0 Site3537CCI-000054Follow 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.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.SRG-APP-000014-WSR-000006<GroupDescription></GroupDescription>IIST-SI-000203A private IIS 10.0 website must only accept Secure Socket Layer (SSL) connections.<VulnDiscussion>Transport Layer Security (TLS) encryption is a required security setting for a private web server. Encryption of private information is essential to ensuring data confidentiality. If private information is not encrypted, it can be intercepted and easily read by an unauthorized party. A private web server must use a FIPS 140-2-approved TLS version, and all non-FIPS-approved SSL versions must be disabled. + +FIPS 140-2-approved TLS versions include TLS V1.1 or greater. NIST SP 800-52 specifies the preferred configurations for government systems.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target IIS 10.0 SiteDISADPMS TargetIIS 10.0 Site3537CCI-000068Note: If the server being reviewed is a public 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.Note: If the server being reviewed is a public IIS 10.0 web server, 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. + +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.SRG-APP-000014-WSR-000006<GroupDescription></GroupDescription>IIST-SI-000204A public IIS 10.0 website must only accept Secure Socket Layer (SSL) connections when authentication is required.<VulnDiscussion>Transport Layer Security (TLS) encryption is a required security setting for a private web server. Encryption of private information is essential to ensuring data confidentiality. If private information is not encrypted, it can be intercepted and easily read by an unauthorized party. A private web server must use a FIPS 140-2-approved TLS version, and all non-FIPS-approved SSL versions must be disabled. + +FIPS 140-2-approved TLS versions include TLS V1.1 or greater. NIST SP 800-52 specifies the preferred configurations for government systems.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target IIS 10.0 SiteDISADPMS TargetIIS 10.0 Site3537CCI-000068Note: 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.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. + +Verify "Require SSL" check box is selected. + +If the "Require SSL" check box is not selected, this is a finding.SRG-APP-000092-WSR-000055<GroupDescription></GroupDescription>IIST-SI-000206Both the log file and Event Tracing for Windows (ETW) for each IIS 10.0 website must be enabled.<VulnDiscussion>Internet Information Services (IIS) on Windows Server 2012 provides basic logging capabilities. However, because IIS takes some time to flush logs to disk, administrators do not have access to logging information in real-time. In addition, text-based log files can be difficult and time-consuming to process. + +In IIS 10.0, the administrator has the option of sending logging information to Event Tracing for Windows (ETW). This option gives the administrator the ability to use standard query tools, or create custom tools, for viewing real-time logging information in ETW. This provides a significant advantage over parsing text-based log files that are not updated in real time. + +Satisfies: SRG-APP-000092-WSR-000055, SRG-APP-000108-WSR-000166</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target IIS 10.0 SiteDISADPMS TargetIIS 10.0 Site3537CCI-000139CCI-001464Note: "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.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=1317SRG-APP-000098-WSR-000060<GroupDescription></GroupDescription>IIST-SI-000208An IIS 10.0 website behind a load balancer or proxy server must produce log records containing the source client IP, and destination information.<VulnDiscussion>Web server logging capability is critical for accurate forensic analysis. Without sufficient and accurate information, a correct replay of the events cannot be determined. + +Ascertaining the correct source (e.g., source IP), of the events is important during forensic analysis. Correctly determining the source of events will add information to the overall reconstruction of the loggable event. By determining the source of the event correctly, analysis of the enterprise can be undertaken to determine if events tied to the source occurred in other areas within the enterprise. + +A web server behind a load balancer or proxy server, when not configured correctly, will record the load balancer or proxy server as the source of every loggable event. When looking at the information forensically, this information is not helpful in the investigation of events. The web server must record with each event the client source of the event.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target IIS 10.0 SiteDISADPMS TargetIIS 10.0 Site3537CCI-000133Access 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.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.SRG-APP-000099-WSR-000061<GroupDescription></GroupDescription>IIST-SI-000209The IIS 10.0 website must produce log records that contain sufficient information to establish the outcome (success or failure) of IIS 10.0 website events.<VulnDiscussion>Web server logging capability is critical for accurate forensic analysis. Without sufficient and accurate information, a correct replay of the events cannot be determined. + +Ascertaining the success or failure of an event is important during forensic analysis. Correctly determining the outcome will add information to the overall reconstruction of the loggable event. By determining the success or failure of the event correctly, analysis of the enterprise can be undertaken to determine if events tied to the event occurred in other areas within the enterprise. + +Without sufficient information establishing the success or failure of the logged event, investigation into the cause of event is severely hindered. The success or failure also provides a means to measure the impact of an event and help authorized personnel to determine the appropriate response. Log record content that may be necessary to satisfy the requirement of this control includes, but is not limited to, time stamps, source and destination IP addresses, user/process identifiers, event descriptions, application-specific events, success/fail indications, file names involved, access control, or flow control rules invoked.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target IIS 10.0 SiteDISADPMS TargetIIS 10.0 Site3537CCI-000134Follow 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.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.SRG-APP-000100-WSR-000064<GroupDescription></GroupDescription>IIST-SI-000210The IIS 10.0 website must produce log records containing sufficient information to establish the identity of any user/subject or process associated with an event.<VulnDiscussion>Web server logging capability is critical for accurate forensic analysis. Without sufficient and accurate information, a correct replay of the events cannot be determined. + +Determining user accounts, processes running on behalf of the user, and running process identifiers also enable a better understanding of the overall event. User tool identification is also helpful to determine if events are related to overall user access or specific client tools. + +Log record content that may be necessary to satisfy the requirement of this control includes: time stamps, source and destination addresses, user/process identifiers, event descriptions, success/fail indications, file names involved, and access control or flow control rules invoked.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target IIS 10.0 SiteDISADPMS TargetIIS 10.0 Site3537CCI-001487Follow 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.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.SRG-APP-000141-WSR-000081<GroupDescription></GroupDescription>IIST-SI-000214The IIS 10.0 website must have Multipurpose Internet Mail Extensions (MIME) that invoke OS shell programs disabled.<VulnDiscussion>Controlling what a user of a hosted application can access is part of the security posture of the web server. Any time a user can access more functionality than is needed for the operation of the hosted application poses a security issue. A user with too much access can view information that is not needed for the user's job role, or could use the function in an unintentional manner. + +A MIME tells the web server what type of program various file types and extensions are and what external utilities or programs are needed to execute the file type. + +A shell is a program that serves as the basic interface between the user and the operating system, so hosted application users must not have access to these programs. Shell programs may execute shell escapes and can then perform unauthorized activities that could damage the security posture of the web server.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target IIS 10.0 SiteDISADPMS TargetIIS 10.0 Site3537CCI-000381Follow 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.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.SRG-APP-000141-WSR-000082<GroupDescription></GroupDescription>IIST-SI-000215Mappings to unused and vulnerable scripts on the IIS 10.0 website must be removed.<VulnDiscussion>IIS 10.0 will either allow or deny script execution based on file extension. The ability to control script execution is controlled through two features with IIS 10.0, Request Filtering and Handler Mappings. + +For Handler Mappings, the ISSO must document and approve all allowable file extensions the website allows (white list) and denies (black list). The white list and black list will be compared to the Handler Mappings in IIS 8. Handler Mappings at the site level take precedence over Handler Mappings at the server level.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target IIS 10.0 SiteDISADPMS TargetIIS 10.0 Site3537CCI-000381Open 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.For Handler Mappings, 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 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 black list are enabled, this is a finding.SRG-APP-000141-WSR-000083<GroupDescription></GroupDescription>IIST-SI-000216The IIS 10.0 website must have resource mappings set to disable the serving of certain file types.<VulnDiscussion>IIS 10.0 will either allow or deny script execution based on file extension. The ability to control script execution is controlled through two features with IIS 10.0, Request Filtering and Handler Mappings. + +For Request Filtering, the ISSO must document and approve all allowable file extensions the website allows (white list) and denies (black list) by the website. 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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target IIS 10.0 SiteDISADPMS TargetIIS 10.0 Site3537CCI-000381Follow 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.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.SRG-APP-000141-WSR-000085<GroupDescription></GroupDescription>IIST-SI-000217The IIS 10.0 website must have Web Distributed Authoring and Versioning (WebDAV) disabled.<VulnDiscussion>A web server can be installed with functionality that by its nature is not secure. Web Distributed Authoring (WebDAV) is an extension to the HTTP protocol that, when developed, was meant to allow users to create, change, and move documents on a server, typically a web server or web share. Allowing this functionality, development, and deployment is much easier for web authors. + +WebDAV is not widely used and has serious security concerns because it may allow clients to modify unauthorized files on the web server.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target IIS 10.0 SiteDISADPMS TargetIIS 10.0 Site3537CCI-000381Follow the procedures below for each site hosted on the IIS 10.0 web server: + +Access Server Manager on the IIS 10.0 website. + +Select the "Local Server". + +Click "Manage". + +Select "Add Roles and Features". + +Click "Next" in the "Before you begin" dialog box. + +Select "Role-based or feature-based installation" in the "Installation Type" dialog box and click "Next". + +Select the IIS 10.0 web server on the "Server Selection" dialog box. + +From the "Windows Features" dialog box, navigate to "World Wide Web Services" >> "Common HTTP Features". + +De-select "WebDAV Publishing" and click "Next" to complete removing the WebDAV Publishing feature from the IIS 10.0 web server. + +Select "Apply" from the "Actions" pane.Follow the procedures below for each site hosted on the IIS 10.0 web server: + +Open the IIS 10.0 Manager. + +Select the IIS 10.0 website. + +Review the features listed under the "IIS" section. + +If the "WebDAV Authoring Rules" icon exists, this is a finding.SRG-APP-000141-WSR-000086<GroupDescription></GroupDescription>IIST-SI-000218The IIS 10.0 production website must configure the Global .NET Trust Level.<VulnDiscussion>A web server may host too many applications. Each application will need certain system resources and privileged operations to operate correctly. An application's trust level determines the permissions granted by the ASP.NET Code Access Security (CAS) policy. An application with full trust permissions may access all resource types on a server and perform privileged operations, while applications running with partial trust have varying levels of operating permissions and access to resources. The CAS determines the permissions granted to the application on the server. Setting a level of trust compatible with the applications will limit the potential harm a compromised application could cause to a system. The web server must be configured to contain and control the applications and protect the system resources and privileged operations from those not needed by the application for operation. + +Limiting the application will confine the potential harm a compromised application could cause to a system.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance>The IIS 10.0 production website must configure the Global .NET Trust Level.</SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target IIS 10.0 SiteDISADPMS TargetIIS 10.0 Site3537CCI-000381Note: If the server being reviewed is a non-production website, this is Not Applicable. + +Follow the procedures below for each site hosted on the IIS 10.0 web server: + +Open the IIS 10.0 Manager. + +Click the site name under review. + +Double-click the ".NET Trust Level" icon. + +Set the ".NET Trust Level" to Full or less and click “Apply”. + +Select "Apply" from the "Actions" pane.Note: If the server being reviewed is a non-production website, this is Not Applicable. + +Follow the procedures below for each site hosted on the IIS 10.0 web server: + +Open the IIS 10.0 Manager. + +Click the site name under review. + +Double-click the ".NET Trust Level" icon. + +If the ".NET Trust Level" is not set to Full or less, this is a finding.SRG-APP-000142-WSR-000089<GroupDescription></GroupDescription>IIST-SI-000219Each IIS 10.0 website must be assigned a default host header.<VulnDiscussion>The web server must be configured to listen on a specified IP address and port. Without specifying an IP address and port for the web server to use, the web server will listen on all IP addresses available to the hosting server. If the web server has multiple IP addresses, i.e., a management IP address, the web server will also accept connections on the management IP address. + +Accessing the hosted application through an IP address normally used for non-application functions opens the possibility of user access to resources, utilities, files, ports, and protocols that are protected on the desired application IP address.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target IIS 10.0 SiteDISADPMS TargetIIS 10.0 Site3537CCI-000382Follow 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.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.SRG-APP-000172-WSR-000104<GroupDescription></GroupDescription>IIST-SI-000220A private IIS 10.0 website authentication mechanism must use client certificates to transmit session identifier to assure integrity.<VulnDiscussion>A DoD private website must use PKI as an authentication mechanism for web users. Information systems residing behind web servers requiring authorization based on individual identity must use the identity provided by certificate-based authentication to support access control decisions. Not using client certificates allows an attacker unauthenticated access to private websites. + +Satisfies: SRG-APP-000172-WSR-000104, SRG-APP-000224-WSR-000135, SRG-APP-000427-WSR-000186</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target IIS 10.0 SiteDISADPMS TargetIIS 10.0 Site3537CCI-000197CCI-001188CCI-002470Note: If the server being reviewed is a public IIS 10.0 web server, this is Not Applicable. +Note: If certificate handling is performed at the Proxy/Load Balancer, this is not a finding. + +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.Note: If the server being reviewed is a public IIS 10.0 web server, this is Not Applicable. +Note: If certificate handling is performed at the Proxy/Load Balancer, this is not a finding. + +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.SRG-APP-000211-WSR-000031<GroupDescription></GroupDescription>IIST-SI-000221Anonymous IIS 10.0 website access accounts must be restricted.<VulnDiscussion>Many of the security problems that occur are not the result of a user gaining access to files or data for which the user does not have permissions, but rather users are assigned incorrect permissions to unauthorized data. The files, directories, and data stored on the web server must be evaluated and a determination made concerning authorized access to information and programs on the server. Only authorized users and administrative accounts will be allowed on the host server in order to maintain the web server, applications, and review the server operations.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target IIS 10.0 SiteDISADPMS TargetIIS 10.0 Site3537CCI-001082Remove the Anonymous access account from all privileged accounts and all privileged groups.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: account name. + +Check privileged groups that may allow the anonymous account inappropriate membership: +Open "Server Manager" on the machine. + +Expand Configuration. + +Expand Local Users and Groups. + +Click "Groups". + +Review 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.SRG-APP-000224-WSR-000136<GroupDescription></GroupDescription>IIST-SI-000223The IIS 10.0 website must generate unique session identifiers that cannot be reliably reproduced.<VulnDiscussion>Communication between a client and the web server is done using the HTTP protocol, but HTTP is a stateless protocol. To maintain a connection or session, a web server will generate a session identifier (ID) for each client session when the session is initiated. The session ID allows the web server to track a user session and, in many cases, the user, if the user previously logged into a hosted application. + +By being able to guess session IDs, an attacker can easily perform a man-in-the-middle attack. To truly generate random session identifiers that cannot be reproduced, the web server session ID generator, when used twice with the same input criteria, must generate an unrelated random ID. + +The session ID generator must be a FIPS 140-2-approved generator.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target IIS 10.0 SiteDISADPMS TargetIIS 10.0 Site3537CCI-001188Follow 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.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.SRG-APP-000233-WSR-000146<GroupDescription></GroupDescription>IIST-SI-000224The IIS 10.0 website document directory must be in a separate partition from the IIS 10.0 websites system files.<VulnDiscussion>The web document (home) directory is accessed by multiple anonymous users when the web server is in production. By locating the web document (home) directory on the same partition as the web server system file, the risk for unauthorized access to these protected files is increased. Additionally, having the web document (home) directory path on the same drive as the system folders also increases the potential for a drive space exhaustion attack.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target IIS 10.0 SiteDISADPMS TargetIIS 10.0 Site3537CCI-001084Follow 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.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. + +Note: If this IIS 10.0 installation is supporting Microsoft Exchange, and not otherwise hosting any content, this requirement is Not Applicable.SRG-APP-000246-WSR-000149<GroupDescription></GroupDescription>IIST-SI-000225The IIS 10.0 website must be configured to limit the maxURL.<VulnDiscussion>Request filtering replaces URLScan in IIS, enabling administrators to create a more granular rule set with which to allow or reject inbound web content. By setting limits on web requests, it helps to ensure availability of web services and may also help mitigate the risk of buffer overflow type attacks. The MaxURL Request Filter limits the number of bytes the server will accept in a URL.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target IIS 10.0 SiteDISADPMS TargetIIS 10.0 Site3537CCI-001094Follow 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.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.SRG-APP-000246-WSR-000149<GroupDescription></GroupDescription>IIST-SI-000226The IIS 10.0 website must be configured to limit the size of web requests.<VulnDiscussion>By setting limits on web requests, it ensures availability of web services and mitigates the risk of buffer overflow type attacks. The maxAllowedContentLength Request Filter limits the number of bytes the server will accept in a request.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target IIS 10.0 SiteDISADPMS TargetIIS 10.0 Site3537CCI-001094Follow the procedures below for each site hosted on the IIS 10.0 web server: + +Open the IIS 10.0 Manager. + +Click the site name under review. + +Double-click the "Request Filtering" icon. + +Click "Edit Feature Settings" in the "Actions" pane. + +Set the "maxAllowedContentLength" value to "30000000" or less.Follow the procedures below for each site hosted on the IIS 10.0 web server: + +Open the IIS 10.0 Manager. + +Click on the site name. + +Double-click the "Request Filtering" icon. + +Click "Edit Feature Settings" in the "Actions" pane. + +If the "maxAllowedContentLength" value is not explicitly set to "30000000" or less or a length documented and approved by the ISSO, this is a finding.SRG-APP-000246-WSR-000149<GroupDescription></GroupDescription>IIST-SI-000227The IIS 10.0 websites Maximum Query String limit must be configured.<VulnDiscussion>Setting limits on web requests helps to ensure availability of web services and may also help mitigate the risk of buffer overflow type attacks. The Maximum Query String Request Filter describes the upper limit on allowable query string lengths. Upon exceeding the configured value, IIS will generate a Status Code 404.15.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target IIS 10.0 SiteDISADPMS TargetIIS 10.0 Site3537CCI-001094Follow the procedures below for each site hosted on the IIS 10.0 web server: + +Open the IIS 10.0 Manager. + +Click the site name under review. + +Double-click the "Request Filtering" icon. + +Click "Edit Feature Settings" in the "Actions" pane. + +Set the "Maximum Query String" value to "2048" or less.Follow the procedures below for each site hosted on the IIS 10.0 web server: + +Open the IIS 10.0 Manager. + +Click the site name. + +Double-click the "Request Filtering" icon. + +Click “Edit Feature Settings” in the "Actions" pane. + +If the "Maximum Query String" value is not set to "2048" or less, this is a finding.SRG-APP-000246-WSR-000149<GroupDescription></GroupDescription>IIST-SI-000228Non-ASCII characters in URLs must be prohibited by any IIS 10.0 website.<VulnDiscussion>Setting limits on web requests ensures availability of web services and mitigates the risk of buffer overflow type attacks. The allow high-bit characters Request Filter enables rejection of requests containing non-ASCII characters.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target IIS 10.0 SiteDISADPMS TargetIIS 10.0 Site3537CCI-001094Follow the procedures below for each site hosted on the IIS 10.0 web server: + +Open the IIS 10.0 Manager. + +Click the site name under review. + +Double-click the "Request Filtering" icon. + +Click "Edit Feature Settings" in the "Actions" pane. + +Uncheck the "Allow high-bit characters" check box.Follow the procedures below for each site hosted on the IIS 10.0 web server: + +Open the IIS 10.0 Manager. + +Click the site name. + +Double-click the "Request Filtering" icon. + +Click "Edit Feature Settings" in the "Actions" pane. + +If the "Allow high-bit characters" check box is checked, this is a finding. + +Note: If this IIS 10.0 installation is supporting Microsoft Exchange, and not otherwise hosting any content, this requirement is Not Applicable.SRG-APP-000246-WSR-000149<GroupDescription></GroupDescription>IIST-SI-000229Double encoded URL requests must be prohibited by any IIS 10.0 website.<VulnDiscussion>Request filtering enables administrators to create a more granular rule set with which to allow or reject inbound web content. Setting limits on web requests ensures availability of web services and mitigates the risk of buffer overflow type attacks. When the "Allow double escaping" option is disabled, it prevents attacks that rely on double-encoded requests.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target IIS 10.0 SiteDISADPMS TargetIIS 10.0 Site3537CCI-001094Follow the procedures below for each site hosted on the IIS 10.0 web server: + +Open the IIS 10.0 Manager. + +Click the site name under review. + +Double-click the "Request Filtering" icon. + +Click "Edit Feature Settings" in the "Actions" pane. + +Uncheck the "Allow double escaping" check box.Follow the procedures below for each site hosted on the IIS 10.0 web server: + +Open the IIS 10.0 Manager. + +Click the site name. + +Double-click the "Request Filtering" icon. + +Click "Edit Feature Settings" in the "Actions" pane. + +If the "Allow double escaping" check box is checked, this is a finding.SRG-APP-000246-WSR-000149<GroupDescription></GroupDescription>IIST-SI-000230Unlisted file extensions in URL requests must be filtered by any IIS 10.0 website.<VulnDiscussion>Request filtering enables administrators to create a more granular rule set to allow or reject inbound web content. Setting limits on web requests helps to ensure availability of web services and may also help mitigate the risk of buffer overflow type attacks. The allow unlisted property of the "File Extensions Request" filter enables rejection of requests containing specific file extensions not defined in the "File Extensions" filter. Tripping this filter will cause IIS to generate a Status Code 404.7.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target IIS 10.0 SiteDISADPMS TargetIIS 10.0 Site3537CCI-001094Follow the procedures below for each site hosted on the IIS 10.0 web server: + +Open the IIS 10.0 Manager. + +Click the site name under review. + +Double-click the "Request Filtering" icon. + +Click "Edit Feature Settings" in the "Actions" pane. + +Uncheck the "Allow unlisted file extensions" check box.Follow the procedures below for each site hosted on the IIS 10.0 web server: + +Open the IIS 10.0 Manager. + +Click the site name. + +Double-click the "Request Filtering" icon. + +Click "Edit Feature Settings" in the "Actions" pane. + +If the "Allow unlisted file name extensions" check box is checked, this is a finding. + +Note: If this IIS 10.0 installation is supporting Microsoft Exchange, and not otherwise hosting any content, this requirement is Not Applicable.SRG-APP-000251-WSR-000157<GroupDescription></GroupDescription>IIST-SI-000231Directory Browsing on the IIS 10.0 website must be disabled.<VulnDiscussion>Directory browsing allows the contents of a directory to be displayed upon request from a web client. If directory browsing is enabled for a directory in IIS, users could receive a web page listing the contents of the directory. If directory browsing is enabled the risk of inadvertently disclosing sensitive content is increased.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target IIS 10.0 SiteDISADPMS TargetIIS 10.0 Site3537CCI-001310Follow the procedures below for each site hosted on the IIS 10.0 web server: + +Open the IIS 10.0 Manager. + +Click the Site. + +Double-click the "Directory Browsing" icon. + +Under the "Actions" pane, click "Disabled".Follow the procedures below for each site hosted on the IIS 10.0 web server: + +Click the Site. + +Double-click the "Directory Browsing" icon. + +If "Directory Browsing" is not installed, this is Not Applicable. + +Under the "Actions" pane, verify "Directory Browsing" is "Disabled". + +If "Directory Browsing" is not "Disabled", this is a finding.SRG-APP-000266-WSR-000159<GroupDescription></GroupDescription>IIST-SI-000233Warning and error messages displayed to clients must be modified to minimize the identity of the IIS 10.0 website, patches, loaded modules, and directory paths.<VulnDiscussion>HTTP error pages contain information that could enable an attacker to gain access to an information system. Failure to prevent the sending of HTTP error pages with full information to remote requesters exposes internal configuration information to potential attackers.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target IIS 10.0 SiteDISADPMS TargetIIS 10.0 Site3537CCI-001312Follow the procedures below for each site hosted on the IIS 10.0 web server: + +Open the IIS 10.0 Manager. + +Click the site name under review. + +Double-click the "Error Pages" icon. + +Click each error message and click "Edit Feature" Setting from the "Actions" pane; set each error message to "Detailed errors for local requests and custom error pages for remote requests".Follow the procedures below for each site hosted on the IIS 10.0 web server: + +Open the IIS 10.0 Manager. + +Click the site name under review. + +Double-click the "Error Pages" icon. + +Click each error message and click "Edit Feature" setting from the "Actions" pane. + +If any error message is not set to "Detailed errors for local requests and custom error pages for remote requests", this is a finding.SRG-APP-000266-WSR-000160<GroupDescription></GroupDescription>IIST-SI-000234Debugging and trace information used to diagnose the IIS 10.0 website must be disabled.<VulnDiscussion>Setting compilation debug to false ensures detailed error information does not inadvertently display during live application usage, mitigating the risk of application information being displayed to users.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target IIS 10.0 SiteDISADPMS TargetIIS 10.0 Site3537CCI-001312Follow the procedures below for each site hosted on the IIS 10.0 web server: + +Open the IIS 10.0 Manager. + +Click the site name under review. + +Double-click ".NET Compilation". + +Scroll down to the "Behavior" section and set the value for "Debug" to "False".Note: If the ".NET feature" is not installed, this check is Not Applicable. + +Follow the procedures below for each site hosted on the IIS 10.0 web server: + +Open the IIS 10.0 Manager. + +Click the site name under review. + +Double-click ".NET Compilation". + +Scroll down to the "Behavior" section and verify the value for "Debug" is set to "False". + +If the "Debug" value is not set to "False", this is a finding.SRG-APP-000295-WSR-000012<GroupDescription></GroupDescription>IIST-SI-000235The Idle Time-out monitor for each IIS 10.0 website must be enabled.<VulnDiscussion>The idle time-out attribute controls the amount of time a worker process will remain idle before it shuts down. A worker process is idle if it is not processing requests and no new requests are received. + +The purpose of this attribute is to conserve system resources; the default value for idle time-out is 20 minutes. + +By default, the World Wide Web (WWW) service establishes an overlapped recycle, in which the worker process to be shut down is kept running until after a new worker process is started.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target IIS 10.0 SiteDISADPMS TargetIIS 10.0 Site3537CCI-002361Follow the procedures below for each site hosted on the IIS 10.0 web server: + +Open the IIS 10.0 Manager. + +Click the Application Pools. + +Highlight an Application Pool to review and click "Advanced Settings" in the "Actions" pane. + +Scroll down to the "Process Model" section and set the value for "Idle Time-out" to something other than "0". "20" or less is recommended if the amount of RAM on the system is limited.Follow the procedures below for each site hosted on the IIS 10.0 web server: + +Open the IIS 10.0 Manager. +Click the Application Pools. +Highlight an Application Pool to review and click "Advanced Settings" in the "Actions" pane. +Scroll down to the "Process Model" section and verify the value for "Idle Time-out" is not "0". + +If the "Idle Time-out" is set to "0", this is a finding.SRG-APP-000295-WSR-000134<GroupDescription></GroupDescription>IIST-SI-000236The IIS 10.0 websites connectionTimeout setting must be explicitly configured to disconnect an idle session.<VulnDiscussion>Leaving sessions open indefinitely is a major security risk. An attacker can easily use an already authenticated session to access the hosted application as the previously authenticated user. By closing sessions after a set period of inactivity, the web server can make certain that those sessions that are not closed through the user logging out of an application are eventually closed. + +Acceptable values are 5 minutes for high-value applications, 10 minutes for medium-value applications, and 20 minutes for low-value applications.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target IIS 10.0 SiteDISADPMS TargetIIS 10.0 Site3537CCI-002361Follow the procedures below for each site hosted on the IIS 10.0 web server: + +Open the IIS 10.0 Manager. + +Click the site name. + +Select "Configuration Editor" under the "Management" section. + +From the "Section:" drop-down list at the top of the configuration editor, locate "system.web/sessionState". + +Set the "timeout" to "00:20:00 or less”, using the lowest value possible depending upon the application. +Acceptable values are 5 minutes for high-value applications, 10 minutes for medium-value applications, and 20 minutes for low-value applications. + +In the "Actions" pane, click "Apply".Follow the procedures below for each site hosted on the IIS 10.0 web server: + +Open the IIS 10.0 Manager. + +Click the site name. + +Select "Configuration Editor" under the "Management" section. + +From the "Section:" drop-down list at the top of the configuration editor, locate "system.web/sessionState". + +Verify the "timeout" is set to "00:20:00 or less”, using the lowest value possible depending upon the application. +Acceptable values are 5 minutes for high-value applications, 10 minutes for medium-value applications, and 20 minutes for low-value applications. + +If "timeout" is not set to "00:20:00 or less”, this is a finding.SRG-APP-000316-WSR-000170<GroupDescription></GroupDescription>IIST-SI-000237The IIS 10.0 website must provide the capability to immediately disconnect or disable remote access to the hosted applications.<VulnDiscussion>During an attack on the web server or any of the hosted applications, the system administrator may need to disconnect or disable access by users to stop the attack. + +The web server must provide a capability to disconnect users to a hosted application without compromising other hosted applications unless deemed necessary to stop the attack. Methods to disconnect or disable connections are to stop the application service for a specified hosted application, stop the web server, or block all connections through web server access list. + +The web server capabilities used to disconnect or disable users from connecting to hosted applications and the web server must be documented to make certain that during an attack, the proper action is taken to conserve connectivity to any other hosted application if possible and to make certain log data is conserved for later forensic analysis.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target IIS 10.0 SiteDISADPMS TargetIIS 10.0 Site3537CCI-002322Prepare documented procedures for shutting down an IIS 10.0 website in the event of an attack. The procedure should, at a minimum, provide the following steps: + +Determine the respective website for the application at risk of an attack. + +Access the IIS 10.0 web server IIS 10.0 Manager. + +Select the respective website. + +In the "Actions" pane, under "Manage Website", click "Stop". + +If necessary, stop all websites. + +If necessary, stop the IIS 10.0 web server by selecting the web server in the IIS 10.0 Manager. + +In the "Actions" pane, under "Manage Server", click "Stop".Interview the System Administrator and Web Manager. + +Ask for documentation for the IIS 10.0 web server administration. + +Verify there are documented procedures for shutting down an IIS 10.0 website in the event of an attack. The procedure should, at a minimum, provide the following steps: + +Determine the respective website for the application at risk of an attack. + +Access the IIS 10.0 web server IIS 10.0 Manager. + +Select the respective website. + +In the "Actions" pane, under "Manage Website", click "Stop". + +If necessary, stop all websites. + +If necessary, stop the IIS 10.0 web server by selecting the web server in the IIS 10.0 Manager. + +In the "Actions" pane, under "Manage Server", click "Stop". + +If there are not documented procedures with, at a minimum, the mentioned steps for stopping a website, this is a finding.SRG-APP-000357-WSR-000150<GroupDescription></GroupDescription>IIST-SI-000238The IIS 10.0 website must use a logging mechanism configured to allocate log record storage capacity large enough to accommodate the logging requirements of the IIS 10.0 website.<VulnDiscussion>To make certain the logging mechanism used by the web server has sufficient storage capacity in which to write the logs, the logging mechanism must be able to allocate log record storage capacity. + +The task of allocating log record storage capacity is usually performed during initial installation of the logging mechanism. The system administrator will usually coordinate the allocation of physical drive space with the web server administrator along with the physical location of the partition and disk. Refer to NIST SP 800-92 for specific requirements on log rotation and storage dependent on the impact of the web server.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target IIS 10.0 SiteDISADPMS TargetIIS 10.0 Site3537CCI-001849Follow the procedures below for each site hosted on the IIS 10.0 web server: + +Under "IIS" double-click on the "Logging" icon. + +If necessary, in the "Logging" configuration box, redesignate a log path to a location able to house the logs. + +Under "Log File Rollover", deselect the "Do not create new log files" setting. + +Configure a schedule to rollover log files on a regular basis.Follow the procedures below for each site hosted on the IIS 10.0 web server: + +Access the IIS 10.0 web server IIS 10.0 Manager. + +Under "IIS" double-click on the "Logging" icon. + +In the "Logging" configuration box, determine the "Directory:" to which the "W3C" logging is being written. + +Confirm with the System Administrator that the designated log path is of sufficient size to maintain the logging. + +Under "Log File Rollover", verify "Do not create new log files" is not selected. + +Verify a schedule is configured to rollover log files on a regular basis. + +Consult with the System Administrator to determine if there is a documented process for moving the log files off of the IIS 10.0 web server to another logging device. + +If the designated logging path device is not of sufficient space to maintain all log files and there is not a schedule to rollover files on a regular basis, this is a finding.SRG-APP-000383-WSR-000175<GroupDescription></GroupDescription>IIST-SI-000239The IIS 10.0 websites must use ports, protocols, and services according to Ports, Protocols, and Services Management (PPSM) guidelines.<VulnDiscussion>Web servers provide numerous processes, features, and functionalities that use TCP/IP ports. Some of these processes may be deemed unnecessary or too unsecure to run on a production system. + +The web server must provide the capability to disable or deactivate network-related services deemed to be non-essential to the server mission, too unsecure, or prohibited by the PPSM CAL and vulnerability assessments. + +Failure to comply with DoD ports, protocols, and services (PPS) requirements can result in compromise of enclave boundary protections and/or functionality of the AIS. + +The ISSM will ensure web servers are configured to use only authorized PPS in accordance with the Network Infrastructure STIG, DoD Instruction 8551.1, PPSM, and the associated PPS Assurance Category Assignments List.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target IIS 10.0 SiteDISADPMS TargetIIS 10.0 Site3537CCI-001762Follow the procedures below for each site hosted on the IIS 10.0 web server: + +Open the IIS 10.0 Manager. + +Click the site name under review. + +In the "Action" Pane, click "Bindings". + +Edit to change an existing binding and set the correct ports and protocol.Review the website to determine if HTTP and HTTPs (e.g., 80 and 443) are used in accordance with those ports and services registered and approved for use by the DoD PPSM. Any variation in PPS will be documented, registered, and approved by the PPSM. + +Follow the procedures below for each site hosted on the IIS 10.0 web server: + +Open the IIS 10.0 Manager. + +Click the site name under review. + +In the "Action" Pane, click "Bindings". + +Review the ports and protocols. If unknown ports or protocols are used, then this is a finding.SRG-APP-000427-WSR-000186<GroupDescription></GroupDescription>IIST-SI-000241The IIS 10.0 website must only accept client certificates issued by DoD PKI or DoD-approved PKI Certification Authorities (CAs).<VulnDiscussion>The use of a DoD PKI certificate ensures clients the private website they are connecting to is legitimate, and is an essential part of the DoD defense-in-depth strategy.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target IIS 10.0 SiteDISADPMS TargetIIS 10.0 Site3537CCI-002470Follow the procedures below for each site hosted on the IIS 10.0 web server: + +Open the IIS 10.0 Manager. + +Click the Server name. + +Double-click "Server Certificates". + +Click "Import" under the "Actions" pane. + +Browse to the DoD certificate location, select it, and click "OK". + +Remove any non-DoD certificates if present. + +Click on the site needing the certificate. + +Select "Bindings" under the "Actions" pane. + +Click on the binding needing a certificate and select "Edit", or add a site binding for HTTPS. + +Assign the certificate to the website by choosing it under the "SSL Certificate" drop-down and clicking "OK".Follow the procedures below for each site hosted on the IIS 10.0 web server: + +Open the IIS 10.0 Manager. + +Click the site name under review. + +Click "Bindings" in the "Action" Pane. + +Click the "HTTPS type" from the box. + +Click "Edit". + +Click "View" and then review and verify the certificate path. + +If the list of CAs in the trust hierarchy does not lead to the DoD PKI Root CA, DoD-approved external certificate authority (ECA), or DoD-approved external partner, this is a finding. + +If HTTPS is not an available type under site bindings, this is a finding. + +If HTTPS is not an available type under site bindings, and the Web Server ONLY communicates directly with a load balancer/proxy server with IP address and Domain Restrictions in place, this is not a finding.SRG-APP-000429-WSR-000113<GroupDescription></GroupDescription>IIST-SI-000242The IIS 10.0 private website must employ cryptographic mechanisms (TLS) and require client certificates.<VulnDiscussion>When data is written to digital media, such as hard drives, mobile computers, external/removable hard drives, personal digital assistants, flash/thumb drives, etc., there is risk of data loss and data compromise. User identities and passwords stored on the hard drive of the hosting hardware must be encrypted to protect the data from easily being discovered and used by an unauthorized user to access the hosted applications. The cryptographic libraries and functionality used to store and retrieve the user identifiers and passwords must be part of the web server. + +Satisfies: SRG-APP-000429-WSR-000113, SRG-APP-000439-WSR-000151, SRG-APP-000441-WSR-000181, SRG-APP-000442-WSR-000182</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target IIS 10.0 SiteDISADPMS TargetIIS 10.0 Site3537CCI-002476Follow 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.Note: If SSL is installed on load balancer/proxy server through which traffic is routed to the IIS 10.0 server, and the IIS 10.0 server receives traffic from the load balancer/proxy server, the SSL requirement must be met on the load balancer/proxy server. + +Note: If this is a public facing web server, 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. +If the "sslFlags" is not set to "ssl128", this is a finding.SRG-APP-000439-WSR-000152<GroupDescription></GroupDescription>IIST-SI-000244IIS 10.0 website session IDs must be sent to the client using TLS.<VulnDiscussion>The HTTP protocol is a stateless protocol. To maintain a session, a session identifier is used. The session identifier is a piece of data used to identify a session and a user. If the session identifier is compromised by an attacker, the session can be hijacked. By encrypting the session identifier, the identifier becomes more difficult for an attacker to hijack, decrypt, and use before the session has expired.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target IIS 10.0 SiteDISADPMS TargetIIS 10.0 Site3537CCI-002418Follow the procedures below for each site hosted on the IIS 10.0 web server: + +Access the IIS 10.0 Manager. + +Select the website being reviewed. + +Under "Management" section, double-click the "Configuration Editor" icon. + +From the "Section:" drop-down list, select "system.webServer/asp". + +Expand the "session" section. + +Select "True" for the "keepSessionIdSecure" setting. + +Select "Apply" from the "Actions" pane.Follow the procedures below for each site hosted on the IIS 10.0 web server: + +Access the IIS 10.0 Manager. + +Select the website being reviewed. + +Under "Management" section, double-click the "Configuration Editor" icon. + +From the "Section:" drop-down list, select "system.webServer/asp". + +Expand the "session" section. + +Verify the "keepSessionIdSecure" is set to "True". + +If the "keepSessionIdSecure" is not set to "True", this is a finding.SRG-APP-000439-WSR-000154<GroupDescription></GroupDescription>IIST-SI-000246Cookies exchanged between the IIS 10.0 website and the client must have cookie properties set to prohibit client-side scripts from reading the cookie data.<VulnDiscussion>A cookie can be read by client-side scripts easily if cookie properties are not set properly. By allowing cookies to be read by the client-side scripts, information such as session identifiers could be compromised and used by an attacker who intercepts the cookie. Setting cookie properties (i.e., HttpOnly property) to disallow client-side scripts from reading cookies better protects the information inside the cookie. + +Satisfies: SRG-APP-000439-WSR-000154, SRG-APP-000439-SSR-000155, SRG-APP-000439-WSR-000153</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target IIS 10.0 SiteDISADPMS TargetIIS 10.0 Site3537CCI-002418Note: If the server being reviewed is a public IIS 10.0 web server, this is Not Applicable. + +Follow the procedures below for each site hosted on the IIS 10.0 web server: + +Access the IIS 10.0 Manager. +Under "Management" section, double-click the "Configuration Editor" icon. +From the "Section:" drop-down list, select "system.web/httpCookies". +Set the "require SSL" to "True". + +From the "Section:" drop-down list, select "system.web/sessionState". +Set the "compressionEnabled" to "False". + +Select "Apply" from the "Actions" pane.Note: If the server being reviewed is a public IIS 10.0 web server, 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. + +Follow the procedures below for each site hosted on the IIS 10.0 web server: + +Access the IIS 10.0 Manager. +Under the "Management" section, double-click the "Configuration Editor" icon. +From the "Section:" drop-down list, select "system.web/httpCookies". +Verify the "require SSL" is set to "True". + +From the "Section:" drop-down list, select "system.web/sessionState". +Verify the "compressionEnabled" is set to "False". + +If both the "system.web/httpCookies:require SSL" is set to "True" and the "system.web/sessionState:compressionEnabled" is set to "False", this is not a finding.SRG-APP-000516-WSR-000174<GroupDescription></GroupDescription>IIST-SI-000251The IIS 10.0 website must have a unique application pool.<VulnDiscussion>Application pools isolate sites and applications to address reliability, availability, and security issues. Sites and applications may be grouped according to configurations, although each site will be associated with a unique application pool.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target IIS 10.0 SiteDISADPMS TargetIIS 10.0 Site3537CCI-000366Open the IIS 10.0 Manager. + +Click the site name under review. + +Assign a unique application pool to each website.Note: If the IIS Application Pool is hosting Microsoft SharePoint, this is Not Applicable. + +If this IIS 10.0 installation is supporting Microsoft Exchange, and not otherwise hosting any content, this requirement is Not Applicable. + +Open the IIS 10.0 Manager. + +Click "Application Pools". + +In the list of Application Pools, review the "Applications" column and verify unique application pools for each website. + +If any Application Pools are being used for more than one website, this is a finding.SRG-APP-000516-WSR-000174<GroupDescription></GroupDescription>IIST-SI-000252The maximum number of requests an application pool can process for each IIS 10.0 website must be explicitly set.<VulnDiscussion>IIS application pools can be periodically recycled to avoid unstable states possibly leading to application crashes, hangs, or memory leaks. By default, application pool recycling is overlapped, which means the worker process to be shut down is kept running until after a new worker process is started. After a new worker process starts, new requests are passed to it. The old worker process shuts down after it finishes processing its existing requests, or after a configured time-out, whichever comes first. This way of recycling ensures uninterrupted service to clients.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target IIS 10.0 SiteDISADPMS TargetIIS 10.0 Site3537CCI-000366Open the IIS 10.0 Manager. + +Click "Application Pools". + +Highlight an Application Pool and click "Advanced Settings" in the "Action" Pane. + +Scroll down to the "Recycling section" and set the value for "Request Limit" to greater than "0". + +Click "OK".Note: If the IIS Application Pool is hosting Microsoft SharePoint, this is Not Applicable. + +If this IIS 10.0 installation is supporting Microsoft Exchange, and not otherwise hosting any content, this requirement is Not Applicable. + +Open the IIS 10.0 Manager. + +Perform for each Application Pool. + +Click "Application Pools". + +Highlight an Application Pool and click "Advanced Settings" in the "Action" Pane. + +Scroll down to the "Recycling section" and verify the value for "Request Limit" is set to a value other than "0". + +If the "Request Limit" is set to a value of "0", this is a finding.SRG-APP-000516-WSR-000174<GroupDescription></GroupDescription>IIST-SI-000253The amount of virtual memory an application pool uses for each IIS 10.0 website must be explicitly set.<VulnDiscussion>IIS application pools can be periodically recycled to avoid unstable states possibly leading to application crashes, hangs, or memory leaks. By default, application pool recycling is overlapped, which means the worker process to be shut down is kept running until after a new worker process is started. After a new worker process starts, new requests are passed to it. The old worker process shuts down after it finishes processing its existing requests, or after a configured time-out, whichever comes first. This way of recycling ensures uninterrupted service to clients.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target IIS 10.0 SiteDISADPMS TargetIIS 10.0 Site3537CCI-000366Open the IIS 10.0 Manager. + +Click “Application Pools”. + +Perform the following for each Application Pool: + +Highlight an Application Pool and click "Advanced Settings" in the "Action" Pane. + +In the "Advanced Settings" dialog box scroll down to the "Recycling" section and set the value for "Virtual Memory Limit" to a value other than "0". + +Click "OK".Note: If the IIS Application Pool is hosting Microsoft SharePoint, this is Not Applicable. + +If this IIS 10.0 installation is supporting Microsoft Exchange, and not otherwise hosting any content, this requirement is Not Applicable. + +Open the IIS 10.0 Manager. + +Perform the following for each Application Pool: + +Click "Application Pools". + +Highlight an Application Pool and click "Advanced Settings" in the Action Pane. + +In the "Advanced Settings" dialog box scroll down to the "Recycling" section and verify the value for "Virtual Memory Limit" is not set to "0". + +If the value for "Virtual Memory Limit" is set to "0", this is a finding.SRG-APP-000516-WSR-000174<GroupDescription></GroupDescription>IIST-SI-000254The amount of private memory an application pool uses for each IIS 10.0 website must be explicitly set.<VulnDiscussion>IIS application pools can be periodically recycled to avoid unstable states possibly leading to application crashes, hangs, or memory leaks. By default, application pool recycling is overlapped, which means the worker process to be shut down is kept running until after a new worker process is started. After a new worker process starts, new requests are passed to it. The old worker process shuts down after it finishes processing its existing requests, or after a configured time-out, whichever comes first. This way of recycling ensures uninterrupted service to clients.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target IIS 10.0 SiteDISADPMS TargetIIS 10.0 Site3537CCI-000366Open the IIS 10.0 Manager. + +Click "Application Pools". + +Perform the following for each Application Pool: + +Highlight an Application Pool and click "Advanced Settings" in the "Action" Pane. + +Scroll down to the "Recycling" section and set the value for "Private Memory Limit" to a value other than "0".Note: If the IIS Application Pool is hosting Microsoft SharePoint, this is Not Applicable. + +If this IIS 10.0 installation is supporting Microsoft Exchange, and not otherwise hosting any content, this requirement is Not Applicable. + +Open the IIS 10.0 Manager. + +Perform the following for each Application Pool: + +Click "Application Pools". + +Highlight an Application Pool and click "Advanced Settings" in the "Action" Pane. + +Scroll down to the "Recycling" section and verify the value for "Private Memory Limit" is set to a value other than "0". + +If the "Private Memory Limit" is set to a value of "0", this is a finding.SRG-APP-000516-WSR-000174<GroupDescription></GroupDescription>IIST-SI-000255The application pool for each IIS 10.0 website must have a recycle time explicitly set.<VulnDiscussion>Application pools can be periodically recycled to avoid unstable states possibly leading to application crashes, hangs, or memory leaks.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target IIS 10.0 SiteDISADPMS TargetIIS 10.0 Site3537CCI-000366Open the IIS 10.0 Manager. + +Click "Application Pools". + +Perform the following for each Application Pool: + +Highlight an Application Pool and click "Advanced Settings" in the "Action" Pane. + +Scroll down to the "Recycling" section and expand the "Generate Recycle Event Log Entry" section. + +Set both the "Regular time interval" and "Specific time" options to "True".Note: If the IIS Application Pool is hosting Microsoft SharePoint, this is Not Applicable. + +If this IIS 10.0 installation is supporting Microsoft Exchange, and not otherwise hosting any content, this requirement is Not Applicable. + +Open the IIS 10.0 Manager. + +Perform the following for each Application Pool: + +Click "Application Pools". + +Highlight an Application Pool and click "Advanced Settings" in the "Action" Pane. + +Scroll down to the "Recycling" section and expand the "Generate Recycle Event Log Entry" section. + +Verify both the "Regular time interval" and "Specific time" options are set to "True". + +If both the "Regular time interval" and "Specific time" options are not set to "True", this is a finding.SRG-APP-000516-WSR-000174<GroupDescription></GroupDescription>IIST-SI-000257The application pools pinging monitor for each IIS 10.0 website must be enabled.<VulnDiscussion>Windows Process Activation Service (WAS) manages application pool configurations and may flag a worker process as unhealthy and shut it down. An application pool’s pinging monitor must be enabled to confirm worker processes are functional. A lack of response from the worker process might mean the worker process does not have a thread to respond to the ping request, or it is hanging for some other reason. The ping interval and ping response time may need adjustment to gain access to timely information about application pool health without triggering false, unhealthy conditions; for example, instability caused by an application.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target IIS 10.0 SiteDISADPMS TargetIIS 10.0 Site3537CCI-000366Open the IIS 10.0 Manager. + +Click "Application Pools". + +Perform the following for each Application Pool: + +Highlight an Application Pool to review and click "Advanced Settings" in the "Actions" pane. + +Scroll down to the "Process Model" section and set the value for "Ping Enabled" to "True". + +Click "OK".Open the Internet Information Services (IIS) Manager. + +Click "Application Pools". + +Perform the following for each Application Pool: + +Highlight an Application Pool to review and click "Advanced Settings" in the "Actions" pane. + +Scroll down to the "Process Model" section and verify the value for "Ping Enabled" is set to "True". + +If the value for "Ping Enabled" is not set to "True", this is a finding.SRG-APP-000516-WSR-000174<GroupDescription></GroupDescription>IIST-SI-000258The application pools rapid fail protection for each IIS 10.0 website must be enabled.<VulnDiscussion>Rapid fail protection is a feature that interrogates the health of worker processes associated with websites and web applications. It can be configured to perform a number of actions such as shutting down and restarting worker processes that have reached failure thresholds. By not setting rapid fail protection, the web server could become unstable in the event of a worker process crash potentially leaving the web server unusable.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target IIS 10.0 SiteDISADPMS TargetIIS 10.0 Site3537CCI-000366Open the IIS 10.0 Manager. + +Click "Application Pools". + +Perform the following for each Application Pool: + +Highlight an Application Pool to review and click "Advanced Settings" in the "Actions" pane. + +Scroll down to the "Rapid Fail Protection" section and set the value for "Enabled" to "True". + +Click "OK".Note: If the IIS Application Pool is hosting Microsoft SharePoint, this is Not Applicable. + +If this IIS 10.0 installation is supporting Microsoft Exchange, and not otherwise hosting any content, this requirement is Not Applicable. + +Open the IIS 10.0 Manager. + +Click "Application Pools". + +Perform the following for each Application Pool: + +Highlight an Application Pool to review and click "Advanced Settings" in the "Actions" pane. + +Scroll down to the "Rapid Fail Protection" section and verify the value for "Enabled" is set to "True". + +If the "Rapid Fail Protection:Enabled" is not set to "True", this is a finding.SRG-APP-000516-WSR-000174<GroupDescription></GroupDescription>IIST-SI-000259The application pools rapid fail protection settings for each IIS 10.0 website must be managed.<VulnDiscussion>Windows Process Activation Service (WAS) manages application pool configuration and may flag a worker process as unhealthy and shut it down. The rapid fail protection must be set to a suitable value. A lack of response from the worker process might mean the worker process does not have a thread to respond to the ping request, or that it is hanging for some other reason. The ping interval and ping response time may need adjustment to gain access to timely information about application pool health without triggering false, unhealthy conditions.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target IIS 10.0 SiteDISADPMS TargetIIS 10.0 Site3537CCI-000366Open the IIS 10.0 Manager. + +Click "Application Pools". + +Perform the following for each Application Pool: + +Highlight an Application Pool to review and click "Advanced Settings" in the "Actions" pane. + +Scroll down to the "Rapid Fail Protection" section and set the value for "Failure Interval" to "5" or less. + +Click "OK".Note: If the IIS Application Pool is hosting Microsoft SharePoint, this is Not Applicable. + +If this IIS 10.0 installation is supporting Microsoft Exchange, and not otherwise hosting any content, this requirement is Not Applicable. + +Open the IIS 10.0 Manager. + +Click "Application Pools". + +Perform the following for each Application Pool: + +Highlight an Application Pool to review and click "Advanced Settings" in the "Actions" pane. + +Scroll down to the "Rapid Fail Protection" section and verify the value for "Failure Interval" is set to "5". + +If the "Failure Interval" is not set to "5" or less, this is a finding.SRG-APP-000141-WSR-000087<GroupDescription></GroupDescription>IIST-SI-000261Interactive scripts on the IIS 10.0 web server must be located in unique and designated folders.<VulnDiscussion>CGI and ASP scripts represent one of the most common and exploitable means of compromising a web server. All CGI and ASP program files must be segregated into their own unique folder to simplify the protection of these files. ASP scripts must be placed into a unique folder only containing other ASP scripts. JAVA and other technology-specific scripts must also be placed into their own unique folders. The placement of CGI, ASP, or equivalent scripts to special folders gives the Web Manager or the System Administrator (SA) control over what goes into those folders and to facilitate access control at the folder level.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target IIS 10.0 SiteDISADPMS TargetIIS 10.0 Site3537CCI-000381All interactive programs must be placed in unique designated folders based on CGI or ASP script type. + +Open the IIS 10.0 Manager. + +Right-click the IIS 10.0 web server name and select "Explore". + +Search for the listed script extensions. + +Move each script type to its unique designated folder. + +Set the permissions to the scripts folders as follows: + +Administrators: FULL +TrustedInstaller: FULL +SYSTEM: FULL +ApplicationPoolId:READ +Custom Service Account: READ +Users: READ +ALL APPLICATION PACKAGES: READDetermine whether scripts are used on the web server for the target website. Common file extensions include, but are not limited to: .cgi, .pl, .vbs, .class, .c, .php, and .asp. + +All interactive programs must be placed in unique designated folders based on CGI or ASP script type. For modular and/or third-party applications, it is permissible to have script files in multiple folders. + +Open the IIS 10.0 Manager. + +Right-click the IIS 10.0 web site name and select "Explore". + +Search for the listed script extensions. Each script type must be in its unique designated folder. + +If scripts are not segregated from web content and in their own unique folders, this is a finding.SRG-APP-000141-WSR-000087<GroupDescription></GroupDescription>IIST-SI-000262Interactive scripts on the IIS 10.0 web server must have restrictive access controls.<VulnDiscussion>CGI is a programming standard for interfacing external applications with information servers, such as HTTP or web servers. CGI, represented by all upper case letters, should not be confused with the .cgi file extension. The .cgi file extension does represent a CGI script, but CGI scripts may be written in a number of programming languages (e.g., PERL, C, PHP, and JavaScript), each having their own unique file extension. + +The use of CGI scripts represent one of the most common and exploitable means of compromising a web server. By definition, CGI scripts are executable by the operating system of the host server. While access control is provided via the web service, the execution of CGI programs is not limited unless the System Administrator (SA) or the Web Manager takes specific measures. CGI programs can access and alter data files, launch other programs, and use the network.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target IIS 10.0 SiteDISADPMS TargetIIS 10.0 Site3537CCI-000381Determine whether scripts are used on the web server for the subject website. Common file extensions include, but are not limited to: .cgi, .pl, .vb, .class, .c, .php, and .asp. + +If the website does not utilize CGI, this finding is NA. + +All interactive programs must have restrictive permissions. + +Open the IIS 10.0 Manager. + +Right-click the IIS 10.0 web server name and select "Explore". + +Search for the listed script extensions. + +Set the permissions to the CGI scripts as follows: + +Administrators: FULL +TrustedInstaller: FULL +ALL APPLICATION PACKAGES: Read +ALL RESTRICTED APPLICATION PACKAGES: Read +SYSTEM: FULL +ApplicationPoolId: READ +Custom Service Account: READ +Users: READDetermine whether scripts are used on the web server for the subject website. Common file extensions include, but are not limited to: .cgi, .pl, .vb, .class, .c, .php, and .asp. + +If the website does not utilize CGI, this finding is Not Applicable. + +All interactive programs must have restrictive permissions. + +Open the IIS 10.0 Manager. + +Right-click the IIS 10.0 web site name and select "Explore". + +Search for the listed script extensions. + +Review the permissions to the CGI scripts and verify only the permissions listed, or more restrictive permissions are assigned. + +Administrators: FULL +TrustedInstaller: FULL +ALL APPLICATION PACKAGES: Read +ALL RESTRICTED APPLICATION PACKAGES: Read +SYSTEM: FULL +ApplicationPoolId: READ +Custom Service Account: READ +Users: READ + +If the permissions are less restrictive than listed above, this is a finding.SRG-APP-000141-WSR-000087<GroupDescription></GroupDescription>IIST-SI-000263Backup interactive scripts on the IIS 10.0 server must be removed.<VulnDiscussion>Copies of backup files will not execute on the server, but they can be read by the anonymous user if special precautions are not taken. Such backup copies contain the same sensitive information as the actual script being executed and, as such, are useful to malicious users. Techniques and systems exist today to search web servers for such files and are able to exploit the information contained in them.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target IIS 10.0 SiteDISADPMS TargetIIS 10.0 Site3537CCI-000381Remove the backup files from the production web server.Determine whether scripts are used on the web server for the subject website. Common file extensions include, but are not limited to: .cgi, .pl, .vb, .class, .c, .php, .asp, and .aspx. The scope of this requirement is to analyze only within the web server content directories, not the entire underlying operating system. + +If the website does not utilize CGI, this finding is Not Applicable. + +Open the IIS 10.0 Manager. + +Right-click the IIS 10.0 web site name and select "Explore". + +Search for the listed script extensions + +Search for the following files: *.bak, *.old, *.temp, *.tmp, *.backup, or “copy of...”. + +If files with these extensions are found, this is a finding.SRG-APP-000516-WSR-000174<GroupDescription></GroupDescription>IIST-SI-000264The required DoD banner page must be displayed to authenticated users accessing a DoD private website.<VulnDiscussion>A consent banner will be in place to inform prospective entrants the website they are about to enter is a DoD website and their activity is subject to monitoring. The document, DoDI 8500.01, establishes the policy on the use of DoD information systems. It requires the use of a standard Notice and Consent Banner and standard text to be included in user agreements. The requirement for the banner is for websites with security and access controls. These are restricted and not publicly accessible. If the website does not require authentication/authorization for use, then the banner does not need to be present. A manual check of the document root directory for a banner page file (such as banner.html) or navigation to the website via a browser can be used to confirm the information provided from interviewing the web staff.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target IIS 10.0 SiteDISADPMS TargetIIS 10.0 Site3537CCI-000366Configure a DoD private website to display the required DoD banner page when authentication is required for user access.Note: This requirement is only applicable for private DoD websites. + +If a banner is required, the following banner page must be in place: + +“You are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only. + +By using this IS (which includes any device attached to this IS), you consent to the following conditions: + +-The USG routinely intercepts and monitors communications on this IS for purposes including, but not limited to, penetration testing, COMSEC monitoring, network operations and defense, personnel misconduct (PM), law enforcement (LE), and counterintelligence (CI) investigations. + +- At any time, the USG may inspect and seize data stored on this IS. + +- Communications using, or data stored on, this IS are not private, are subject to routine monitoring, interception, and search, and may be disclosed or used for any USG-authorized purpose. + +- This IS includes security measures (e.g., authentication and access controls) to protect USG interests—not for your personal benefit or privacy. + +- Notwithstanding the above, using this IS does not constitute consent to PM, LE or CI investigative searching or monitoring of the content of privileged communications, or work product, related to personal representation or services by attorneys, psychotherapists, or clergy, and their assistants. Such communications and work product are private and confidential. See User Agreement for details.” + +OR + +If your system cannot meet the character limits to store this amount of text in the banner, the following is another option for the warning banner: + +"I've read & consent to terms in IS user agreem't." + +NOTE: While DoDI 8500.01 does not contain a copy of the banner to be used, it does point to the RMF Knowledge Service for a copy of the required text. It is also noted that the banner is to be displayed only once when the individual enters the site and not for each page. + +If the access-controlled website does not display this banner page before entry, this is a finding. diff --git a/source/StigData/Processed/IISServer-10.0-1.1.org.default.xml b/source/StigData/Processed/IISServer-10.0-1.1.org.default.xml new file mode 100644 index 000000000..b42a19d87 --- /dev/null +++ b/source/StigData/Processed/IISServer-10.0-1.1.org.default.xml @@ -0,0 +1,11 @@ + + + + + diff --git a/source/StigData/Processed/IISServer-10.0-1.1.xml b/source/StigData/Processed/IISServer-10.0-1.1.xml new file mode 100644 index 000000000..2274b0c55 --- /dev/null +++ b/source/StigData/Processed/IISServer-10.0-1.1.xml @@ -0,0 +1,1484 @@ + + + + <VulnDiscussion>Logging onto a web server remotely using an unencrypted protocol or service when performing updates and maintenance is a major risk. Data, such as user account, is transmitted in plaintext and can easily be compromised. When performing remote administrative tasks, a protocol or service that encrypts the communication channel must be used. + +An alternative to remote administration of the web server is to perform web server administration locally at the console. Local administration at the console implies physical access to the server.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + False + False + + If web administration is performed at the console, this check is NA. + +If web administration is performed remotely the following checks will apply: + +If administration of the server is performed remotely, it will only be performed securely by system administrators. + +If website administration or web application administration has been delegated, those users will be documented and approved by the ISSO. + +Remote administration must be in compliance with any requirements contained within the Windows Server STIGs, and any applicable Network STIGs. + +Remote administration of any kind will be restricted to documented and authorized personnel. + +All users performing remote administration must be authenticated. + +All remote sessions will be encrypted and utilize FIPS 140-2-approved protocols. + +FIPS 140-2-approved TLS versions include TLS V1.1 or greater. + +Review with site management how remote administration is configured on the website, if applicable. + +If remote management meets the criteria listed above, this is not a finding. + +If remote management is utilized and does not meet the criteria listed above, this is a finding. + + + <VulnDiscussion>User management and authentication can be an essential part of any application hosted by the web server. Along with authenticating users, the user management function must perform several other tasks enterprise-wide, such as password complexity, locking users after a configurable number of failed logons, and management of temporary and emergency accounts. + +The web server contains a minimal user management function, but the web server user management function does not offer enterprise-wide user management, and user management is not the primary function of the web server. User management for the hosted applications should be done through a facility built for enterprise-wide user management, such as LDAP and Active Directory.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + False + False + + Interview the System Administrator about the role of the IIS 10.0 web server. + +If the IIS 10.0 web server is hosting an application, have the SA provide supporting documentation on how the application's user management is accomplished outside of the IIS 10.0 web server. + +If the IIS 10.0 web server is not hosting an application, this is Not Applicable. + +If the IIS web server is performing user management for hosted applications, this is a finding. + +If the IIS 10.0 web server is hosting an application and the SA cannot provide supporting documentation on how the application's user management is accomplished outside of the IIS 10.0 web server, this is a finding. + + + <VulnDiscussion>A web server can provide many features, services, and processes. Some of these may be deemed unnecessary or too unsecure to run on a production DoD system. + +The web server must provide the capability to disable, uninstall, or deactivate functionality and services deemed non-essential to the web server mission or that adversely impact server performance.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + False + False + + Click “Start”. + +Open Control Panel. + +Click “Programs”. + +Click “Programs and Features”. + +Review the installed programs. If any programs are installed other than those required for the IIS 10.0 web services, this is a finding. + +Note: If additional software is needed, supporting documentation must be signed by the ISSO. + + + <VulnDiscussion>As a rule, accounts on a web server are to be kept to a minimum. Only administrators, web managers, developers, auditors, and web authors require accounts on the machine hosting the web server. This is in addition to the anonymous web user account. The resources to which these accounts have access must also be closely monitored and controlled. Only the SA needs access to all the system’s capabilities, while the web administrator and associated staff require access and control of the web content and web server configuration files. The anonymous web user account must not have access to system resources as that account could then control the server.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + False + False + + Obtain a list of the user accounts with access to the system, including all local and domain accounts. + +Review the privileges to the web server for each account. + +Verify with the system administrator or the ISSO that all privileged accounts are mission essential and documented. + +Verify with the system administrator or the ISSO that all non-administrator access to shell scripts and operating system functions are mission essential and documented. + +If undocumented privileged accounts are found, this is a finding. + +If undocumented non-administrator access to shell scripts and operating system functions are found, this is a finding. + +If this IIS 10 installation is supporting Microsoft Exchange, and not otherwise hosting any content, this requirement is Not Applicable. + + + <VulnDiscussion>Making certain that the web server has not been updated by an unauthorized user is always a concern. Adding patches, functions, and modules that are untested and not part of the baseline opens the possibility for security risks. The web server must offer, and not hinder, a method that allows for the quick and easy reinstallation of a verified and patched baseline to guarantee the production web server is up-to-date and has not been modified to add functionality or expose security risks. + +When the web server does not offer a method to roll back to a clean baseline, external methods, such as a baseline snapshot or virtualizing the web server, can be used.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + False + False + + Interview the System Administrator for the IIS 10.0 web server. + +Ask for documentation on the disaster recovery methods tested and planned for the IIS 10.0 web server in the event of the necessity for rollback. + +If documentation for a disaster recovery has not been established, this is a finding. + + + <VulnDiscussion>The indexing service can be used to facilitate a search function for websites. Enabling indexing may facilitate a directory traversal exploit and reveal unwanted information to a malicious user. Indexing must be limited to web document directories only.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + False + False + + Access the IIS 10.0 Web Server. + +Access an administrator command prompt and type "regedit <enter>" to access the server's registry. + +Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\ContentIndex\Catalogs\. + +If this key exists, then indexing is enabled. + +If the key does not exist, this check is Not Applicable. + +Review the Catalog keys to determine if directories other than web document directories are being indexed. + +If so, this is a finding. + + + <VulnDiscussion>Logging into a web server remotely using an unencrypted protocol or service when performing updates and maintenance is a major risk. Data, such as user account, is transmitted in plaintext and can easily be compromised. When performing remote administrative tasks, a protocol or service that encrypts the communication channel must be used.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + False + False + + If web administration is performed at the console, this check is Not Applicable. + +If web administration is performed remotely the following checks will apply. + +If administration of the server is performed remotely, it will only be performed securely by system administrators. + +If website administration or web application administration has been delegated, those users will be documented and approved by the ISSO. + +Remote administration must be in compliance with any requirements contained within the Windows Server STIGs, and any applicable network STIGs. + +Remote administration of any kind will be restricted to documented and authorized personnel. + +All users performing remote administration must be authenticated. + +All remote sessions will be encrypted and utilize FIPS 140-2-approved protocols. + +FIPS 140-2-approved TLS versions include TLS V1.1 or greater. + +Review with site management how remote administration, if applicable, is configured on the website. + +If remote management meets the criteria listed above, this is not a finding. + +If remote management is utilized and does not meet the criteria listed above, this is a finding. + + + <VulnDiscussion>During an attack on the web server or any of the hosted applications, the system administrator may need to disconnect or disable access by users to stop the attack. + +The web server must provide a capability to disconnect users to a hosted application without compromising other hosted applications unless deemed necessary to stop the attack. Methods to disconnect or disable connections are to stop the application service for a specified hosted application, stop the web server, or block all connections through web server access list. + +The web server capabilities used to disconnect or disable users from connecting to hosted applications and the web server must be documented to make certain that, during an attack, the proper action is taken to conserve connectivity to any other hosted application if possible and to make certain log data is conserved for later forensic analysis.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + False + False + + Interview the System Administrator and Web Manager. + +Ask for documentation for the IIS 10.0 web server administration. + +Verify there are documented procedures for shutting down an IIS 10.0 website in the event of an attack. The procedure should, at a minimum, provide the following steps: + +Determine the respective website for the application at risk of an attack. + +Access the IIS 10.0 web server IIS Manager. + +Select the respective website. + +In the "Actions" pane, under "Manage Website", click "Stop". + +If necessary, stop all websites. + +If necessary, stop the IIS 10.0 web server by selecting the web server in the IIS Manager. + +In the "Actions" pane, under "Manage Server", click "Stop". + +If the web server is not capable or cannot be configured to disconnect or disable remote access to the hosted applications when necessary, this is a finding. + + + <VulnDiscussion>To ensure the logging mechanism used by the web server has sufficient storage capacity in which to write the logs, the logging mechanism must be able to allocate log record storage capacity. + +The task of allocating log record storage capacity is usually performed during initial installation of the logging mechanism. The system administrator will usually coordinate the allocation of physical drive space with the web server administrator along with the physical location of the partition and disk. Refer to NIST SP 800-92 for specific requirements on log rotation and storage dependent on the impact of the web server.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + False + False + + Open the IIS 10.0 Manager. + +Click the IIS 10.0 web server name. + +Under "IIS" double-click the "Logging" icon. + +In the "Logging" configuration box, determine the "Directory:" to which the "W3C" logging is being written. + +Confirm with the System Administrator that the designated log path is of sufficient size to maintain the logging. + +Under "Log File Rollover", verify "Do not create new log files" is not selected. + +Verify a schedule is configured to rollover log files on a regular basis. + +Consult with the System Administrator to determine if there is a documented process for moving the log files off of the IIS 10.0 web server to another logging device. + +If the designated logging path device is not of sufficient space to maintain all log files, and there is not a schedule to rollover files on a regular basis, this is a finding. + + + <VulnDiscussion>A web server can be modified through parameter modification, patch installation, upgrades to the web server or modules, and security parameter changes. With each of these changes, there is the potential for an adverse effect such as a DoS, web server instability, or hosted application instability. + +To limit changes to the web server and limit exposure to any adverse effects from the changes, files such as the web server application files, libraries, and configuration files must have permissions and ownership set properly to only allow privileged users access. + +The key web service administrative and configuration tools must only be accessible by the web server staff. All users granted this authority will be documented and approved by the ISSO. Access to the IIS Manager will be limited to authorized users and administrators. + +Satisfies: SRG-APP-000380-WSR-000072, SRG-APP-000435-WSR-000147, SRG-APP-000033-WSR-000169</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + False + False + + Right-click "InetMgr.exe", then click "Properties" from the "Context" menu. + +Select the "Security" tab. + +Review the groups and user names. + +The following accounts may have Full control privileges: + +TrustedInstaller +Web Managers +Web Manager designees +CREATOR OWNER: Full Control, Subfolders and files only + +The following accounts may have read and execute, or read permissions: + +Non Web Manager Administrators +ALL APPLICATION PACKAGES (built-in security group) +ALL RESTRICTED APPLICATION PACKAGES (built-in security group) +SYSTEM +Users + +Specific users may be granted read and execute and read permissions. + +Compare the local documentation authorizing specific users, against the users observed when reviewing the groups and users. + +If any other access is observed, this is a finding. + + + <VulnDiscussion>Web servers provide numerous processes, features, and functionalities that utilize TCP/IP ports. Some of these processes may be deemed unnecessary or too unsecure to run on a production system. + +The web server must provide the capability to disable or deactivate network-related services deemed non-essential to the server mission, are too unsecure, or are prohibited by the PPSM CAL and vulnerability assessments.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + False + False + + Review programs installed on the OS. + +Open Control Panel. + +Open Programs and Features. + +The following programs may be installed without any additional documentation: + +Administration Pack for IIS +IIS Search Engine Optimization Toolkit +Microsoft .NET Framework version 3.5 SP1 or greater +Microsoft Web Platform Installer version 3.x or greater +Virtual Machine Additions + +Review the installed programs, if any programs are installed other than those listed above, this is a finding. + +Note: If additional software is needed and has supporting documentation signed by the ISSO, this is not a finding. + + + <VulnDiscussion>A Denial of Service (DoS) can occur when the web server is overwhelmed and can no longer respond to additional requests. A web server not properly tuned may become overwhelmed and cause a DoS condition even with expected traffic from users. To avoid a DoS, the web server must be tuned to handle the expected traffic for the hosted applications.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + False + False + + If the IIS 10.0 web server is not hosting any applications, this is Not Applicable. + +If the IIS 10.0 web server is hosting applications, consult with the System Administrator to determine risk analysis performed when the application was written and deployed to the IIS 10.0 web server. + +Obtain documentation on the configuration. + +Verify, at a minimum, the following tuning settings in the registry. + +Access the IIS 10.0 web server registry. + +Verify the following keys are present and configured. The required setting depends upon the requirements of the application. + +Recommended settings are not provided as these settings must be explicitly configured to show a conscientious tuning has been made. + +Navigate to HKLM\SYSTEM\CurrentControlSet\Services\HTTP\Parameters\ +"URIEnableCache" +"UriMaxUriBytes" +"UriScavengerPeriod" + +If explicit settings are not configured for "URIEnableCache", "UriMaxUriBytes" and "UriScavengerPeriod", this is a finding. + + + <VulnDiscussion>TLS is a required transmission protocol for a web server hosting controlled information. The use of TLS provides confidentiality of data in transit between the web server and client. FIPS 140-2-approved TLS versions must be enabled and non-FIPS-approved SSL versions must be disabled. + +NIST SP 800-52 defines the approved TLS versions for government applications.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + False + False + + Review the web server documentation and deployed configuration to determine which version of TLS is being used. + +If the TLS version is not TLS 1.2 or higher, according to NIST SP 800-52, or if non-FIPS-approved algorithms are enabled, this is a finding. + + + + + <VulnDiscussion>Log files are a critical component to the successful management of an IS used within the DoD. By generating log files with useful information, web administrators can leverage them in the event of a disaster, malicious attack, or other site specific needs. + +Ascertaining the correct order of the events that occurred is important during forensic analysis. Events that appear harmless by themselves might be flagged as a potential threat when properly viewed in sequence. By also establishing the event date and time, an event can be properly viewed with an enterprise tool to fully see a possible threat in its entirety. + +Without sufficient information establishing when the log event occurred, investigation into the cause of event is severely hindered. Log record content that may be necessary to satisfy the requirement of this control includes, but is not limited to, time stamps, source and destination IP addresses, user/process identifiers, event descriptions, application-specific events, success/fail indications, file names involved, access control, or flow control rules invoked. + +Satisfies: SRG-APP-000092-WSR-000055, SRG-APP-000093-WSR-000053, SRG-APP-000095-WSR-000056, SRG-APP-000096-WSR-000057, SRG-APP-000097-WSR-000058, SRG-APP-000097-WSR-000059</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + False + + Date,Time,ClientIP,UserName,Method,UriQuery,HttpStatus,Referer + + + + False + + Open the IIS 10.0 Manager. + +Click the IIS 10.0 web server name. + +Click the "Logging" icon. + +Under Format select "W3C". + +Click "Select Fields", verify at a minimum the following fields are checked: Date, Time, Client IP Address, User Name, Method, URI Query, Protocol Status, and Referrer. + +If not, this is a finding. + + + <VulnDiscussion>Internet Information Services (IIS) on Windows Server 2012 provides basic logging capabilities. However, because IIS takes some time to flush logs to disk, administrators do not have access to logging information in real-time. In addition, text-based log files can be difficult and time-consuming to process. + +In IIS 10.0, the administrator has the option of sending logging information to Event Tracing for Windows (ETW). This option gives the administrator the ability to use standard query tools, or create custom tools, for viewing real-time logging information in ETW. This provides a significant advantage over parsing text-based log files that are not updated in real time. + +Satisfies: SRG-APP-000092-WSR-000055, SRG-APP-000108-WSR-000166, SRG-APP-000358-WSR-000063</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + False + + + + + File,ETW + False + + Open the IIS 10.0 Manager. + +Click the IIS 10.0 server name. + +Click the "Logging" icon. + +Under Log Event Destination, verify the "Both log file and ETW event" radio button is selected. + +If the "Both log file and ETW event" radio button is not selected, this is a finding. + + + <VulnDiscussion>Web server logging capability is critical for accurate forensic analysis. Without sufficient and accurate information, a correct replay of the events cannot be determined. + +Ascertaining the success or failure of an event is important during forensic analysis. Correctly determining the outcome will add information to the overall reconstruction of the loggable event. By determining the success or failure of the event correctly, analysis of the enterprise can be undertaken to determine if events tied to the event occurred in other areas within the enterprise. + +Without sufficient information establishing the success or failure of the logged event, investigation into the cause of event is severely hindered. The success or failure also provides a means to measure the impact of an event and help authorized personnel determine the appropriate response. Log record content that may be necessary to satisfy the requirement of this control includes, but is not limited to, time stamps, source and destination IP addresses, user/process identifiers, event descriptions, application-specific events, success/fail indications, file names involved, access control, or flow control rules invoked.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + False + + + RequestHeader + Connection + + + RequestHeader + Warning + + + + W3C + + + False + + Access the IIS 10.0 web server IIS Manager. +Click the IIS 10.0 web server name. +Under "IIS", double-click the "Logging" icon. +Verify the "Format:" under "Log File" is configured to "W3C". +Select the "Fields" button. +Under "Custom Fields", verify the following fields have been configured: +Request Header >> Connection +Request Header >> Warning +If any of the above fields are not selected, this is a finding. + + + <VulnDiscussion>Web server logging capability is critical for accurate forensic analysis. Without sufficient and accurate information, a correct replay of the events cannot be determined. + +Determining user accounts, processes running on behalf of the user, and running process identifiers also enable a better understanding of the overall event. User tool identification is also helpful to determine if events are related to overall user access or specific client tools. + +Log record content that may be necessary to satisfy the requirement of this control includes: time stamps, source and destination addresses, user/process identifiers, event descriptions, success/fail indications, file names involved, and access control or flow control rules invoked.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + False + + + RequestHeader + Authorization + + + ResponseHeader + Content-Type + + + UserAgent,UserName,Referer + W3C + + + False + + Access the IIS 10.0 web server IIS Manager. +Click the IIS 10.0 web server name. +Under "IIS", double-click the "Logging" icon. +Verify the "Format:" under "Log File" is configured to "W3C". +Select the "Fields" button. +Under "Standard Fields", verify "User Agent", "User Name", and "Referrer" are selected. +Under "Custom Fields", verify the following field has been configured: +Request Header >> Authorization +Response Header >> Content-Type +If any of the above fields are not selected, this is a finding. + + + + + <VulnDiscussion>Web server logging capability is critical for accurate forensic analysis. Without sufficient and accurate information, a correct replay of the events cannot be determined. + +Ascertaining the correct source (e.g., source IP), of the events is important during forensic analysis. Correctly determining the source of events will add information to the overall reconstruction of the loggable event. By determining the source of the event correctly, analysis of the enterprise can be undertaken to determine if events tied to the source occurred in other areas within the enterprise. + +A web server behind a load balancer or proxy server, when not configured correctly, will record the load balancer or proxy server as the source of every loggable event. When looking at the information forensically, this information is not helpful in the investigation of events. The web server must record with each event the client source of the event.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + False + False + + 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 web server 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 this procedure for web server and each website: + +Open the IIS 10.0 Manager. + +Click the IIS 10.0 web server name. + +Click the "Logging" icon. + +Click on "View log files" under the "Actions" pane. + +When the log file is displayed, review source IP information in log entries and verify the 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. + + + <VulnDiscussion>A major tool in exploring the website use, attempted use, unusual conditions, and problems are the access and error logs. In the event of a security incident, these logs can provide the System Administrator (SA) and the web manager with valuable information. Failure to protect log files could enable an attacker to modify the log file data or falsify events to mask an attacker's activity. + +Satisfies: SRG-APP-000120-WSR-000070, SRG-APP-000118-WSR-000068, SRG-APP-000118-WSR-000069</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + False + False + + This check does not apply to service account IDs utilized by automated services necessary to process, manage, and store log files. +Open the IIS 10.0 Manager. +Click the IIS 10.0 web server name. +Click the "Logging" icon. +Click "Browse" and navigate to the directory where the log files are stored. +Right-click the log file name to review. +Click "Properties". +Click the "Security" tab. +Verify log file access is restricted as follows. Otherwise, this is a finding. +SYSTEM - Full Control +Administrators - Full Control + + + <VulnDiscussion>Protection of log data includes ensuring log data is not accidentally lost or deleted. Backing up log records to an unrelated system, or onto separate media than the system on which the web server is running, helps to ensure the log records will be retained in the event of a catastrophic system failure.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + False + False + + The IIS 10.0 web server and website log files should be backed up by the system backup. + +To determine if log files are backed up by the system backup, determine the location of the web server log files and each website's log files. + +Open the IIS 10.0 Manager. + +Click the IIS 10.0 server name. + +Click the "Logging" icon. + +Under "Log File" >> "Directory" obtain the path of the log file. + +Once all locations are known, consult with the System Administrator to review the server's backup procedure and policy. + +Verify the paths of all log files are part of the system backup. +Verify log files are backed up to an unrelated system or onto separate media on which the system the web server is running. + +If the paths of all log files are not part of the system backup and/or not backed up to a separate media, this is a finding. + + + <VulnDiscussion>A web server should be primarily a web server or a proxy server but not both, for the same reasons that other multi-use servers are not recommended. Scanning for web servers that also proxy requests into an otherwise protected network is a common attack, making the attack anonymous.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + False + False + + Open the IIS 10.0 Manager. + +Under the "Connections" pane on the left side of the management console, select the IIS 10.0 web server. + +If, under the IIS installed features, "Application Request Routing Cache" is not present, this is not a finding. + +If, under the IIS installed features, "Application Request Routing Cache" is present, double-click the icon to open the feature. + +From the right "Actions" pane, under "Proxy", select "Server Proxy Settings...". + +In the "Application Request Routing" settings window, verify whether "Enable proxy" is selected. + +If “Enable proxy" is selected under the "Application Request Routing" settings, this is a finding. + + + <VulnDiscussion>Web server documentation, sample code, example applications, and tutorials may be an exploitable threat to a web server. A production web server may only contain components that are operationally necessary (i.e., compiled code, scripts, web content, etc.). Delete all directories containing samples and any scripts used to execute the samples.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + False + False + + Navigate to the following folders: + +inetpub\ +Program Files\Common Files\System\msadc +Program Files (x86)\Common Files\System\msadc + +If the folder or sub-folders contain any executable sample code, example applications, or tutorials which are not explicitly used by a production website, this is a finding. + + + <VulnDiscussion>Accounts used for web server features such as documentation, sample code, example applications, tutorials, utilities, and services created when the feature is not installed, become an exploitable threat to a web server. + +These accounts become inactive, are not monitored through regular use, and passwords for the accounts are not created or updated. An attacker, through very little effort, can use these accounts to gain access to the web server and begin investigating ways to elevate the account privileges. + +The accounts used for web server features not installed must not be created and must be deleted when these features are uninstalled.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + False + False + + Access the IIS 10.0 web server. + +Access “Apps” menu. Under “Administrative Tools”, select “Computer Management”. + +In the left pane, expand "Local Users and Groups" and click "Users". + +Review the local users listed in the middle pane. + +If any local accounts are present and were created by features which have been uninstalled or are not used, this is a finding. + + + <VulnDiscussion>Just as running unneeded services and protocols is a danger to the web server at the lower levels of the OSI model, running unneeded utilities and programs is a danger at the application layer of the OSI model. Office suites, development tools, and graphic editors are examples of such troublesome programs. + +Individual productivity tools have no legitimate place or use on an enterprise production web server and are prone to security risks. The web server installation process must provide options allowing the installer to choose which utility programs, services, and modules are to be installed or removed. By having a process for installation and removal, the web server is guaranteed to be in a more stable and secure state than if these services and programs were installed and removed manually.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + False + False + + Consult with the System Administrator and review all of the IIS 10.0 and Operating System features installed. + +Determine if any features installed are no longer necessary for operation. + +If any utility programs, features, or modules are installed which are not necessary for operation, this is a finding. + +If any unnecessary Operating System features are installed, this is a finding. + + + <VulnDiscussion>This check verifies the server certificate is actually a DoD-issued certificate used by the organization being reviewed. This is used to verify the authenticity of the website to the user. If the certificate is not issued by the DoD or if the certificate has expired, then there is no assurance the use of the certificate is valid, and therefore; the entire purpose of using a certificate is compromised.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + False + False + + Open the IIS 10.0 Manager. + +Click the IIS 10.0 web server name. + +Double-click the "Server Certificate" icon. + +Double-click each certificate and verify the certificate path is to a DoD root CA. + +If the “Issued By” field of the PKI certificate being used by the IIS 10.0 server/site does not indicate the issuing Certificate Authority (CA) is part of the DoD PKI or an approved ECA, this is a finding. + + + <VulnDiscussion>Mobile code in hosted applications allows the developer to add functionality and displays to hosted applications that are fluid, as opposed to a static web page. The data presentation becomes more appealing to the user, is easier to analyze, and is less complicated to navigate through the hosted application and data. + +Some mobile code technologies in use in today's applications are: Java, JavaScript, ActiveX, PDF, Postscript, Shockwave movies, Flash animations, and VBScript. The DoD has created policies that define the usage of mobile code on DoD systems. The usage restrictions and implementation guidance apply to both the selection and use of mobile code installed on organizational servers and mobile code downloaded and executed on individual workstations. + +Source code for a Java program is often stored in files with either .java or .jpp file extensions. From the .java and .jpp files the Java compiler produces a binary file with an extension of .class. The .java or .jpp file could therefore reveal sensitive information regarding an application's logic and permissions to resources on the server.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + False + False + + Search the system for files with either .java or .jpp extensions. + +If files with .java or .jpp extensions are found, this is a finding. + + + <VulnDiscussion>The separation of user functionality from web server management can be accomplished by moving management functions to a separate IP address or port. To further separate the management functions, separate authentication methods and certificates should be used. + +By moving the management functionality, the possibility of accidental discovery of the management functions by non-privileged users during hosted application use is minimized.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + False + False + + Review the IIS 10.0 web server configuration with the System Administrator. + +Determine if the IIS 10.0 web server hosts any applications. + +If the IIS 10.0 web server does not host any applications, this is Not Applicable. + +If the IIS 10.0 web server hosts applications, review the application's management functionality and authentication methods with the System Administrator to determine if the management of the application is accomplished with the same functions and authentication methods as the web server management. + +If the IIS 10.0 web server management and the application's management functionality is not separated, this is a finding. + + + <VulnDiscussion>Remote access to the web server is any access that communicates through an external, non-organization-controlled network. Remote access can be used to access hosted applications or to perform management functions. + +A web server can be accessed remotely and must be capable of restricting access from what the DoD defines as non-secure zones. Non-secure zones are defined as any IP, subnet, or region defined as a threat to the organization. The non-secure zones must be defined for public web servers logically located in a DMZ, as well as private web servers with perimeter protection devices. By restricting access from non-secure zones through internal web server access lists, the web server can stop or slow denial of service (DoS) attacks on the web server.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + False + False + + Note: This requirement applies to the Web Management Service. If the Web Management Service is not installed, this is Not Applicable. + +Open the IIS 10.0 Manager. + +Click the IIS 10.0 web server name. + +Under "Management", double-click "Management Service". + +If "Enable remote connections" is not selected, this is Not Applicable. + +If "Enable remote connections" is selected, review the entries under "IP Address Restrictions". + +Verify only known, secure IP ranges are configured as "Allow". + +If "IP Address Restrictions" are not configured or IP ranges configured to "Allow" are not restrictive enough to prevent connections from nonsecure zones, this is a finding. + + + <VulnDiscussion>The use of IPP on an IIS web server allows client access to shared printers. This privileged access could allow remote code execution by increasing the web servers attack surface. Additionally, since IPP does not support SSL, it is considered a risk and will not be deployed.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + False + False + + If the Print Services role and the Internet Printing role are not installed, this check is Not Applicable. + +Navigate to the following directory: + +%windir%\web\printers + +If this folder exists, this is a finding. + +Determine whether Internet Printing is enabled: + +Click “Start”, click “Administrative Tools”, and then click “Server Manager”. + +Expand the roles node, right-click “Print Services”, and then select “Remove Roles Services”. + +If the Internet Printing option is enabled, this is a finding. + + + <VulnDiscussion>During installation of the web server software, accounts are created for the web server to operate properly. The accounts installed can have either no password installed or a default password, which will be known and documented by the vendor and the user community. + +The first things an attacker will try when presented with a logon screen are the default user identifiers with default passwords. Installed applications may also install accounts with no password, making the logon even easier. Once the web server is installed, the passwords for any created accounts should be changed and documented. The new passwords must meet the requirements for all passwords, i.e., upper/lower characters, numbers, special characters, time until change, reuse policy, etc. + +Service accounts or system accounts that have no logon capability do not need to have passwords set or changed.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + False + False + + Access the IIS 10.0 web server. + +Access the "Apps" menu. Under "Administrative Tools", select "Computer Management". + +In left pane, expand "Local Users and Groups" and click "Users". + +Review the local users listed in the middle pane. + +If any local accounts are present and used by IIS 10.0, verify with System Administrator that default passwords have been changed. + +If passwords have not been changed from the default, this is a finding. + + + <VulnDiscussion>Authorization rules can be configured at the server, website, folder (including Virtual Directories), or file level. It is recommended that URL Authorization be configured to only grant access to the necessary security principals. Configuring a global Authorization rule that restricts access ensures inheritance of the settings down through the hierarchy of web directories. This will ensure access to current and future content is only granted to the appropriate principals, mitigating risk of unauthorized access.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + False + False + + Open the IIS 10.0 Manager. + +Click the IIS 10.0 web server name. + +Double-click the ".NET Authorization Rules" icon. + +If any user other than "Administrator" is listed, this is a finding. + +If .NET is not installed, this is Not Applicable. + + + <VulnDiscussion>Resource exhaustion can occur when an unlimited number of concurrent requests are allowed on a website, facilitating a Denial of Service (DoS) attack. Mitigating this kind of attack will include limiting the number of concurrent HTTP/HTTPS requests per IP address and may include, where feasible, limiting parameter values associated with keepalive (i.e., a parameter used to limit the amount of time a connection may be inactive).</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + False + False + + Access the IIS 10.0 IIS Manager. + +Click the IIS 10.0 server. + +Select "Configuration Editor" under the "Management" section. + +From the "Section:" drop-down list at the top of the configuration editor, locate "system.applicationHost/sites". + +Expand "siteDefaults". +Expand "limits". + +Review the results and verify the value is greater than zero for the "maxconnections" parameter. + +If the maxconnections parameter is set to zero, this is a finding. + + + <VulnDiscussion>HTTP Strict Transport Security (HSTS) ensures browsers always connect to a website over TLS. HSTS exists to remove the need for redirection configurations. HSTS relies on the browser, web server, and a public "Whitelist". If the browser does not support HSTS, it will be ignored.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + False + False + + Access the IIS 10.0 Web Server. + +Open IIS Manager. + +In the "Connections" pane, select the server name. + +In the "Features View" pane, open "HTTP Response Headers". + +Verify an entry exists named "Strict-Transport-Security". + +Open "Strict-Transport-Security" and verify the value box contains a value greater than 0. + +Click "OK". + +If HSTS has not been enabled, this is a finding. +The recommended max age is 8 minutes (480 seconds) or greater. Any value greater than 0 is not a finding. +If the version of Windows Server does not natively support HSTS, this is not a finding. + + + + + <VulnDiscussion>Controlling what a user of a hosted application can access is part of the security posture of the web server. Any time a user can access more functionality than is needed for the operation of the hosted application poses a security issue. A user with too much access can view information that is not needed for the user's job role, or the user could use the function in an unintentional manner. + +A MIME tells the web server the type of program, various file types, and extensions and what external utilities or programs are needed to execute the file type. + +A shell is a program that serves as the basic interface between the user and the operating system to ensure hosted application users do not have access to these programs. Shell programs may execute shell escapes and can perform unauthorized activities that could damage the security posture of the web server.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + Absent + .exe + False + application/octet-stream + False + + Open the IIS 10.0 Manager. +Click the IIS 10.0 web server name. +Under IIS, double-click the "MIME Types" icon. +From the "Group by:" drop-down list, select "Content Type". +From the list of extensions under "Application", verify MIME types for OS shell program extensions have been removed, to include at a minimum, the following extensions: +If any OS shell MIME types are configured, this is a finding. +.exe + + + <VulnDiscussion>Controlling what a user of a hosted application can access is part of the security posture of the web server. Any time a user can access more functionality than is needed for the operation of the hosted application poses a security issue. A user with too much access can view information that is not needed for the user's job role, or the user could use the function in an unintentional manner. + +A MIME tells the web server the type of program, various file types, and extensions and what external utilities or programs are needed to execute the file type. + +A shell is a program that serves as the basic interface between the user and the operating system to ensure hosted application users do not have access to these programs. Shell programs may execute shell escapes and can perform unauthorized activities that could damage the security posture of the web server.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + Absent + .dll + False + application/x-msdownload + False + + Open the IIS 10.0 Manager. +Click the IIS 10.0 web server name. +Under IIS, double-click the "MIME Types" icon. +From the "Group by:" drop-down list, select "Content Type". +From the list of extensions under "Application", verify MIME types for OS shell program extensions have been removed, to include at a minimum, the following extensions: +If any OS shell MIME types are configured, this is a finding. +.dll + + + <VulnDiscussion>Controlling what a user of a hosted application can access is part of the security posture of the web server. Any time a user can access more functionality than is needed for the operation of the hosted application poses a security issue. A user with too much access can view information that is not needed for the user's job role, or the user could use the function in an unintentional manner. + +A MIME tells the web server the type of program, various file types, and extensions and what external utilities or programs are needed to execute the file type. + +A shell is a program that serves as the basic interface between the user and the operating system to ensure hosted application users do not have access to these programs. Shell programs may execute shell escapes and can perform unauthorized activities that could damage the security posture of the web server.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + Absent + .com + False + application/octet-stream + False + + Open the IIS 10.0 Manager. +Click the IIS 10.0 web server name. +Under IIS, double-click the "MIME Types" icon. +From the "Group by:" drop-down list, select "Content Type". +From the list of extensions under "Application", verify MIME types for OS shell program extensions have been removed, to include at a minimum, the following extensions: +If any OS shell MIME types are configured, this is a finding. +.com + + + <VulnDiscussion>Controlling what a user of a hosted application can access is part of the security posture of the web server. Any time a user can access more functionality than is needed for the operation of the hosted application poses a security issue. A user with too much access can view information that is not needed for the user's job role, or the user could use the function in an unintentional manner. + +A MIME tells the web server the type of program, various file types, and extensions and what external utilities or programs are needed to execute the file type. + +A shell is a program that serves as the basic interface between the user and the operating system to ensure hosted application users do not have access to these programs. Shell programs may execute shell escapes and can perform unauthorized activities that could damage the security posture of the web server.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + Absent + .bat + False + application/x-bat + False + + Open the IIS 10.0 Manager. +Click the IIS 10.0 web server name. +Under IIS, double-click the "MIME Types" icon. +From the "Group by:" drop-down list, select "Content Type". +From the list of extensions under "Application", verify MIME types for OS shell program extensions have been removed, to include at a minimum, the following extensions: +If any OS shell MIME types are configured, this is a finding. +.bat + + + <VulnDiscussion>Controlling what a user of a hosted application can access is part of the security posture of the web server. Any time a user can access more functionality than is needed for the operation of the hosted application poses a security issue. A user with too much access can view information that is not needed for the user's job role, or the user could use the function in an unintentional manner. + +A MIME tells the web server the type of program, various file types, and extensions and what external utilities or programs are needed to execute the file type. + +A shell is a program that serves as the basic interface between the user and the operating system to ensure hosted application users do not have access to these programs. Shell programs may execute shell escapes and can perform unauthorized activities that could damage the security posture of the web server.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + Absent + .csh + False + application/x-csh + False + + Open the IIS 10.0 Manager. +Click the IIS 10.0 web server name. +Under IIS, double-click the "MIME Types" icon. +From the "Group by:" drop-down list, select "Content Type". +From the list of extensions under "Application", verify MIME types for OS shell program extensions have been removed, to include at a minimum, the following extensions: +If any OS shell MIME types are configured, this is a finding. +.csh + + + + + + + + + System + False + + + FullControl + + + + + Administrators + False + + + FullControl + + + + + TrustedInstaller + False + + + FullControl + + + + + ALL APPLICATION PACKAGES + False + + + ReadAndExecute + + + + + ALL RESTRICTED APPLICATION PACKAGES + False + + + ReadAndExecute + + + + + Users + False + + + ReadAndExecute,ListDirectory + + + + + CREATOR OWNER + False + Subfolders and files only + FullControl + + + <VulnDiscussion>This check verifies the key web server system configuration files are owned by the SA or the web administrator controlled account. These same files that control the configuration of the web server, and thus its behavior, must also be accessible by the account running the web service. If these files are altered by a malicious user, the web server would no longer be under the control of its managers and owners; properties in the web server configuration could be altered to compromise the entire server platform.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + True + False + False + + %SystemDrive%\inetpub + Open Explorer and navigate to the inetpub directory. + +Right-click "inetpub" and select "Properties". + +Click the "Security" tab. + +Verify the permissions for the following users; if the permissions are less restrictive, this is a finding. + +System: Full control +Administrators: Full control +TrustedInstaller: Full control +ALL APPLICATION PACKAGES (built-in security group): Read and execute +ALL RESTRICTED APPLICATION PACKAGES (built-in security group): Read and execute +Users: Read and execute, list folder contents +CREATOR OWNER: Full Control, Subfolders and files only + + + + + <VulnDiscussion>TLS encryption is a required security setting for a private web server. Encryption of private information is essential to ensuring data confidentiality. If private information is not encrypted, it can be intercepted and easily read by an unauthorized party. A private web server must use a FIPS 140-2-approved TLS version, and all non-FIPS-approved SSL versions must be disabled. + +FIPS 140-2-approved TLS versions include TLS V1.1 or greater. NIST SP 800-52 specifies the preferred configurations for government systems.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + Present + False + HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.1\Server + False + + Access the IIS 10.0 Web Server. + +Access an administrator command prompt and type "regedit <enter>" to access the server's registry. + +Navigate to: +HKLM\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2\Server + +Verify a REG_DWORD value of "0" for "DisabledByDefault" + +Navigate to: +HKLM\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.0\Server + +HKLM\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.1\Server + +HKLM\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\SSL 2.0\Server + +HKLM\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\SSL 3.0\Server + +Verify a REG_DWORD value of "1" for "DisabledByDefault" +Verify a REG_DWORD value of "0" for "Enabled" + +If any of the respective registry paths do not exist or are configured with the wrong value, this is a finding. + 1 + DisabledByDefault + DWORD + + + <VulnDiscussion>TLS encryption is a required security setting for a private web server. Encryption of private information is essential to ensuring data confidentiality. If private information is not encrypted, it can be intercepted and easily read by an unauthorized party. A private web server must use a FIPS 140-2-approved TLS version, and all non-FIPS-approved SSL versions must be disabled. + +FIPS 140-2-approved TLS versions include TLS V1.1 or greater. NIST SP 800-52 specifies the preferred configurations for government systems.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + Present + False + HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2\Server + False + + Access the IIS 10.0 Web Server. + +Access an administrator command prompt and type "regedit <enter>" to access the server's registry. + +Navigate to: +HKLM\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2\Server + +Verify a REG_DWORD value of "0" for "DisabledByDefault" + +Navigate to: +HKLM\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.0\Server + +HKLM\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.1\Server + +HKLM\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\SSL 2.0\Server + +HKLM\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\SSL 3.0\Server + +Verify a REG_DWORD value of "1" for "DisabledByDefault" +Verify a REG_DWORD value of "0" for "Enabled" + +If any of the respective registry paths do not exist or are configured with the wrong value, this is a finding. + 0 + DisabledByDefault + DWORD + + + <VulnDiscussion>TLS encryption is a required security setting for a private web server. Encryption of private information is essential to ensuring data confidentiality. If private information is not encrypted, it can be intercepted and easily read by an unauthorized party. A private web server must use a FIPS 140-2-approved TLS version, and all non-FIPS-approved SSL versions must be disabled. + +FIPS 140-2-approved TLS versions include TLS V1.1 or greater. NIST SP 800-52 specifies the preferred configurations for government systems.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + Present + False + HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.0\Server + False + + Access the IIS 10.0 Web Server. + +Access an administrator command prompt and type "regedit <enter>" to access the server's registry. + +Navigate to: +HKLM\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2\Server + +Verify a REG_DWORD value of "0" for "DisabledByDefault" + +Navigate to: +HKLM\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.0\Server + +HKLM\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.1\Server + +HKLM\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\SSL 2.0\Server + +HKLM\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\SSL 3.0\Server + +Verify a REG_DWORD value of "1" for "DisabledByDefault" +Verify a REG_DWORD value of "0" for "Enabled" + +If any of the respective registry paths do not exist or are configured with the wrong value, this is a finding. + 1 + DisabledByDefault + DWORD + + + <VulnDiscussion>TLS encryption is a required security setting for a private web server. Encryption of private information is essential to ensuring data confidentiality. If private information is not encrypted, it can be intercepted and easily read by an unauthorized party. A private web server must use a FIPS 140-2-approved TLS version, and all non-FIPS-approved SSL versions must be disabled. + +FIPS 140-2-approved TLS versions include TLS V1.1 or greater. NIST SP 800-52 specifies the preferred configurations for government systems.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + Present + False + HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\SSL 2.0\Server + False + + Access the IIS 10.0 Web Server. + +Access an administrator command prompt and type "regedit <enter>" to access the server's registry. + +Navigate to: +HKLM\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2\Server + +Verify a REG_DWORD value of "0" for "DisabledByDefault" + +Navigate to: +HKLM\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.0\Server + +HKLM\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.1\Server + +HKLM\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\SSL 2.0\Server + +HKLM\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\SSL 3.0\Server + +Verify a REG_DWORD value of "1" for "DisabledByDefault" +Verify a REG_DWORD value of "0" for "Enabled" + +If any of the respective registry paths do not exist or are configured with the wrong value, this is a finding. + 1 + DisabledByDefault + DWORD + + + <VulnDiscussion>TLS encryption is a required security setting for a private web server. Encryption of private information is essential to ensuring data confidentiality. If private information is not encrypted, it can be intercepted and easily read by an unauthorized party. A private web server must use a FIPS 140-2-approved TLS version, and all non-FIPS-approved SSL versions must be disabled. + +FIPS 140-2-approved TLS versions include TLS V1.1 or greater. NIST SP 800-52 specifies the preferred configurations for government systems.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + Present + False + HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\SSL 3.0\Server + False + + Access the IIS 10.0 Web Server. + +Access an administrator command prompt and type "regedit <enter>" to access the server's registry. + +Navigate to: +HKLM\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2\Server + +Verify a REG_DWORD value of "0" for "DisabledByDefault" + +Navigate to: +HKLM\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.0\Server + +HKLM\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.1\Server + +HKLM\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\SSL 2.0\Server + +HKLM\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\SSL 3.0\Server + +Verify a REG_DWORD value of "1" for "DisabledByDefault" +Verify a REG_DWORD value of "0" for "Enabled" + +If any of the respective registry paths do not exist or are configured with the wrong value, this is a finding. + 1 + DisabledByDefault + DWORD + + + <VulnDiscussion>TLS encryption is a required security setting for a private web server. Encryption of private information is essential to ensuring data confidentiality. If private information is not encrypted, it can be intercepted and easily read by an unauthorized party. A private web server must use a FIPS 140-2-approved TLS version, and all non-FIPS-approved SSL versions must be disabled. + +FIPS 140-2-approved TLS versions include TLS V1.1 or greater. NIST SP 800-52 specifies the preferred configurations for government systems.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + Present + False + HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.0\Server + False + + Access the IIS 10.0 Web Server. + +Access an administrator command prompt and type "regedit <enter>" to access the server's registry. + +Navigate to: +HKLM\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2\Server + +Verify a REG_DWORD value of "0" for "DisabledByDefault" + +Navigate to: +HKLM\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.0\Server + +HKLM\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.1\Server + +HKLM\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\SSL 2.0\Server + +HKLM\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\SSL 3.0\Server + +Verify a REG_DWORD value of "1" for "DisabledByDefault" +Verify a REG_DWORD value of "0" for "Enabled" + +If any of the respective registry paths do not exist or are configured with the wrong value, this is a finding. + 0 + Enabled + DWORD + + + <VulnDiscussion>TLS encryption is a required security setting for a private web server. Encryption of private information is essential to ensuring data confidentiality. If private information is not encrypted, it can be intercepted and easily read by an unauthorized party. A private web server must use a FIPS 140-2-approved TLS version, and all non-FIPS-approved SSL versions must be disabled. + +FIPS 140-2-approved TLS versions include TLS V1.1 or greater. NIST SP 800-52 specifies the preferred configurations for government systems.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + Present + False + HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\SSL 2.0\Server + False + + Access the IIS 10.0 Web Server. + +Access an administrator command prompt and type "regedit <enter>" to access the server's registry. + +Navigate to: +HKLM\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2\Server + +Verify a REG_DWORD value of "0" for "DisabledByDefault" + +Navigate to: +HKLM\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.0\Server + +HKLM\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.1\Server + +HKLM\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\SSL 2.0\Server + +HKLM\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\SSL 3.0\Server + +Verify a REG_DWORD value of "1" for "DisabledByDefault" +Verify a REG_DWORD value of "0" for "Enabled" + +If any of the respective registry paths do not exist or are configured with the wrong value, this is a finding. + 0 + Enabled + DWORD + + + <VulnDiscussion>TLS encryption is a required security setting for a private web server. Encryption of private information is essential to ensuring data confidentiality. If private information is not encrypted, it can be intercepted and easily read by an unauthorized party. A private web server must use a FIPS 140-2-approved TLS version, and all non-FIPS-approved SSL versions must be disabled. + +FIPS 140-2-approved TLS versions include TLS V1.1 or greater. NIST SP 800-52 specifies the preferred configurations for government systems.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + Present + False + HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\SSL 3.0\Server + False + + Access the IIS 10.0 Web Server. + +Access an administrator command prompt and type "regedit <enter>" to access the server's registry. + +Navigate to: +HKLM\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2\Server + +Verify a REG_DWORD value of "0" for "DisabledByDefault" + +Navigate to: +HKLM\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.0\Server + +HKLM\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.1\Server + +HKLM\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\SSL 2.0\Server + +HKLM\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\SSL 3.0\Server + +Verify a REG_DWORD value of "1" for "DisabledByDefault" +Verify a REG_DWORD value of "0" for "Enabled" + +If any of the respective registry paths do not exist or are configured with the wrong value, this is a finding. + 0 + Enabled + DWORD + + + <VulnDiscussion>TLS encryption is a required security setting for a private web server. Encryption of private information is essential to ensuring data confidentiality. If private information is not encrypted, it can be intercepted and easily read by an unauthorized party. A private web server must use a FIPS 140-2-approved TLS version, and all non-FIPS-approved SSL versions must be disabled. + +FIPS 140-2-approved TLS versions include TLS V1.1 or greater. NIST SP 800-52 specifies the preferred configurations for government systems.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + Present + False + HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.1\Server + False + + Access the IIS 10.0 Web Server. + +Access an administrator command prompt and type "regedit <enter>" to access the server's registry. + +Navigate to: +HKLM\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2\Server + +Verify a REG_DWORD value of "0" for "DisabledByDefault" + +Navigate to: +HKLM\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.0\Server + +HKLM\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.1\Server + +HKLM\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\SSL 2.0\Server + +HKLM\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\SSL 3.0\Server + +Verify a REG_DWORD value of "1" for "DisabledByDefault" +Verify a REG_DWORD value of "0" for "Enabled" + +If any of the respective registry paths do not exist or are configured with the wrong value, this is a finding. + 0 + Enabled + DWORD + + + + + /system.web/sessionState + <VulnDiscussion>Cookies are used to exchange data between the web server and the client. Cookies, such as a session cookie, may contain session information and user credentials used to maintain a persistent connection between the user and the hosted application since HTTP/HTTPS is a stateless protocol. + +Using URI will embed the session ID as a query string in the Uniform Resource Identifier (URI) request and then the URI is redirected to the originally requested URL. The changed URI request is used for the duration of the session, so no cookie is necessary. + +By requiring expired session IDs to be regenerated while using URI, potential attackers have less time to capture a cookie and gain access to the Web server content. + +Satisfies: SRG-APP-000223-WSR-000011, SRG-APP-000220-WSR-000201</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + False + cookieless + False + + Open the IIS 10.0 Manager. +Click the IIS 10.0 web server name. +Under "ASP.Net", double-click the "Session State" icon. +Under "Cookie Settings", verify the "Mode" has "Use Cookies" selected from the drop-down list. +If the "Cookie Settings" "Mode" is not set to "Use Cookies", this is a finding. + +Alternative method: + +Click the site name. +Select "Configuration Editor" under the "Management" section. +From the "Section:" drop-down list at the top of the configuration editor, locate "system.web/sessionState". +Verify the "cookieless" is set to "UseCookies". +If the "cookieless" is not set to "UseCookies", this is a finding. + +Note: If IIS 10.0 server/site is used only for system-to-system maintenance, does not allow users to connect to interface, and is restricted to specific system IPs, this is Not Applicable. + UseCookies + + + /system.web/sessionState + <VulnDiscussion>ASP.NET provides a session state, which is available as the HttpSessionState class, as a method of storing session-specific information that is visible only within the session. ASP.NET session state identifies requests from the same browser during a limited time window as a session and provides the ability to persist variable values for the duration of that session. + +When using the URI mode for cookie settings under session state, IIS will reject and reissue session IDs that do not have active sessions. Configuring IIS to expire session IDs and regenerate tokens gives a potential attacker less time to capture a cookie and gain access to server content.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + V-100143 + False + cookieless + False + + From the "Section:" drop-down list at the top of the configuration editor, locate "system.web/sessionState". +Verify the "cookieless" is set to "UseCookies". + UseCookies + + + /system.web/machineKey + <VulnDiscussion>The Machine Key element of the ASP.NET web.config specifies the algorithm and keys that ASP.NET will use for encryption. The Machine Key feature can be managed to specify hashing and encryption settings for application services such as view state, forms authentication, membership and roles, and anonymous identification. Ensuring a strong encryption method can mitigate the risk of data tampering in crucial functional areas such as forms authentication cookies, or view state.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + False + validation + False + + Open the IIS 10.0 Manager. +Click the IIS 10.0 web server name. +Double-click the "Machine Key" icon in the website Home Pane. +If "HMACSHA256" or stronger encryption is not selected for the Validation method and/or "Auto" is not selected for the Encryption method, this is a finding. +If .NET is not installed, this is Not Applicable. +Verify "HMACSHA256" + HMACSHA256 + + + /system.web/machineKey + <VulnDiscussion>The Machine Key element of the ASP.NET web.config specifies the algorithm and keys that ASP.NET will use for encryption. The Machine Key feature can be managed to specify hashing and encryption settings for application services such as view state, forms authentication, membership and roles, and anonymous identification. Ensuring a strong encryption method can mitigate the risk of data tampering in crucial functional areas such as forms authentication cookies, or view state.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + False + decryption + False + + Open the IIS 10.0 Manager. +Click the IIS 10.0 web server name. +Double-click the "Machine Key" icon in the website Home Pane. +If "HMACSHA256" or stronger encryption is not selected for the Validation method and/or "Auto" is not selected for the Encryption method, this is a finding. +If .NET is not installed, this is Not Applicable. +"Auto" is selected for the Encryption method + Auto + + + /system.webServer/directoryBrowse + <VulnDiscussion>Directory browsing allows the contents of a directory to be displayed upon request from a web client. If directory browsing is enabled for a directory in IIS, users could receive a web page listing the contents of the directory. If directory browsing is enabled, the risk of inadvertently disclosing sensitive content is increased.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + False + enabled + False + + Open the IIS 10.0 Manager. + +Click the IIS 10.0 web server name. + +Double-click the "Directory Browsing" icon. + +Under the “Actions” pane verify "Directory Browsing" is disabled. + +If “Directory Browsing” is not disabled, this is a finding. + false + + + /system.webServer/httpErrors + <VulnDiscussion>HTTP error pages contain information that could enable an attacker to gain access to an information system. Failure to prevent the sending of HTTP error pages with full information to remote requesters exposes internal configuration information to potential attackers.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + False + errormode + False + + Open the IIS 10.0 Manager. + +Click the IIS 10.0 web server name. + +Double-click the "Error Pages" icon. + +Click any error message, and then click "Edit Feature Setting" from the "Actions" Pane. This will apply to all error messages. + +If the feature setting is not set to “Detailed errors for local requests and custom error pages for remote requests”, this is a finding. + DetailedLocalOnly + + + /system.webServer/asp/session + <VulnDiscussion>The HTTP protocol is a stateless protocol. To maintain a session, a session identifier is used. The session identifier is a piece of data used to identify a session and a user. If the session identifier is compromised by an attacker, the session can be hijacked. By encrypting the session identifier, the identifier becomes more difficult for an attacker to hijack, decrypt, and use before the session has expired.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + False + keepSessionIdSecure + False + + Open the IIS 10.0 Manager. + +Click the IIS 10.0 web server name. + +Under the "Management" section, double-click the "Configuration Editor" icon. + +From the "Section:" drop-down list, select "system.webServer/asp". + +Expand the "session" section. + +Verify the "keepSessionIdSecure" is set to "True". + +If the "keepSessionIdSecure" is not set to "True", this is a finding. + True + + + /system.webServer/security/isapiCgiRestriction + <VulnDiscussion>By allowing unspecified file extensions to execute, the web servers attack surface is significantly increased. This increased risk can be reduced by only allowing specific ISAPI extensions or CGI extensions to run on the web server.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + False + notListedCgisAllowed + False + + Open the IIS 10.0 Manager. +Click the IIS 10.0 web server name. +Double-click the "ISAPI and CGI restrictions" icon. +Click “Edit Feature Settings". +Verify the "Allow unspecified CGI modules" check box is not checked + false + + + /system.webServer/security/isapiCgiRestriction + <VulnDiscussion>By allowing unspecified file extensions to execute, the web servers attack surface is significantly increased. This increased risk can be reduced by only allowing specific ISAPI extensions or CGI extensions to run on the web server.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + False + notListedIsapisAllowed + False + + Open the IIS 10.0 Manager. +Click the IIS 10.0 web server name. +Double-click the "ISAPI and CGI restrictions" icon. +Click “Edit Feature Settings". +Verify the "Allow unspecified ISAPI modules" check box is not checked + false + + + + + <VulnDiscussion>A web server can be installed with functionality that by its nature is not secure. Web Distributed Authoring (WebDAV) is an extension to the HTTP protocol which, when developed, was meant to allow users to create, change, and move documents on a server, typically a web server or web share. Allowing this functionality, development, and deployment is much easier for web authors. + +WebDAV is not widely used and has serious security concerns because it may allow clients to modify unauthorized files on the web server.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + Absent + False + Web-DAV-Publishing + False + + Open the IIS 10.0 Manager. + +Click the IIS 10.0 web server name. + +Review the features listed under the “IIS" section. + +If the "WebDAV Authoring Rules" icon exists, this is a finding. + + + diff --git a/source/StigData/Processed/IISSite-10.0-1.1.org.default.xml b/source/StigData/Processed/IISSite-10.0-1.1.org.default.xml new file mode 100644 index 000000000..404c3970f --- /dev/null +++ b/source/StigData/Processed/IISSite-10.0-1.1.org.default.xml @@ -0,0 +1,29 @@ + + + + + + + + + + + + + + + + + + + + + + + diff --git a/source/StigData/Processed/IISSite-10.0-1.1.xml b/source/StigData/Processed/IISSite-10.0-1.1.xml new file mode 100644 index 000000000..aa03ded14 --- /dev/null +++ b/source/StigData/Processed/IISSite-10.0-1.1.xml @@ -0,0 +1,1355 @@ + + + + <VulnDiscussion>IIS 10.0 will either allow or deny script execution based on file extension. The ability to control script execution is controlled through two features with IIS 10.0, Request Filtering and Handler Mappings. + +For Handler Mappings, the ISSO must document and approve all allowable file extensions the website allows (white list) and denies (black list). The white list and black list will be compared to the Handler Mappings in IIS 8. Handler Mappings at the site level take precedence over Handler Mappings at the server level.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + False + False + + For Handler Mappings, 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 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 black list are enabled, this is a finding. + + + <VulnDiscussion>IIS 10.0 will either allow or deny script execution based on file extension. The ability to control script execution is controlled through two features with IIS 10.0, Request Filtering and Handler Mappings. + +For Request Filtering, the ISSO must document and approve all allowable file extensions the website allows (white list) and denies (black list) by the website. 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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + False + False + + 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. + + + <VulnDiscussion>The web server must be configured to listen on a specified IP address and port. Without specifying an IP address and port for the web server to use, the web server will listen on all IP addresses available to the hosting server. If the web server has multiple IP addresses, i.e., a management IP address, the web server will also accept connections on the management IP address. + +Accessing the hosted application through an IP address normally used for non-application functions opens the possibility of user access to resources, utilities, files, ports, and protocols that are protected on the desired application IP address.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + False + False + + 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. + + + <VulnDiscussion>During an attack on the web server or any of the hosted applications, the system administrator may need to disconnect or disable access by users to stop the attack. + +The web server must provide a capability to disconnect users to a hosted application without compromising other hosted applications unless deemed necessary to stop the attack. Methods to disconnect or disable connections are to stop the application service for a specified hosted application, stop the web server, or block all connections through web server access list. + +The web server capabilities used to disconnect or disable users from connecting to hosted applications and the web server must be documented to make certain that during an attack, the proper action is taken to conserve connectivity to any other hosted application if possible and to make certain log data is conserved for later forensic analysis.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + False + False + + Interview the System Administrator and Web Manager. + +Ask for documentation for the IIS 10.0 web server administration. + +Verify there are documented procedures for shutting down an IIS 10.0 website in the event of an attack. The procedure should, at a minimum, provide the following steps: + +Determine the respective website for the application at risk of an attack. + +Access the IIS 10.0 web server IIS 10.0 Manager. + +Select the respective website. + +In the "Actions" pane, under "Manage Website", click "Stop". + +If necessary, stop all websites. + +If necessary, stop the IIS 10.0 web server by selecting the web server in the IIS 10.0 Manager. + +In the "Actions" pane, under "Manage Server", click "Stop". + +If there are not documented procedures with, at a minimum, the mentioned steps for stopping a website, this is a finding. + + + <VulnDiscussion>To make certain the logging mechanism used by the web server has sufficient storage capacity in which to write the logs, the logging mechanism must be able to allocate log record storage capacity. + +The task of allocating log record storage capacity is usually performed during initial installation of the logging mechanism. The system administrator will usually coordinate the allocation of physical drive space with the web server administrator along with the physical location of the partition and disk. Refer to NIST SP 800-92 for specific requirements on log rotation and storage dependent on the impact of the web server.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + False + False + + Follow the procedures below for each site hosted on the IIS 10.0 web server: + +Access the IIS 10.0 web server IIS 10.0 Manager. + +Under "IIS" double-click on the "Logging" icon. + +In the "Logging" configuration box, determine the "Directory:" to which the "W3C" logging is being written. + +Confirm with the System Administrator that the designated log path is of sufficient size to maintain the logging. + +Under "Log File Rollover", verify "Do not create new log files" is not selected. + +Verify a schedule is configured to rollover log files on a regular basis. + +Consult with the System Administrator to determine if there is a documented process for moving the log files off of the IIS 10.0 web server to another logging device. + +If the designated logging path device is not of sufficient space to maintain all log files and there is not a schedule to rollover files on a regular basis, this is a finding. + + + <VulnDiscussion>Web servers provide numerous processes, features, and functionalities that use TCP/IP ports. Some of these processes may be deemed unnecessary or too unsecure to run on a production system. + +The web server must provide the capability to disable or deactivate network-related services deemed to be non-essential to the server mission, too unsecure, or prohibited by the PPSM CAL and vulnerability assessments. + +Failure to comply with DoD ports, protocols, and services (PPS) requirements can result in compromise of enclave boundary protections and/or functionality of the AIS. + +The ISSM will ensure web servers are configured to use only authorized PPS in accordance with the Network Infrastructure STIG, DoD Instruction 8551.1, PPSM, and the associated PPS Assurance Category Assignments List.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + False + False + + Review the website to determine if HTTP and HTTPs (e.g., 80 and 443) are used in accordance with those ports and services registered and approved for use by the DoD PPSM. Any variation in PPS will be documented, registered, and approved by the PPSM. + +Follow the procedures below for each site hosted on the IIS 10.0 web server: + +Open the IIS 10.0 Manager. + +Click the site name under review. + +In the "Action" Pane, click "Bindings". + +Review the ports and protocols. If unknown ports or protocols are used, then this is a finding. + + + + + <VulnDiscussion>Internet Information Services (IIS) on Windows Server 2012 provides basic logging capabilities. However, because IIS takes some time to flush logs to disk, administrators do not have access to logging information in real-time. In addition, text-based log files can be difficult and time-consuming to process. + +In IIS 10.0, the administrator has the option of sending logging information to Event Tracing for Windows (ETW). This option gives the administrator the ability to use standard query tools, or create custom tools, for viewing real-time logging information in ETW. This provides a significant advantage over parsing text-based log files that are not updated in real time. + +Satisfies: SRG-APP-000092-WSR-000055, SRG-APP-000108-WSR-000166</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + False + + + + + File,ETW + False + + 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 + + + <VulnDiscussion>Web server logging capability is critical for accurate forensic analysis. Without sufficient and accurate information, a correct replay of the events cannot be determined. + +Ascertaining the success or failure of an event is important during forensic analysis. Correctly determining the outcome will add information to the overall reconstruction of the loggable event. By determining the success or failure of the event correctly, analysis of the enterprise can be undertaken to determine if events tied to the event occurred in other areas within the enterprise. + +Without sufficient information establishing the success or failure of the logged event, investigation into the cause of event is severely hindered. The success or failure also provides a means to measure the impact of an event and help authorized personnel to determine the appropriate response. Log record content that may be necessary to satisfy the requirement of this control includes, but is not limited to, time stamps, source and destination IP addresses, user/process identifiers, event descriptions, application-specific events, success/fail indications, file names involved, access control, or flow control rules invoked.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + False + + + RequestHeader + Connection + + + RequestHeader + Warning + + + + W3C + + + False + + 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. + + + <VulnDiscussion>Web server logging capability is critical for accurate forensic analysis. Without sufficient and accurate information, a correct replay of the events cannot be determined. + +Determining user accounts, processes running on behalf of the user, and running process identifiers also enable a better understanding of the overall event. User tool identification is also helpful to determine if events are related to overall user access or specific client tools. + +Log record content that may be necessary to satisfy the requirement of this control includes: time stamps, source and destination addresses, user/process identifiers, event descriptions, success/fail indications, file names involved, and access control or flow control rules invoked.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + False + + + RequestHeader + Authorization + + + ResponseHeader + Content-Type + + + UserAgent,UserName,Referer + W3C + + + False + + 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. + + + + + <VulnDiscussion>Web server logging capability is critical for accurate forensic analysis. Without sufficient and accurate information, a correct replay of the events cannot be determined. + +Ascertaining the correct source (e.g., source IP), of the events is important during forensic analysis. Correctly determining the source of events will add information to the overall reconstruction of the loggable event. By determining the source of the event correctly, analysis of the enterprise can be undertaken to determine if events tied to the source occurred in other areas within the enterprise. + +A web server behind a load balancer or proxy server, when not configured correctly, will record the load balancer or proxy server as the source of every loggable event. When looking at the information forensically, this information is not helpful in the investigation of events. The web server must record with each event the client source of the event.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + False + False + + 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. + + + <VulnDiscussion>Many of the security problems that occur are not the result of a user gaining access to files or data for which the user does not have permissions, but rather users are assigned incorrect permissions to unauthorized data. The files, directories, and data stored on the web server must be evaluated and a determination made concerning authorized access to information and programs on the server. Only authorized users and administrative accounts will be allowed on the host server in order to maintain the web server, applications, and review the server operations.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + False + False + + 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: account name. + +Check privileged groups that may allow the anonymous account inappropriate membership: +Open "Server Manager" on the machine. + +Expand Configuration. + +Expand Local Users and Groups. + +Click "Groups". + +Review 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. + + + <VulnDiscussion>The web document (home) directory is accessed by multiple anonymous users when the web server is in production. By locating the web document (home) directory on the same partition as the web server system file, the risk for unauthorized access to these protected files is increased. Additionally, having the web document (home) directory path on the same drive as the system folders also increases the potential for a drive space exhaustion attack.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + False + False + + 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. + +Note: If this IIS 10.0 installation is supporting Microsoft Exchange, and not otherwise hosting any content, this requirement is Not Applicable. + + + <VulnDiscussion>The use of a DoD PKI certificate ensures clients the private website they are connecting to is legitimate, and is an essential part of the DoD defense-in-depth strategy.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + False + False + + Follow the procedures below for each site hosted on the IIS 10.0 web server: + +Open the IIS 10.0 Manager. + +Click the site name under review. + +Click "Bindings" in the "Action" Pane. + +Click the "HTTPS type" from the box. + +Click "Edit". + +Click "View" and then review and verify the certificate path. + +If the list of CAs in the trust hierarchy does not lead to the DoD PKI Root CA, DoD-approved external certificate authority (ECA), or DoD-approved external partner, this is a finding. + +If HTTPS is not an available type under site bindings, this is a finding. + +If HTTPS is not an available type under site bindings, and the Web Server ONLY communicates directly with a load balancer/proxy server with IP address and Domain Restrictions in place, this is not a finding. + + + <VulnDiscussion>Application pools isolate sites and applications to address reliability, availability, and security issues. Sites and applications may be grouped according to configurations, although each site will be associated with a unique application pool.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + False + False + + Note: If the IIS Application Pool is hosting Microsoft SharePoint, this is Not Applicable. + +If this IIS 10.0 installation is supporting Microsoft Exchange, and not otherwise hosting any content, this requirement is Not Applicable. + +Open the IIS 10.0 Manager. + +Click "Application Pools". + +In the list of Application Pools, review the "Applications" column and verify unique application pools for each website. + +If any Application Pools are being used for more than one website, this is a finding. + + + <VulnDiscussion>CGI and ASP scripts represent one of the most common and exploitable means of compromising a web server. All CGI and ASP program files must be segregated into their own unique folder to simplify the protection of these files. ASP scripts must be placed into a unique folder only containing other ASP scripts. JAVA and other technology-specific scripts must also be placed into their own unique folders. The placement of CGI, ASP, or equivalent scripts to special folders gives the Web Manager or the System Administrator (SA) control over what goes into those folders and to facilitate access control at the folder level.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + False + False + + Determine whether scripts are used on the web server for the target website. Common file extensions include, but are not limited to: .cgi, .pl, .vbs, .class, .c, .php, and .asp. + +All interactive programs must be placed in unique designated folders based on CGI or ASP script type. For modular and/or third-party applications, it is permissible to have script files in multiple folders. + +Open the IIS 10.0 Manager. + +Right-click the IIS 10.0 web site name and select "Explore". + +Search for the listed script extensions. Each script type must be in its unique designated folder. + +If scripts are not segregated from web content and in their own unique folders, this is a finding. + + + <VulnDiscussion>CGI is a programming standard for interfacing external applications with information servers, such as HTTP or web servers. CGI, represented by all upper case letters, should not be confused with the .cgi file extension. The .cgi file extension does represent a CGI script, but CGI scripts may be written in a number of programming languages (e.g., PERL, C, PHP, and JavaScript), each having their own unique file extension. + +The use of CGI scripts represent one of the most common and exploitable means of compromising a web server. By definition, CGI scripts are executable by the operating system of the host server. While access control is provided via the web service, the execution of CGI programs is not limited unless the System Administrator (SA) or the Web Manager takes specific measures. CGI programs can access and alter data files, launch other programs, and use the network.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + False + False + + Determine whether scripts are used on the web server for the subject website. Common file extensions include, but are not limited to: .cgi, .pl, .vb, .class, .c, .php, and .asp. + +If the website does not utilize CGI, this finding is Not Applicable. + +All interactive programs must have restrictive permissions. + +Open the IIS 10.0 Manager. + +Right-click the IIS 10.0 web site name and select "Explore". + +Search for the listed script extensions. + +Review the permissions to the CGI scripts and verify only the permissions listed, or more restrictive permissions are assigned. + +Administrators: FULL +TrustedInstaller: FULL +ALL APPLICATION PACKAGES: Read +ALL RESTRICTED APPLICATION PACKAGES: Read +SYSTEM: FULL +ApplicationPoolId: READ +Custom Service Account: READ +Users: READ + +If the permissions are less restrictive than listed above, this is a finding. + + + <VulnDiscussion>Copies of backup files will not execute on the server, but they can be read by the anonymous user if special precautions are not taken. Such backup copies contain the same sensitive information as the actual script being executed and, as such, are useful to malicious users. Techniques and systems exist today to search web servers for such files and are able to exploit the information contained in them.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + False + False + + Determine whether scripts are used on the web server for the subject website. Common file extensions include, but are not limited to: .cgi, .pl, .vb, .class, .c, .php, .asp, and .aspx. The scope of this requirement is to analyze only within the web server content directories, not the entire underlying operating system. + +If the website does not utilize CGI, this finding is Not Applicable. + +Open the IIS 10.0 Manager. + +Right-click the IIS 10.0 web site name and select "Explore". + +Search for the listed script extensions + +Search for the following files: *.bak, *.old, *.temp, *.tmp, *.backup, or “copy of...”. + +If files with these extensions are found, this is a finding. + + + <VulnDiscussion>A consent banner will be in place to inform prospective entrants the website they are about to enter is a DoD website and their activity is subject to monitoring. The document, DoDI 8500.01, establishes the policy on the use of DoD information systems. It requires the use of a standard Notice and Consent Banner and standard text to be included in user agreements. The requirement for the banner is for websites with security and access controls. These are restricted and not publicly accessible. If the website does not require authentication/authorization for use, then the banner does not need to be present. A manual check of the document root directory for a banner page file (such as banner.html) or navigation to the website via a browser can be used to confirm the information provided from interviewing the web staff.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + False + False + + Note: This requirement is only applicable for private DoD websites. + +If a banner is required, the following banner page must be in place: + +“You are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only. + +By using this IS (which includes any device attached to this IS), you consent to the following conditions: + +-The USG routinely intercepts and monitors communications on this IS for purposes including, but not limited to, penetration testing, COMSEC monitoring, network operations and defense, personnel misconduct (PM), law enforcement (LE), and counterintelligence (CI) investigations. + +- At any time, the USG may inspect and seize data stored on this IS. + +- Communications using, or data stored on, this IS are not private, are subject to routine monitoring, interception, and search, and may be disclosed or used for any USG-authorized purpose. + +- This IS includes security measures (e.g., authentication and access controls) to protect USG interests—not for your personal benefit or privacy. + +- Notwithstanding the above, using this IS does not constitute consent to PM, LE or CI investigative searching or monitoring of the content of privileged communications, or work product, related to personal representation or services by attorneys, psychotherapists, or clergy, and their assistants. Such communications and work product are private and confidential. See User Agreement for details.” + +OR + +If your system cannot meet the character limits to store this amount of text in the banner, the following is another option for the warning banner: + +"I've read & consent to terms in IS user agreem't." + +NOTE: While DoDI 8500.01 does not contain a copy of the banner to be used, it does point to the RMF Knowledge Service for a copy of the required text. It is also noted that the banner is to be displayed only once when the individual enters the site and not for each page. + +If the access-controlled website does not display this banner page before entry, this is a finding. + + + + + <VulnDiscussion>Controlling what a user of a hosted application can access is part of the security posture of the web server. Any time a user can access more functionality than is needed for the operation of the hosted application poses a security issue. A user with too much access can view information that is not needed for the user's job role, or could use the function in an unintentional manner. + +A MIME tells the web server what type of program various file types and extensions are and what external utilities or programs are needed to execute the file type. + +A shell is a program that serves as the basic interface between the user and the operating system, so hosted application users must not have access to these programs. Shell programs may execute shell escapes and can then perform unauthorized activities that could damage the security posture of the web server.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + Absent + .exe + False + application/octet-stream + False + + 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: +If any OS shell MIME types are configured, this is a finding. +.exe + + + <VulnDiscussion>Controlling what a user of a hosted application can access is part of the security posture of the web server. Any time a user can access more functionality than is needed for the operation of the hosted application poses a security issue. A user with too much access can view information that is not needed for the user's job role, or could use the function in an unintentional manner. + +A MIME tells the web server what type of program various file types and extensions are and what external utilities or programs are needed to execute the file type. + +A shell is a program that serves as the basic interface between the user and the operating system, so hosted application users must not have access to these programs. Shell programs may execute shell escapes and can then perform unauthorized activities that could damage the security posture of the web server.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + Absent + .dll + False + application/x-msdownload + False + + 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: +If any OS shell MIME types are configured, this is a finding. +.dll + + + <VulnDiscussion>Controlling what a user of a hosted application can access is part of the security posture of the web server. Any time a user can access more functionality than is needed for the operation of the hosted application poses a security issue. A user with too much access can view information that is not needed for the user's job role, or could use the function in an unintentional manner. + +A MIME tells the web server what type of program various file types and extensions are and what external utilities or programs are needed to execute the file type. + +A shell is a program that serves as the basic interface between the user and the operating system, so hosted application users must not have access to these programs. Shell programs may execute shell escapes and can then perform unauthorized activities that could damage the security posture of the web server.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + Absent + .com + False + application/octet-stream + False + + 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: +If any OS shell MIME types are configured, this is a finding. +.com + + + <VulnDiscussion>Controlling what a user of a hosted application can access is part of the security posture of the web server. Any time a user can access more functionality than is needed for the operation of the hosted application poses a security issue. A user with too much access can view information that is not needed for the user's job role, or could use the function in an unintentional manner. + +A MIME tells the web server what type of program various file types and extensions are and what external utilities or programs are needed to execute the file type. + +A shell is a program that serves as the basic interface between the user and the operating system, so hosted application users must not have access to these programs. Shell programs may execute shell escapes and can then perform unauthorized activities that could damage the security posture of the web server.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + Absent + .bat + False + application/x-bat + False + + 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: +If any OS shell MIME types are configured, this is a finding. +.bat + + + <VulnDiscussion>Controlling what a user of a hosted application can access is part of the security posture of the web server. Any time a user can access more functionality than is needed for the operation of the hosted application poses a security issue. A user with too much access can view information that is not needed for the user's job role, or could use the function in an unintentional manner. + +A MIME tells the web server what type of program various file types and extensions are and what external utilities or programs are needed to execute the file type. + +A shell is a program that serves as the basic interface between the user and the operating system, so hosted application users must not have access to these programs. Shell programs may execute shell escapes and can then perform unauthorized activities that could damage the security posture of the web server.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + Absent + .csh + False + application/x-csh + False + + 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: +If any OS shell MIME types are configured, this is a finding. +.csh + + + + + <VulnDiscussion>Transport Layer Security (TLS) encryption is a required security setting for a private web server. Encryption of private information is essential to ensuring data confidentiality. If private information is not encrypted, it can be intercepted and easily read by an unauthorized party. A private web server must use a FIPS 140-2-approved TLS version, and all non-FIPS-approved SSL versions must be disabled. + +FIPS 140-2-approved TLS versions include TLS V1.1 or greater. NIST SP 800-52 specifies the preferred configurations for government systems.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + False + False + + Note: If the server being reviewed is a public IIS 10.0 web server, 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. + +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. + Ssl + + + <VulnDiscussion>Transport Layer Security (TLS) encryption is a required security setting for a private web server. Encryption of private information is essential to ensuring data confidentiality. If private information is not encrypted, it can be intercepted and easily read by an unauthorized party. A private web server must use a FIPS 140-2-approved TLS version, and all non-FIPS-approved SSL versions must be disabled. + +FIPS 140-2-approved TLS versions include TLS V1.1 or greater. NIST SP 800-52 specifies the preferred configurations for government systems.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + V-100195 + False + False + + 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. + +Verify "Require SSL" check box is selected. + +If the "Require SSL" check box is not selected, this is a finding. + Ssl + + + <VulnDiscussion>A DoD private website must use PKI as an authentication mechanism for web users. Information systems residing behind web servers requiring authorization based on individual identity must use the identity provided by certificate-based authentication to support access control decisions. Not using client certificates allows an attacker unauthenticated access to private websites. + +Satisfies: SRG-APP-000172-WSR-000104, SRG-APP-000224-WSR-000135, SRG-APP-000427-WSR-000186</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + False + False + + Note: If the server being reviewed is a public IIS 10.0 web server, this is Not Applicable. +Note: If certificate handling is performed at the Proxy/Load Balancer, this is not a finding. + +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. + SslRequireCert + + + <VulnDiscussion>When data is written to digital media, such as hard drives, mobile computers, external/removable hard drives, personal digital assistants, flash/thumb drives, etc., there is risk of data loss and data compromise. User identities and passwords stored on the hard drive of the hosting hardware must be encrypted to protect the data from easily being discovered and used by an unauthorized user to access the hosted applications. The cryptographic libraries and functionality used to store and retrieve the user identifiers and passwords must be part of the web server. + +Satisfies: SRG-APP-000429-WSR-000113, SRG-APP-000439-WSR-000151, SRG-APP-000441-WSR-000181, SRG-APP-000442-WSR-000182</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + False + False + + Note: If SSL is installed on load balancer/proxy server through which traffic is routed to the IIS 10.0 server, and the IIS 10.0 server receives traffic from the load balancer/proxy server, the SSL requirement must be met on the load balancer/proxy server. + +Note: If this is a public facing web server, 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. +If the "sslFlags" is not set to "ssl128", this is a finding. + Ssl,SslNegotiateCert,SslRequireCert,Ssl128 + + + + + <VulnDiscussion>The idle time-out attribute controls the amount of time a worker process will remain idle before it shuts down. A worker process is idle if it is not processing requests and no new requests are received. + +The purpose of this attribute is to conserve system resources; the default value for idle time-out is 20 minutes. + +By default, the World Wide Web (WWW) service establishes an overlapped recycle, in which the worker process to be shut down is kept running until after a new worker process is started.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + False + idleTimeout + True + [TimeSpan]{0} -le [TimeSpan]'00:20:00' -and [TimeSpan]{0} -gt [TimeSpan]'00:00:00' + Follow the procedures below for each site hosted on the IIS 10.0 web server: + +Open the IIS 10.0 Manager. +Click the Application Pools. +Highlight an Application Pool to review and click "Advanced Settings" in the "Actions" pane. +Scroll down to the "Process Model" section and verify the value for "Idle Time-out" is not "0". + +If the "Idle Time-out" is set to "0", this is a finding. + + + + + <VulnDiscussion>IIS application pools can be periodically recycled to avoid unstable states possibly leading to application crashes, hangs, or memory leaks. By default, application pool recycling is overlapped, which means the worker process to be shut down is kept running until after a new worker process is started. After a new worker process starts, new requests are passed to it. The old worker process shuts down after it finishes processing its existing requests, or after a configured time-out, whichever comes first. This way of recycling ensures uninterrupted service to clients.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + False + restartRequestsLimit + True + {0} -ne 0 + Note: If the IIS Application Pool is hosting Microsoft SharePoint, this is Not Applicable. + +If this IIS 10.0 installation is supporting Microsoft Exchange, and not otherwise hosting any content, this requirement is Not Applicable. + +Open the IIS 10.0 Manager. + +Perform for each Application Pool. + +Click "Application Pools". + +Highlight an Application Pool and click "Advanced Settings" in the "Action" Pane. + +Scroll down to the "Recycling section" and verify the value for "Request Limit" is set to a value other than "0". + +If the "Request Limit" is set to a value of "0", this is a finding. + + + + + <VulnDiscussion>IIS application pools can be periodically recycled to avoid unstable states possibly leading to application crashes, hangs, or memory leaks. By default, application pool recycling is overlapped, which means the worker process to be shut down is kept running until after a new worker process is started. After a new worker process starts, new requests are passed to it. The old worker process shuts down after it finishes processing its existing requests, or after a configured time-out, whichever comes first. This way of recycling ensures uninterrupted service to clients.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + False + restartMemoryLimit + True + {0} -ne 0 + Note: If the IIS Application Pool is hosting Microsoft SharePoint, this is Not Applicable. + +If this IIS 10.0 installation is supporting Microsoft Exchange, and not otherwise hosting any content, this requirement is Not Applicable. + +Open the IIS 10.0 Manager. + +Perform the following for each Application Pool: + +Click "Application Pools". + +Highlight an Application Pool and click "Advanced Settings" in the Action Pane. + +In the "Advanced Settings" dialog box scroll down to the "Recycling" section and verify the value for "Virtual Memory Limit" is not set to "0". + +If the value for "Virtual Memory Limit" is set to "0", this is a finding. + + + + + <VulnDiscussion>IIS application pools can be periodically recycled to avoid unstable states possibly leading to application crashes, hangs, or memory leaks. By default, application pool recycling is overlapped, which means the worker process to be shut down is kept running until after a new worker process is started. After a new worker process starts, new requests are passed to it. The old worker process shuts down after it finishes processing its existing requests, or after a configured time-out, whichever comes first. This way of recycling ensures uninterrupted service to clients.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + False + restartPrivateMemoryLimit + True + {0} -ne 0 + Note: If the IIS Application Pool is hosting Microsoft SharePoint, this is Not Applicable. + +If this IIS 10.0 installation is supporting Microsoft Exchange, and not otherwise hosting any content, this requirement is Not Applicable. + +Open the IIS 10.0 Manager. + +Perform the following for each Application Pool: + +Click "Application Pools". + +Highlight an Application Pool and click "Advanced Settings" in the "Action" Pane. + +Scroll down to the "Recycling" section and verify the value for "Private Memory Limit" is set to a value other than "0". + +If the "Private Memory Limit" is set to a value of "0", this is a finding. + + + + + <VulnDiscussion>Application pools can be periodically recycled to avoid unstable states possibly leading to application crashes, hangs, or memory leaks.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + False + logEventOnRecycle + False + + Note: If the IIS Application Pool is hosting Microsoft SharePoint, this is Not Applicable. + +If this IIS 10.0 installation is supporting Microsoft Exchange, and not otherwise hosting any content, this requirement is Not Applicable. + +Open the IIS 10.0 Manager. + +Perform the following for each Application Pool: + +Click "Application Pools". + +Highlight an Application Pool and click "Advanced Settings" in the "Action" Pane. + +Scroll down to the "Recycling" section and expand the "Generate Recycle Event Log Entry" section. + +Verify both the "Regular time interval" and "Specific time" options are set to "True". + +If both the "Regular time interval" and "Specific time" options are not set to "True", this is a finding. + 'Time,Schedule' + + + <VulnDiscussion>Windows Process Activation Service (WAS) manages application pool configurations and may flag a worker process as unhealthy and shut it down. An application pool’s pinging monitor must be enabled to confirm worker processes are functional. A lack of response from the worker process might mean the worker process does not have a thread to respond to the ping request, or it is hanging for some other reason. The ping interval and ping response time may need adjustment to gain access to timely information about application pool health without triggering false, unhealthy conditions; for example, instability caused by an application.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + False + pingingEnabled + False + + Open the Internet Information Services (IIS) Manager. + +Click "Application Pools". + +Perform the following for each Application Pool: + +Highlight an Application Pool to review and click "Advanced Settings" in the "Actions" pane. + +Scroll down to the "Process Model" section and verify the value for "Ping Enabled" is set to "True". + +If the value for "Ping Enabled" is not set to "True", this is a finding. + $true + + + <VulnDiscussion>Rapid fail protection is a feature that interrogates the health of worker processes associated with websites and web applications. It can be configured to perform a number of actions such as shutting down and restarting worker processes that have reached failure thresholds. By not setting rapid fail protection, the web server could become unstable in the event of a worker process crash potentially leaving the web server unusable.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + False + rapidFailProtection + False + + Note: If the IIS Application Pool is hosting Microsoft SharePoint, this is Not Applicable. + +If this IIS 10.0 installation is supporting Microsoft Exchange, and not otherwise hosting any content, this requirement is Not Applicable. + +Open the IIS 10.0 Manager. + +Click "Application Pools". + +Perform the following for each Application Pool: + +Highlight an Application Pool to review and click "Advanced Settings" in the "Actions" pane. + +Scroll down to the "Rapid Fail Protection" section and verify the value for "Enabled" is set to "True". + +If the "Rapid Fail Protection:Enabled" is not set to "True", this is a finding. + $true + + + <VulnDiscussion>Windows Process Activation Service (WAS) manages application pool configuration and may flag a worker process as unhealthy and shut it down. The rapid fail protection must be set to a suitable value. A lack of response from the worker process might mean the worker process does not have a thread to respond to the ping request, or that it is hanging for some other reason. The ping interval and ping response time may need adjustment to gain access to timely information about application pool health without triggering false, unhealthy conditions.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + False + rapidFailProtectionInterval + True + [TimeSpan]{0} -le [TimeSpan]'00:05:00' + Note: If the IIS Application Pool is hosting Microsoft SharePoint, this is Not Applicable. + +If this IIS 10.0 installation is supporting Microsoft Exchange, and not otherwise hosting any content, this requirement is Not Applicable. + +Open the IIS 10.0 Manager. + +Click "Application Pools". + +Perform the following for each Application Pool: + +Highlight an Application Pool to review and click "Advanced Settings" in the "Actions" pane. + +Scroll down to the "Rapid Fail Protection" section and verify the value for "Failure Interval" is set to "5". + +If the "Failure Interval" is not set to "5" or less, this is a finding. + + + + + + + /system.web/sessionState + <VulnDiscussion>When the session information is stored on the client, the session ID, along with the user authorization and identity information, is sent along with each client request and is either stored in a cookie, embedded in the uniform resource locator (URL), or placed in a hidden field on the displayed form. Each of these offers advantages and disadvantages. The biggest disadvantage to all three is the hijacking of a session along with all of the user's credentials. + +When the user authorization and identity information is stored on the server in a protected and encrypted database, the communication between the client and web server will only send the session identifier, and the server can then retrieve user credentials for the session when needed. If, during transmission, the session were to be hijacked, the user's credentials would not be compromised. + +ASP.NET provides a session state, which is available as the HttpSessionState class, as a method of storing session-specific information that is visible only within the session. ASP.NET session state identifies requests from the same browser during a limited time window as a session, and provides the ability to persist variable values for the duration of that session.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + False + mode + False + + 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 "Session State Mode Settings" is set to "In Process", 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. + InProc + + + /system.web/sessionState + <VulnDiscussion>When the session information is stored on the client, the session ID, along with the user authorization and identity information, is sent along with each client request and is stored in either a cookie, embedded in the uniform resource locator (URL), or placed in a hidden field on the displayed form. Each of these offers advantages and disadvantages. The biggest disadvantage to all three is the hijacking of a session along with all of the user's credentials. + +When the user authorization and identity information is stored on the server in a protected and encrypted database, the communication between the client and website will only send the session identifier, and the server can then retrieve user credentials for the session when needed. If, during transmission, the session were to be hijacked, the user's credentials would not be compromised. + +ASP.NET provides a session state, which is available as the HttpSessionState class, as a method of storing session-specific information visible only within the session. ASP.NET session state identifies requests from the same browser during a limited time window as a session and provides the ability to persist variable values for the duration of that session. + +When using the URI mode for cookie settings under session state, IIS will reject and reissue session IDs that do not have active sessions. Configuring IIS to expire session IDs and regenerate tokens gives a potential attacker less time to capture a cookie and gain access to server content.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + False + cookieless + False + + 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. + UseCookies + + + /system.web/trust + <VulnDiscussion>A web server may host too many applications. Each application will need certain system resources and privileged operations to operate correctly. An application's trust level determines the permissions granted by the ASP.NET Code Access Security (CAS) policy. An application with full trust permissions may access all resource types on a server and perform privileged operations, while applications running with partial trust have varying levels of operating permissions and access to resources. The CAS determines the permissions granted to the application on the server. Setting a level of trust compatible with the applications will limit the potential harm a compromised application could cause to a system. The web server must be configured to contain and control the applications and protect the system resources and privileged operations from those not needed by the application for operation. + +Limiting the application will confine the potential harm a compromised application could cause to a system.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance>The IIS 10.0 production website must configure the Global .NET Trust Level.</SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + False + level + True + '{0}' -cmatch '^(Full|High)$' + Note: If the server being reviewed is a non-production website, this is Not Applicable. + +Follow the procedures below for each site hosted on the IIS 10.0 web server: + +Open the IIS 10.0 Manager. + +Click the site name under review. + +Double-click the ".NET Trust Level" icon. + +If the ".NET Trust Level" is not set to Full or less, this is a finding. + + + + + /system.web/sessionState + <VulnDiscussion>Communication between a client and the web server is done using the HTTP protocol, but HTTP is a stateless protocol. To maintain a connection or session, a web server will generate a session identifier (ID) for each client session when the session is initiated. The session ID allows the web server to track a user session and, in many cases, the user, if the user previously logged into a hosted application. + +By being able to guess session IDs, an attacker can easily perform a man-in-the-middle attack. To truly generate random session identifiers that cannot be reproduced, the web server session ID generator, when used twice with the same input criteria, must generate an unrelated random ID. + +The session ID generator must be a FIPS 140-2-approved generator.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + V-100191 + False + mode + False + + 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. + InProc + + + /system.webServer/security/requestFiltering/requestlimits + <VulnDiscussion>Request filtering replaces URLScan in IIS, enabling administrators to create a more granular rule set with which to allow or reject inbound web content. By setting limits on web requests, it helps to ensure availability of web services and may also help mitigate the risk of buffer overflow type attacks. The MaxURL Request Filter limits the number of bytes the server will accept in a URL.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + False + maxUrl + True + {0} -le 4096 + 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. + + + + + /system.webServer/security/requestFiltering/requestlimits + <VulnDiscussion>By setting limits on web requests, it ensures availability of web services and mitigates the risk of buffer overflow type attacks. The maxAllowedContentLength Request Filter limits the number of bytes the server will accept in a request.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + False + maxAllowedContentLength + True + {0} -le 30000000 + Follow the procedures below for each site hosted on the IIS 10.0 web server: + +Open the IIS 10.0 Manager. + +Click on the site name. + +Double-click the "Request Filtering" icon. + +Click "Edit Feature Settings" in the "Actions" pane. + +If the "maxAllowedContentLength" value is not explicitly set to "30000000" or less or a length documented and approved by the ISSO, this is a finding. + + + + + /system.webServer/security/requestFiltering/requestlimits + <VulnDiscussion>Setting limits on web requests helps to ensure availability of web services and may also help mitigate the risk of buffer overflow type attacks. The Maximum Query String Request Filter describes the upper limit on allowable query string lengths. Upon exceeding the configured value, IIS will generate a Status Code 404.15.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + False + maxQueryString + True + {0} -le 2048 + Follow the procedures below for each site hosted on the IIS 10.0 web server: + +Open the IIS 10.0 Manager. + +Click the site name. + +Double-click the "Request Filtering" icon. + +Click “Edit Feature Settings” in the "Actions" pane. + +If the "Maximum Query String" value is not set to "2048" or less, this is a finding. + + + + + /system.webServer/security/requestFiltering + <VulnDiscussion>Setting limits on web requests ensures availability of web services and mitigates the risk of buffer overflow type attacks. The allow high-bit characters Request Filter enables rejection of requests containing non-ASCII characters.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + False + allowHighBitCharacters + False + + Follow the procedures below for each site hosted on the IIS 10.0 web server: + +Open the IIS 10.0 Manager. + +Click the site name. + +Double-click the "Request Filtering" icon. + +Click "Edit Feature Settings" in the "Actions" pane. + +If the "Allow high-bit characters" check box is checked, this is a finding. + +Note: If this IIS 10.0 installation is supporting Microsoft Exchange, and not otherwise hosting any content, this requirement is Not Applicable. + false + + + /system.webServer/security/requestFiltering + <VulnDiscussion>Request filtering enables administrators to create a more granular rule set with which to allow or reject inbound web content. Setting limits on web requests ensures availability of web services and mitigates the risk of buffer overflow type attacks. When the "Allow double escaping" option is disabled, it prevents attacks that rely on double-encoded requests.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + False + allowDoubleEscaping + False + + Follow the procedures below for each site hosted on the IIS 10.0 web server: + +Open the IIS 10.0 Manager. + +Click the site name. + +Double-click the "Request Filtering" icon. + +Click "Edit Feature Settings" in the "Actions" pane. + +If the "Allow double escaping" check box is checked, this is a finding. + false + + + /system.webServer/security/requestFiltering/fileExtensions + <VulnDiscussion>Request filtering enables administrators to create a more granular rule set to allow or reject inbound web content. Setting limits on web requests helps to ensure availability of web services and may also help mitigate the risk of buffer overflow type attacks. The allow unlisted property of the "File Extensions Request" filter enables rejection of requests containing specific file extensions not defined in the "File Extensions" filter. Tripping this filter will cause IIS to generate a Status Code 404.7.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + False + allowUnlisted + False + + Follow the procedures below for each site hosted on the IIS 10.0 web server: + +Open the IIS 10.0 Manager. + +Click the site name. + +Double-click the "Request Filtering" icon. + +Click "Edit Feature Settings" in the "Actions" pane. + +If the "Allow unlisted file name extensions" check box is checked, this is a finding. + +Note: If this IIS 10.0 installation is supporting Microsoft Exchange, and not otherwise hosting any content, this requirement is Not Applicable. + false + + + /system.webServer/directoryBrowse + <VulnDiscussion>Directory browsing allows the contents of a directory to be displayed upon request from a web client. If directory browsing is enabled for a directory in IIS, users could receive a web page listing the contents of the directory. If directory browsing is enabled the risk of inadvertently disclosing sensitive content is increased.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + False + enabled + False + + Follow the procedures below for each site hosted on the IIS 10.0 web server: + +Click the Site. + +Double-click the "Directory Browsing" icon. + +If "Directory Browsing" is not installed, this is Not Applicable. + +Under the "Actions" pane, verify "Directory Browsing" is "Disabled". + +If "Directory Browsing" is not "Disabled", this is a finding. + false + + + /system.webServer/httpErrors + <VulnDiscussion>HTTP error pages contain information that could enable an attacker to gain access to an information system. Failure to prevent the sending of HTTP error pages with full information to remote requesters exposes internal configuration information to potential attackers.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + False + errormode + False + + Follow the procedures below for each site hosted on the IIS 10.0 web server: + +Open the IIS 10.0 Manager. + +Click the site name under review. + +Double-click the "Error Pages" icon. + +Click each error message and click "Edit Feature" setting from the "Actions" pane. + +If any error message is not set to "Detailed errors for local requests and custom error pages for remote requests", this is a finding. + DetailedLocalOnly + + + /system.web/compilation + <VulnDiscussion>Setting compilation debug to false ensures detailed error information does not inadvertently display during live application usage, mitigating the risk of application information being displayed to users.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + False + debug + False + + Note: If the ".NET feature" is not installed, this check is Not Applicable. + +Follow the procedures below for each site hosted on the IIS 10.0 web server: + +Open the IIS 10.0 Manager. + +Click the site name under review. + +Double-click ".NET Compilation". + +Scroll down to the "Behavior" section and verify the value for "Debug" is set to "False". + +If the "Debug" value is not set to "False", this is a finding. + false + + + /system.web/sessionState + <VulnDiscussion>Leaving sessions open indefinitely is a major security risk. An attacker can easily use an already authenticated session to access the hosted application as the previously authenticated user. By closing sessions after a set period of inactivity, the web server can make certain that those sessions that are not closed through the user logging out of an application are eventually closed. + +Acceptable values are 5 minutes for high-value applications, 10 minutes for medium-value applications, and 20 minutes for low-value applications.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + False + timeout + True + '{0}' -le '00:20:00' + Follow the procedures below for each site hosted on the IIS 10.0 web server: + +Open the IIS 10.0 Manager. + +Click the site name. + +Select "Configuration Editor" under the "Management" section. + +From the "Section:" drop-down list at the top of the configuration editor, locate "system.web/sessionState". + +Verify the "timeout" is set to "00:20:00 or less”, using the lowest value possible depending upon the application. +Acceptable values are 5 minutes for high-value applications, 10 minutes for medium-value applications, and 20 minutes for low-value applications. + +If "timeout" is not set to "00:20:00 or less”, this is a finding. + + + + + /system.webServer/asp/session + <VulnDiscussion>The HTTP protocol is a stateless protocol. To maintain a session, a session identifier is used. The session identifier is a piece of data used to identify a session and a user. If the session identifier is compromised by an attacker, the session can be hijacked. By encrypting the session identifier, the identifier becomes more difficult for an attacker to hijack, decrypt, and use before the session has expired.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + False + keepSessionIdSecure + False + + Follow the procedures below for each site hosted on the IIS 10.0 web server: + +Access the IIS 10.0 Manager. + +Select the website being reviewed. + +Under "Management" section, double-click the "Configuration Editor" icon. + +From the "Section:" drop-down list, select "system.webServer/asp". + +Expand the "session" section. + +Verify the "keepSessionIdSecure" is set to "True". + +If the "keepSessionIdSecure" is not set to "True", this is a finding. + True + + + /system.web/httpCookies + <VulnDiscussion>A cookie can be read by client-side scripts easily if cookie properties are not set properly. By allowing cookies to be read by the client-side scripts, information such as session identifiers could be compromised and used by an attacker who intercepts the cookie. Setting cookie properties (i.e., HttpOnly property) to disallow client-side scripts from reading cookies better protects the information inside the cookie. + +Satisfies: SRG-APP-000439-WSR-000154, SRG-APP-000439-SSR-000155, SRG-APP-000439-WSR-000153</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + False + requireSSL + False + + From the "Section:" drop-down list, select "system.web/httpCookies". +Verify the "require SSL" is set to "True". + True + + + /system.web/sessionState + <VulnDiscussion>A cookie can be read by client-side scripts easily if cookie properties are not set properly. By allowing cookies to be read by the client-side scripts, information such as session identifiers could be compromised and used by an attacker who intercepts the cookie. Setting cookie properties (i.e., HttpOnly property) to disallow client-side scripts from reading cookies better protects the information inside the cookie. + +Satisfies: SRG-APP-000439-WSR-000154, SRG-APP-000439-SSR-000155, SRG-APP-000439-WSR-000153</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + False + compressionEnabled + False + + From the "Section:" drop-down list, select "system.web/sessionState". +Verify the "compressionEnabled" is set to "False". + False + + + + + <VulnDiscussion>A web server can be installed with functionality that by its nature is not secure. Web Distributed Authoring (WebDAV) is an extension to the HTTP protocol that, when developed, was meant to allow users to create, change, and move documents on a server, typically a web server or web share. Allowing this functionality, development, and deployment is much easier for web authors. + +WebDAV is not widely used and has serious security concerns because it may allow clients to modify unauthorized files on the web server.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + Absent + False + Web-DAV-Publishing + False + + Follow the procedures below for each site hosted on the IIS 10.0 web server: + +Open the IIS 10.0 Manager. + +Select the IIS 10.0 website. + +Review the features listed under the "IIS" section. + +If the "WebDAV Authoring Rules" icon exists, this is a finding. + + +