implementing-ot-incident-response-playbook

Develops OT incident response playbooks aligned with SANS PICERL, IEC 62443, and NIST SP 800-82.

954|172|Updated Mar 13, 2026
One-click install
npx skills add https://github.com/xalgord/xalgorix --skill implementing-ot-incident-response-playbook
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: implementing-ot-incident-response-playbook
Source: https://github.com/xalgord/xalgorix/tree/main/internal/tools/skills/data/ot-ics-security/implementing-ot-incident-response-playbook
Command: npx skills add https://github.com/xalgord/xalgorix --skill implementing-ot-incident-response-playbook

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generic IT incident response playbooks fail in industrial environments because they ignore safety-critical systems, limited downtime tolerance, and the need to coordinate IT SOC, OT engineering, and plant operations teams. This Skill provides OT-specific response procedures that address ICS/SCADA realities like PLC firmware, SIS integrity, and regulatory reporting clocks.

Core Features & Use Cases

  • OT Incident Classification: Categorizes incidents by severity (SEV1-SAFETY through SEV5-IT-SPILLOVER) and category (ransomware, SIS compromise, process manipulation, insider threat).
  • Category-Specific Playbooks: Executes structured response procedures for OT ransomware and safety system compromise, including immediate actions, containment steps, recovery priority order, and reporting requirements (CIRCIA 72-hour, NERC 1-hour, sector ISAC).
  • PICERL Phase Guidance: Maps SANS Preparation, Identification, Containment, Eradication, Recovery, and Lessons Learned phases to OT-specific actions such as offline PLC backups, conduit isolation at the DMZ, and staged process restart.
  • Use Case: When ransomware spreads from IT to Level 3 historian servers, activate the OT ransomware playbook to sever IT-OT conduits, verify PLC and SIS integrity, restore HMIs from offline backups, and meet CISA reporting deadlines.

Quick Start

Ask the AI to generate an OT incident response playbook for a ransomware incident affecting historian servers and HMIs, including containment steps and reporting timelines.

Frequently Asked Questions about implementing-ot-incident-response-playbook

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create an OT incident response playbook for ICS environments?

Define OT-specific severity levels and incident categories, then build response procedures for each SANS PICERL phase with ICS considerations like offline PLC backups, conduit isolation at the DMZ, and staged process recovery. Align the playbook with IEC 62443 and NIST SP 800-82.

How should ransomware in an OT network be contained?

Disconnect the IT-OT conduit at the DMZ firewalls, verify SIS and PLCs are operating independently, and switch critical processes to manual or local control. Never power off PLCs, since they run firmware rather than Windows and shutting them down disrupts the physical process.

What is the difference between IT and OT incident response?

OT incident response must account for safety-critical systems, limited downtime tolerance, and physical process impact, whereas IT response focuses on data and system availability. OT containment isolates network segments rather than shutting down controllers, and requires coordination with plant operations and process safety teams.

What reporting deadlines apply to OT security incidents?

CIRCIA requires reporting to CISA within 72 hours for covered critical infrastructure incidents. NERC requires reporting within 1 hour for BES-impacting events, and sector ISACs typically expect IOC sharing within 24 hours.

When should this OT playbook not be used?

Do not use it for IT-only incidents without OT components, where standard NIST 800-61 playbooks apply. It also does not cover day-to-day OT security monitoring or tabletop exercise design, which require separate procedures.