Ensure there is no unrestricted inbound access to TCP port 6379 (Redis)

Security & Compliance

TCP port 6379 is commonly used by Redis, an in-memory data structure store that is often used as a database, cache, and message broker. Redis uses this port for its default client-server communication protocol. If this port is left open without any restrictions, it can be accessed by anyone on the internet, leaving the system vulnerable to potential attacks such as data theft, unauthorized data modifications, and ransomware attacks.


Here are the remediation steps to ensure there is no unrestricted inbound access to TCP port 6379 (Redis):

  1. Restrict access to the Redis port to only authorized hosts or networks. This can be achieved by updating the firewall rules and access control lists.
  2. Configure Redis to require authentication for client connections. This can be done by setting a strong password in the Redis configuration file and restarting the Redis service.
  3. Encrypt Redis traffic using SSL/TLS to prevent eavesdropping and unauthorized access. This can be done by configuring Redis to use SSL/TLS certificates and updating the client applications to use SSL/TLS when connecting to Redis.
  4. Implement network monitoring to detect and alert on any unauthorized access attempts to the Redis port. This can be done using network intrusion detection systems (IDS) and security information and event management (SIEM) solutions.
  5. Keep Redis updated with the latest security patches and updates. This can be done by regularly checking for updates and applying them as soon as they become available.

By following these remediation steps, you can ensure that the Redis port is not accessible to unauthorized users, and that the Redis server is secure against potential attacks.

Enforced Resources
Note: Remediation steps provided by Lightlytics are meant to be suggestions and guidelines only. It is crucial to thoroughly verify and test any remediation steps before applying them to production environments. Each organization's infrastructure and security needs may differ, and blindly applying suggested remediation steps without proper testing could potentially cause unforeseen issues or vulnerabilities. Therefore, it is strongly recommended that you validate and customize any remediation steps to meet your organization's specific requirements and ensure that they align with your security policies and best practices.