Sensitive Data Classification
Classify data as public, internal, confidential or highly sensitive so handling rules follow the value and consequence of exposure.
Frame the problem
Security starts with a concrete asset, attacker capability and trust crossing.
Why the system fails
All data receives the same controls, so highly sensitive fields spread into logs, test systems and broad analytics stores.
The important question is not “what is Sensitive Data Classification?” but “which assumption let untrusted data or an over-scoped identity cross data value → storage and processing policy?” Trace the decision at the boundary, then constrain what can happen after the first control fails.
Design the control in layers
Start with the control closest to the interpretation or privilege boundary: Classify fields and minimize collection Then add a control that reduces blast radius and telemetry that proves the decision was enforced.
The resulting design is not labelled secure. Record the identified controls, the known failure paths, the remaining exposure, and the evidence you would need during an incident.
| Prevent | Detect | Recover |
|---|---|---|
| Classify fields and minimize collection · Attach access, retention and logging rules to classification · Tokenize or separate the highest-value data | Data discovery scans and access to highly sensitive classes | Contain the affected identity or component, scope impact from audit evidence, and preserve a regression test. |
Key points
- Asset: Personal data, password hashes, messages, payment data, health data and secrets.
- Boundary: Data value → storage and processing policy
- Primary control: Classify fields and minimize collection
- Detection signal: Data discovery scans and access to highly sensitive classes
- Always ask what limits damage when the primary control fails.
Boundary control exercise
This lesson uses the shared boundary-control exercise.
Follow the attack
Safe conceptual simulation: capability → missing control → crossed boundary → asset impact.
- 1Attacker starts with: Any identity with access to a store, log, backup or analytics copy.
- 2All data receives the same controls, so highly sensitive fields spread into logs, test systems and broad analytics stores.
- 3The weak or missing boundary control is crossed: Data value → storage and processing policy
- 4Impact: Privacy, contractual, safety and regulatory harm.
- Privacy, contractual, safety and regulatory harm.
Defend, detect, recover
One prevention is a single point of security failure. Layer it and make failure observable.
- • Classify fields and minimize collection
- • Attach access, retention and logging rules to classification
- • Tokenize or separate the highest-value data
- • Data discovery scans and access to highly sensitive classes
- • Contain the affected identity or component.
- • Scope access from audit evidence.
- • Fix the boundary and add a regression test.
- • Misconfiguration and new access paths can bypass the intended control.
- • A privileged insider or compromised control plane may still reach the asset.