# CIS Controls v8 3.7 — Establish and Maintain a Data Classification Scheme

- Source: https://support.icompaas.com/compliance/cis-controls-v8/3-7-establish-and-maintain-a-data-classification-scheme
- Section: [Compliance](https://support.icompaas.com/compliance) › [CIS Critical Security Controls v8](https://support.icompaas.com/compliance/cis-controls-v8) › Control 3 — Data Protection
- Last updated: 2026-06-05
- Publisher: iCompaas, Inc. (https://www.icompaas.com)

**CIS Controls v8**·Control `3.7`·high·Component: **Identify**

## What this control requires

> Establish and maintain an overall data classification scheme for the enterprise. Enterprises may use labels, such as "Sensitive," "Confidential," and "Public," and classify their data according to those labels. Review and update the classification scheme annually, or when significant enterprise changes occur that could impact this Safeguard.
> 
> — CIS Controls v8, Control 3.7

### In plain English

Establish and maintain an overall data classification scheme for the enterprise. In practice, this means you can prove you establish and maintain data classification scheme-level controls on a defined cadence.

## Why it matters

The CIS Controls are an industry-vetted, prioritised defence: skipping a safeguard widens the attack surface that the safeguards above and below it assume is closed. Audit frameworks (FedRAMP, PCI DSS, HIPAA) all cite CIS as evidence of due care.

This control is rated **high**. Auditors expect a named owner, a remediation SLA, and a tooling artefact that evidences continuous operation.

## What an auditor looks for

A CIS-aligned reviewer wants to see (a) which Implementation Group you are targeting, (b) a documented owner for the safeguard, and (c) a tooling or process artefact (config, scan output, ticket) that proves the safeguard runs on the cadence the control demands.

Within **Identify**, the assessor will trace your implementation back to the catalogue reference (Control 3.7) and look for objective evidence on the latest two assessment cycles.

## How to implement

#### Policy Management

**Docs.** Keep each policy in version-controlled Markdown alongside the code that implements it; ship a signed PDF snapshot at each annual review and link the SHA into the SoA.

### Operational checklist

-   **Establish And Maintain.** Document the trigger, the owner and the cadence.
-   **Classify.** Document the trigger, the owner and the cadence.
-   **Scope:** data classification scheme, sensitive, confidential, public, enterprise.

## Evidence to collect

-   **Policy Document.** A signed and version-controlled policy / standard / procedure document.

Signed policy or standard documents the safeguard. Focus: Establish and Maintain a Data Classification Scheme.

## Common pitfalls

-   Policies that no engineer has read; the version in Confluence drifts from the version that's actually being enforced.

## Related controls in CIS Controls v8

-   [**Control 3.2** — Establish and Maintain a Data Inventory](https://support.icompaas.com/compliance/cis-controls-v8/3-2-establish-and-maintain-a-data-inventory)
-   [**Control 3.1** — Establish and Maintain a Data Management Process](https://support.icompaas.com/compliance/cis-controls-v8/3-1-establish-and-maintain-a-data-management-process)
-   [**Control 3.8** — Document Data Flows](https://support.icompaas.com/compliance/cis-controls-v8/3-8-document-data-flows)
-   [**Control 11.1** — Establish and Maintain a Data Recovery Process](https://support.icompaas.com/compliance/cis-controls-v8/11-1-establish-and-maintain-a-data-recovery-process)
-   [**Control 12.4** — Establish and Maintain Architecture Diagram(s)](https://support.icompaas.com/compliance/cis-controls-v8/12-4-establish-and-maintain-architecture-diagram-s)
-   [**Control 3.12** — Segment Data Processing and Storage Based on Sensitivity](https://support.icompaas.com/compliance/cis-controls-v8/3-12-segment-data-processing-and-storage-based-on-sensitivity)

## References

-   [Center for Internet Security — CIS Controls v8](https://www.cisecurity.org/controls/v8)
-   Catalogue identifier: `Control 3.7`

Topics: governance riskpatch managementpolicy management

## Related compliance guidance

- [SOC 2 compliance: a practical implementation guide for cloud-native SaaS teams](https://support.icompaas.com/compliance/soc-2-trust-services-criteria): Configuration checks like this one are the technical half of a SOC 2 / ISO 27001 programme — the guide shows where they fit, what else an auditor expects, and how to evidence them.
- [ISO/IEC 27001:2022 compliance: a practical implementation guide](https://support.icompaas.com/compliance/iso-27001-2022): ISO 27001 Annex A.8 (technological controls) is where cloud hardening evidence lands; the guide shows how to run the ISMS around it.