Details

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 generated by web applications to uniquely identify an application user’s session. Unique session IDs help to reduce predictability of said identifiers. When a user logs out, or when any other session termination event occurs, the web server must terminate the user session to minimize the potential for an attacker to hijack that particular user session.

Satisfies: SRG-APP-000220-WSR-000201, SRG-APP-000295-WSR-000012

Solution

Determine the location of the ‘HTTPD_ROOT’ directory and the ‘httpd.conf’ file:

# httpd -V | egrep -i ‘httpd_root|server_config_file’
-D HTTPD_ROOT=’/etc/httpd’
-D SERVER_CONFIG_FILE=’conf/httpd.conf’

Add the following line to the ‘httpd.conf’ file:

SessionMaxAge 600

Restart Apache: apachectl restart

Supportive Information

The following resource is also helpful.

• https://dl.dod.cyber.mil/wp-content/uploads/stigs/zip/U_Apache_Server_2-4_UNIX_Y22M01_STIG.zip

This security hardening control applies to the following category of controls within NIST 800-53: Access Control, System and Communications Protection.This control applies to the following type of system Unix.

References

• 800-53|AC-12
• 800-53|SC-23(1)
• CAT|II
• CCI|CCI-001185
• CCI|CCI-002361
• Rule-ID|SV-214250r612240_rule
• STIG-ID|AS24-U1-000460
• STIG-Legacy|SV-102765
• STIG-Legacy|V-92677
• Vuln-ID|V-214250

Source

• Tenable.com/audits