Data Classification
Define simple levels for data sensitivity and required handling.
Purpose
Data handling work should classify sensitivity, define retention, identify approved storage locations, and preserve the minimum evidence needed for accountability.
Policy shape
| Rule | State the expected behavior in direct language. |
|---|---|
| Reason | Explain the operating risk or obligation behind the rule. |
| Owner | Name who maintains the policy and decides exceptions. |
| Evidence | Define what proves the policy is being followed. |
| Review | Set a review cadence and update trigger. |
When to use
- When the work repeats often enough that memory is no longer reliable.
- When more than one person may request, perform, review, or inherit the work.
- When risk, approval, evidence, or handoff needs to be visible later.
Common failure modes
- Retention is longer than needed.
- Sensitive data is copied into informal tools.
- Deletion exceptions are not approved.
Review guidance
Review this page after a material incident, after a role or system change, and on a normal cadence appropriate to its risk. During review, check whether the owner is still correct, whether inputs are still complete, whether the output is still useful, and whether related pages need updates.
External guidance
These resources are references for terminology, control thinking, or review design. DailyWF adapts the ideas into lightweight operating pages rather than reproducing full standards.
- NIST SP 800-53 Rev. 5 control catalogSecurity and privacy control language useful when translating operating work into controls.
- NIST Cybersecurity Framework 2.0General cybersecurity risk management structure: govern, identify, protect, detect, respond, recover.