# CIS Controls v8 15.3 — Classify Service Providers

- Source: https://support.icompaas.com/compliance/cis-controls-v8/15-3-classify-service-providers
- Section: [Compliance](https://support.icompaas.com/compliance) › [CIS Critical Security Controls v8](https://support.icompaas.com/compliance/cis-controls-v8) › Control 15 — Service Provider Management
- Last updated: 2026-06-05
- Publisher: iCompaas, Inc. (https://www.icompaas.com)

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

## What this control requires

> Classify service providers. Classification consideration may include one or more characteristics, such as data sensitivity, data volume, availability requirements, applicable regulations, inherent risk, and mitigated risk. Update and review classifications annually, or when significant enterprise changes occur that could impact this Safeguard.
> 
> — CIS Controls v8, Control 15.3

### In plain English

Classify service providers. In practice, this means you can prove you classify data-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 15.3) and look for objective evidence on the latest two assessment cycles.

## How to implement

1.  Write a short policy stating intent, scope and named owner.
2.  Encode it as a platform guardrail — SCP, Azure Policy initiative, Organisation Policy, or repository policy.
3.  Wire a monitoring signal that catches drift (CSPM rule, SIEM rule, scheduled query, Workspace alert) and ticket it.
4.  Review on a documented cadence and capture the review in the risk register or compliance tracker.

### Operational checklist

-   **Classify.** Document the trigger, the owner and the cadence.
-   **Scope:** data, service, classification, service providers, one, more characteristics, data sensitivity, data volume.

## Evidence to collect

-   **Vendor Risk Management.** `vendor_risk_management` evidence

Third-party risk management evidence (assessments, contracts, due diligence) shows supplier oversight. Focus: Classify Service Providers.

## Related controls in CIS Controls v8

-   [**Control 15.1** — Establish and Maintain an Inventory of Service Providers](https://support.icompaas.com/compliance/cis-controls-v8/15-1-establish-and-maintain-an-inventory-of-service-providers)
-   [**Control 3.8** — Document Data Flows](https://support.icompaas.com/compliance/cis-controls-v8/3-8-document-data-flows)
-   [**Control 15.2** — Establish and Maintain a Service Provider Management Policy](https://support.icompaas.com/compliance/cis-controls-v8/15-2-establish-and-maintain-a-service-provider-management-policy)
-   [**Control 15.7** — Securely Decommission Service Providers](https://support.icompaas.com/compliance/cis-controls-v8/15-7-securely-decommission-service-providers)

## References

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

Topics: vendor riskvendor managementsupply chain securitypatch managementthird party monitoring

## 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.