APACHE Server 2.0 for Unix

All directives specified in this STIG must be specifically set (i.e. the server is not allowed to revert to programmed defaults for these directives). Included files should be reviewed if they are used. Procedures for reviewing included files are included in the overview document. The use of .htaccess files are not authorized for use according to the STIG. However, if they are used, there are procedures for reviewing them in the overview document. The Web Policy STIG should be used in addition to the Apache Site and Server STIGs in order to do a comprehensive web server review.

Details

Version / Release: V1R2

Published: 2014-09-02

Updated At: 2018-09-23 02:00:43

Compare/View Releases

Select any two versions of this STIG to compare the individual requirements

Select any old version/release of this STIG to view the previous requirements

Actions

Download

Filter


Findings
Severity Open Not Reviewed Not Applicable Not a Finding
Overall 0 0 0 0
Low 0 0 0 0
Medium 0 0 0 0
High 0 0 0 0
Drop CKL or SCAP (XCCDF) results here.

    Vuln Rule Version CCI Severity Title Description Status Finding Details Comments
    SV-36309r2_rule WG370 A22 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 server. A shell is a program that serves as the basic inter
    SV-6930r1_rule WG420 A22 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 the actual script being executed and, as such, are useful
    SV-32788r1_rule WG050 A22 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 SA or Web Manager will need password access to the web serve
    SV-32957r1_rule WG040 A22 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 shared between the public web server and private servers th
    SV-32956r2_rule WG080 A22 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 code can be uploaded and compiled on the server under
    SV-32932r2_rule WA060 A22 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 publically based sources, such as the public Internet. Onc
    SV-32935r1_rule WA070 A22 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, in either case, can cause a disruption in service of the w
    SV-36441r1_rule WG190 A22 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. Maintaining the web server at a current version makes the efforts
    SV-2247r2_rule WG200 W13 HIGH Only administrators are 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. This is in addition to the anonymous web user account. The re
    SV-32948r1_rule WG220 A22 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 damage that may ultimately compromise the mission. Adequate pr
    SV-32955r1_rule WG130 A22 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 layer of the OSI model. Office suites, development tools, and g
    SV-36478r2_rule WG270 A22 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 rule can be specified that allows or denies partial access rig
    SV-32951r1_rule WA120 A22 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 the server’s operation, and the operating system. By mi
    SV-32938r1_rule WG300 A22 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 server, and thus its behavior, must also be accessible by th
    SV-32937r1_rule WG330 A22 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 Internet. It is specialized application that requires the dedic
    SV-32927r1_rule WG440 A22 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 server’s resources. These files make appealing targets f
    SV-32964r1_rule WA140 A22 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 determine and recover from subsequent unauthorized changes to the
    SV-32950r1_rule WG204 A22 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 streaming media on the same server that is providing the web publi
    SV-36672r1_rule WG520 A22 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 version, operating system and version, and ports associate
    SV-32969r1_rule WA230 A22 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 available to notify users of known security threats. The s
    SV-32936r1_rule WG355 A22 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 authenticity. Most web browsers perform server authentication automatic
    SV-32933r1_rule WG385 A22 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 necessary (e.g., compiled code, scripts, web-content, etc.)
    SV-32954r1_rule WG145 A22 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 the web server. This also defeats the purpose of the multi-
    SV-32977r1_rule WA000-WWA020 A22 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 to provide reasonable limits for the protection of the web
    SV-32844r1_rule WA000-WWA022 A22 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 requirements are set to mitigate the effects of several types o
    SV-32877r1_rule WA000-WWA024 A22 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. Setting KeepAliveTimeout to a high value may cause performance p
    SV-36645r1_rule WA000-WWA026 A22 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 provide reasonable limits for the protection of the web serve
    SV-36646r1_rule WA000-WWA028 A22 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 provide reasonable limits for the protection of the web serve
    SV-36648r1_rule WA000-WWA030 A22 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 provide reasonable limits for the protection of the web serve
    SV-36649r1_rule WA000-WWA032 A22 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 provide reasonable limits for the protection of the web serve
    SV-32763r1_rule WA000-WWA050 A22 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 particular directory. The ExecCGI option controls the execution of
    SV-40129r1_rule WA000-WWA052 A22 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 symbolic link allows a file or a directory to be referenced usi
    SV-32753r1_rule WA000-WWA054 A22 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 disabling the exec command, which is used to execute external scrip
    SV-32754r1_rule WA000-WWA056 A22 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 directive within a , or section in httpd.conf, or (if AllowOv
    SV-32755r1_rule WA000-WWA058 A22 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 (e.g., index.html) in that directory, then mod_autoindex w
    SV-32756r1_rule WA000-WWA060 A22 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 system memory. Subsequently an attacker may be able to elev
    SV-32757r1_rule WA000-WWA062 A22 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 system memory. Subsequently an attacker may be able to elev
    SV-32766r2_rule WA000-WWA064 A22 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 system memory. Subsequently an attacker may be able to elev
    SV-32768r2_rule WA000-WWA066 A22 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 system memory. Subsequently an attacker may be able to elev
    SV-33215r1_rule WA00500 A22 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 available. By minimizing the enabled modules to only those th
    SV-33216r1_rule WA00505 A22 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 clients to create, move, and delete files and resources on the w
    SV-33218r1_rule WA00510 A22 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. While having server configuration and status information ava
    SV-33220r1_rule WA00520 A22 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 intended to proxy requests to or from another network then th
    SV-33221r1_rule WA00525 A22 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 directory that will be accessed. The user directories should not b
    SV-33222r1_rule WA00530 A22 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 on the health of the process. If the PidFile is placed in
    SV-33223r1_rule WA00535 A22 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 configured file for the inter-process communication. Therefo
    SV-33226r1_rule WA00540 A22 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 not allow access to Operating System directories and files,
    SV-33213r1_rule WA00545 A22 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 directive for the root OS level is used to create a default minimal
    SV-33227r1_rule WA00550 A22 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 investigation and prosecution of unauthorized access to we
    SV-33228r1_rule WA00555 A22 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 system, the specific IP address or addresses intended must b
    SV-33229r1_rule WA00560 A22 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 potential exists to expose the script source code.Web Admin
    SV-33219r1_rule WA00515 A22 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 http://example.com/icons/apache_pb2.png may tell the attacke
    SV-33232r1_rule WA00547 A22 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 control, and options. When the server finds an .htaccess file (
    SV-33236r1_rule WA00565 A22 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 keeping with the primary security principal of minimize features