CIS Controls v8 15.4 — Ensure Service Provider Contracts Include Security Requirements

What this control requires

Ensure service provider contracts include security requirements. Example requirements may include minimum security program requirements, security incident and/or data breach notification and response, data encryption requirements, and data disposal commitments. These security requirements must be consistent with the enterprise's service provider management policy. Review service provider contracts annually to ensure contracts are not missing security requirements.

In plain English

Ensure service provider contracts include security requirements. In practice, this means you can prove you ensure disposal-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 Protect, the assessor will trace your implementation back to the catalogue reference (Control 15.4) and look for objective evidence on the latest two assessment cycles.

How to implement

Incident Response

Runbook. Maintain a runbook keyed by incident type with named roles (IC, comms, scribe), an out-of-band comms channel, and a 72-hour timeline for external notification.

Tabletop. Run a quarterly tabletop exercise (ransomware, insider, supply-chain) and feed gaps back into the runbook.

Operational checklist

• Ensure. Document the trigger, the owner and the cadence.
• Protect. Document the trigger, the owner and the cadence.
• Scope: disposal, data, service, response, service provider management policy, service provider contracts include security requirements, minimum security program requirements, security incident.

Evidence to collect

• Vendor Risk Management. vendor_risk_management evidence

Third-party risk management evidence (assessments, contracts, due diligence) shows supplier oversight. Focus: Ensure Service Provider Contracts Include Security Requirements.

Common pitfalls

• Runbooks that name a role but no person, or list a paging channel that no longer exists.

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.

• SOC 2 (2017 TSC) P6.5 — Third-Party Breach Notification Commitments
• NIST SP 800-53 Rev. 5 IR-6(3) — Supply Chain Coordination

Related controls in CIS Controls v8

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

References

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

Topics: governance riskdata protectionvendor riskvendor managementincident responsesupply chain securityencryption at rest