Module 2: Sensitive Information Types & Data Classification

🔐 Purview Course · Module 2 of 6

Sensitive Information Types & Data Classification

Purview
SC-400 Exam Alignment
SC-400

Skill: Create and manage sensitive information types — Understand the role of SITs as the detection engine for DLP and auto-labelling, create custom SITs using keywords and regular expressions, configure EDM classifiers for exact data matching, and deploy trainable classifiers for content-based detection.

  • Know the three SIT components: primary element (regex pattern), supporting evidence (keywords/other patterns), and confidence level (low/medium/high)
  • Understand that Exact Data Match (EDM) matches specific values from a data schema — not pattern-based, must match actual data in your database
  • Know that trainable classifiers use machine learning trained on sample documents — they classify by content meaning, not patterns or keywords
  • Content Explorer requires the Content Explorer Content Viewer role to see individual item content; Content Explorer List Viewer to see counts only
Exam Tip: Rule of thumb: use built-in SITs for common regulated data (credit cards, NI numbers, passports); custom SITs for organisation-specific patterns (employee IDs, project codes); EDM when you need to match actual values in your employee or customer database; trainable classifiers when content is too varied for patterns (e.g. detecting “source code” or “HR policies” by meaning).
Before you can protect sensitive data — through DLP policies, sensitivity labels, or auto-labelling — Microsoft Purview needs to know what sensitive data looks like. That’s the job of sensitive information types (SITs). SITs are the detection engine that every other Purview feature builds on.

🔍 Sensitive Information Types (SITs)

A sensitive information type is a named pattern that Purview uses to detect sensitive content in files and emails. Every SIT has three components:

Component What It Does Example
Primary element The core pattern that must match — usually a regular expression Regex for 16-digit credit card number
Supporting evidence Keywords or other patterns near the primary element that increase confidence Keywords: “Visa”, “MasterCard”, “card number”, “CVV” within 300 characters
Confidence level How certain Purview is that a match is genuine — Low / Medium / High — determined by how much supporting evidence is present High = primary element + keyword found; Low = only primary element found

💡 Why Confidence Level Matters

DLP policies and auto-labelling let you set a minimum confidence threshold. A policy set to “High confidence” only triggers when both the pattern AND supporting keywords are found — fewer false positives but may miss some true instances. A policy set to “Low confidence” triggers on pattern alone — more sensitive but generates more false positives.

📋 Built-In Sensitive Information Types

Microsoft provides over 300 built-in SITs covering regulated data across many countries and industries.

Category Examples Common Use Cases
Financial Credit Card Number, Bank Account Numbers (UK sort code + account), IBAN, ABA Routing Number PCI-DSS compliance, financial data DLP
Identity (UK) UK National Insurance Number, UK Passport Number, UK Driver’s Licence, UK NHS Number GDPR personal data protection, healthcare compliance
Identity (US) US Social Security Number, US Individual Taxpayer Identification Number, US Passport Number CCPA, HIPAA, US federal compliance
Healthcare International Classification of Disease (ICD) codes, Drug Enforcement Agency number HIPAA compliance, healthcare data governance
Credentials Azure Storage Account Key, AWS Secret Access Key, GitHub Personal Access Token, General Password Source code scanning, secret sprawl prevention

🔧 Custom Sensitive Information Types

When built-in SITs don’t cover your organisation’s data, you create custom SITs. Common uses include employee ID numbers, internal project codes, patient reference numbers, and proprietary data formats.

Step What You Configure
1. Name and description Unique name and description for the SIT — used in DLP policies and label policies to reference it
2. Detection pattern The primary element: regex pattern. Example: employee IDs follow EMP-[0-9]{6}
3. Supporting elements Keywords (“Employee ID”, “Staff number”) within a specified character window of the primary element — increases confidence
4. Confidence levels Low (pattern only), Medium (pattern + 1 keyword), High (pattern + 2+ keywords) — DLP policies filter by minimum confidence
5. Test Upload test documents to validate the SIT detects correctly before publishing
PowerShell — Custom Sensitive Information Types

