Checked | Name | Title |
---|
☐ | SV-214306r505936_rule | The Apache web server must limit the number of allowed simultaneous session requests. |
☐ | SV-214307r505936_rule | The Apache web server must perform server-side session management. |
☐ | SV-214308r505936_rule | 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. |
☐ | SV-214309r505936_rule | System logging must be enabled. |
☐ | SV-214310r505936_rule | The Apache web server must generate, at a minimum, log records for system startup and shutdown, system access, and system authentication events. |
☐ | SV-214311r505936_rule | The Apache web server must produce log records containing sufficient information to establish what type of events occurred. |
☐ | SV-214312r505936_rule | 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. |
☐ | SV-214313r505936_rule | 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. |
☐ | SV-214314r505936_rule | The Apache web server log files must only be accessible by privileged users. |
☐ | SV-214315r505936_rule | The log information from the Apache web server must be protected from unauthorized deletion and modification. |
☐ | SV-214316r505936_rule | The log data and records from the Apache web server must be backed up onto a different system or media. |
☐ | SV-214318r505936_rule | The Apache web server must not perform user management for hosted applications. |
☐ | SV-214319r505936_rule | The Apache web server must only contain services and functions necessary for operation. |
☐ | SV-214320r505936_rule | The Apache web server must not be a proxy server. |
☐ | SV-214321r505936_rule | The Apache web server must provide install options to exclude the installation of documentation, sample code, example applications, and tutorials. |
☐ | SV-214322r505936_rule | Apache web server application directories, libraries, and configuration files must only be accessible to privileged users. |
☐ | SV-214323r505936_rule | The Apache web server must have resource mappings set to disable the serving of certain file types. |
☐ | SV-214324r505936_rule | The Apache web server must allow the mappings to unused and vulnerable scripts to be removed. |
☐ | SV-214325r505936_rule | The Apache web server must have Web Distributed Authoring (WebDAV) disabled. |
☐ | SV-214326r505936_rule | The Apache web server must be configured to use a specified IP address and port. |
☐ | SV-214327r505936_rule | The Apache web server must encrypt passwords during transmission. |
☐ | SV-214328r505936_rule | The Apache web server must perform RFC 5280-compliant certification path validation. |
☐ | SV-214329r505936_rule | Apache web server accounts accessing the directory tree, the shell, or other operating system functions and utilities must only be administrative accounts. |
☐ | SV-214330r505936_rule | The Apache web server must separate the hosted applications from hosted Apache web server management functionality. |
☐ | SV-214331r505936_rule | The Apache web server must invalidate session identifiers upon hosted application user logout or other session termination. |
☐ | SV-214332r505936_rule | 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. |
☐ | SV-214333r505936_rule | The Apache web server must accept only system-generated session identifiers. |
☐ | SV-214334r505936_rule | The Apache web server must generate unique session identifiers that cannot be reliably reproduced. |
☐ | SV-214335r505936_rule | The Apache web server must generate unique session identifiers with definable entropy. |
☐ | SV-214336r505936_rule | The Apache web server must be built to fail to a known safe state if system initialization fails, shutdown fails, or aborts fail. |
☐ | SV-214337r505936_rule | The Apache web server document directory must be in a separate partition from the Apache web servers system files. |
☐ | SV-214338r505936_rule | The Apache web server must restrict the ability of users to launch denial-of-service (DoS) attacks against other information systems or networks. |
☐ | SV-214339r505936_rule | 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. |
☐ | SV-214340r505936_rule | Debugging and trace information used to diagnose the Apache web server must be disabled. |
☐ | SV-214341r557320_rule | The Apache web server must set an absolute timeout for sessions. |
☐ | SV-214342r505936_rule | The Apache web server must set an inactive timeout for completing the TLS handshake |
☐ | SV-214343r505936_rule | The Apache web server must restrict inbound connections from nonsecure zones. |
☐ | SV-214344r505936_rule | The Apache web server must be configured to immediately disconnect or disable remote access to the hosted applications. |
☐ | SV-214345r505936_rule | Non-privileged accounts on the hosting system must only access Apache web server security-relevant information and functions through a distinct administrative account. |
☐ | SV-214346r505936_rule | An Apache web server that is part of a web server cluster must route all remote management through a centrally managed access control point. |
☐ | SV-214347r505936_rule | 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. |
☐ | SV-214348r505936_rule | The Apache web server must not impede the ability to write specified log record content to an audit log server. |
☐ | SV-214349r505936_rule | The Apache web server must be configurable to integrate with an organizations security infrastructure. |
☐ | SV-214350r505936_rule | 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% of maximum log record storage capacity. |
☐ | SV-214351r505936_rule | 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. |
☐ | SV-214352r505936_rule | The Apache web server must only accept client certificates issued by DoD PKI or DoD-approved PKI Certification Authorities (CAs). |
☐ | SV-214353r505936_rule | The Apache web server must be protected from being stopped by a non-privileged user. |
☐ | SV-214354r505936_rule | The Apache web server must be tuned to handle the operational requirements of the hosted application. |
☐ | SV-214355r505936_rule | The Apache web server cookies, such as session cookies, sent to the client using SSL/TLS must not be compressed. |
☐ | SV-214356r505936_rule | 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). |
☐ | SV-214357r505936_rule | All accounts installed with the Apache web server software and tools must have passwords assigned and default passwords changed. |
☐ | SV-214358r505936_rule | 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. |
☐ | SV-214359r505936_rule | The Apache web server software must be a vendor-supported version. |
☐ | SV-214360r505936_rule | The Apache web server must alert the ISSO and SA (at a minimum) in the event of an audit processing failure. |