Classify data by sensitivity tier
Every access, export, and encryption rule needs a tier to key on. This skill assigns each category a tier and the concrete controls that tier mandates.
Procedure
Define three or four tiers with concrete meanings: Public, Internal, Confidential (PII), Restricted (special-category, financial, or health). Never more tiers than you can enforce.
Assign categories: product catalogue = Public; internal metrics = Internal; name, email, address = Confidential; health, biometrics, precise geolocation = Restricted.
Attach controls per tier: who may read, whether it may leave the region, minimum encryption, logging requirement, retention class.
Tag the data at the source with a column comment, asset tag, or catalogue entry keyed to table.column.
Enforce by policy, not by comment: row-level security, masking views, or IAM conditions on the tag.
Set export rules: Restricted data must not reach local laptops or third-party tools; block it with DLP or remove the export path.
Define breach impact per tier so triage can prioritise: a Restricted breach is a notification candidate, an Internal one is not.
Review the mapping with the data owner at least yearly and on every schema change.
Publish a one-page tier-to-control mapping so engineers apply it without asking.
Pitfalls
- Too many tiers collapse into "everything is Confidential"; keep the set small and enforceable.
- Classification living only in a spreadsheet drifts from reality; tie it to the catalogue and the schema.
- Aggregation escalates tier; a large enough list of Internal rows becomes Restricted when it can profile people.
- Derived data inherits the highest tier of its inputs; a summary of health data is still health data.
- Tiers without an enforcement point are documentation, not a control.
Verification
psql "$DB" -c "select distinct sec_tier, count(*) from classified_assets group by 1 order by 1"
Report the tier counts, any untiered asset, and the controls actually enforced per tier today.
1---2name: classify-data-by-sensitivity-tier3description: Use when access, export, and encryption rules need a label to key on and none exists. Assign each data category a small, enforceable tier set and the controls each tier requires.4metadata:5 source: https://skillmd.com/skills/jiayaoqijia/classify-data-by-sensitivity-tier6---78# Classify data by sensitivity tier910Every access, export, and encryption rule needs a tier to key on. This skill assigns each category a tier and the concrete controls that tier mandates.1112## Procedure13141. Define three or four tiers with concrete meanings: Public, Internal, Confidential (PII), Restricted (special-category, financial, or health). Never more tiers than you can enforce.15162. Assign categories: product catalogue = Public; internal metrics = Internal; name, email, address = Confidential; health, biometrics, precise geolocation = Restricted.17183. Attach controls per tier: who may read, whether it may leave the region, minimum encryption, logging requirement, retention class.19204. Tag the data at the source with a column comment, asset tag, or catalogue entry keyed to `table.column`.21225. Enforce by policy, not by comment: row-level security, masking views, or IAM conditions on the tag.23246. Set export rules: Restricted data must not reach local laptops or third-party tools; block it with DLP or remove the export path.25267. Define breach impact per tier so triage can prioritise: a Restricted breach is a notification candidate, an Internal one is not.27288. Review the mapping with the data owner at least yearly and on every schema change.29309. Publish a one-page tier-to-control mapping so engineers apply it without asking.3132## Pitfalls3334- Too many tiers collapse into "everything is Confidential"; keep the set small and enforceable.35- Classification living only in a spreadsheet drifts from reality; tie it to the catalogue and the schema.36- Aggregation escalates tier; a large enough list of Internal rows becomes Restricted when it can profile people.37- Derived data inherits the highest tier of its inputs; a summary of health data is still health data.38- Tiers without an enforcement point are documentation, not a control.3940## Verification4142 psql "$DB" -c "select distinct sec_tier, count(*) from classified_assets group by 1 order by 1"4344Report the tier counts, any untiered asset, and the controls actually enforced per tier today.