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-251208

CAT II (Medium)

Redis Enterprise DBMS must prohibit user installation of logic modules (stored procedures, functions, triggers, views, etc.) without explicit privileged status.

Rule ID

SV-251208r1018617_rule

STIG

Redis Enterprise 6.x Security Technical Implementation Guide

Version

V2R2

CCIs

CCI-003980CCI-001812

Discussion

Redis Enterprise permits the installation of logic modules through a control plane layer to the database, which requires privilege access to the control plane. This is provisioned for support during database runtime by a user with permissions to create a database. The ability to load modules directly within the database is not supported in Redis Enterprise; however, it is supported in open-source Redis.

Check Content

Modules may be added to the Redis Enterprise control plane (adminUI) by navigating to the settings tab and then modules. Only admin users can view the settings tab.

To verify that users without explicit privileged status are not able to install modules, do the following:
1. Log in to the Redis Enterprise control plane (adminUI) with a user with administrative privileges.
2. Navigate to the access control tab.
3. Verify that only organizationally defined users have the appropriate privileges.

If a user is not assigned appropriate permissions, this is a finding.

Fix Text

To ensure a regular user is unable to perform updates:
1. Log in to the Redis Enterprise control plane.
2. Navigate to the access controls tab.
3. In the users section, review each users role to ensure they are assigned the appropriate permissions.
4. If a user is not assigned appropriate permissions, ensure they are moved to an appropriate role.