The WebSphere Application Server security cookies must be set to HTTPOnly.

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-81221WBSP-AS-000190SV-95935r1_ruleCCI-001453medium
Description
Web applications use cookies to track users across requests. These cookies, while typically not sensitive in themselves, connect you to your existing state on the back end system. If an intruder were to capture one of your cookies, they could potentially use the cookie to act as you. Important Web traffic should be encrypted using SSL. This includes important cookies. In the case of WebSphere Application Server, the most important cookie is the LTPA cookie, and therefore it should be configured to be sent only over SSL.
STIGDate
IBM WebSphere Traditional V9.x Security Technical Implementation Guide2018-08-24

Related Frameworks

3 paths across 3 frameworks
NIST 800-531 mapping
  • DISA · 1 · disa_xccdf · related
  • DISA · 2025-01-23 · disa_cci_list · equivalent
NIST 800-1711 mapping
3.1.13
1.00
  • DISA · 1 · disa_xccdf · related
  • DISA · 2025-01-23 · disa_cci_list · equivalent
  • NIST · Rev 2 (Feb 2020, errata Jan 2021) · nist_800_171_app_d · equivalent
CCI1 mapping
CCI-001453
1.00
  • DISA · 1 · disa_xccdf · related

Details

Check Text (C-95935r1_chk)

From the administrative console, navigate to Security >> Global Security. Expand "Web and SIP security". Click on "Single sign-on (SSO)". If "Set security cookies to HTTPOnly" is not selected, this is a finding.

Fix Text (F-88001r1_fix)

From the administrative console, navigate to Security >> Global Security. Expand "Web and SIP security". Select "Set security cookies to HTTPOnly". Click "OK". Click "Save". Restart the DMGR and all the JVMs.