Hashed data export to all destinations | Community
Skip to main content
M
Md__AjazAn
Level 3
December 1, 2023
Question

Hashed data export to all destinations

  • December 1, 2023
  • 1 reply
  • 1298 views

We have data from different internal data sources which are sensitive and in plain text (not hashed). Requirement is to enforce data hashing for all destinations when exporting data.

I know we can enforce policies to restrict data exports based on marketing actions assigned to Destinations. Also, we can apply transformations at Dest mapping level (https://experienceleague.adobe.com/docs/experience-platform/destinations/ui/activate/activate-segment-streaming-destinations.html?lang=en#apply-transformation). But, all these dont satisfy my requirement.

 

I need to enforce that whenever any Destination is created (in future) and if data is not hashed, appropriate enforcement data privacy polices are applied to restrict it in exporting data in plain text.

 

Any suggestions?

 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

1 reply

abhinavbalooni
Community Advisor
abhinavbalooniCommunity Advisor
Community Advisor
December 1, 2023

Hey @md__ajazan 

 

You've looked into marketing actions so you are already aware of the functionality. When you say that it does not suffice your requirement, could you elaborate. Usually, we apply data usage labels to specific fields, in your case, the plan text data, then combined marketing actions with data usage policies to ensure that any segments based on these fields or there export as an attribute is not supported for a particular destination.

 

You might have already looked at the above but still sharing for reference : https://experienceleague.adobe.com/docs/experience-platform/data-governance/policies/overview.html?lang=en

 

Cheers,

Abhinav

M
Md__AjazAnAuthor
Level 3
December 1, 2023

Apologies for being ambiguous if it was not clear.

 

Let me elaborate further with an example. The restriction need not be imposed on export of emails as hash but rather need to be restricted if email is exported in plain text. Hope it is clean now.

abhinavbalooni
Community Advisor
abhinavbalooniCommunity Advisor
Community Advisor
December 1, 2023

Hi @md__ajazan 

 

Thanks for adding more details to it.

This is how I would approach it. Might not work for you. I have worked on a couple of setups where we had email in plain and hashed in separate fields. Plain text email field data usage label was labeled accordingly to avoid that being passed through to any destination.

 

There is one more option, if you do not want those plain text fields to be imported into AEP as is, then you can hash them during the data mapping stage using data prep functions.

 

Hope this would work for you too.

 

Cheers.

    Terms & ConditionsAccessibility statement

    Loading footer...