# CIS 15.1 — Establish and Maintain an Inventory of Service Providers

- Source: https://support.icompaas.com/support/solutions/articles/a_gen_cis_151_ed79ee7ece-cis-151-establish-and-maintain-an-inventory-of-service-providers
- Section: [Solutions](https://support.icompaas.com/support/solutions) › [AWS Checks New Version](https://support.icompaas.com/support/solutions/62000112673) › [Identify](https://support.icompaas.com/support/solutions/folders/f_gen_62000112673_identify)
- Last updated: 2026-05-30
- Publisher: iCompaas, Inc. (https://www.icompaas.com)

CIS · Control 15.1 · Priority: critical · Component: Identify

### What this control covers

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.

### Why it matters

Risk is the language an executive team understands; this control connects technical reality to board-level decisions and budget allocation.

### How to implement

#### AWS

Codify the policy intent as **SCPs, AWS Config conformance packs, and Security Hub standards** so the cloud enforces what the document says.

#### Azure

Codify in **Azure Policy initiatives** (built-in regulatory compliance for CIS, ISO 27001, SOC 2, HIPAA) and assign at management-group level.

#### GCP

**Cloud Asset Inventory** exports a daily snapshot of every resource and IAM policy to BigQuery; combine with **Org Policy** for tag enforcement.

#### GitHub

**Dependabot** security updates + version updates, plus **CodeQL** for SAST and a renovate bot for major-version drift management.

#### On-premises

Maintain a policy library with a documented review cadence (annual minimum); store in your GRC tool with attestation tracking. Map each policy to controls so an audit pull cites the exact policy clause.

### Evidence to collect

-   `vendor_risk_management` — See the iCompaas Evidence library for the canonical source for this evidence type.
-   `policy_document` — A signed, version-controlled policy stating leadership intent and the named owner.

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.

### Quick checklist

-   Establish And Maintain — Service / Classification
-   Designate — Service / Classification

### Related articles on this site

-   [Source Code Supply Chain Security](https://support.icompaas.com/support/solutions/articles/62000225179-source-code-supply-chain-security)
-   [Maintain different contact details to security, billing and operations](https://support.icompaas.com/support/solutions/articles/62000233375-maintain-different-contact-details-to-security-billing-and-operations)
-   [Maintain current contact details](https://support.icompaas.com/support/solutions/articles/62000081044-maintain-current-contact-details)
-   [Ensure security contact information is registered](https://support.icompaas.com/support/solutions/articles/62000081061-ensure-security-contact-information-is-registered)

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