CloudWiki
Rules
Critical

Ensure there is no unrestricted inbound access to TCP port 7474 (Neo4j)

Security & Compliance
No items found.
Description

Ensure there is no unrestricted inbound access to TCP port 7474 (Neo4j) is a security best practice that involves blocking all external traffic to TCP port 7474, which is used by the Neo4j database management system. This port is the default for Neo4j's web administration interface, and it is used to manage the database and access its features via a web browser. Allowing unrestricted inbound access to this port can pose a serious security risk, as it could enable attackers to gain unauthorized access to sensitive data, perform database modifications or execute arbitrary code. Therefore, it is essential to restrict inbound access to only authorized sources or, if possible, disable external access to this port altogether.

Remediation

To remediate the issue of unrestricted inbound access to TCP port 7474 (Neo4j), follow these steps:

  1. Identify the security group(s) associated with the affected instances that have unrestricted inbound access to TCP port 7474.
  2. Modify the inbound rules of the associated security group(s) to limit access to TCP port 7474 only to the necessary IP addresses or ranges.
  3. If necessary, create a new security group with the appropriate inbound rules and associate it with the affected instances.
  4. Test the changes to ensure that the necessary traffic is allowed and unwanted traffic is blocked.
  5. Review the security group rules on a regular basis to ensure that they remain up-to-date and do not allow any unnecessary traffic.
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.