SecuPi
Compare with…SecuPi combines data classification with fine-grained access policies and de-identification. Its coverage list spans applications, databases and cloud stores, but the enforcement method must be confirmed for each interface. [1]
Discovery & classification, Access governance and Encryption & tokenization [1]
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
S3, RDS, Redshift and other services are listed. Validate enforcement per interface. [2]
- Google Cloud
- Partial
BigQuery, Cloud SQL and other services are listed. Confirm the required control for each. [2]
- Snowflake and Databricks
- Partial
Snowflake and Databricks are listed. The public matrix does not establish identical controls across both. [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
Deployment options include agents, gateways, APIs and SDKs. [1]
- Scope
- The chosen application and data interface determine the deployment. Confirm the processing location before a trial.
Pricing and operating workload are not published in the reviewed sources.
Questions for the vendor
- Which enforcement component is needed for each data access path?
- Can administrators or alternate clients bypass the policy?