Security and Starburst Enterprise #

Starburst Enterprise platform (SEP) is a fully supported, production-tested and enterprise-grade distribution of open source Trino.

Private deployment #

SEP is deployed entirely within an environment controlled by the customer. This allows you to apply any layers of security based on your unique organizational policies and risk tolerance. This also means that any data sources are completely under your control and you can take any security measures desired to control access from SEP to the data sources. Starburst supports integration with numerous authentication and authorizations and other security related features. Learn more about all these in the security section of the reference documentation.

Data sources and transfer #

Since SEP and all data sources are completely within your systems, Starburst does not have any access. Telemetry data about your usage is automatically submitted to Starburst using an end-to-end encrypted connection, but can also be submitted manually.

Your consent is requested, if data is transferred to Starburst as part of a support request, Because it is not required for the service to operate, generally this transaction is classified as a “causal and incidental” transfer of data.

Data security #

You can configure SEP to use encryption (TLS/SSL) for all data in transit and at rest. The connections include client tool connections to SEP, cluster internal communication, and access to the configured data sources. No data is stored in SEP. The desired configuration must be implemented and managed by you.

Releases #

Starburst follows a quarterly release process for the LTS (Long Term Support) version and we patch these LTS versions regularly. These patches include security and bug fixes, and each patch release is assessed and reviewed by a core review board prior to the work being executed.

New releases and patches are communicated to customers via our account team and are publicly available on our reference documentation.