Skip Headers
Oracle® Enterprise Manager Cloud Control Oracle Database Compliance Standards
12c Release 4 (12.1.0.4)

E36074-03
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

5 Oracle Listener Compliance Standards

These are the compliance rules for the Oracle Listener compliance standards. The compliance standards are:

5.1 Basic Security Configuration for Oracle Listener

The compliance rules for the Basic Security Configuration for Oracle Listener compliance standard follow.

5.1.1 Listener Trace Directory Permission

Description: Ensures that the listener trace directory does not have public read/write permissions.

Severity: Critical

Rationale: Allowing access to the trace directory can expose it to public scrutiny with possible security implications

5.1.2 Listener Trace File Permission (Windows)

Description: Ensures that the listener trace file is not accessible to public.

Severity: Critical

Rationale: Allowing access to the trace files can expose them to public scrutiny with possible security implications.

5.1.3 Listener Trace Directory Permission (Windows)

Description: Ensures that the listener trace directory does not have public read/write permissions.

Severity: Critical

Rationale: Allowing access to the trace directory can expose them to public scrutiny with possible security implications.

5.1.4 Listener Logfile Permission

Description: Ensures that the listener log file cannot be read by or written to by public.

Severity: Critical

Rationale: The information in the log file can reveal important network and database connection details. Allowing access to the log file can expose them to public scrutiny with possible security implications.

5.1.5 Listener Trace File Permission

Description: Ensures that the listener trace file is not accessible to public.

Severity: Critical

Rationale: Allowing access to the trace files can expose them to public scrutiny with possible security implications.

5.1.6 Listener Logfile Permission (Windows)

Description: Ensures that the listener log file cannot be read by or written to by public.

Severity: Critical

Rationale: The information in the log file can reveal important network and database connection details. Allowing access to the log file can expose them to public scrutiny with possible security implications.

5.2 High Security Configuration for Oracle Listener

The compliance rules for the High Security Configuration for Oracle Listener compliance standard follow.

5.2.1 Oracle Net Tcp Valid Node Checking

Description: Ensures that tcp.validnode_checking parameter is set to yes.

Severity: Minor Warning

Rationale: Not setting valid node check can potentially allow anyone to connect to the server, including a malicious user.

5.2.2 Listener Logging Status

Description: Ensures that listener logging is enabled.

Severity: Warning

Rationale: Without listener logging attacks on the listener can go unnoticed.

5.2.3 Use of Host Name in Listener.ora

Description: Ensures that the listener host is specified as IP address and not host name in listener.ora.

Severity: Warning

Rationale: An insecure Domain Name System (DNS) Server can be taken advantage of for mounting a spoofing attack. Name server failure can result in the listener unable to resolve the host.

5.2.4 Secure Remote Listener Administration

Description: Ensures that administration requests are accepted only for TCPS or IPC.

Severity: Warning

Rationale: Limiting the transports for remote administration to TCPS and IPC reduces the risk of unauthorized access.

5.2.5 Listener Direct Administration

Description: Ensures that no runtime modifications to the listener configuration is allowed.

Severity: Critical

Rationale: An attacker who has access to a running listener can perform runtime modifications (for example, SET operations) using the lsnrctl program.

5.2.6 Listener Default Name

Description: Ensures that the default name of the listener is not used.

Severity: Warning

Rationale: Having a listener with the default name increases the risk of unauthorized access and denial of service attacks.

5.2.7 Listener Logfile Owner

Description: Ensures that the listener log file is owned by the Oracle software owner.

Severity: Critical

Rationale: The information in the log file can reveal important network and database connection details. Having a log file not owned by the Oracle software owner can expose them to public scrutiny with possible security implications.

5.2.8 Listener Trace Directory Owner

Description: Ensures that the listener trace directory is a valid directory owned by Oracle software owner.

Severity: Critical

Rationale: Having a trace directory not owned by the Oracle software owner can expose the trace files to public scrutiny with possible security implications.

5.2.9 Restrict Sqlnet.ora Permission (Windows)

Description: Ensures that the sqlnet.ora file is not accessible to public.

Severity: Critical

Rationale: If sqlnet.ora is public readable a malicious user may attempt to read this hence could lead to sensitive information getting exposed. For example, log and trace destination information of the client and server.

5.2.10 Listener.ora Permission (Windows)

Description: Ensures that the file permissions for listener.ora are restricted to the owner of Oracle software.

Severity: Critical

Rationale: If the listener.ora file is public readable, passwords may be extracted from this file. This can also lead to exposure of detailed information on the Listener, database, and application configuration. Also, if public has write permissions, a malicious user can remove any password that has been set on the listener.

5.2.11 Listener Trace File Owner

Description: Ensures that the listener trace file owner is the same as the Oracle software owner.

Severity: Critical

Rationale: Having trace files not owned by the Oracle software owner can expose them to public scrutiny with possible security implications.

5.2.12 tcp.excluded_nodes

Description: Ensures that tcp.excludeded_nodes parameter is set.

Severity: Warning

Rationale: Not setting valid node check can potentially allow anyone to connect to the server, including a malicious user.

5.2.13 Accept Only Secure Registration Request

Description: Ensures that registration requests are accepted only for TCPS or IPC.

Severity: Warning

Rationale: Not configuring SECURE_REGISTER_listener_name parameter makes listener to accept registration request for any transport of a connection.

5.2.14 Listener Password

Description: Ensures that access to listener is password protected.

Severity: Warning

Rationale: Without password protection, a user can gain access to the listener. Once someone has access to the listener, he/she can stop the listener. He/she can also set a password and prevent others from managing the listener.

5.2.15 Restrict Sqlnet.ora Permission

Description: Ensures that the sqlnet.ora file is not accessible to public.

Severity: Critical

Rationale: If sqlnet.ora is public readable a malicious user may attempt to read this hence could lead to sensitive information getting exposed. For example, log and trace destination information of the client and server.

5.2.16 Listener.ora Permission

Description: Ensures that the file permissions for listener.ora are restricted to the owner of Oracle software.

Severity: Critical

Rationale: If the listener.ora file is public readable, passwords may be extracted from this file. This can also lead to exposure of detailed information on the Listener, database, and application configuration. Also, if public has write permissions, a malicious user can remove any password that has been set on the listener.

5.2.17 Listener Inbound Connect Timeout

Description: Ensures that all incomplete inbound connections to Oracle Listener has a limited lifetime.

Severity: Warning

Rationale: This limit protects the listener from consuming and holding resources for client connection requests that do not complete. A malicious user could use this to flood the listener with requests that result in a denial of service to authorized users.

5.2.18 tcp.invited_nodes

Description: Ensures that tcp.invited_nodes parameter is set.

Severity: Warning

Rationale: Not setting valid node check can potentially allow anyone to connect to the server, including a malicious user.

5.2.19 Use Secure Transport for Administration and Registration

Description: Ensures that Administration and Registration requests are accepted only for TCPS or IPC transports

Severity: Warning

Rationale: Makes listener to accept administration and registration request for any transport of a connection.

5.2.20 Limit Loading External DLL and Libraries

Description: Ensures that the parameter EXTPROC_DLLS in listener.ora is set to ONLY.

Severity: Warning

Rationale: To achieve a higher level of security in a production environment, to restrict the DLLs that the extproc agent can load by listing them explicitly in the listener.ora file.