Security enabling cross company data sharing
Zachary Friedman, associate director of product management at Immuta, on security in the modern data stack
The important shift is that data security starts paying for growth once it lets a company turn internal data into a product or partner feed. Immuta sits in the control layer between identity systems like Okta and warehouses like Snowflake or Databricks, so a bank, pharma company, or SaaS vendor can let another company query the same data while masking rows and columns they should not see. That makes security a direct enabler of revenue, not just a brake on risk.
-
Immuta is bought both to reduce breach and compliance risk and to unlock new data use cases. In practice, customers define business rules once, then enforce them across Snowflake, Databricks, BigQuery, Redshift, and Starburst, which is especially useful when multiple teams own access decisions.
-
The revenue upside comes from sharing and multi tenancy. Some customers use Immuta as the policy layer for services they sell to their own customers, so different tenants can query shared infrastructure without one customer seeing another customer's sensitive data.
-
This becomes sticky because warehouse sharing is already getting easier inside platforms like Snowflake, but cross company sharing still needs a neutral control plane. BigID is closer to finding and classifying sensitive data, while Immuta is closer to deciding who can see which records at query time.
The market is heading toward data sharing becoming a standard enterprise feature, much like SSO became a standard software feature. As more SaaS vendors and large enterprises expose warehouse data to customers and partners, the durable winners will be the products that let them do it on one shared dataset, across multiple platforms, with auditability built in.