STIGhubSTIGhub
STIGsSearchCompare

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
  • Compare Versions

Resources

  • About
  • Release Notes
  • VPAT
  • DISA STIG Library
STIGs updated 3 hours ago
Powered by Pylon
© 2026 Beacon Cloud Solutions, Inc. All rights reserved.
← Back to CA API Gateway ALG Security Technical Implementation Guide

V-237395

CAT II (Medium)

The CA API Gateway must prohibit the use of cached authenticators after an organization-defined time period.

Rule ID

SV-237395r831420_rule

STIG

CA API Gateway ALG Security Technical Implementation Guide

Version

V1R3

CCIs

CCI-002007

Discussion

If the cached authenticator information is out of date, the validity of the authentication information may be questionable. This requirement applies to all ALGs that may cache user authenticators for use throughout a session. This requirement also applies to ALGs that provide user authentication intermediary services (e.g., authentication gateway or TLS gateway). This does not apply to authentication for the purpose of configuring the device itself (device management). The CA API Gateway must be configured to use an organization-defined value for determining the expiration of cached data from an identity provider or third party, such as a SAML Token Service.

Check Content

Open the CA API Gateway - Policy Manager and select the "Identity Provider" tab. 

Verify the "Cache Size" and "Cache Maximum Age" are set in accordance with organization-defined requirements. 

If the values are not set or are not set in accordance with organizational requirements, this is a finding.

Fix Text

Open the CA API Gateway - Policy Manager and select the "Identity Provider" tab. 

Update the "Cache Size" and "Cache Maximum Age" in accordance with organization-defined requirements.