Best security practices for setting up databases with Zing

Keeping your data secure

Zing already has robust controls to keep your data private:

• Encrypting data at rest and in transit
• Optional two factor authentication through Google Single Sign On
• Sharing access to your data sources is limited to users with the same domain name to avoid data being shared accidentally with users outside your organization

In addition to Zing’s built-in security, we suggest the two best practices to ensure your data is as secure as possible.

1. Provide Zing read-only access (instead of full access) to your database. Zing doesn’t need write permissions and best security protocols dictate minimizing permissions. You see how to do this on StackOverflow for Postgres and mySQL.

2. Limit the IP addresses which can access your database. You’ll need to whitelist Zing’s domain to (getzingdata.com) ensure our servers can access your database when you set it up.

Read mode about Zing’s data security and protection here addresses some of the most common questions about security, compliance, and data security that we’re asked by CTOs and VPs of Engineering considering Zing.