# CIS Controls v8 7.7 — Remediate Detected Vulnerabilities - Source: https://support.icompaas.com/compliance/cis-controls-v8/7-7-remediate-detected-vulnerabilities - Section: [Compliance](https://support.icompaas.com/compliance) › [CIS Critical Security Controls v8](https://support.icompaas.com/compliance/cis-controls-v8) › Control 7 — Continuous Vulnerability Management - Last updated: 2026-06-05 - Publisher: iCompaas, Inc. (https://www.icompaas.com) **CIS Controls v8**·Control `7.7`·high·Component: **Respond** ## What this control requires > Remediate detected vulnerabilities in software through processes and tooling on a monthly, or more frequent, basis, based on the remediation process. > > — CIS Controls v8, Control 7.7 ### In plain English Remediate detected vulnerabilities in software through processes and tooling on a monthly, or more frequent, basis, based on the remediation process. In practice, this means you can prove you remediate 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 **Respond**, the assessor will trace your implementation back to the catalogue reference (Control 7.7) and look for objective evidence on the latest two assessment cycles. ## How to implement #### Policy Management **Docs.** Keep each policy in version-controlled Markdown alongside the code that implements it; ship a signed PDF snapshot at each annual review and link the SHA into the SoA. #### 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 - **Remediate.** Document the trigger, the owner and the cadence. - **Scope:** software, remediation process, vulnerability. ## Evidence to collect - **Policy Document.** A signed and version-controlled policy / standard / procedure document. Signed policy or standard documents the safeguard. Focus: Remediate Detected Vulnerabilities. ## Common pitfalls - Policies that no engineer has read; the version in Confluence drifts from the version that's actually being enforced. - 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. - [**NIST SP 800-53 Rev. 5 MA-3(6)** — Software Updates And Patches](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/ma-3-6-software-updates-and-patches) - [**ISO/IEC 27001:2022 A.8.19** — Installation of software on operational systems](https://support.icompaas.com/compliance/iso-27001-2022/a-8-19-installation-of-software-on-operational-systems) - [**NIST SP 800-171 Rev. 3 3.12.2** — Plan of Action and Milestones](https://support.icompaas.com/compliance/nist-sp-800-171-rev-3/3-12-2-plan-of-action-and-milestones) - [**SOC 2 (2017 TSC) CC3.1** — Objective Setting](https://support.icompaas.com/compliance/soc-2-trust-services-criteria/cc3-1-objective-setting) ## Related controls in CIS Controls v8 - [**Control 7.2** — Establish and Maintain a Remediation Process](https://support.icompaas.com/compliance/cis-controls-v8/7-2-establish-and-maintain-a-remediation-process) - [**Control 2.3** — Address Unauthorized Software](https://support.icompaas.com/compliance/cis-controls-v8/2-3-address-unauthorized-software) - [**Control 7.1** — Establish and Maintain a Vulnerability Management Process](https://support.icompaas.com/compliance/cis-controls-v8/7-1-establish-and-maintain-a-vulnerability-management-process) - [**Control 7.5** — Perform Automated Vulnerability Scans of Internal Enterprise Assets](https://support.icompaas.com/compliance/cis-controls-v8/7-5-perform-automated-vulnerability-scans-of-internal-enterprise-assets) - [**Control 7.6** — Perform Automated Vulnerability Scans of Externally-Exposed Enterprise Assets](https://support.icompaas.com/compliance/cis-controls-v8/7-6-perform-automated-vulnerability-scans-of-externally-exposed-enterprise-assets) - [**Control 2.6** — Allowlist Authorized Libraries](https://support.icompaas.com/compliance/cis-controls-v8/2-6-allowlist-authorized-libraries) ## References - [Center for Internet Security — CIS Controls v8](https://www.cisecurity.org/controls/v8) - Catalogue identifier: `Control 7.7` Topics: governance riskpolicy managementvulnerability management ## 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.