7.4
IG1 IG2 IG3

Perform Automated Application Patch Management

Asset Type: Applications
Security Function: Protect

Description

Perform application updates on enterprise assets through automated patch management on a monthly, or more frequent, basis.

Implementation Checklist

1
Assess current protection controls in place
2
Configure and deploy required security controls
3
Test control effectiveness in non-production environment
4
Deploy to production and verify functionality
5
Document configuration and operational procedures

Threats & Vulnerabilities (CIS RAM)

Threat Scenarios

Exploitation of Unpatched Third-Party Applications

Confidentiality

Attackers target vulnerabilities in unpatched third-party applications like browsers, PDF readers, Java, and office suites, which are frequently used as initial access vectors through phishing campaigns delivering malicious documents or links.

Supply Chain Attack via Outdated Application Dependencies

Integrity

Unpatched applications contain vulnerable libraries and dependencies that attackers exploit through supply chain attacks, as seen with SolarWinds and 3CX compromises where outdated application components were leveraged.

Zero-Day Exploitation Window Extended by Slow Application Patching

Confidentiality

When application vendors release emergency patches for actively exploited zero-days, the absence of automated application patching extends the organization's exposure window from hours to weeks or months.

Vulnerabilities (When Safeguard Absent)

No Automated Third-Party Application Patching

The organization relies on individual users or manual IT processes to update third-party applications, leaving hundreds of endpoints running outdated versions of commonly exploited software like Chrome, Adobe Reader, and Zoom.

Incomplete Application Inventory for Patch Coverage

Without a comprehensive inventory of installed applications, the automated patching system cannot ensure coverage of all deployed software, leaving shadow installations and non-standard applications perpetually unpatched.

Evidence Requirements

Type Evidence Item Collection Frequency
Technical Configuration screenshots or exports showing protection controls enabled Captured quarterly
Document Procedure documentation for protection measures Reviewed annually
Document Governing policy document (current, approved, communicated) Reviewed annually