I have a DLP policy looking for specific data objects in Github using a regex, but it is triggering on known test data. Any ideas on how I can configure the DLP policy to ignore my spreadsheet of known test objects? For instance create an incident for ABC123, but ignore ABC111. Thx
Solved
Github API Data Protection Whitelist
Best answer by sshiflett
It might be depending on the age of your tenant. I'd suggest reaching out to your local account team or Technical Success Manager to discuss enabling it. It became available starting in R91.
https://docs.netskope.com/en/netskope-help/netskope-release-notes/netskope-cloud-release-notes/netskope-release-notes-version-91-0-0/new-features-and-enhancements-in-release-91-0-0/
There are some considerations to migrations if I recall correctly (I may be mistaken as it's been some time since I last looked into it. It would be good to validate that you can enable it without any changes to existing entities.
This topic has been closed for replies.
Hello @jschuele,
Is the ABC111 test data or a file name? If you're using custom regex, you can look at the entity modifiers which allow you to specify data that should not match. See the Advanced Options here including the "Does not match" option:
https://docs.netskope.com/en/netskope-help/data-security/data-loss-prevention/dlp-entity/
If it's the file name, you can use the file profile to filter the name and then does not match within the DLP profile to exclude it from the profile.
I was wondering why I had not heard of the option in the link you provided. I don't see Entities. Does this have to be turned on in he backend?
It might be depending on the age of your tenant. I'd suggest reaching out to your local account team or Technical Success Manager to discuss enabling it. It became available starting in R91.
https://docs.netskope.com/en/netskope-help/netskope-release-notes/netskope-cloud-release-notes/netskope-release-notes-version-91-0-0/new-features-and-enhancements-in-release-91-0-0/
There are some considerations to migrations if I recall correctly (I may be mistaken as it's been some time since I last looked into it. It would be good to validate that you can enable it without any changes to existing entities.
Sign up
Already have an account? Login
Sign in or register securely using Single Sign-On (SSO)
Employee Continue as Customer / Partner (Login or Create Account)Login to the community
Sign in or register securely using Single Sign-On (SSO)
Employee Continue as Customer / Partner (Login or Create Account)Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.