implementing-ot-incident-response-playbook

name	implementing-ot-incident-response-playbook
description	Develop and implement OT-specific incident response playbooks aligned with SANS PICERL framework, IEC 62443, and NIST SP 800-82 that address unique ICS challenges including safety-critical systems, limited downtime tolerance, and coordination between IT SOC, OT engineering, and plant operations teams. . Use when working with implementing ot incident response playbook.
domain	cybersecurity
tags	["ot-security","ics","incident-response","playbook","sans","iec62443","nist","safety-critical"]
subdomain	ot-ics-security
version	1.0
author	oyi77
license	Apache-2.0
nist_csf	["PR.IR-01","DE.CM-01","ID.AM-05","GV.OC-02"]

Implementing Ot Incident Response Playbook

Overview

Cybersecurity skill for implementing ot incident response playbook. Follows industry best practices and security standards.

When to Use

Trigger phrases:

• "implementing ot incident response playbook"

• "Develop and implement OT-specific incident response playbooks aligned with SANS "

• When building OT-specific incident response procedures for the first time

• When existing IT IR playbooks do not address ICS/SCADA-specific requirements

• When preparing for OT ransomware scenarios like EKANS or LockerGoga

• When aligning IR procedures with IEC 62443 and NERC CIP incident reporting requirements

• When conducting post-incident reviews to improve OT IR capabilities

Do not use for IT-only incident response without OT components (use standard NIST 800-61 playbooks), for day-to-day OT security monitoring (see implementing-dragos-platform-for-ot-monitoring), or for tabletop exercise design (see performing-ics-tabletop-exercise).

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 criticality ratings and safety system identification
• Defined roles: OT IR Lead, IT SOC Analyst, Plant Operations Manager, Process Safety Engineer
• Communication plan including out-of-band channels (OT incidents may compromise IT communications)
• Known-good backups of PLC programs, HMI configurations, and historian data
• Contact information for ICS vendors, Dragos/Claroty support, and CISA ICS-CERT

Workflow

# Example: IOC detection
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()}