CloudWiki
Rules
Get a free AWS Well-Architected Assessment ->
Critical

Ensure there is no unrestricted inbound access to TCP port 27018 (MongoDB)

Security & Compliance
Description

Ensuring that there is no unrestricted inbound access to TCP port 27018 is an important security measure to protect MongoDB from unauthorized access and potential attacks. This port is used for internal communication between members of a MongoDB replica set and if it is left open and unrestricted, it can allow attackers to gain access to sensitive data or even take control of the database.

Remediation

To ensure that there is no unrestricted inbound access to TCP port 27018 (MongoDB), you can follow these remediation steps:

  1. Identify all the systems that have TCP port 27018 open to unrestricted inbound access.
  2. Configure the firewall rules to block inbound access to TCP port 27018 from all external IP addresses or unauthorized sources.
  3. If possible, limit access to TCP port 27018 to only those IP addresses that require access. For example, you can create a whitelist of IP addresses that are allowed to access the port.
  4. Ensure that MongoDB is configured to use SSL/TLS encryption for all network traffic. This will help to secure the communication channel between the MongoDB server and the client.
  5. Regularly monitor the access logs to ensure that there are no unauthorized attempts to access the MongoDB server through TCP port 27018.

By following these steps, you can reduce the risk of unauthorized access to the MongoDB server through TCP port 27018 and prevent potential data breaches or 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.
Deploy cloud infrastructure changes with confidence. Troubleshoot faster with the complete context of your cloud environment.
GET STARTED