CIS Controls v8 15.1 — Establish and Maintain an Inventory of Service Providers

What this control requires

Establish and maintain an inventory of service providers. The inventory is to list all known service providers, include classification(s), and designate an enterprise contact for each service provider. Review and update the inventory annually, or when significant enterprise changes occur that could impact this Safeguard.

In plain English

Establish and maintain an inventory of service providers. In practice, this means you can prove you establish and maintain 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.

This control is rated critical in the source catalogue. Treat gaps here as production incidents in the risk register, not housekeeping.

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.1) and look for objective evidence on the latest two assessment cycles.

How to implement

Asset Inventory

AWS. AWS Config Aggregator across every account + region gives a real-time inventory; ship the daily snapshot to S3 and surface drift in Security Hub.

Azure. Azure Resource Graph plus Defender for Cloud's inventory blade enumerates every subscription; export to Log Analytics for retention and Workbooks for reporting.

GCP. Cloud Asset Inventory exports a daily feed of every resource and IAM binding; query via BigQuery and alert on appearance/disappearance.

Endpoints. Pipe MDM telemetry (Intune / Jamf / Workspace ONE) into your CMDB so laptops and phones are inventoried with the same rigour as cloud resources.

Operational checklist

• Establish And Maintain. Document the trigger, the owner and the cadence.
• Designate. Document the trigger, the owner and the cadence.
• Scope: service, classification, service providers, enterprise.

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: Establish and Maintain an Inventory of Service Providers.

Common pitfalls

• Inventories that exclude SaaS, shadow IT and ephemeral cloud resources (Lambda, Cloud Run, K8s pods) miss the assets where most modern incidents start.

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.16.3 — External System Services
• ISO/IEC 27701:2025 A.3.10 — Supplier agreements
• ISO/IEC 42001:2023 A.10.2 — Allocation of responsibilities
• BSI C5:2020 PS-01 — Physical Security and Environmental Control Requirements

Related controls in CIS Controls v8

• Control 15.2 — Establish and Maintain a Service Provider Management Policy
• Control 3.8 — Document Data Flows
• Control 15.6 — Monitor Service Providers
• Control 15.3 — Classify Service Providers
• Control 3.13 — Deploy a Data Loss Prevention Solution
• Control 15.5 — Assess Service Providers

References

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

Topics: governance riskvendor riskvendor managementsupply chain securityasset inventorypatch management