About security in Tiger Cloud

TigerData implements a variety of secure software engineering practices in TimescaleDB, including code static analysis for security hardening, automated scanning for dependency vulnerabilities, and code security reviews. Additionally, TigerData has developed the https://github.com/timescale/pgspot open-source extension that we use to identify security issues with PostgreSQL extensions. This has helped tighten our security posture. TigerData products do not have any identified weaknesses.

This page lists the additional things we do to ensure operational security and to lock down Tiger Cloud services. To see our security features at a glance, see TigerData Security.

Your data on Tiger Cloud is encrypted both in transit and at rest. Both active databases and backups are encrypted.

Tiger Cloud uses AWS as its cloud provider, with all the security that AWS provides. Data encryption uses the industry-standard AES-256 algorithm. Cryptographic keys are managed by AWS Key Management Service (AWS KMS). Keys are never stored in plaintext.

For more information about AWS security, see the AWS documentation on security in Amazon Elastic Compute Cloud and Elastic Block Storage.

Customer access to Tiger Cloud services is only provided over TLS-encrypted connections. There is no option to use unencrypted plaintext connections.

When using VPC peering, no public Internet-based access is provided to the service. Service addresses are published in public DNS, but they can only be connected to from the customer's peered VPC using private network addresses.

VPC peering only enables communication to be initiated from your Customer VPC to Tiger Cloud services running in the Tiger Cloud VPC. Tiger Cloud cannot initiate communication with your VPC. To learn how to set up VPC Peering, see Secure your Tiger Cloud services with VPC Peering and AWS PrivateLink.

You can allow only trusted IP addresses to access your Tiger Cloud services. You do this by creating IP address allow lists and attaching them to your services.

Normally all the resources required for providing Tiger Cloud services are automatically created, maintained and terminated by the Tiger Cloud infrastructure. No manual operator intervention is required.

However, the TigerData operations team has the capability to securely log in to the service virtual machines for troubleshooting purposes. These accesses are audit logged.

No customer access to the virtual machine level is provided.

Customer data privacy is of utmost importance at TigerData. By default, your data is encrypted both in transit and at rest. To do this, TigerData uses various technical mechanisms, processes, and software development lifecycle practices, to help ensure the security and privacy of your data.

TigerData complies with the European Union's General Data Protection Regulation (GDPR), and all practices are covered by our Privacy Policy and the Terms of Service. All customer data is processed in accordance with TigerData's GDPR-compliant Data Processor Addendum, which applies to all TigerData customers.

TigerData operators never access customer data, unless explicitly requested by the customer to troubleshoot a technical issue. The TigerData operations team has mandatory recurring training regarding the applicable policies.

The Tiger Cloud Enterprise plan is Health Insurance Portability and Accountability Act (HIPAA) compliant. This allows organizations to securely manage and analyze sensitive healthcare data, ensuring they meet regulatory requirements while building compliant applications.