We identify where sensitive data is stored and how it’s shared. We first evaluate rules in monitoring or simulation mode, review false matches and decide on the scope of blocking.
Microsoft Purview DLPSensitivity labelsData classificationEndpoint DLPKVKK personal dataTurkish ID number detectionOneDrive / SharePoint
Need and approach
Why is this service needed?
Which rules can be applied on the email, cloud, endpoint and USB channels depends on the license and the product used. We define the scope accordingly.
01
Which license does Purview DLP require?
Email and SharePoint/OneDrive DLP are included in many Microsoft 365 bundles; features such as Endpoint DLP and auto-labeling require E5 or an add-on license. We plan the scope based on your license.
02
Does DLP mean reading our employees’ emails?
No. Rules detect content types automatically; alerts are reviewed only by authorized people following a defined procedure. We recommend informing employees in advance.
03
What about old data on file servers?
File servers can be scanned with an on-premises scanner; based on the findings, we recommend archiving, moving or restricting access.
04
Will false alarms disrupt our work?
Thanks to audit mode and rules that users can override by entering a justification, rule accuracy improves without stopping the workflow.
Implementation approach
Controlled, documented, sustainable
01 / ANALYSIS
Data discovery
Sensitive data types are defined and existing locations are scanned.
02 / PLAN
Model design
Label levels and policy scope are defined with the business units.
03 / EXECUTION
Audit mode
Policies run in monitoring mode and the reports are reviewed.
04 / HANDOVER
Implementation and tuning
Warning and blocking rules are enabled in phases and the process is handed over.