Classifying Data Sensitivity
Welcome to the Course
As a Data Governance Analyst, you already feel the pull of two forces every week: colleagues who want to use data fast, and a quiet worry about whether a given use is actually safe. This course gives you a calm, repeatable way to handle that tension without needing to be a lawyer, a security engineer, or a privacy officer. The whole idea is risk triage for non-specialists: a steady habit you apply to any data request so you can decide what you safely can, document it, and escalate the rest to the right expert.
By the end of this course, you'll be able to:
- Triage any data risk with a repeatable pattern: identify the risk, gather context, consult the right partner, document a recommendation, and escalate when needed.
- Classify data as public, internal, confidential, or restricted using plain business-risk criteria.
- Apply core privacy principles to narrow over-broad data requests without blocking the work.
- Coordinate with security partners using the CIA triad, supplying the inputs they need while leaving implementation to them.
- Support retention and disposal decisions that balance business, legal, operational, and historical needs.
- Spot ethical and bias risks, such as proxy variables and unfair exclusion, and recommend safeguards.
This first unit builds the foundation everything else rests on: how to triage a risk, how data sensitivity shifts across its lifecycle, and how to classify a dataset by how much harm its misuse could cause.
Triaging Risk Across the Data Lifecycle
Before you classify anything, you need a mental routine you can run on autopilot. That routine is the risk-triage pattern, and it has five moves. First, identify the risk: ask "what could go wrong if this data were seen, changed, or shared by the wrong person?" Second, gather context: who wants it, why, for how long, and where will it go? Third, consult the right partner when the risk is beyond your seat. Fourth, document a clear recommendation so the decision is visible and reusable. Fifth, escalate when the stakes are high, meaning regulated data, external sharing, or anything you are genuinely unsure about.
Notice your job here. You are not the final approver on the hardest calls. You are the person who triages quickly, handles the routine cases, and routes the serious ones to legal, privacy, security, or compliance with the facts already organized. That framing keeps you fast without making you reckless.
The second piece of this foundation is that risk is not fixed. The same dataset carries different expectations depending on where it sits in its data lifecycle: creation, storage, active use, archive, retention, and disposal. A fresh customer record in active use needs to be accurate and available to the teams working it. That same record, years later in archive, should be locked down tighter, shared with far fewer people, and eventually disposed of responsibly. So when you triage, always ask which stage the data is in, because the stage changes what "responsible handling" looks like. Data you would happily share during active use might be something you minimize or delete entirely once its purpose is done.

