Policy Implementation
Supported File Formats¶
The table below outlines the file formats supported for different compliance workflow policies.
| Compliance workflow policies | CSV | Avro | Parquet | JSON | ORC |
|---|---|---|---|---|---|
| Workflow with Encryption | Yes | Yes | Yes | Yes | Yes |
| Workflow without Encryption | Yes | Yes | Yes | Yes | Yes |
| De-identification | Yes | Yes | Yes | Yes | Yes |
| Right to Privacy (RTP) | Yes | Yes | Yes | Yes | Yes |
| Expunge | Yes | Yes | Yes | Yes | - |
Compliance Workflow Support Matrix¶
The following table lists the supported Connectors for discovery compliance policies.
Important
- Connectors can be used across cloud environments (AWS or Azure) if they are hosted with public access.
- For example, if MSSQL is hosted on Azure with public access, it can also be used in an EKS or AWS Docker environment.
| Environment | Connector | Right to Privacy | Expunge | De-identification | Workflow Encryption | Workflow | Disallowed Tag | Disallowed Movement |
|---|---|---|---|---|---|---|---|---|
| AWS | S3 | YES | YES | YES | YES | YES | YES | NA |
| AWS | Redshift | YES | YES | YES | NA | NA | YES | NA |
| AWS | Snowflake | YES | YES | YES | NA | NA | YES | NA |
| AWS/Azure | MySQL | YES | YES | YES | NA | NA | YES | NA |
| AWS/Azure | PostgreSQL | YES | YES | YES | NA | NA | YES | NA |
| AWS/Azure | Oracle | YES | YES | YES | NA | NA | YES | NA |
| AWS/Azure | Vertica | YES | YES | YES | NA | NA | YES | NA |
| AWS/Azure | Databricks SQL | NA | NA | NA | NA | NA | YES | NA |
| AWS | Databricks Unity Catalog | YES | NA | YES | NA | NA | YES | NA |
| AWS/Azure | Trino | NA | NA | NA | NA | NA | YES | NA |
| Azure | ADLS | YES | YES | YES | YES | YES | YES | NA |
| AWS/Azure | MSSQL | YES | YES | YES | NA | NA | YES | NA |
| Azure | Synapse | YES | YES | YES | NA | NA | YES | NA |
| GCP | GCS | NA | NA | NA | NA | YES | YES | YES |
| GCP | GBQ | NA | NA | NA | NA | NA | YES | YES |
- Previous topic: Data Zones
- Next topic: