What this policy is
Defines the organization's data sensitivity tiers (e.g. Public / Internal / Confidential / Restricted), what handling each tier requires, and how data inherits its classification through processing.
Why every organization needs one
Without a classification scheme, every protection control has to apply equally to everything — which is unaffordable and slows the business. With one, controls can be proportionate.
What a competent Data Classification Policy typically contains
- Purpose and scope
- Roles and responsibilities
- Definitions
- Tier definitions and handling requirements per tier
- Labelling convention
- Default classification for unlabelled data
- Reclassification triggers
- Review cadence (typically annual) and version control
- Approval, sign-off and effective date
How iCompaas tracks this policy
The icompaas policy-doc producer manages this document through an 8-state lifecycle: draft → generated → internal_qa → customer_review → in_review → approved → signed (with rejected as a terminal side-state). The producer publishes a policy_doc_data_classification_policy_signed compliance finding once at least one document of this kind reaches the signed state for the account being assessed; the finding then rolls up into every compliance framework that references this policy (see the table below).
Compliance frameworks that reference this policy
The icompaas compliance controls library links every policy document to the controls in each framework that require, evidence, or otherwise rely on it. Below: every control across every framework in the iCompaas catalogue that names this policy as part of its evidence base. Each control links to its own dedicated page with auditor-view content + implementation guidance.
| Framework | Control | Title | Component |
|---|---|---|---|
| ISO/IEC 27001:2022 | A.5.12 | Classification of information | Organizational controls |
| ISO/IEC 27701:2025 | A.1.2.9 | Records related to processing PII | Conditions for collection and processing |
| ISO/IEC 27701:2025 | A.3.5 | Classification of information | Security considerations |
3 controls across 2 frameworks reference this policy.
About this page
This article is part of the iCompaas Policy Documents library — one page per signed-document type the icompaas policy-doc producer tracks for customer accounts. The article is intentionally framework-agnostic: a customer signing a policy of this kind gets the same regulatory benefit across every framework that references it.