Skip to main content

VPM-05.4: Automated Software & Firmware Updates

VPM 5 — Medium Protect

Automated mechanisms exist to install the latest stable versions of security-relevant software and firmware updates.

Control Question: Does the organization use automated mechanisms to install the latest stable versions of security-relevant software and firmware updates?

General (12)
Framework Mapping Values
CIS CSC 8.1 7.4
CIS CSC 8.1 IG1 7.4
CIS CSC 8.1 IG2 7.4
CIS CSC 8.1 IG3 7.4
CSA CCM 4 TVM-04 TVM-05
CSA IoT SCF 2 CCM-06 CCM-07 CLS-06 IAM-22 IOT-03 IOT-09 VLN-03
IEC 62443-4-2 2019 NDR 3.10 (15.7.3(1))
NIST 800-53 R4 SI-2(5)
NIST 800-53 R5 (source) SI-2(4) SI-2(5)
NIST 800-53 R5 (NOC) (source) SI-2(4) SI-2(5)
NIST 800-161 R1 SI-2(5)
NIST 800-161 R1 Level 2 SI-2(5)
US (3)
Framework Mapping Values
US DHS ZTCF EPM-02
US IRS 1075 SI-2(4) SI-2(5)
US - VT Act 171 of 2018 2447(c)(7)
EMEA (4)
APAC (3)

Capability Maturity Model

Level 0 — Not Performed

There is no evidence of a capability to install the latest stable versions of security-relevant software and firmware updates.

Level 1 — Performed Informally

C|P-CMM1 is N/A, since a structured process is required to install the latest stable versions of security-relevant software and firmware updates.

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

See C|P-CMM3. There are no defined C|P-CMM4 criteria, since it is reasonable to assume a quantitatively-controlled process is not necessary to install the latest stable versions of security-relevant software and firmware updates.

Level 5 — Continuously Improving

See C|P-CMM4. There are no defined C|P-CMM5 criteria, since it is reasonable to assume a continuously-improving process is not necessary to install the latest stable versions of security-relevant software and firmware updates.

Assessment Objectives

  1. VPM-05.4_A01 the system components requiring automated patch management tools to facilitate flaw remediation are defined.
  2. VPM-05.4_A02 automated patch management tools are employed to facilitate flaw remediation to components.
  3. VPM-05.4_A03 security-relevant software and firmware updates to be automatically installed to system components are defined.
  4. VPM-05.4_A04 system components requiring security-relevant software updates to be automatically installed are defined.
  5. VPM-05.4_A05 security-relevant software and firmware updates are installed automatically to system components.

Technology Recommendations

Micro/Small

  • Azure Update Manager (https://azure.microsoft.com)
  • ManageEngine Endpoint Central (https://manageengine.com)

Small

  • Azure Update Manager (https://azure.microsoft.com)
  • ManageEngine Endpoint Central (https://manageengine.com)

Medium

  • Azure Update Manager (https://azure.microsoft.com)
  • ManageEngine Endpoint Central (https://manageengine.com)

Large

  • Azure Update Manager (https://azure.microsoft.com)
  • ManageEngine Endpoint Central (https://manageengine.com)

Enterprise

  • Azure Update Manager (https://azure.microsoft.com)
  • ManageEngine Endpoint Central (https://manageengine.com)

The Secure Controls Framework (SCF) is maintained by SCF Council. Use of SCF content is subject to the SCF Terms & Conditions.

Manage this control in SCF Connect

Track implementation status, collect evidence, and map controls to your compliance frameworks automatically.