Details
The SECURE_REGISTER_
Rationale:
Listener configuration changes via unencrypted remote connections can result in unauthorized users sniffing control configuration information from the network.
Solution
To remediate this recommendation:
Use a text editor such as vi to set the SECURE_REGISTER_
References:
http://docs.oracle.com/database/121/NETRF/listener.htm#NETRF328
https://support.oracle.com/epmos/faces/ui/km/DocumentDisplay.jspx?id=1453883.1
https://support.oracle.com/epmos/faces/ui/km/DocumentDisplay.jspx?id=1340831.1
http://www.joxeankoret.com/download/tnspoison.pdf
Notes:
Oracle Real Application Cluster requires a different approach to fix the TNS Poisoning problem. See Oracle support note 1453883.1 for details.
Supportive Information
The following resource is also helpful.
This security hardening control applies to the following category of controls within NIST 800-53: System and Communications Protection.This control applies to the following type of system Windows.