Best Practices

Best practices to manage your e6data deployment

e6data follows secure-by-design & privacy-by-design approaches to its systems. This means that all architectural decisions are based on minimizing access to users' data.

While most security settings are set to provide least privilege by default, some settings & configurations should be hardened by users prior to going to production.

The security best practices for different environments can be found below:

Last updated

#930: Cross account hive GCP

Change request updated