Data Loss Prevention Flashcards
What is the primary goal of Microsoft Purview Data Loss Prevention (DLP)?
To avoid unintentional data leaks and ensure sensitive data is protected.
How does DLP identify and monitor sensitive data?
DLP identifies sensitive data and monitors specific locations (e.g., SharePoint, OneDrive, Exchange, endpoints) for potential breaches.
What happens when a DLP rule is breached?
Automated actions are triggered based on the rule’s conditions, and alerts are generated, which can be reviewed and responded to in the Compliance Portal.
How does DLP help educate users?
DLP policies provide policy tips or notifications to educate users when they unintentionally risk data leakage.
What tools in the Data Classification view help identify sensitive content?
The Content Explorer and the Activity Explorer.
What does the Content Explorer do?
It allows you to search documents and emails by Sensitive Information Types (SITs) and filter information across SharePoint, OneDrive, and Exchange.
What does the Activity Explorer track?
It logs the last 30 days of actions on labeled data, providing insights into activities like sharing or printing sensitive documents.
How can Trainable Classifiers be used in DLP?
Trainable Classifiers help identify more complex, custom-sensitive information that does not fit pre-built SITs.
What is the difference between pre-built and custom DLP policies?
Pre-built policies are designed to comply with regulatory standards (e.g., GDPR, HIPAA), while custom policies allow you to define specific rules tailored to your organization.
What are the steps to configure a DLP policy?
1) Choose pre-built or custom, 2) Name the policy, 3) Select locations, 4) Define policy settings, 5) Choose the policy mode (Test or Enforce).
What is the difference between Test Mode and Enforce Mode?
In Test Mode, policy breaches are logged but no actions are enforced. In Enforce Mode, actual actions (e.g., block or notify) are taken when breaches occur.
What is the purpose of the Rule Editor in DLP?
The Rule Editor allows the creation of custom rules, with conditions, actions, and exceptions.
What are the default rules in DLP based on?
Default rules are usually set to detect low-volume breaches (e.g., 1-2 policy breaches trigger a warning) and high-volume breaches (e.g., 100+ SITs shared externally trigger a security breach alert).
What factors influence the conditions in a DLP rule?
Conditions depend on the locations being monitored (e.g., different conditions for email vs endpoints).
What types of actions can DLP policies enforce?
Actions can include blocking, restricting, notifying users, or triggering DLP alerts.