CloudWiki
Rules
Critical

Ensure there is no unrestricted inbound access to TCP port 2484 (Oracle DB SSL)

Security & Compliance
Description

TCP port 2484 is commonly used for secure communication between clients and Oracle database servers using SSL/TLS. However, allowing unrestricted inbound access to this port can expose your database to security risks such as unauthorized access, data breaches, and malicious attacks. To ensure the security of your Oracle database server, it is essential to restrict access to port 2484 to only necessary IP addresses and ports, implement additional security measures such as two-factor authentication, SSL/TLS encryption, and regular review and update your firewall rules and access control lists to address any new threats or vulnerabilities that may arise.

Remediation

To ensure there is no unrestricted inbound access to TCP port 2484 (Oracle DB SSL), 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 2484.
  2. If such rules exist, modify them to restrict access to only the 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 2484 and investigate any anomalies promptly.
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.