CIS Controls v8·Control 16.2·high·Component: Protect

What this control requires

Establish and maintain a process to accept and address software vulnerability reports, including input from external entities. The process should define reporting steps, responsible parties, and procedures for intake, assignment, remediation, and testing. Use a tracking system with severity ratings and metrics for identifying, analyzing, and fixing vulnerabilities. Review and update the process annually or after significant changes. Third-party developers should treat this as an externally-facing policy.
— CIS Controls v8, Control 16.2

In plain English

Establish and maintain a process to accept and address software vulnerability reports, including input from external entities. In practice, this means you can prove you establish and maintain 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.2) 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.

Code Review Testing

Pipeline. Require at least one human reviewer plus passing CI (lint, type, unit, security scan) before merge — protected branches enforce this.

Operational checklist

  • Establish And Maintain. Document the trigger, the owner and the cadence.
  • Address. Document the trigger, the owner and the cadence.
  • Protect. Document the trigger, the owner and the cadence.
  • Define. Document the trigger, the owner and the cadence.
  • Scope: software, vulnerability.

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 a Process to Accept and Address Software Vulnerabilities.

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.

Related controls in CIS Controls v8

References

Topics: governance riskvendor riskvendor managementsupply chain securityvulnerability managementcode review testing