| Finding ID |
Severity |
Title |
Description |
|
V-218750
|
High |
Anonymous IIS 10.0 website access accounts must be restricted. |
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... |
|
V-218782
|
Medium |
The required DoD banner page must be displayed to authenticated users accessing a DoD private website. |
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... |
|
V-218781
|
Medium |
Backup interactive scripts on the IIS 10.0 server must be removed. |
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... |
|
V-218780
|
Medium |
Interactive scripts on the IIS 10.0 web server must have restrictive access controls. |
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... |
|
V-218779
|
Medium |
Interactive scripts on the IIS 10.0 web server must be located in unique and designated folders. |
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... |
|
V-218778
|
Medium |
The application pools rapid fail protection settings for each IIS 10.0 website must be managed. |
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... |
|
V-218777
|
Medium |
The application pools rapid fail protection for each IIS 10.0 website must be enabled. |
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... |
|
V-218775
|
Medium |
The application pool for each IIS 10.0 website must have a recycle time explicitly set. |
Application pools can be periodically recycled to avoid unstable states possibly leading to application crashes, hangs, or memory leaks. |
|
V-218772
|
Medium |
The maximum number of requests an application pool can process for each IIS 10.0 website must be explicitly set. |
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... |
|
V-218771
|
Medium |
The IIS 10.0 website must have a unique application pool. |
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. |
|
V-218770
|
Medium |
Cookies 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. |
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... |
|
V-218769
|
Medium |
IIS 10.0 website session IDs must be sent to the client using TLS. |
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... |
|
V-218768
|
Medium |
The IIS 10.0 private website must employ cryptographic mechanisms (TLS) and require client certificates. |
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,... |
|
V-218767
|
Medium |
The IIS 10.0 website must only accept client certificates issued by DoD PKI or DoD-approved PKI Certification Authorities (CAs). |
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. |
|
V-218766
|
Medium |
The IIS 10.0 websites must use ports, protocols, and services according to Ports, Protocols, and Services Management (PPSM) guidelines. |
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,... |
|
V-218765
|
Medium |
The 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. |
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... |
|
V-218764
|
Medium |
The IIS 10.0 website must provide the capability to immediately disconnect or disable remote access to the hosted applications. |
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... |
|
V-218763
|
Medium |
The IIS 10.0 websites connectionTimeout setting must be explicitly configured to disconnect an idle session. |
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... |
|
V-218762
|
Medium |
The Idle Time-out monitor for each IIS 10.0 website must be enabled. |
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... |
|
V-218761
|
Medium |
Debugging and trace information used to diagnose the IIS 10.0 website must be disabled. |
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. |
|
V-218760
|
Medium |
Warning 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. |
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. |
|
V-218759
|
Medium |
Directory Browsing on the IIS 10.0 website must be disabled. |
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... |
|
V-218758
|
Medium |
Unlisted file extensions in URL requests must be filtered by any IIS 10.0 website. |
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... |
|
V-218757
|
Medium |
Double encoded URL requests must be prohibited by any IIS 10.0 website. |
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... |
|
V-218756
|
Medium |
Non-ASCII characters in URLs must be prohibited by any IIS 10.0 website. |
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. |
|
V-218755
|
Medium |
The IIS 10.0 websites Maximum Query String limit must be configured. |
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... |
|
V-218754
|
Medium |
The IIS 10.0 website must be configured to limit the size of web requests. |
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. |
|
V-218753
|
Medium |
The IIS 10.0 website must be configured to limit the maxURL. |
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.... |
|
V-218752
|
Medium |
The IIS 10.0 website document directory must be in a separate partition from the IIS 10.0 websites system files. |
The content database is accessed by multiple anonymous users when the web server is in production. By locating the content database on the same partition as the web server system file, the risk for unauthorized access to these protected files is increased. Additionally, having the content database path on the... |
|
V-218751
|
Medium |
The IIS 10.0 website must generate unique session identifiers that cannot be reliably reproduced. |
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... |
|
V-218749
|
Medium |
A private IIS 10.0 website authentication mechanism must use client certificates to transmit session identifier to assure integrity. |
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... |
|
V-218748
|
Medium |
Each IIS 10.0 website must be assigned a default host header. |
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,... |
|
V-218746
|
Medium |
The IIS 10.0 website must have Web Distributed Authoring and Versioning (WebDAV) disabled. |
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.... |
|
V-218745
|
Medium |
The IIS 10.0 website must have resource mappings set to disable the serving of certain file types. |
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)... |
|
V-218744
|
Medium |
Mappings to unused and vulnerable scripts on the IIS 10.0 website must be removed. |
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)... |
|
V-218743
|
Medium |
The IIS 10.0 website must have Multipurpose Internet Mail Extensions (MIME) that invoke OS shell programs disabled. |
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... |
|
V-218742
|
Medium |
The 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. |
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... |
|
V-218741
|
Medium |
The 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. |
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... |
|
V-218740
|
Medium |
An IIS 10.0 website behind a load balancer or proxy server must produce log records containing the source client IP, and destination information. |
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... |
|
V-218739
|
Medium |
Both the log file and Event Tracing for Windows (ETW) for each IIS 10.0 website must be enabled. |
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... |
|
V-218738
|
Medium |
A public IIS 10.0 website must only accept Secure Socket Layer (SSL) connections when authentication is required. |
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... |
|
V-218737
|
Medium |
A private IIS 10.0 website must only accept Secure Socket Layer (SSL) connections. |
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... |
|
V-218736
|
Medium |
The IIS 10.0 website session state cookie settings must be configured to Use Cookies mode. |
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... |
|
V-218735
|
Medium |
The IIS 10.0 website session state must be enabled. |
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... |