NDB Cluster Security Issues PLUGIN_LICENSE: GPL LOAD_OPTION: ON *************************** 3. row *************************** PLUGIN_NAME: ndb_transid_mysql_connection_map PLUGIN_VERSION: 0.1 PLUGIN_STATUS: ACTIVE PLUGIN_TYPE: INFORMATION SCHEMA PLUGIN_TYPE_VERSION: 80025.0 PLUGIN_LIBRARY: NULL PLUGIN_LIBRARY_VERSION: NULL PLUGIN_AUTHOR: Oracle Corporation PLUGIN_DESCRIPTION: Map between MySQL connection ID and NDB transaction ID PLUGIN_LICENSE: GPL LOAD_OPTION: ON You can also use the  SHOW PLUGINS  statement to display this information, but the output from that statement cannot easily be filtered. See also The MySQL Plugin API, which describes where and how the information in the  PLUGINS  table is obtained. You can also query the tables in the  ndbinfo  information database for real-time data about many NDB Cluster operations. See Section 23.5.14, “ndbinfo: The NDB Cluster Information Database” . This section discusses security considerations to take into account when setting up and running NDB Cluster. In this section, we discuss basic network security issues as they relate to NDB Cluster. It is extremely important to remember that NDB Cluster “out of the box”  is not secure; you or your network administrator must take the proper steps to ensure that your cluster cannot be compromised over the network. Cluster communication protocols are inherently insecure, and no encryption or similar security measures are used in communications between nodes in the cluster. Because network speed and latency have a direct impact on the cluster’s efficiency, it is also not advisable to employ SSL or other encryption to network connections between nodes, as such schemes cause slow communications. It is also true that no authentication is used for controlling API node access to an NDB Cluster. As with encryption, the overhead of imposing authentication requirements would have an adverse impact on Cluster performance. In addition, there is no checking of the source IP address for either of the following when accessing the cluster: This means that, if there are any empty  [mysqld]  or  [api]  sections in the  config.ini  file, then any API nodes (including SQL nodes) that know the management server’s host name (or IP address) and 4601 •SQL or API nodes using “free slots”  created by empty  [mysqld]  or  [api]  sections in the  config.ini file •MySQL standard security procedures as applicable to NDB Cluster •NDB Cluster and the MySQL privilege system •Configuration issues relating to running NDB Cluster securely •NDB Cluster and network security issues Topics covered in this section include the following: 23.5.17 NDB Cluster Security Issues 23.5.17.1 NDB Cluster Security and Networking Issues