Ensure there is no unrestricted inbound access to TCP port 61621 (Cassandra)

Security & Compliance

TCP port 61621 is commonly used by Apache Cassandra, an open-source NoSQL database management system. Unrestricted inbound access to this port can pose a security risk by allowing unauthorized access to the database or its sensitive information. To ensure there is no unrestricted inbound access to TCP port 61621, appropriate remediation steps should be taken.


To ensure there is no unrestricted inbound access to TCP port 61621 (Cassandra), you should take the following remediation steps:

  1. Review your firewall rules and access control lists to identify if any rules are allowing unrestricted inbound access to port 61621.
  2. Modify the firewall rules and access control lists to restrict access to only necessary IP addresses and ports. For example, you can limit access to specific IP addresses, subnets, or VPN connections.
  3. If the server is publicly accessible, consider implementing additional security measures such as two-factor authentication, SSL/TLS encryption, or a web application firewall.
  4. Regularly review and update your firewall rules and access control lists to ensure that they continue to meet your security needs and to address any new threats or vulnerabilities that may arise.
  5. Monitor your network traffic and logs for any suspicious activity related to port 61621 and investigate any anomalies promptly.

It's important to note that securing port 61621 alone may not be sufficient to protect your Cassandra cluster. Other security measures, such as limiting administrative access, implementing authentication and authorization controls, and encrypting data in transit and at rest, should also be considered to ensure the security of your system.

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.