Ensure there is no unrestricted inbound access to TCP port 2379 (etcd)

Security & Compliance
No items found.

TCP port 2379 is used by etcd, a distributed key-value store that is commonly used for storing configuration data in cloud-native applications. To ensure the security of an etcd cluster, it is important to restrict access to this port to only authorized users and systems.Unrestricted inbound access to TCP port 2379 can potentially allow attackers to read, modify, or delete critical configuration data stored in etcd, which can have severe consequences for the application or system that depends on it.‍


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

  1. Identify all systems that require access to the etcd cluster through TCP port 2379.
  2. Implement firewall rules and access control lists (ACLs) to block all incoming traffic to port 2379, except for authorized hosts or IP addresses that require access to the etcd cluster.
  3. Use a network security group (NSG) to filter traffic to the etcd cluster's network interface, and configure it to only allow traffic from authorized sources.
  4. Enable Transport Layer Security (TLS) encryption for all communication to and from the etcd cluster to protect against eavesdropping and man-in-the-middle attacks.
  5. Regularly monitor the network traffic to the etcd cluster to detect any unauthorized attempts to access the TCP port 2379.
  6. Regularly review and update the firewall rules, access control lists, and network security groups to ensure they are up to date and configured correctly.

By following these remediation steps, you can ensure that the etcd cluster is secured and that access to the TCP port 2379 is restricted only to authorized sources, reducing the risk of unauthorized access, data loss, and other security incidents.

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.