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

References

Topics: vendor riskvendor managementcertificate managementdata loss preventionencryption in transit