ot-incident-resolution

Generate OT incident resolution notes with containment actions and remediation steps.

34|13|Updated Feb 6, 2026
One-click install
npx skills add https://github.com/Happy-Technologies-LLC/happy-servicenow-skills --skill ot-incident-resolution
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ot-incident-resolution
Source: https://github.com/Happy-Technologies-LLC/happy-servicenow-skills/tree/main/skills/otsm/ot-incident-resolution
Command: npx skills add https://github.com/Happy-Technologies-LLC/happy-servicenow-skills --skill ot-incident-resolution

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generate structured OT incident resolution notes that capture containment actions, safety impact assessments, device tracking, and remediation steps for OT/ICS environments, ensuring compliant documentation across regulatory and audit requirements.

Core Features & Use Cases

  • Structured resolution notes for OT incidents including safety considerations and containment status.
  • Device and zone tracking across OT environments (ICS/SCADA) with Purdue model awareness.
  • Regulatory and audit readiness through documented remediation steps, change requests, and post-resolution verification.
  • Use Case: When an OT security incident occurs affecting Zone 2 devices, produce a complete resolution report with containment, remediation, and verification steps.

Quick Start

Load the ot-incident-resolution skill into your session and provide the incident context to generate the full resolution notes.

Frequently Asked Questions about ot-incident-resolution

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

FAQPage Schema
How do I generate OT incident resolution notes in ServiceNow for ICS and SCADA environments?

OT incident resolution notes are generated by automating containment actions, safety impact assessments, and remediation steps for ICS and SCADA devices within ServiceNow. The process structures regulatory-ready documentation across Purdue model zones.

What should be included in OT incident containment and safety impact assessments?

OT incident containment and safety impact assessments must include cross-zone containment actions, safety considerations, device tracking, and remediation steps. This documentation captures data from OT vulnerabilities, asset records, and change requests to satisfy audit requirements.

Does this approach work with incidents affecting specific Purdue model zones?

Yes, OT incident resolution supports incidents affecting specific Purdue model zones including Zone 2 devices. It tracks industrial devices across OT environments and applies cross-zone containment to ensure comprehensive safety validations and remediation.

What's the best way to document remediation and change requests for OT security incidents?

The best way to document remediation for OT security incidents is capturing structured resolution notes that link change requests, post-resolution verification, and safety validations. This ensures regulatory and audit readiness for industrial control system environments.

Can I use this to produce regulatory-ready reports for OT vulnerabilities and asset records?

Yes, you can produce regulatory-ready reports by capturing OT vulnerabilities, asset records, and change requests into structured resolution notes. This satisfies containment, safety impact assessment, remediation, and verification requirements for compliance audits.

Why do I need safety validations and post-resolution verification for OT incidents?

Safety validations and post-resolution verification are needed for OT incidents to ensure cross-zone containment actions do not compromise industrial device safety. Documenting these steps provides regulatory-ready reporting and confirms remediation effectiveness across ICS environments.