Protegrity
Compare with…Protegrity applies field-level tokenization, encryption and masking through protectors integrated with data platforms. Evaluate the protector and runtime for each store because policy enforcement depends on the integration path. [1] [2]
Sources reviewed 2 sources
Data coverage
Read the scope beside each mark. Support for an environment does not establish every capability in every store.
- Microsoft 365
- Unconfirmed
- AWS
- Partial
Cloud Protectors name S3, Redshift, RDS and Glue. Confirm the protector and supported runtime for each workflow. [1]
- Google Cloud
- Partial
BigQuery and Dataflow are named. Confirm the required protector and execution path. [1]
- Snowflake and Databricks
- Full
Snowflake and Databricks integrations are documented. Protector choice and table format affect the implementation. [1] [2]
- On-prem shares
- Unconfirmed
- SaaS apps
- Unconfirmed
Unconfirmed means the reviewed sources do not establish coverage. How coverage is assessed
Deployment and cost
How it runs
Protector behavior is specific to the integration. [2]
- Databricks Iceberg
- The Python Iceberg Protector contacts the Protegrity platform for policy decisions and keys.
- Authorization
- The documented integration evaluates identity, role and other attributes when protecting or unprotecting values.
Pricing and operating workload are not published in the reviewed sources.
Questions for the vendor
- Which runtimes and clients can access unprotected values?
- How are policy and key-service failures handled during ingestion and queries?