V-251241

Discussion

Failure to a known state can address safety or security in accordance with the mission/business needs of the organization. Failure to a known secure state helps prevent a loss of confidentiality, integrity, or availability in the event of a failure of the information system or a component of the system. Preserving information system state information helps to facilitate system restart and return to the operational mode of the organization with less disruption of mission/business processes. Since it is usually not possible to test this capability in a production environment, systems should either be validated in a testing environment or prior to installation. This requirement is usually a function of the design of the IDPS component. Compliance can be verified by acceptance/validation processes or vendor attestation. Additional information can be found at: https://docs.redislabs.com/latest/rs/administering/troubleshooting/cluster-recovery/

Check Content

In the Redis Enterprise web UI, select settings and then alerts.

Verify the alerts documented by the ISSO/ISSM  are checked.

If required alerts are not checked, this is a finding.

In the Redis Enterprise web UI, select databases, then select the individual databases.

For each database, select configuration.

Verify that "Persistence", "Periodic backup", and "Alerts" are all configured as organizationally defined and documented by the ISSO or ISSM. 

Verify that organizationally defined path for the centralized log server is also applied and configured external to the database.

If any of these items are not configured as documented, this is a finding.