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

V-251230

CAT II (Medium)

Redis Enterprise DBMS must uniquely identify and authenticate non-organizational users (or processes acting on behalf of non-organizational users).

Rule ID

SV-251230r961053_rule

STIG

Redis Enterprise 6.x Security Technical Implementation Guide

Version

V2R2

CCIs

CCI-000804

Discussion

Non-organizational users include all information system users other than organizational users, which include organizational employees or individuals the organization deems to have equivalent status of employees (e.g., contractors, guest researchers, individuals from allied nations). Non-organizational users must be uniquely identified and authenticated for all accesses other than those accesses explicitly identified and documented by the organization when related to the use of anonymous access, such as accessing a web server. Accordingly, a risk assessment is used in determining the authentication needs of the organization. Scalability, practicality, and security are simultaneously considered in balancing the need to ensure ease of use for access to federal information and information systems with the need to protect and adequately mitigate risk to organizational operations, organizational assets, individuals, other organizations, and the nation.

Check Content

Redis Enterprise databases can be configured and set to deny by default posture. Access is granted when the database is configured and can be granted by admins at a later time. Verify in the database configuration that the default user is disabled. This would force non-organizational users to authenticate with a username and password similar to any organizationally defined user. 

In web UI:
1. Log in to Redis Enterprise as an admin user.
2. Select the Database tab.
3. Select the Configuration subtab.
4. Confirm "Default database access" reads "nopass" and is "Inactive".

If default database access is active and there is no password set, this is a finding.

Fix Text

When adding user access to the database, either during initial creation or at a later time, admins must establish a unique username and password for all users and the default user account must be disabled.

In web UI:
1. Log in to Redis Enterprise as an admin user.
2. Select the Database tab.
3. Select the Configuration subtab.
4. Select "Edit".
5. Ensure that "Default database access" is unchecked.