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.

Solution

Open the <'INSTALL PATH'>confhttpd.conf file.

Set the ‘SessionMaxAge’ directive to a value of no more than ‘600’.
Add the directive if it does not exist.

Restart the Apache service.

Supportive Information

The following resource is also helpful.

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

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

References

• 800-53|SC-23(1)
• CAT|II
• CCI|CCI-001185
• Rule-ID|SV-214331r505936_rule
• STIG-ID|AS24-W1-000460
• STIG-Legacy|SV-102493
• STIG-Legacy|V-92405
• Vuln-ID|V-214331

Source

• Tenable.com/audits