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

Access to the Redis Enterprise control plane must be restricted.

DISA Rule

SV-251236r961095_rule

Vulnerability Number

V-251236

Group Title

SRG-APP-000211-DB-000122

Rule Version

RD6X-00-010150

Severity

CAT I

CCI(s)

• CCI-001082 - Separate user functionality, including user interface services, from system management functionality.

Weight

10

Fix Recommendation

Configure a management network defined through physical or logical means to achieve network separation. Update system documentation (SSP) and identify the documented management networks as well as the documented client networks.

Configure the administrative control plane to only be accessible via the management network.

Alternatively, ensure a firewall rule is enabled on the network layer and the administrative control plane is only available through trusted and approved IPs.

Use firewalld (the host-based firewall service) on the server to set up a whitelist of IPs that it will accept to use the control plane and REST API ports. The default for these are 8443 and 9443. Below is an example:
firewall-cmd --permanent --add-rich-rule='rule family="ipv4" source address="<Trusted IP address>" port protocol="tcp" port="8443" accept'
firewall-cmd --permanent --add-rich-rule='rule family="ipv4" source address="<Trusted IP address>" port protocol="tcp" port="9443" accept'

Restart the firewall to save the rule:
systemctl restart firewalld

Check Contents

Review system documentation (SSP) and identify the documented management networks as well as the documented client networks. A management network can be defined through physical means or logical means to achieve network separation.

Check the network interface to verify the administrative console is on a separate management network interface.

If the control plane is set up to only be accessed via a defined management network, this is not a finding.

If a management network does not exist or network separation is not established, verify the control plane can only be accessed via trusted approved machines.

Review system documentation and obtain a list of approved machines for administrator use.

Check the firewall rules on the server. An example command is:
firewall-cmd --list-all

Check for rules showing that only the trusted and approved machines have access to the ports for the control plane (default is 8443) and REST API interface (default 9443). Below is an example of the output:
rich rules:
rule family="ipv4" source address="<trusted ip>" forward-port port="8443" protocol="tcp" to-port="80"
rule family="ipv4" source address="<trusted ip>" forward-port port="9443" protocol="tcp" to-port="80"

If access is not limited using a management network, network separation such as vlans, or a firewall rule, this a finding.

Vulnerability Number

V-251236

Documentable

False

Rule Version

RD6X-00-010150

Severity Override Guidance

Review system documentation (SSP) and identify the documented management networks as well as the documented client networks. A management network can be defined through physical means or logical means to achieve network separation.

Check the network interface to verify the administrative console is on a separate management network interface.

If the control plane is set up to only be accessed via a defined management network, this is not a finding.

If a management network does not exist or network separation is not established, verify the control plane can only be accessed via trusted approved machines.

Review system documentation and obtain a list of approved machines for administrator use.

Check the firewall rules on the server. An example command is:
firewall-cmd --list-all

Check for rules showing that only the trusted and approved machines have access to the ports for the control plane (default is 8443) and REST API interface (default 9443). Below is an example of the output:
rich rules:
rule family="ipv4" source address="<trusted ip>" forward-port port="8443" protocol="tcp" to-port="80"
rule family="ipv4" source address="<trusted ip>" forward-port port="9443" protocol="tcp" to-port="80"

If access is not limited using a management network, network separation such as vlans, or a firewall rule, this a finding.

Check Content Reference

M

Target Key

5443