CIS Controls v8 15.5 — Assess Service Providers

What this control requires

Assess service providers consistent with the enterprise's service provider management policy. Assessment scope may vary based on classification(s), and may include review of standardized assessment reports, such as Service Organization Control 2 (SOC 2) and Payment Card Industry (PCI) Attestation of Compliance (AoC), customized questionnaires, or other appropriately rigorous processes. Reassess service providers annually, at a minimum, or with new and renewed contracts.

In plain English

Assess service providers consistent with the enterprise's service provider management policy. In practice, this means you can prove you assess service-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 Identify, the assessor will trace your implementation back to the catalogue reference (Control 15.5) 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

• Assess. Document the trigger, the owner and the cadence.
• Scope: service, classification, service provider management policy, service providers, service organization control, soc, payment card industry, pci.

Evidence to collect

• Vendor Risk Management. vendor_risk_management evidence
• Policy Document. A signed and version-controlled policy / standard / procedure document.

Third-party risk management evidence (assessments, contracts, due diligence) shows supplier oversight. Signed policy or standard documents the safeguard. Focus: Assess Service Providers.

Common pitfalls

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

How it maps to other frameworks

Computed from shared tags, control component and key-operation subjects — handy when you are reconciling controls across an audit.

• NIST SP 800-171 Rev. 3 3.11.1 — Risk Assessment
• NIST SP 800-53 Rev. 5 SA-9(3) — Establish And Maintain Trust Relationship With Providers

Related controls in CIS Controls v8

• Control 15.2 — Establish and Maintain a Service Provider Management Policy
• Control 15.6 — Monitor Service Providers
• Control 15.1 — Establish and Maintain an Inventory of Service Providers
• Control 3.8 — Document Data Flows

References

• Center for Internet Security — CIS Controls v8
• Catalogue identifier: Control 15.5

Topics: governance riskvendor riskvendor managementsupply chain securitypolicy managementthird party monitoring