Skip to content

Commit

Permalink
Merge pull request #2580 from EnterpriseDB/aswright491-patch-1
Browse files Browse the repository at this point in the history
Update index.mdx
  • Loading branch information
drothery-edb authored Apr 25, 2022
2 parents 31ccfa0 + 231be2d commit 8da7167
Showing 1 changed file with 2 additions and 2 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@ BigAnimal runs in your own cloud account, isolates your data from other users, a

- **Data isolation:** Clusters are installed and managed in your cloud environment. Complete segregation of your data is ensured. Your data never leaves your cloud account, and compromise of another BigAnimal customer's systems doesn't put your data at risk.

- **Granular access control:** You can use single sign-on (SSO) and define your own sets of roles and role-based access control (RBAC) policies to manage your individual cloud environments. See [Managing portal access](../administering_cluster/01_portal_access) for more information.
- **Granular access control:** You can use single sign-on (SSO) and define your own sets of roles and role-based access control (RBAC) policies to manage your individual cloud environments. See [Managing portal access](../../administering_cluster/01_portal_access/) for more information.

- **Data encryption:** All data in BigAnimal is encrypted in motion and at rest. Network traffic is encrypted using Transport Layer Security (TLS) v1.2 or greater, where applicable. Data at rest is encrypted using AES with 256-bit keys. Data encryption keys are envelope encrypted, and the wrapped data encryption keys are securely stored in an Azure Key Vault instance in your account. Encryption keys never leave your environment.

Expand All @@ -15,4 +15,4 @@ BigAnimal runs in your own cloud account, isolates your data from other users, a
- **Database logging and auditing:** Functionality to track and analyze database activities is enabled automatically. For PostgreSQL, the PostgreSQL Audit Extension (pgAudit) is enabled for you when deploying a Postgres cluster. For EDB Postgres Advanced Server, the EDB Audit extension (edbAudit) is enabled for you.
- **pgAudit:** The classes of statements being logged for pgAudit are set globally on a cluster with `pgaudit.log = 'write,ddl'`. The following statements made on tables are logged by default when the cluster type is PostgreSQL: `INSERT`, `UPDATE`, `DELETE`, `TRUNCATE`, AND `COPY`. All `DDL` is logged.

- **Database cluster permissions** The edb_admin account created during the *create cluster* process includes the `CREATEDB` and `CREATEROLE` database roles. EDB recommends using the edb_admin account to create a new application user and new application database for further isolation. See [Managing Postgres access](../using_cluster/01_postgres_access) for more information.
- **Database cluster permissions** The edb_admin account created during the *create cluster* process includes the `CREATEDB` and `CREATEROLE` database roles. EDB recommends using the edb_admin account to create a new application user and new application database for further isolation. See [Managing Postgres access](../../using_cluster/01_postgres_access/) for more information.

0 comments on commit 8da7167

Please sign in to comment.