This guide describes how to secure a Greenplum Database system. The guide assumes knowledge of Linux/UNIX system administration and database management systems. Familiarity with structured query language (SQL) is helpful.
NoteVMware supports PostgresSQL 9.4 until VMware Greenplum 6 is End of Support /End of Life (EOS/EOL). For the exact support period timeframes for each VMware Greenplum release, see the VMware Support Lifecycle Policy page.
ImportantVMware Greenplum is based on PostgreSQL, therefore certain commercial security scanning software, when trying to identify VMware Greenplum Database vulnerabilities, may use a PostgreSQL database profile. The reports generated by these tools can produce misleading results, and cannot be trusted as an accurate assessment of vulnerabilities that may exist in VMware Greenplum. For further assistance, or to report any specific VMware Greenplum security concerns, refer to the VMware Tanzu Security Response Center guidelines.
Because Greenplum Database is based on PostgreSQL 9.4, this guide assumes some familiarity with PostgreSQL. References to PostgreSQL documentation are provided throughout this guide for features that are similar to those in Greenplum Database.
This information is intended for system administrators responsible for administering a Greenplum Database system.
If you install any endpoint security software on your Greenplum Database hosts, such as anti-virus, data protection, network security, or other security related software, the additional CPU, IO, network or memory load can interfere with Greenplum Database operations and may affect database performance and stability.
Refer to your endpoint security vendor and perform careful testing in a non-production environment to ensure it does not have any negative impact on Greenplum Database operations.