# CIS Controls v8 8.12 — Collect Service Provider Logs

- Source: https://support.icompaas.com/compliance/cis-controls-v8/8-12-collect-service-provider-logs
- Section: [Compliance](https://support.icompaas.com/compliance) › [CIS Critical Security Controls v8](https://support.icompaas.com/compliance/cis-controls-v8) › Control 8 — Audit Log Management
- Last updated: 2026-06-05
- Publisher: iCompaas, Inc. (https://www.icompaas.com)

**CIS Controls v8**·Control `8.12`·medium·Component: **Detect**

## What this control requires

> Collect service provider logs, where supported. Example implementations include collecting authentication and authorization events, data creation and disposal events, and user management events.
> 
> — CIS Controls v8, Control 8.12

### In plain English

Collect service provider logs, where supported. In practice, this means you can prove you disposal 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.

## 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 **Detect**, the assessor will trace your implementation back to the catalogue reference (Control 8.12) 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

-   **Disposal.** Document the trigger, the owner and the cadence.
-   **Collect.** Document the trigger, the owner and the cadence.
-   **Encryption.** Document the trigger, the owner and the cadence.
-   **Scope:** data, user, logs, service provider logs, authorization events, data creation, disposal events, user management events.

## Evidence to collect

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

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

## Related controls in CIS Controls v8

-   [**Control 15.6** — Monitor Service Providers](https://support.icompaas.com/compliance/cis-controls-v8/15-6-monitor-service-providers)

## References

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

Topics: vendor riskvendor managementcertificate managementdata loss preventionencryption in transit

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