STIGQter: STIG Summary: Redis Enterprise 6.x Security Technical Implementation Guide Version: 2 Release: 2 Benchmark Date: 24 Oct 2024:

Redis Enterprise DBMS must enforce authorized access to all PKI private keys stored/used by Redis Enterprise DBMS.

DISA Rule

SV-251226r961041_rule

Vulnerability Number

V-251226

Group Title

SRG-APP-000176-DB-000068

Rule Version

RD6X-00-009200

Severity

CAT I

CCI(s)

• CCI-000186 - For public key-based authentication, enforce authorized access to the corresponding private key.

Weight

10

Fix Recommendation

Apply or modify access controls and permissions (in the file system/operating system) to tools used to view or modify where the certificates are stored. Tools must be accessible by authorized personnel only.

/etc/opt/redislabs (or wherever the organizationally defined location for certificates are stored) should have an appropriate and documented admin user and group owner and the directory should not have permissions more than 700.

To update these permissions, run the following commands:
chown redislabs:redislabs /etc/opt/redislabs
chmod 700 /etc/opt/redislabs/proxy_cert.pem

Check Contents

All keys must be stored by the host RHEL OS that Redis Enterprise resides on. On the server, look for proxy_cert.pem found in /etc/opt/redislabs. If proxy_cert.pem has file permissions that would allow unauthorized users to access it, this is a finding.

Keys can also be manipulated on the Redis Enterprise UI. RBAC prevents unauthorized users from doing this; to check:

Review organization documentation to determine which users should have administrative privileges. From there:
1. Log in to Redis Enterprise UI as a user in the administrator role.
2. Navigate to the Access Control tab.
3. Compare the documented users to the users found in the user settings on the web UI.

If any users have administrative privileges and are not documented, this is a finding.

If access to the DBMS's private key(s) is not restricted to authenticated and authorized users, this is a finding.

Vulnerability Number

V-251226

Documentable

False

Rule Version

RD6X-00-009200

Severity Override Guidance

All keys must be stored by the host RHEL OS that Redis Enterprise resides on. On the server, look for proxy_cert.pem found in /etc/opt/redislabs. If proxy_cert.pem has file permissions that would allow unauthorized users to access it, this is a finding.

Keys can also be manipulated on the Redis Enterprise UI. RBAC prevents unauthorized users from doing this; to check:

Review organization documentation to determine which users should have administrative privileges. From there:
1. Log in to Redis Enterprise UI as a user in the administrator role.
2. Navigate to the Access Control tab.
3. Compare the documented users to the users found in the user settings on the web UI.

If any users have administrative privileges and are not documented, this is a finding.

If access to the DBMS's private key(s) is not restricted to authenticated and authorized users, this is a finding.

Check Content Reference

M

Target Key

5443