Learning Objectives
After completing this unit, you'll be able to:
- Explain what Data Detect does.
- Describe detection rules, scan scope, and results.
- Identify where sensitive data hides in an org.
Why Sensitive Data Hides in Plain Sight
Most orgs protect the fields they know are sensitive, like Social Security number fields. The trouble is the data people type where it doesn't belong: a card number pasted into a case description, a date of birth in a note. Data Detect scans your data to find it.
Note
Data Detect reads your data to classify it. It doesn't change records on its own; you decide what to do with what it finds.
How Data Detect Works
A Data Detect policy groups three things:
- Detection rules that describe the patterns to look for, using built-in classifiers or regular expressions.
- A scan scope that lists the objects and fields to read.
- Results that show every match, with the record, field, and a confidence score.
Term
Detection rule
Quick Check
You want a policy to finish quickly while you test it. What should you do?
Plan Your First Policy
Order the Steps
Put the steps for a first policy in order.
1Set a narrow scan scope
2Pick the sensitive data you care about
3Review the results
4Add detection rules for those patterns
5Run the policy
Resources
Quiz
To complete this unit, you need to answer all the quiz questions correctly.
+100 Points
1Where does sensitive data most often hide?
2What does a confidence score tell you?