| V-214321 | | The Apache web server must provide install options to exclude the installation of documentation, sample code, example applications, and tutorials. | Web server documentation, sample code, example applications, and tutorials may be an exploitable threat to a web server because this type of code has ... |
| V-214322 | | Apache web server application directories, libraries, and configuration files must only be accessible to privileged users. | When accounts used for web server features such as documentation, sample code, example applications, tutorials, utilities, and services are created ev... |
| V-214357 | | All accounts installed with the Apache web server software and tools must have passwords assigned and default passwords changed. | During installation of the Apache web server software, accounts are created for the Apache web server to operate properly. The accounts installed can ... |
| V-214359 | | 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 t... |
| V-214306 | | 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 num... |
| V-214307 | | 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. Storing of this data can occur on the cl... |
| V-214308 | | The Apache web server must use encryption strength in accordance with the categorization of data hosted by the Apache web server when remote connections are provided. | The Apache web server has several remote communications channels. Examples are user requests via http/https, communication to a backend database, and ... |
| V-214309 | | System logging must be enabled. | The server error logs are invaluable because they can also be used to identify potential problems and enable proactive remediation. Log data can revea... |
| V-214310 | | 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 serve... |
| V-214311 | | The Apache web server must produce log records containing sufficient information to establish what type of events occurred. | Web server logging capability is critical for accurate forensic analysis. Without sufficient and accurate information, a correct replay of the events ... |
| V-214312 | | 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 ... |
| V-214313 | | The Apache web server must use a logging mechanism that is configured to alert the (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 t... |
| V-214314 | | 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 so... |
| V-214315 | | The log information from the Apache web server must be protected from unauthorized deletion and modification. | Log data is essential in the investigation of events. The accuracy of the information is always pertinent. Information that is not accurate does not h... |
| V-214316 | | 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 ... |
| V-214318 | | 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 man... |
| V-214319 | | 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 sy... |
| V-214320 | | 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 multiuse servers are not recommended. Sc... |
| V-214323 | | 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... |
| V-214324 | | 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. Rem... |
| V-214325 | | The Apache web server must have Web Distributed Authoring (WebDAV) disabled. | A web server can be installed with functionality that, just by its nature, is not secure. WebDAV is an extension to the HTTP protocol that, when devel... |
| V-214326 | | 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, t... |
| V-214327 | | The Apache web server must encrypt passwords during transmission. | Data used to authenticate, especially passwords, needs to be protected at all times, and encryption is the standard method for protecting authenticati... |
| V-214328 | | The Apache web server must perform RFC 5280-compliant certification path validation. | A certificate's certification path is the path from the end entity certificate to a trusted root certification authority (CA). Certification path vali... |
| V-214329 | | 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 acco... |
| V-214330 | | 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. T... |
| V-214331 | | 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 previo... |
| V-214332 | | 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 c... |
| V-214333 | | The Apache web server must accept only system-generated session identifiers. | 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 sessi... |
| V-214334 | | The Apache web server must generate unique session identifiers that cannot be reliably reproduced. | Communication between a client and the Apache web server is done using the HTTP protocol, but HTTP is a stateless protocol. To maintain a connection o... |
| V-214335 | | The Apache web server must generate unique session identifiers with definable entropy. | Generating a session identifier (ID) that is not easily guessed through brute force is essential to deter several types of session attacks. By knowing... |
| V-214336 | | 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 DoS for users depends on what type of application the web server is hosting... |
| V-214337 | | The Apache web server document directory must be in a separate partition from the Apache web servers system files. | A web server is used to deliver content on the request of a client. The content delivered to a client must be controlled, allowing only hosted applica... |
| V-214338 | | The Apache web server must restrict the ability of users to launch denial-of-service (DoS) attacks against other information systems or networks. | Apache web server can limit the ability of the web server being used in a DoS attack through several methods. The methods employed will depend upon th... |
| V-214339 | | 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... |
| V-214340 | | 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... |
| V-214341 | | The Apache web server must set an absolute 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 applicat... |
| V-214342 | | The Apache web server must set an inactive timeout for completing the TLS handshake | Leaving sessions open indefinitely is a major security risk. An attacker can easily use an already authenticated session to access the hosted applicat... |
| V-214343 | | 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 ... |
| V-214344 | | 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 may need to disconnect or disable access by user... |
| V-214345 | | 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 we... |
| V-214346 | | An Apache web server that is part of a web server cluster must route all remote management through a centrally managed access control point. | A web server cluster is a group of independent Apache web servers that are managed as a single system for higher availability, easier manageability, a... |
| V-214347 | | 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 ne... |
| V-214348 | | 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 a... |
| V-214349 | | The Apache web server must be configurable 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 informat... |
| V-214350 | | The Apache web server must use a logging mechanism that is configured to provide a warning to the Information System Security Officer (ISSO) and System Administrator (SA) when allocated record storage volume reaches 75 percent of maximum log record storage capacity. | It is critical for the appropriate personnel to be aware if a system is at risk of failing to process logs as required. Log processing failures includ... |
| V-214351 | | The Apache web server must generate log records that can be mapped to Coordinated Universal Time (UTC) or Greenwich Mean Time (GMT) with 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 device... |
| V-214352 | | The Apache web server must only accept client certificates issued by DoD PKI or DoD-approved PKI Certification Authorities (CAs). | Non-DoD-approved PKIs have not been evaluated to ensure they have security controls and identity vetting procedures in place that are sufficient for D... |
| V-214353 | | 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 ... |
| V-214354 | | 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 no... |
| V-214355 | | The Apache web server cookies, such as session cookies, sent to the client using SSL/TLS must not be compressed. | A cookie is used when a web server needs to share data with the client's browser. The data is often used to remember the client when the client return... |
| V-214356 | | 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 discovere... |
| V-214360 | | The Apache web server must alert the ISSO and SA (at a minimum) in the event of an audit processing failure. | It is critical for the appropriate personnel to be aware if a system is at risk of failing to process audit logs as required. Without this notificatio... |
| V-214358 | | 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 fed... |
