CIS Controls v8 16.5 — Use Up-to-Date and Trusted Third-Party Software Components

What this control requires

Use up-to-date and trusted third-party software components. When possible, choose established and proven frameworks and libraries that provide adequate security. Acquire these components from trusted sources or evaluate the software for vulnerabilities before use.

In plain English

Use up-to-date and trusted third-party software components. In practice, this means you can prove you protect software-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 16.5) and look for objective evidence on the latest two assessment cycles.

How to implement

Vulnerability Management

Scanners. Pair an unauthenticated scanner (Nessus / Qualys / Tenable.io) for external surface with an authenticated agent for OS/library CVEs on every host.

SLA. Document remediation SLAs by CVSS / EPSS: critical 7 days, high 30 days, medium 90 days; report monthly trend to leadership.

Containers. Scan images in CI (Trivy / Grype / Snyk Container) AND at runtime; block deploys on critical findings without exception.

Operational checklist

• Protect. Document the trigger, the owner and the cadence.
• Scope: software, vulnerability, date.

Evidence to collect

• Vendor Risk Management. vendor_risk_management evidence

Third-party risk management evidence (assessments, contracts, due diligence) shows supplier oversight. Focus: Use Up-to-Date and Trusted Third-Party Software Components.

Common pitfalls

• Scans that hit only the perimeter; missing authenticated scans of OS, runtime libs and base images so most CVEs are invisible.

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.

• BSI C5:2020 OIS-03 — Interfaces and Dependencies
• SOC 2 (2017 TSC) CC9.2 — Vendor Risk Management
• GDPR Article 76 — Confidentiality
• ISO/IEC 27001:2022 A.5.20 — Addressing information security within supplier agreements
• ISO/IEC 42001:2023 A.10.2 — Allocation of responsibilities

Related controls in CIS Controls v8

• Control 16.2 — Establish and Maintain a Process to Accept and Address Software Vulnerabilities
• Control 16.4 — Establish and Manage an Inventory of Third-Party Software Components
• Control 9.1 — Ensure Use of Only Fully Supported Browsers and Email Clients
• Control 16.1 — Establish and Maintain a Secure Application Development Process
• Control 15.7 — Securely Decommission Service Providers

References

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

Topics: vendor riskvendor managementsupply chain securitythird party monitoringvulnerability management