| V-13733 | High | Server side includes (SSIs) must run with execution capability disabled. | The Options directive configures the web server features that are available in particular directories. The IncludesNOEXEC feature controls the ability of the server to utilize SSIs while... |
| V-13621 | High | All web server documentation, sample code, example applications, and tutorials must be removed from a production web server. | 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... |
| V-2246 | High | Web server software must be a vendor-supported version. | Many vulnerabilities are associated with older versions of web server software. As hot fixes and patches are issued, these solutions are included in the next version of the server software.... |
| V-2247 | High | Administrators must be the only users allowed access to the directory tree, the shell, or other operating system functions and utilities. | 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.... |
| V-13738 | Medium | The HTTP request header field size must be limited. | Buffer overflow attacks are carried out by a malicious attacker sending amounts of data that the web server cannot store in a given size buffer. The eventual overflow of this buffer can overwrite... |
| V-13739 | Medium | The HTTP request line must be limited. | Buffer overflow attacks are carried out by a malicious attacker sending amounts of data that the web server cannot store in a given size buffer. The eventual overflow of this buffer can overwrite... |
| V-13730 | Medium | The httpd.conf MaxClients directive must be set properly. | These requirements are set to mitigate the effects of several types of denial of service attacks. Although there is some latitude concerning the settings themselves, the requirements attempt to... |
| V-13731 | Medium | All interactive programs must be placed in a designated directory with appropriate permissions. | Directory options directives are directives that can be applied to further restrict access to file and directories. The Options directive controls which server features are available in a... |
| V-13732 | Medium | The "–FollowSymLinks” setting must be disabled.
| The Options directive configures the web server features that are available in particular directories. The FollowSymLinks option controls the ability of the server to follow symbolic links. A... |
| V-13734 | Medium | The MultiViews directive must be disabled. | Directory options directives are directives that can be applied to further restrict access to file and directories. MultiViews is a per-directory option, meaning it can be set with an Options... |
| V-13735 | Medium | Directory indexing must be disabled on directories not containing index files. | Directory options directives are directives that can be applied to further restrict access to file and directories. If a URL which maps to a directory is requested, and there is no DirectoryIndex... |
| V-13736 | Medium | The HTTP request message body size must be limited. | Buffer overflow attacks are carried out by a malicious attacker sending amounts of data that the web server cannot store in a given size buffer. The eventual overflow of this buffer can overwrite... |
| V-13737 | Medium | The HTTP request header fields must be limited. | Buffer overflow attacks are carried out by a malicious attacker sending amounts of data that the web server cannot store in a given size buffer. The eventual overflow of this buffer can overwrite... |
| V-26393 | Medium | The ability to override the access configuration for the OS root directory must be disabled. | The Apache OverRide directive allows for .htaccess files to be used to override much of the configuration, including authentication, handling of document types, auto generated indexes, access... |
| V-26396 | Medium | HTTP request methods must be limited. | The HTTP 1.1 protocol supports several request methods which are rarely used and potentially high risk. For example, methods such as PUT and DELETE are rarely used and should be disabled in... |
| V-13620 | Medium | A private web server’s list of CAs in a trust hierarchy must lead to an authorized DoD PKI Root CA. | A PKI certificate is a digital identifier that establishes the identity of an individual or a platform. A server that has a certificate provides users with third-party confirmation of... |
| V-2234 | Medium | Public web server resources must not be shared with private assets. | It is important to segregate public web server resources from private resources located behind the DoD DMZ in order to protect private assets. When folders, drives or other resources are directly... |
| V-2236 | Medium | Installation of a compiler on production web server is prohibited. | The presence of a compiler on a production server facilitates the malicious user’s task of creating custom versions of programs and installing Trojan Horses or viruses. For example, the attacker’s... |
| V-2232 | Medium | The web server password(s) must be entrusted to the SA or Web Manager. | Normally, a service account is established for the web server. This is because a privileged account is not desirable and the server is designed to run for long uninterrupted periods of time. The... |
| V-26294 | Medium | Web server status module must be disabled. | The Apache mod_info module provides information on the server configuration via access to a /server-info URL location, while the mod_status module provides current server performance statistics.... |
| V-2243 | Medium | A private web server must be located on a separate controlled access subnet. | Private web servers, which host sites that serve controlled access data, must be protected from outside threats in addition to insider threats. Insider threat may be accidental or intentional but,... |
| V-2259 | Medium | Web server system files must conform to minimum file permission requirements. | This check verifies that 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... |
| V-2256 | Medium | The access control files are owned by a privileged web server account. | This check verifies that the key web server system configuration files are owned by the SA or Web Manager controlled account. These same files which control the configuration of the web server,... |
| V-2271 | Medium | Monitoring software must include CGI or equivalent programs in its scope. | By their very nature, CGI type files permit the anonymous web user to interact with data and perhaps store data on the web server. In many cases, CGI scripts exercise system-level control over the... |
| V-2255 | Medium | The web server’s htpasswd files (if present) must reflect proper ownership and permissions | In addition to OS restrictions, access rights to files and directories can be set on a web site using the web server software. That is, in addition to allowing or denying all access rights, a... |
| V-26299 | Medium | The web server must not be configured as a proxy server. | The Apache proxy modules allow the server to act as a proxy (either forward or reverse proxy) of http and other protocols with additional proxy modules loaded. If the Apache installation is not... |
| V-6577 | Medium | A web server must be segregated from other services. | The web server installation and configuration plan should not support the co-hosting of multiple services such as Domain Name Service (DNS), e-mail, databases, search engines, indexing, or... |
| V-13728 | Medium | The httpd.conf MinSpareServers directive must be set properly. | These requirements are set to mitigate the effects of several types of denial of service attacks. Although there is some latitude concerning the settings themselves, the requirements attempt to... |
| V-13727 | Medium | The httpd.conf StartServers directive must be set properly. | These requirements are set to mitigate the effects of several types of denial of service attacks. Although there is some latitude concerning the settings themselves, the requirements attempt to... |
| V-13726 | Medium | The KeepAliveTimeout directive must be defined. | The number of seconds Apache will wait for a subsequent request before closing the connection. Once a request has been received, the timeout value specified by the Timeout directive applies.... |
| V-13725 | Medium | The KeepAlive directive must be enabled. | The KeepAlive extension to HTTP/1.0 and the persistent connection feature of HTTP/1.1 provide long lived HTTP sessions which allow multiple requests to be sent over the same connection. These... |
| V-13724 | Medium | The Timeout directive must be properly set. | The Timeout requirements are set to mitigate the effects of several types of denial of service attacks. Although there is some latitude concerning the settings themselves, the requirements attempt... |
| V-26305 | Medium | The process ID (PID) file must be properly secured. | The PidFile directive sets the file path to the process ID file to which the server records the process id of the server, which is useful for sending a signal to the server process or for checking... |
| V-2261 | Medium | A public web server must limit email to outbound only. | Incoming E-mail has been known to provide hackers with access to servers. Disabling the incoming mail service prevents this type of attacks. Additionally, Email represents the main use of the... |
| V-26302 | Medium | User specific directories must not be globally enabled. | The UserDir directive must be disabled so that user home directories are not accessed via the web site with a tilde (~) preceding the username. The directive also sets the path name of the... |
| V-13613 | Medium | The Web site software used with the web server must have all applicable security patches applied and documented. | The IAVM process does not address all patches that have been identified for the host operating system or, in this case, the web server software environment. Many vendors have subscription services... |
| V-2242 | Medium | A public web server, if hosted on the NIPRNet, must be isolated in an accredited DoD DMZ Extension. | To minimize exposure of private assets to unnecessary risk by attackers, public web servers must be isolated from internal systems. Public web servers are by nature more vulnerable to attack from... |
| V-2225 | Medium | MIME types for csh or sh shell programs must be disabled. | Users must not be allowed to access the shell programs. Shell programs might execute shell escapes and could then perform unauthorized activities that could damage the security posture of the web... |
| V-13672 | Medium | The private web server must use an approved DoD certificate validation process. | Without the use of a certificate validation process, the site is vulnerable to accepting certificates that have expired or have been revoked. This would allow unauthorized individuals access to... |
| V-26285 | Medium | Active software modules must be minimized. | Modules are the source of Apache httpd servers core and dynamic capabilities. Thus not every module available is needed for operation. Most installations only need a small subset of the modules... |
| V-26287 | Medium | Web Distributed Authoring and Versioning (WebDAV) must be disabled. | The Apache mod_dav and mod_dav_fs modules support WebDAV ('Web-based Distributed Authoring and Versioning') functionality for Apache. WebDAV is an extension to the HTTP protocol which allows... |
| V-60707 | Medium | The web server must remove all export ciphers from the cipher suite. | During the initial setup of a Transport Layer Security (TLS) connection to the web server, the client sends a list of supported cipher suites in order of preference. The web server will reply... |
| V-2248 | Medium | Web administration tools must be restricted to the web manager and the web manager’s designees. | All automated information systems are at risk of data loss due to disaster or compromise. Failure to provide adequate protection to the administration tools creates risk of potential theft or... |
| V-26323 | Medium | The web server must be configured to explicitly deny access to the OS root. | The Apache Directory directive allows for directory specific configuration of access controls and many other features and options. One important usage is to create a default deny policy that does... |
| V-26322 | Medium | The score board file must be properly secured.
| The ScoreBoardfile directive sets a file path which the server will use for Inter-Process Communication (IPC) among the Apache processes. If the directive is specified, then Apache will use the... |
| V-26368 | Medium | Automatic directory indexing must be disabled. | To identify the type of web servers and versions software installed it is common for attackers to scan for icons or special content specific to the server type and version. A simple request like... |
| V-26327 | Medium | The URL-path name must be set to the file path name or the directory path name. | The ScriptAlias directive controls which directories the Apache server "sees" as containing scripts. If the directive uses a URL-path name that is different than the actual file system path, the... |
| V-26326 | Medium | The web server must be configured to listen on a specific IP address and port. | The Apache Listen directive specifies the IP addresses and port numbers the Apache web server will listen for requests. Rather than be unrestricted to listen on all IP addresses available to the... |
| V-26325 | Medium | The TRACE method must be disabled. | Diagnostics help establish a history of activities, and can be useful in detecting attack attempts or determining tuning adjustments to improve server availability. Trace logs are essential to the... |
| V-26324 | Medium | Web server options for the OS root must be disabled. | The Apache Options directive allows for specific configuration of options, including execution of CGI, following symbolic links, server side includes, and content negotiation. The Options... |
| V-6485 | Low | Web server content and configuration files must be part of a routine backup program. | Backing up web server data and web server application software after upgrades or maintenance ensures that recovery can be accomplished up to the current version. It also provides a means to... |
| V-2230 | Low | Backup interactive scripts on the production web server are prohibited. | 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... |
| V-2251 | Low | All utility programs, not necessary for operations, must be removed or disabled. | 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 also a danger at the application... |
| V-13729 | Low | The httpd.conf MaxSpareServers directive must be set properly. | These requirements are set to mitigate the effects of several types of denial of service attacks. Although there is some latitude concerning the settings themselves, the requirements attempt to... |
| V-6724 | Low | Web server and/or operating system information must be protected.
| The web server response header of an HTTP response can contain several fields of information including the requested HTML page. The information included in this response can be web server type and... |
| V-2257 | Low | Administrative users and groups that have access rights to the web server must be documented. | There are typically several individuals and groups that are involved in running a production web server. These accounts must be restricted to only those necessary to maintain web services, review... |
