How to configure Automatic DLP

[@googlecloudtech]

Why are you configuring Automatic DLP? Let us know in the comments! Be sure to subscribe to get alerts when more episodes are released 😊 → goo.gle/GoogleCloudTech

[@thejuanes90]

Hello, thanks for the video it was very clear, however, it’s there any way to configure and define the number of rows we want to scan from the tables in the automatic DLP ? So we don’t scan all the table entirely ? Thank you.

[@cloudlover9186]

Can i do the same stuff thru python script? , how do i enable DLP thru python code . Please advise.

[@jsalsman]

Can you explain how finding, e.g., names, emails, and dates of birth in bigquery tables older than 48 hours and ending with "_temp" can help prevent data loss, please? I'm not saying it can't, just that the example shown is pretty opaque as to how it would address data loss at all.

[@saimabehan217]

I think this video is about data discovery stage. What to do with sensitive data could be in following videos.

[@jsalsman]

@@saimabehan217 sure, but it's just not clear to me how this kind of discovery is likely to help prevent loss.

[@debicabreragoog]

@@jsalsman ​ Hi James! I appreciate your feedback. In this case we had some tables that ended in _temp to demonstrate that they were supposed to be 'temporary'. Instead of "_temp" you can imagine a table that ends with "_socialsecurity" or "_sensitive". The 48 hours time range is so that we make sure empty or partially filled in tables aren't being profiled, as it can sometimes take a day for them to fill up completely. It all depends on the data that your organization stores - names, emails and dates of birth can all be considered PII, but this could be CC numbers, social security numbers or home addresses. Check out the next video in the series when it is posted soon to get some specific scenario examples. Hope that helps!

[@jsalsman]

@@debicabreragoog thanks! I'm watching the other videos in this series with great interest.

[@JohnDoe-rk7ex]

😍😍