3 Messages
Collibra Protect Bi-Directional Integration with Snowflake
Hello @spring-team.collibra.com, @sweeti.ranjit from Great American Insurance Group has the below questions regarding Collibra Protect. Would you be able to help us address? Thank you in Advance.
Snowflake
Could you also find out with the Snowflake Product team if I can implement the attached documentation integration in the GAIG platform using professional Service?
Our use case is Snowflake silver layer to connect the catalog to business terms and then send those tags back to Snowflake for improved searching.
This requires bi-directional communication from Snowflake to Collibra and Collibra to Snowflake. At the moment, I use Catalog to ingest physical data dictionaries only.
Can this implementation allow bi-directional communication/transformation integration?
Does the bi-direction data mask PII and PHI data would be masked not just Snowflake, but to other application that gets fed from Snowflake?
Do these features allow us to push the BT relation from the Collibra application to get visible in Snowflake as TAG_NAME and TAG_VALUE?
What does effort look like? And what type of permission is required to push from Collibra to Snowflake?
antoniocastelo
18 Messages
2 years ago
@miguel.guillen , not entirely sure if and how would help anyone pushing business terms down to Snowflake . The template that you see in the marketplace was initially built for the Snowflake Data Governance Accelerated Program last year and is intended to remain as a template. people can use for reference, possibly extend for their own purposes if they wish to. The document found in the marketplace explains well the scope of the integration. All it does is to push classifications, data categories, domains and standards as object tags to Snowflake and help determine what masking policies to apply when. As we get to know those classifications and standards better we do apply one masking policy or another, maybe none. All of it to asure data access is secure. It does not push tags, does not pull object tags, or nothing like that. This integration is scope of the recent Collibra Protect (not GA) development and that should be your starting point… Hope it helps.
0
sweetiranjit
16 Messages
•
50 Points
2 years ago
@antonio.castelo, Thank you for taking time to explain the protect features and it’s intended use case. I am well aware that Protect feature is design keeping the PII and PHI sensitivity. However, My organization has a use case is to tag Snowflake physical data dictionary ingested in Collibra platform with the standard business terms documented in DGC. And send those standard business term back to Snowflake for improved searching. I saw the video and documentation on the TAG_Name and TAG_Value that **allows the bi-directional capabilities and documentation below also mentioned that tagging strategy can be extended and applied to any available asset type with little to no effort. I have tested the capabilties tagging the business term in DGC and export csv file. Snowflake DBA ran a script to ingest those tag back to Snowflake. At the moment it is manual process and I would like to implement automation using protect features to extend the capabilities to tag the standard business term and send it back to Snowflake . I have attached the sample screenshot of POC.
Snowflake Policy Enforcement documentation:
Tags by themselves don’t enforce any security controls but applying a good tagging strategy is a great way to describe the data. Tags are key value pairs that you can apply for your Snowflake resources, including table and columns in your data lake. This integration applies a very simple tagging strategy: for the columns that have been classified as Name, make Classification tag equals Name; for columns that contain Personally Identifiable Information, make Category tag equals Personally Identifiable Information. The tagging strategy can be extended and applied to any available asset type with little to no effort.
Thank you,
Sweeti
0
0
antoniocastelo
18 Messages
2 years ago
Hi Sweeti, yes. The integration in the marketplace does push tags to snowflake so it provides enough context to decide what masking policies to apply or not. It pushes classifications first, and as you connect columns to domains it pushes the domains and the inherited data categories and standards as Snowflake object tags because those help us decide what masking policies to apply. That’s the purpose. Assign or unassign masking policies as we learn context. The app does not push business terms down to snowflake. Was never meant to help with searching data in Snowflake. The app also requires customers to adopt or follow our ‘recommended’ operating model where we have a logical model abstraction and a conceptual model. The documentation in the marketplace lists those expectations. Deviations to the model would fail. You can probably find ways to reuse some of that code for your own purpose and have terms pushed to Snowflake as they get somehow connected to the columns of tables (you need a way to navigate from the business term to the column it relates to) but might be easier to build something specific to your needs. Hope that helps.
1
0
sweetiranjit
16 Messages
•
50 Points
2 years ago
@antonio.castelo Thank you for sharing additional insights. This is super helpful. I will share the information with the Snowflake internal technical team. I will schedule a time with the professional service before implementing the feature in the platform. appreciated!
0
kamakshivenkateswaran
8 Messages
2 years ago
Team - Is there a way to push data from Collibra DGC to Snowflake back. We use connector to push metadata from snowflake to Collibra. But is there an option for other way around, if yes, could you enlighten
0
0