# List all SITs — Publisher 'Microsoft' = built-in, your org name = custom
Get-DlpSensitiveInformationType | Select-Object Name,Publisher,Category | Sort-Object Publisher

# Get details of a specific SIT (patterns, confidence levels)
Get-DlpSensitiveInformationType -Identity 'Credit Card Number'

# Create a custom SIT via XML rule package (recommended for production)
New-DlpSensitiveInformationTypeRulePackage -FileData ([System.IO.File]::ReadAllBytes('.\EmployeeID-SIT.xml'))

# Test SIT classification against sample text
Test-DataClassification -TextToClassify 'Employee EMP-123456 joined Finance team' `
  -SensitiveInformationTypes @{Name='Contoso Employee ID'}

🎯 Exact Data Match (EDM)

EDM is a data-specific classification method that detects exact values from your organisation’s actual data — not just patterns.

Step What Happens
1. Define schema Create an EDM schema that describes the structure of your sensitive data table — field names, types, primary fields (what to match on)
2. Hash and upload data Export a CSV of your sensitive data, hash it using the EDM Upload Agent (data never leaves in plaintext), upload the hash file to Purview
3. Create EDM SIT Create a new SIT that references the EDM schema — this SIT can now be used in DLP policies and auto-labelling like any other SIT
4. Refresh data Re-hash and re-upload your data on a schedule to keep the matching dataset current

⚠️ EDM Limitations

  • Maximum 100 million rows per EDM schema
  • EDM data must be re-hashed and uploaded manually or via scheduled task — it does NOT auto-sync from your database
  • EDM requires at least Microsoft 365 E5 Compliance or equivalent add-on licence
  • The hashing process uses SHA-256 with a salt — the actual data values are never uploaded to Microsoft

🤖 Trainable Classifiers

Trainable classifiers use machine learning to detect content by its meaning and context, not by patterns or keywords.

Type Description Examples
Pre-trained classifiers Built by Microsoft, ready to use immediately with no training required Source code, Resumes/CVs, Medical data, Profanity, Targeting harassment, Threat, Adult content
Custom trainable classifiers You provide sample documents (“positive” examples and “negative” examples), Purview trains the model Company-specific document types: procurement contracts, M&A documents, clinical trial protocols

🗺️ Content Explorer & Activity Explorer

Tool What It Shows Required Role
Content Explorer A read-only inventory of ALL classified content across Exchange, SharePoint, and OneDrive — showing what SITs or sensitivity labels each item has Content Explorer List Viewer (counts) or Content Explorer Content Viewer (item content)
Activity Explorer A timeline of classification events — label applied, label changed, DLP policy match, file uploaded/downloaded. Shows what happened and when. Compliance Administrator or specific Activity Explorer Viewer roles

✅ When to Use Which

Content Explorer = “What sensitive data do we have and where is it?” — use for data discovery and baseline assessment.
Activity Explorer = “What happened to our sensitive data and who did what?” — use for incident investigation and compliance monitoring.

💡 Best Practices

  • Before creating custom SITs, search the 300+ built-in types first — Microsoft may already have a SIT for your country’s national ID format, passport, or tax number
  • Always test custom SITs against representative sample documents before deploying to DLP policies — a poorly calibrated SIT causes false positives that frustrate users and create alert fatigue
  • Use EDM for customer/employee PII databases where exact matching is required to avoid false positives — a regex for a 9-digit number matches millions of things; EDM matches only your actual employees’ SSNs
  • Use Content Explorer as your starting point for any new DLP or labelling programme — it shows you how much sensitive data you have and where it lives before you start blocking or alerting

🎓 Interview Q&A

Q: Your organisation has a proprietary project code format (PRJ-YYYY-NNNN) used in sensitive planning documents. A junior analyst suggests using a keyword match on “PRJ-“. What’s the best approach?
Answer: A keyword match on “PRJ-” alone is insufficient because it’s a prefix, not a full pattern, and would generate high false positive rates. The best approach is to create a custom sensitive information type using a regular expression pattern — for example PRJ-\d{4}-\d{4} — which requires the exact four-digit year and four-digit number format. You’d then add supporting keywords (“Project code”, “Project reference”) to set confidence levels appropriately. High confidence requires both the regex pattern and at least one supporting keyword nearby, dramatically reducing false positives.

🎯 SC-400 Mock Test
Module 2 — Sensitive Information Types & Data Classification
5 questions · Scenario-based · Pass mark: 70%

Q1 of 5

A DLP policy is configured to detect UK National Insurance Numbers using the built-in SIT at “High confidence.” Users report that many legitimate emails with NI numbers are NOT being flagged. What is the most likely cause?

AThe SIT is not published and needs to be enabled in the DLP policy settings
BThe DLP policy is set to simulation mode and is not enforcing blocks
CThe emails contain the NI number pattern but lack nearby supporting keywords — so they only match at Low or Medium confidence, not the High confidence the policy requires
DThe built-in NI Number SIT requires Exact Data Match to function correctly

C. “High confidence” requires the NI number pattern PLUS nearby supporting keywords (such as “national insurance”, “NI number”, “NINO”). Emails that simply contain an NI number without those contextual keywords will only match at Low or Medium confidence — and will be missed if the policy requires High confidence. The fix is to change the policy to match at Medium or Low confidence, or add an additional rule at lower confidence.

Q2 of 5

An organisation wants to prevent specific customer account numbers (from their CRM database of 2 million records) from being sent externally. The account numbers follow a common 10-digit format. Which classification method should they use?

ABuilt-in SIT for account numbers — it already detects 10-digit financial account numbers
BExact Data Match (EDM) — matches the specific customer account numbers from the CRM database, not the pattern
CTrainable classifier — train it on sample emails containing customer account numbers
DCustom SIT with a regex for 10-digit numbers and keyword “account”

B. Because account numbers share the same format as many other 10-digit numbers, a regex-based SIT would generate massive false positives. EDM solves this by matching only the EXACT values from the CRM database — only the organisation’s actual customer account numbers trigger a match.

Q3 of 5

A compliance team wants to automatically apply a “Legal Hold” sensitivity label to documents that are legal contracts — regardless of how they’re formatted. Which classification method is most appropriate?

ACustom SIT with keywords like “whereas”, “notwithstanding”, “indemnification”
BBuilt-in SIT for legal documents
CExact Data Match using the organisation’s contracts database
DCustom trainable classifier trained on sample legal contracts from the organisation’s SharePoint

D. Legal contracts vary enormously in format, jurisdiction, and terminology — a keyword-based SIT would generate both false positives and false negatives. A custom trainable classifier trained on the organisation’s actual legal contracts learns the overall meaning and structure of those documents, making it the ideal approach for content-meaning-based classification.

Q4 of 5

A security analyst needs to see ALL files in SharePoint Online that contain credit card numbers — including the actual card number values in context. Which role must be assigned?

AContent Explorer Content Viewer
BContent Explorer List Viewer
CCompliance Administrator
DGlobal Reader

A. Content Explorer has two viewer roles: List Viewer lets you see counts and locations but NOT the actual content. Content Viewer lets you open and read the actual item content — necessary to see the credit card number values in context. Compliance Administrator grants access to the whole portal but does NOT automatically grant the ability to read item content in Content Explorer.

Q5 of 5

You need to investigate which users downloaded files labelled “Confidential” from SharePoint in the past 7 days. Which tool provides this information?

AContent Explorer — filter by label “Confidential” and view all matching files
BCompliance Manager — review the control related to file access monitoring
CActivity Explorer — filter by activity type “File downloaded” and label “Confidential”
DeDiscovery → Content Search — search SharePoint for “Confidential” label

C. Activity Explorer (Data classification → Activity Explorer) shows a timeline of events including file downloads, label applications, DLP matches, and access events — filtered by label, user, location, and activity type. Content Explorer shows current state (what exists and where), not historical events.



🔒

Locked — Pass Module 1 quiz to unlock this module.