Book Image

Microsoft Information Protection Administrator SC-400 Certification Guide

By : Shabaz Darr, Viktor Hedberg
2 (1)
Book Image

Microsoft Information Protection Administrator SC-400 Certification Guide

2 (1)
By: Shabaz Darr, Viktor Hedberg

Overview of this book

Cloud technologies have massively increased the amount of data being produced and the places in which this data is stored. Without proper planning and discipline in configuring information protection for your data, you may be compromising information and regulatory compliance. Microsoft Information Protection Administrator SC-400 Certification Guide begins with an overview of the SC-400 exam, and then enables you to envision, implement, and administer the Information Protection suite offered by Microsoft. The book also provides you with hands-on labs, along with the theory of creating policies and rules for content classification, data loss prevention, governance, and protection. Toward the end, you'll be able to take mock tests to help you prepare effectively for the exam. By the end of this Microsoft book, you'll have covered everything needed to pass the SC-400 certification exam, and have a handy, on-the-job desktop reference guide.
Table of Contents (19 chapters)
1
Section 1: Exam Overview and Introduction to Information Protection
4
Section 2: Implementing Information Protection
9
Section 3: Implementing Data Loss Prevention
13
Section 4: Implementing Information Governance

Configuring data loss prevention for policy precedence

When data loss prevention policies and rules contained within a policy are processed, that process is referred to as policy precedence. The order in which the rule is evaluated can be manually configured, with the lowest priority number being processed first. The default rule is that the first rule is configured as priority 0, while the one after that is configured as priority 1; this continues in sequence.

Although only one DLP policy is enforced, all potential policy matches are in the logs, and you can also see this information in reports.

Specific condition matches can have configured actions that contradict each other. An example of this is that you can configure a DLP policy that blocks personal data from being shared externally, without an override allowed. You can then have another policy for financial data, which does allow end users to perform overrides. In this scenario, if only the final matching policy is applied...