Sensitive Information Types & Data Classification
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
🔍 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 |
# 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
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.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?
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?
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?
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?
You need to investigate which users downloaded files labelled “Confidential” from SharePoint in the past 7 days. Which tool provides this information?