| name | implementing-patch-management-for-ot-systems |
| description | Use when this skill covers implementing a structured patch management program for OT/ICS environments where traditional IT patching approaches can cause process disruption or safety hazards. It addresses vendor compatibility testing, risk-based patch prioritization, staged deployment through test environments, maintenance window coordination, rollback procedures, and compensating controls when patches cannot be applied due to operational constraints or vendor restrictions. |
| domain | cybersecurity |
| tags | ["ot-security","ics","scada","industrial-control","iec62443","patch-management","vulnerability-management"] |
| subdomain | ot-ics-security |
| version | 1.0.0 |
| author | oyi77 |
| license | Apache-2.0 |
| nist_csf | ["PR.IR-01","DE.CM-01","ID.AM-05","GV.OC-02"] |
Implementing Patch Management For Ot Systems
Overview
Cybersecurity skill for implementing patch management for ot systems. Follows industry best practices and security standards.
When to Use
Trigger phrases:
-
"implementing patch management for ot systems"
-
"This skill covers implementing a structured patch management program for OT/ICS "
-
When establishing a formal OT patch management program for the first time
-
When responding to critical ICS-CERT advisories affecting deployed OT systems
-
When preparing for NERC CIP-007-6 or IEC 62443 patch management compliance audits
-
When planning patch deployment during limited maintenance windows in continuous operations
-
When evaluating compensating controls for systems that cannot be patched
Do not use for IT-only patch management without OT considerations, for emergency patching during active cyber incidents (see performing-ot-incident-response), or for firmware upgrades that change PLC functionality (requires separate change management).
When NOT to Use
- When you lack proper authorization for testing
- For production systems without change management
- When the task requires legal or compliance expertise beyond technical scope
Prerequisites
- OT asset inventory with firmware/OS versions for all patchable systems
- Vendor patch notification subscriptions (Siemens ProductCERT, Rockwell, Schneider, etc.)
- Test/staging environment mirroring production OT systems for patch validation
- Maintenance window schedule aligned with process shutdowns and turnarounds
- Change management board approval process including operations and safety representatives
Workflow
import re
IOC_PATTERNS = {
"ip": r"\b(?:\d{1,3}\.){3}\d{1,3}\b",
"domain": r"\b[a-z0-9-]+\.[a-z]{2,}\b",
"hash_md5": r"\b[a-f0-9]{32}\b",
"hash_sha256": r"\b[a-f0-9]{64}\b",
}
def extract_iocs() -> :
{k: re.findall(v, text) k, v IOC_PATTERNS.items()}
