Apache Server 2.4 UNIX Server Security Technical Implementation Guide
Rules, Groups, and Values defined within the XCCDF Benchmark
-
SRG-APP-000141-WSR-000082
Group -
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 operat...Rule Medium Severity -
SRG-APP-000141-WSR-000085
Group -
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, an...Rule Medium Severity -
SRG-APP-000142-WSR-000089
Group -
SRG-APP-000211-WSR-000030
Group -
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. The...Rule Medium Severity -
SRG-APP-000211-WSR-000031
Group -
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 non-pr...Rule High Severity -
SRG-APP-000211-WSR-000129
Group -
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, se...Rule Medium Severity -
SRG-APP-000220-WSR-000201
Group -
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 tokens...Rule Medium Severity -
SRG-APP-000223-WSR-000011
Group -
SRG-APP-000224-WSR-000137
Group -
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 ...Rule Medium Severity -
SRG-APP-000224-WSR-000138
Group -
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 ...Rule High Severity -
SRG-APP-000225-WSR-000140
Group -
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 p...Rule Medium Severity
Node 2
The content of the drawer really is up to you. It could have form fields, definition lists, text lists, labels, charts, progress bars, etc. Spacing recommendation is 24px margins. You can put tabs in here, and can also make the drawer scrollable.