Protected Data

Data classification, handling requirements, and regulatory compliance

Week 5 TOPIC 5.4 - IR & Forensics Fundamentals

Understanding Protected Data

Protected data refers to information that requires special handling due to its sensitivity, regulatory requirements, or business value. SOC analysts must understand data classifications to properly prioritize alerts and respond to potential data breaches.

Types of Protected Data

Personally Identifiable Information (PII)

Data that can identify an individual: SSN, driver's license, biometric data, full name + address.

Protected Health Information (PHI)

Medical records, diagnoses, treatment information. Governed by HIPAA.

Payment Card Data (PCI)

Credit card numbers, CVV codes, cardholder data. Governed by PCI DSS.

Intellectual Property (IP)

Trade secrets, source code, patents, proprietary business processes.

What SOC Analysts Must Recognize

When a DLP alert fires, you need to instantly assess what type of data is at risk. The response escalation depends on the data type:

Data TypeExamples of IdentifiersDLP Detection PatternBreach Impact
PII SSN (XXX-XX-XXXX), passport numbers, biometric templates Regex: \d{3}-\d{2}-\d{4}, keyword: "social security" Identity theft, regulatory fines, class-action lawsuits
PHI Medical record numbers, diagnoses (ICD codes), prescription data Keyword lists, document fingerprinting of medical forms HIPAA violation ($100-$50,000 per record), criminal penalties
PCI Primary Account Number (PAN), track data, CVV Luhn algorithm validation, BIN matching, regex for 16-digit patterns Card brand fines ($5K-$100K/month), loss of processing ability
IP Source code, design documents, customer lists, trade secrets Document classification labels, bulk transfer detection Competitive advantage loss, potentially billions in value
The Insider Threat Dimension

Most data breaches involving protected data come from inside the organization — employees with legitimate access who exfiltrate data before leaving (see the SOC Triage Simulator scenario 4 for a hands-on example). DLP alerts for departing employees should always receive elevated scrutiny, especially during notice periods.

Foundation Content

This topic extends the Data Lifecycle Visualizer from Shield House, adding SOC-specific data protection monitoring perspectives.

Source: Shield House > Fundamentals > Data Lifecycle Visualizer Open Source Content

Data Classification Levels

Level Description Examples Handling
Public Information freely available Marketing materials, public website No restrictions
Internal For employees only Org charts, internal procedures Don't share externally
Confidential Limited business access Financial reports, contracts Encryption, access controls
Restricted Highest sensitivity PII, PHI, trade secrets, PCI Strict encryption, audit logging, DLP

Regulatory Data Protection Requirements

GDPR (EU)

72-hour breach notification, right to erasure, data portability, consent requirements.

CCPA (California)

Consumer rights to know, delete, opt-out of sale. Applies to large businesses.

HIPAA (Healthcare)

Privacy and security rules for PHI. Breach notification within 60 days.

PCI DSS (Payment)

12 requirements for cardholder data protection. Quarterly scans, annual audits.

Breach Notification Timelines

Different regulations have different notification requirements. GDPR: 72 hours. HIPAA: 60 days. PCI: Varies by contract. Know your organization's obligations!

SOC Analyst Application

DLP Alert Triage

Alert Type Data Type Priority Action
Email with SSN pattern PII High Verify intent, check recipient, escalate if external
Large file upload to cloud storage Unknown Medium Check file type, user role, destination service
Credit card pattern in logs PCI Critical Immediate investigation - should never appear in logs
Medical record access off-hours PHI High Verify user role, check if patient is assigned

Data Exfiltration Indicators

High Risk Indicators

Large outbound transfers, uploads to personal cloud, encrypted archives, unusual USB activity.

Medium Risk Indicators

After-hours database queries, bulk record access, printing sensitive documents.

Context Dependent

Email to competitors, file shares with external parties, VPN from unusual locations.

SOC Analyst Tip

Know What's Where: Work with data governance to understand where protected data lives in your environment. DLP is only effective if it knows what to protect. Ask: "Where is our crown jewels data stored?"

Data Breach Response Checklist

1. Confirm the Breach

Verify data was actually exposed, not just accessed. Document evidence.

2. Identify Scope

What data types? How many records? What time period?

3. Contain

Stop ongoing exfiltration, preserve evidence, isolate affected systems.

4. Escalate

Legal, Privacy Officer, Management - follow IR plan escalation matrix.

Knowledge Check

Test your understanding of protected data. Score 80% or higher to pass.

1. Which data classification level would apply to customer Social Security Numbers?

2. What is the GDPR breach notification timeline?

3. A DLP alert shows credit card numbers appearing in application logs. What priority is this?

4. Which regulation specifically governs Protected Health Information (PHI)?

5. What is the FIRST step when a potential data breach is detected?