| V-214248 ||High ||Apache web server application directories, libraries, and configuration files must only be accessible to privileged users. ||By separating Apache web server security functions from non-privileged users, roles can be developed that can then be used to administer the Apache web server. Forcing users to change from a... |
| V-214242 ||High ||The Apache web server must provide install options to exclude the installation of documentation, sample code, example applications, and tutorials. ||Apache web server documentation, sample code, example applications, and tutorials may be an exploitable threat to an Apache web server because this type of code has not been evaluated and... |
| V-214253 ||High ||The Apache web server must generate a session ID using as much of the character set as possible to reduce the risk of brute force. ||Generating a session identifier (ID) that is not easily guessed through brute force is essential to deter several types of session attacks. By knowing the session ID, an attacker can hijack a user... |
| V-214273 ||High ||The Apache 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-214271 ||High ||The account used to run the Apache web server must not have a valid login shell and password defined. ||During installation of the Apache web server software, accounts are created for the Apache web server to operate properly. The accounts installed can have either no password installed or a default... |
| V-214245 ||Medium ||The Apache web server must have Web Distributed Authoring (WebDAV) disabled. ||A web server can be installed with functionality that, by its nature, is not secure. WebDAV is an extension to the HTTP protocol that, when developed, was meant to allow users to create, change,... |
| V-214228 ||Medium ||The Apache web server must limit the number of allowed simultaneous session requests. ||Apache web server management includes the ability to control the number of users and user sessions that utilize an Apache web server. Limiting the number of allowed users and sessions per user is... |
| V-214243 ||Medium ||The Apache web server must have resource mappings set to disable the serving of certain file types. ||Resource mapping is the process of tying a particular file type to a process in the web server that can serve that type of file to a requesting client and to identify which file types are not to... |
| V-214240 ||Medium ||The Apache web server must only contain services and functions necessary for operation. ||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... |
| V-214238 ||Medium ||Expansion modules must be fully reviewed, tested, and signed before they can exist on a production Apache web server. ||In the case of a production web server, areas for content development and testing will not exist, as this type of content is only permissible on a development website. The process of developing on... |
| V-214268 ||Medium ||Cookies exchanged between the Apache web server and the client, such as session cookies, 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... |
| V-214269 ||Medium ||The Apache web server must remove all export ciphers to protect the confidentiality and integrity of transmitted information. ||During the initial setup of a Transport Layer Security (TLS) connection to the Apache web server, the client sends a list of supported cipher suites in order of preference. The Apache web server... |
| V-214260 ||Medium ||The Apache web server must be configured to immediately disconnect or disable remote access to the hosted applications. ||During an attack on the Apache web server or any of the hosted applications, the System Administrator (SA) may need to disconnect or disable access by users to stop the attack.
The Apache web... |
| V-214249 ||Medium ||The Apache web server must separate the hosted applications from hosted Apache web server management functionality. ||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,... |
| V-214246 ||Medium ||The Apache web server must be configured to use a specified IP address and port. ||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... |
| V-214247 ||Medium ||Apache web server accounts accessing the directory tree, the shell, or other operating system functions and utilities must only be administrative accounts. ||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-214244 ||Medium ||The Apache web server must allow the mappings to unused and vulnerable scripts to be removed. ||Scripts allow server-side processing on behalf of the hosted application user or as processes needed in the implementation of hosted applications. Removing scripts not needed for application... |
| V-214263 ||Medium ||The Apache web server must not impede the ability to write specified log record content to an audit log server. ||Writing events to a centralized management audit system offers many benefits to the enterprise over having dispersed logs. Centralized management of audit records and logs provides for efficiency... |
| V-214264 ||Medium ||The Apache web server must be configured to integrate with an organizations security infrastructure. ||A web server will typically use logging mechanisms for maintaining a historical log of activity that occurs within a hosted application. This information can then be used for diagnostic purposes,... |
| V-214229 ||Medium ||The Apache web server must perform server-side session management. ||Session management is the practice of protecting the bulk of the user authorization and identity information. This data can be stored on the client system or on the server.
When the session... |
| V-214266 ||Medium ||The Apache web server must prohibit or restrict the use of nonsecure or unnecessary ports, protocols, modules, and/or services. ||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.
| V-214241 ||Medium ||The Apache web server must not be a proxy server. ||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 will also proxy... |
| V-214239 ||Medium ||The Apache web server must not perform user management for hosted applications. ||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... |
| V-214265 ||Medium ||The Apache web server must generate log records that can be mapped to Coordinated Universal Time (UTC) or Greenwich Mean Time (GMT) which are stamped at a minimum granularity of one second. ||If time stamps are not consistently applied and there is no common time reference, it is difficult to perform forensic analysis across multiple devices and log records.
Time stamps generated by... |
| V-214256 ||Medium ||Warning and error messages displayed to clients must be modified to minimize the identity of the Apache web server, patches, loaded modules, and directory paths. ||Information needed by an attacker to begin looking for possible vulnerabilities in a web server includes any information about the web server, backend systems being accessed, and plug-ins or... |
| V-214237 ||Medium ||The log data and records from the Apache web server must be backed up onto a different system or media. ||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 the web server is... |
| V-214236 ||Medium ||The log information from the Apache web server must be protected from unauthorized modification or deletion. ||Log data is essential in the investigation of events. If log data were to become compromised, competent forensic analysis and discovery of the true source of potentially malicious system activity... |
| V-214261 ||Medium ||Non-privileged accounts on the hosting system must only access Apache web server security-relevant information and functions through a distinct administrative account. ||By separating Apache web server security functions from non-privileged users, roles can be developed that can then be used to administer the Apache web server. Forcing users to change from a... |
| V-214235 ||Medium ||The Apache web server log files must only be accessible by privileged users. ||Log data is essential in the investigation of events. If log data were to become compromised, competent forensic analysis and discovery of the true source of potentially malicious system activity... |
| V-214234 ||Medium ||The Apache web server must use a logging mechanism that is configured to alert the Information System Security Officer (ISSO) and System Administrator (SA) in the event of a processing failure. ||Reviewing log data allows an investigator to recreate the path of an attacker and to capture forensic data for later use. Log data is also essential to SAs in their daily administrative duties on... |
| V-214233 ||Medium ||An Apache web server, behind a load balancer or proxy server, must produce log records containing the client IP information as the source and destination and not the load balancer or proxy IP information with each event. ||Apache 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... |
| V-214231 ||Medium ||The Apache web server must have system logging enabled. ||The server error logs are invaluable because they can also be used to identify potential problems and enable proactive remediation. Log data can reveal anomalous behavior such as “not found” or... |
| V-214232 ||Medium ||The Apache web server must generate, at a minimum, log records for system startup and shutdown, system access, and system authentication events. ||Log records can be generated from various components within the Apache web server (e.g., httpd, plug-ins to external backends, etc.). From a web server perspective, certain specific Apache web... |
| V-214251 ||Medium ||Cookies exchanged between the Apache web server and client, such as session cookies, must have security settings that disallow cookie access outside the originating Apache web server and hosted application. ||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... |
| V-214250 ||Medium ||The Apache web server must invalidate session identifiers upon hosted application user logout or other session termination. ||Captured sessions can be reused in "replay" attacks. This requirement limits the ability of adversaries from capturing and continuing to employ previously valid session IDs.
Session IDs are... |
| V-214252 ||Medium ||The Apache web server must generate a session ID long enough that it cannot be guessed through brute force. ||Generating a session identifier (ID) that is not easily guessed through brute force is essential to deter several types of session attacks. By knowing the session ID, an attacker can hijack a user... |
| V-214255 ||Medium ||The Apache web server must be tuned to handle the operational requirements of the hosted application. ||A denial of service (DoS) can occur when the Apache web server is so overwhelmed that it can no longer respond to additional requests. A web server not properly tuned may become overwhelmed and... |
| V-214254 ||Medium ||The Apache web server must be built to fail to a known safe state if system initialization fails, shutdown fails, or aborts fail. ||Determining a safe state for failure and weighing that against a potential denial of service for users depends on what type of application the web server is hosting. For an application presenting... |
| V-214257 ||Medium ||Debugging and trace information used to diagnose the Apache web server must be disabled. ||Information needed by an attacker to begin looking for possible vulnerabilities in a web server includes any information about the web server and plug-ins or modules being used.
When debugging or... |
| V-214230 ||Medium ||The Apache web server must use cryptography to protect the integrity of remote sessions. ||Data exchanged between the user and the Apache web server can range from static display data to credentials used to log on to the hosted application. Even when data appears to be static, the... |
| V-214258 ||Medium ||The Apache web server must set an inactive timeout for sessions. ||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... |
| V-214270 ||Medium ||The Apache web server must install security-relevant software updates within the configured time period directed by an authoritative source (e.g., IAVM, CTOs, DTMs, and STIGs). ||Security flaws with software applications are discovered daily. Vendors are constantly updating and patching their products to address newly discovered security vulnerabilities. Organizations... |
| V-214275 ||Medium ||HTTP request methods must be limited. ||The HTTP 1.1 protocol supports several request methods that are rarely used and potentially high risk. For example, methods such as PUT and DELETE are rarely used and should be disabled in keeping... |
| V-214274 ||Medium ||The Apache web server 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 website using the web server software. That is, in addition to allowing or denying all access rights, a rule... |
| V-214259 ||Medium ||The Apache web server must restrict inbound connections from nonsecure zones. ||Remote access to the Apache 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... |
| V-214267 ||Medium ||The Apache web server must be protected from being stopped by a non-privileged user. ||An attacker has at least two reasons to stop a web server. The first is to cause a denial of service (DoS), and the second is to put in place changes the attacker made to the web server... |
| V-214262 ||Medium ||The Apache web server must use a logging mechanism that is configured to allocate log record storage capacity large enough to accommodate the logging requirements of the Apache web server. ||To make certain that the logging mechanism used by the web server has sufficient storage capacity in which to write the logs, the logging mechanism needs to be able to allocate log record storage... |
| V-214272 ||Low ||The Apache web server must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. ||Configuring the Apache web server to implement organization-wide security implementation guides and security checklists guarantees compliance with federal standards and establishes a common... |