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 3 hours ago
Powered by Pylon
© 2026 Beacon Cloud Solutions, Inc. All rights reserved.
← Back to Redis Enterprise 6.x Security Technical Implementation Guide

V-251224

CAT II (Medium)

Redis Enterprise DBMS must prohibit the use of cached authenticators after an organization-defined time period.

Rule ID

SV-251224r961521_rule

STIG

Redis Enterprise 6.x Security Technical Implementation Guide

Version

V2R2

CCIs

CCI-002007

Discussion

If cached authentication information is out of date, the validity of the authentication information may be questionable. For more information on configuring time out periods on Redis Enterprise refer to: https://docs.redislabs.com/latest/rs/administering/access-control/

Check Content

Interview the system administrator to determine what, if any, the organizational policy is for cached authentication. By default, Redis Enterprise terminates authenticators after a user logs or times out.

To view the current time out period for authentication, log in to the RHEL server that the Redis Enterprise database is hosted on as an admin user.
1. Type: rladmin
2. Once rladmin is started, type: info cluster  

Check documentation to verify that organizationally defined limits, if any, have been set. Compare documentation to actual settings found on the DB. 

If the settings do not match the documentation, this is a finding.

Fix Text

Configure Redis Enterprise settings to meet organizationally defined requirements. To configure the time out period, refer to Redis Enterprise Documentation: 

To set time out period for authentication, log in to the RHEL server that the Redis Enterprise database is hosted on as an admin user. Escalate to root privileges.
1. Type: rladmin
2. Once rladmin is started, type:  cluster config cm_session_timeout_minutes <value_to_enter>

By default, the timeout is set to 15 minutes.