14.7
IG1 IG2 IG3

Train Workforce on How to Identify and Report if Their Enterprise Assets are Missing Security Updates

Asset Type: N/A
Security Function: Protect

Description

Train workforce to understand how to verify and report out-of-date software patches or any failures in automated processes and tools. Part of this training should include notifying IT personnel of any failures in automated processes and tools.

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
6
Develop or procure training content
7
Define training audience and completion requirements
8
Deploy training and track completion rates
9
Measure training effectiveness through testing/simulation
10
Draft policy/procedure document
11
Obtain stakeholder review and approval
12
Communicate to affected personnel
13
Schedule periodic review and updates

Threats & Vulnerabilities (CIS RAM)

Threat Scenarios

Exploitation of Known Vulnerability on Unpatched System

Integrity

An attacker exploits a publicly disclosed vulnerability on a system where automated patching failed, and the failure went unreported because the user was not trained to recognize or report missing security updates.

Extended Exposure Window from Unreported Patch Failure

Availability

An endpoint's automatic update mechanism breaks silently, leaving the system unpatched for months because the employee using the device was never trained to verify patch status or report anomalies.

Vulnerabilities (When Safeguard Absent)

Users Unable to Identify Missing Security Updates

Without training on how to verify software patch status, employees cannot recognize when their systems are out of date or when automated patching tools have failed.

No Process for Users to Report Automated Tool Failures

Employees who are not trained on reporting update failures do not escalate issues when they notice software is outdated, leaving IT unaware of patching gaps across the fleet.

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
Record Training completion records and compliance rates Tracked continuously, reported quarterly
Document Training content and curriculum documentation Reviewed annually
Document Governing policy document (current, approved, communicated) Reviewed annually