Forum Discussion
How to make DLP\Auto labeling more efficient
Good Morning All
As part of come new compliance policy, I have introduced labels to an organisation to manage some data. Part of the requirements is auto labeling. I have identified a set of documents that I want to apply this to, selected around 10 to 15 of the these documents and put these into a test SharePoint site.
I created a bespoke sensitive info type and tested by uploading the file to this, it does recognize this document falls under this remit however when I apply this to an auto labeling policy it does not pick anything up, I have attempted to change the confidence level and still getting little to no success. I run a DLP policy and it picked up 2 of the documents, even though they are all pretty much the same document.
I originally used a regex to target as the primary element that is specific to all these files (project code), however I got no results, so I reverted to a keyword list that had specific words in all these folders, and still I get very in-accurate results.
Are there any tips to making DLP/Auto labeling more efficient?
2 Replies
When businesses begin operationalizing DLP and auto-labeling as part of larger compliance initiatives, we frequently encounter this difficulty. The policies appear simple on paper, but when actual documents are involved, accuracy and uniformity become challenging.
As a Microsoft partner, Kanerika assists teams in increasing the efficacy of Purview DLP and auto-labeling by coordinating policy design with the actual creation, storage, and use of data across M365 and SharePoint.
We would be happy to talk about your situation and go over how comparable companies have handled it if that would be helpful. Tell me a time and date that works for you.
CamStephensMicrosoft
Assuming I understand your timeline of events correctly.
If you upload files to SharePoint, then create a new SIT and wonder why the files arent being auto labelled based on the new SIT, it is because when the file(s) are uploaded/created/modified SharePoint indexes them and their contents are evaluated against existing SITs. The files are not reindexed when you create a new SIT unless the file is modified again, so your auto-labelling policy doesnt realise the test files contain the new SIT.
To fix it you have 3 options.
- Try modifying some of the test files and see if they then are auto-labelled soon afterwards.
- Run a reindex of the test SharePoint site which will force SharePoint to update its knowledge of what these files contain.
- Use Purview's On-demand Classification tool. It requires PAYG billing to be setup which you wouldn't do for a test environment, but it could be useful if you had a lot of legacy (project?) files that are no longer being accessed but you wanted them to be labelled.
Hope this helps.
