VPM-04: Continuous Vulnerability Remediation Activities
Mechanisms exist to address new threats and vulnerabilities on an ongoing basis and ensure assets are protected against known attacks.
Control Question: Does the organization address new threats and vulnerabilities on an ongoing basis and ensure assets are protected against known attacks?
General (28)
| Framework | Mapping Values |
|---|---|
| AICPA TSC 2017:2022 (used for SOC 2) (source) | CC4.2 |
| CIS CSC 8.1 | 12.1 18.3 7 7.7 |
| CIS CSC 8.1 IG1 | 12.1 |
| CIS CSC 8.1 IG2 | 7.7 12.1 18.3 |
| CIS CSC 8.1 IG3 | 7.7 12.1 18.3 |
| COBIT 2019 | DSS03.01 DSS03.02 DSS03.03 DSS03.04 DSS03.05 DSS06.04 MEA01.05 |
| COSO 2017 | Principle 17 |
| CSA CCM 4 | AIS-07 TVM-03 |
| CSA IoT SCF 2 | CLS-06 VLN-03 |
| NIST 800-53 R4 | SC-18(1) |
| NIST 800-53 R5 (source) | SC-18(1) |
| NIST 800-53 R5 (NOC) (source) | SC-18(1) |
| NIST 800-171 R2 (source) | 3.11.3 |
| NIST 800-171 R3 (source) | 03.11.02.b 03.14.01.a 03.14.01.b |
| NIST 800-171A R3 (source) | A.03.11.02.b |
| OWASP Top 10 2021 | A05:2021 A06:2021 |
| PCI DSS 4.0.1 (source) | 6.3.3 11.3 |
| PCI DSS 4.0.1 SAQ A (source) | 6.3.3 |
| PCI DSS 4.0.1 SAQ A-EP (source) | 6.3.3 |
| PCI DSS 4.0.1 SAQ B-IP (source) | 6.3.3 |
| PCI DSS 4.0.1 SAQ C (source) | 6.3.3 |
| PCI DSS 4.0.1 SAQ C-VT (source) | 6.3.3 |
| PCI DSS 4.0.1 SAQ D Merchant (source) | 6.3.3 |
| PCI DSS 4.0.1 SAQ D Service Provider (source) | 6.3.3 |
| SWIFT CSF 2023 | 2.7 |
| SCF CORE Mergers, Acquisitions & Divestitures (MA&D) | VPM-04 |
| SCF CORE ESP Level 2 Critical Infrastructure | VPM-04 |
| SCF CORE ESP Level 3 Advanced Threats | VPM-04 |
US (14)
| Framework | Mapping Values |
|---|---|
| US C2M2 2.1 | RISK-2.I.MIL3 |
| US CERT RMM 1.2 | KIM:SG3.SP2 VAR:SG1.SP2 |
| US CISA CPG 2022 | 1.E |
| US CMMC 2.0 Level 2 (source) | RA.L2-3.11.3 |
| US DHS CISA TIC 3.0 | 3.UNI.VMANG |
| US DHS ZTCF | EPM-02 |
| US FCA CRM | 609.930(c)(2) |
| US FFIEC | D1.RM.RA.E.1 |
| US HIPAA HICP Large Practice | 7.L.B |
| US IRS 1075 | SC-18(1) |
| US NNPI (unclass) | 9.1 17.1 |
| US NSTC NSPM-33 | 6.11 |
| US - CA CCPA 2025 | 7123(c)(5)(D) |
| US - NY DFS 23 NYCRR500 2023 Amd 2 | 500.5(b) |
EMEA (6)
| Framework | Mapping Values |
|---|---|
| EMEA EU NIS2 | 21.4 |
| EMEA Germany C5 2020 | OPS-18 PSS-02 |
| EMEA Israel CDMO 1.0 | 22.6 22.11 |
| EMEA Saudi Arabia CSCC-1 2019 | 2-9-1-3 |
| EMEA Saudi Arabia ECC-1 2018 | 2-10-3-3 |
| EMEA Saudi Arabia OTCC-1 2022 | 2-9-1-2 2-9-1-3 |
APAC (5)
| Framework | Mapping Values |
|---|---|
| APAC Australia ISM June 2024 | ISM-1801 |
| APAC Australia Prudential Standard CPS234 | 21 |
| APAC Japan ISMAP | 4.6 4.6.1 |
| APAC New Zealand NZISM 3.6 | 6.2.6.C.01 23.2.19.C.01 |
| APAC Singapore MAS TRM 2021 | 13.6.1(a) 13.6.1(b) 13.6.1(c) |
Americas (3)
| Framework | Mapping Values |
|---|---|
| Americas Canada CSAG | 2.7 |
| Americas Canada OSFI B-13 | 3.2.6 |
| Americas Canada ITSP-10-171 | 03.11.02.B 03.14.01.A 03.14.01.B |
Capability Maturity Model
Level 0 — Not Performed
There is no evidence of a capability to address new threats and vulnerabilities on an ongoing basis and ensure assets are protected against known attacks.
Level 1 — Performed Informally
C|P-CMM1 is N/A, since a structured process is required to address new threats and vulnerabilities on an ongoing basis and ensure assets are protected against known attacks.
Level 2 — Planned & Tracked
Vulnerability & Patch Management (VPM) efforts are requirements-driven and governed at a local/regional level, but are not consistent across the organization. CMM Level 2 control maturity would reasonably expect all, or at least most, the following criteria to exist: o Identify cybersecurity and data protection controls to address applicable statutory, regulatory and contractual requirements for ASM. o Apply software patches and other vulnerability remediation efforts.
- Attack Surface Management (ASM) is decentralized (e.g., a localized/regionalized function) and uses non-standardized methods to implement secure, resilient and compliant practices.
- IT/cybersecurity personnel:
- Administrative processes and technologies focus on protecting High Value Assets (HVAs), including environments where sensitive/regulated data is stored, transmitted and processed.
Level 3 — Well Defined
Vulnerability & Patch Management (VPM) efforts are standardized across the organization and centrally managed, where technically feasible, to ensure consistency. CMM Level 3 control maturity would reasonably expect all, or at least most, the following criteria to exist: o Defines the scope of ASM activities. o Provides governance oversight for the implementation of applicable statutory, regulatory and contractual cybersecurity and data protection controls to protect the confidentiality, integrity, availability and safety of the organization's applications, systems, services and data with regards to ASM. o Provides oversight of ASM activities to centrally manage the flaw remediation process as part of the organization's overall Patch& Vulnerability & Patch Management Program (VPMP). o Manages the identification, tracking and remediation of vulnerabilities. o Utilizes a Security Incident Event monitor (SIEM), or similar automated tool, to monitor for unauthorized activities, accounts, connections, devices and software according to organization-specific Indicators of Compromise (IoC), including feeds from applications, hosts, network devices and vulnerability scanners.
- An IT Asset Management (ITAM) function, or similar function, categorizes devices according to the data the asset stores, transmits and/ or processes and applies the appropriate technology controls to protect the asset and data.
- A Governance, Risk & Compliance (GRC) function, or similar function:
- A Security Operations Center (SOC), or similar function:
- Asset custodians install the latest stable version of security-related updates on all systems within the organization-defined time requirements.
Level 4 — Quantitatively Controlled
Vulnerability & Patch Management (VPM) efforts are metrics driven and provide sufficient management insight (based on a quantitative understanding of process capabilities) to predict optimal performance, ensure continued operations and identify areas for improvement. In addition to CMM Level 3 criteria, CMM Level 4 control maturity would reasonably expect all, or at least most, the following criteria to exist:
- Metrics reporting includes quantitative analysis of Key Performance Indicators (KPIs).
- Metrics reporting includes quantitative analysis of Key Risk Indicators (KRIs).
- Scope of metrics, KPIs and KRIs covers organization-wide cybersecurity and data protection controls, including functions performed by third-parties.
- Organizational leadership maintains a formal process to objectively review and respond to metrics, KPIs and KRIs (e.g., monthly or quarterly review).
- Based on metrics analysis, process improvement recommendations are submitted for review and are handled in accordance with change control processes.
- Both business and technical stakeholders are involved in reviewing and approving proposed changes.
Level 5 — Continuously Improving
Vulnerability & Patch Management (VPM) efforts are “world-class” capabilities that leverage predictive analysis (e.g., machine learning, AI, etc.). In addition to CMM Level 4 criteria, CMM Level 5 control maturity would reasonably expect all, or at least most, the following criteria to exist:
- Stakeholders make time-sensitive decisions to support operational efficiency, which may include automated remediation actions.
- Based on predictive analysis, process improvements are implemented according to “continuous improvement” practices that affect process changes.
Assessment Objectives
- VPM-04_A01 sources of new threats and vulnerabilities are defined.
- VPM-04_A02 a time period is defined to seek out new, applicable threats and vulnerabilities.
- VPM-04_A03 a capability exists to respond to new threats and vulnerabilities on an ongoing basis.
- VPM-04_A04 system vulnerabilities are remediated within organization-defined response times.
- VPM-04_A05 system vulnerabilities are remediated within <A.03.11.02.ODP[03]: response times>.
Evidence Requirements
- E-MNT-03 Patch Management
-
Documented evidence of maintenance activities for systems, applications and services management (e.g., patch management).
Maintenance - E-THR-05 Threat Mitigation
-
Documented evidence of steps taken to mitigate identified threats.
Threat Management