STIGhubSTIGhub
STIGsRMF ControlsCompare

STIGhub

A free tool to search and browse the entire DISA STIG library. Saves up to 75% in security compliance research time.

Navigation

  • Browse STIGs
  • Search
  • RMF Controls
  • Compare Versions

Resources

  • About
  • Release Notes
  • VPAT
  • DISA STIG Library
STIGs updated 2 hours ago
Powered by Pylon
© 2026 Beacon Cloud Solutions, Inc. All rights reserved.
← Back to IBM WebSphere Traditional V9.x Security Technical Implementation Guide

V-255872

CAT II (Medium)

The WebSphere Application Server must prohibit the use of cached authenticators after an organization-defined time period.

Rule ID

SV-255872r961521_rule

STIG

IBM WebSphere Traditional V9.x Security Technical Implementation Guide

Version

V2R1

CCIs

CCI-002007

Discussion

When the application server is using PKI authentication, a local revocation cache must be stored for instances when the revocation cannot be authenticated through the network, but if cached authentication information is out of date, the validity of the authentication information may be questionable.

Check Content

Review System Security Plan documentation.

Identify the cache timeout parameters for authentication.

Standard value for admin timeout is 10 minutes; however, the ISSO may allow a case by case exception based on operational requirements.

From the admin console, navigate to Security >> Global Security >> Authentication cache settings.

If "Enable authentication cache" check box is set and "Cache timeout" is larger than the parameters specified in the security plan, this is a finding.

Fix Text

From the admin console, navigate to Security >> Global Security >> Authentication.

Click on "Authentication cache" settings.

Enter the settings for "Cache timeout" in accordance with the parameters defined in the Systems Security Plan.