Detect cyber attacks targeting OT historian servers (OSIsoft PI, Ignition, Wonderware) that sit at the IT/OT boundary and serve as pivot points for lateral movement between enterprise and control networks, including data manipulation, unauthorized queries, and exploitation of historian-specific vulnerabilities.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Um comando direto ignora o prompt de revisão. Verifique a origem antes de executá-lo.
Instruções da origem · Visualização somente leitura
name
detecting-attacks-on-historian-servers
description
Detect cyber attacks targeting OT historian servers (OSIsoft PI, Ignition, Wonderware) that sit at the IT/OT boundary and serve as pivot points for lateral movement between enterprise and control networks, including data manipulation, unauthorized queries, and exploitation of historian-specific vulnerabilities.
When monitoring historian servers that bridge IT and OT networks for compromise indicators
When detecting unauthorized queries or data manipulation in process historian databases
When investigating lateral movement through historian servers between IT and OT zones
When responding to alerts about exploitation of historian-specific vulnerabilities (CVE-2025-0921)
When validating historian data integrity after a suspected OT security incident
Do not use for general database security monitoring (see database security skills), for historian deployment and configuration, or for IT-only data warehouse security.
Detection Gaps & Validation
The SQL/ODBC path and the OPC/PI path are different attack surfaces. Queries arriving over the historian's SQL/ODBC interface (exfiltration, injection) look nothing like writes over OPC HDA/UA or the PI Web API. Monitoring only one interface misses the other; baseline both per client application and per tag set.
Flatlined or replayed tags evade simple thresholds. A Stuxnet-style replay feeds prior good values to the HMI while the process is manipulated. The tell is a constant value across hundreds of points (PI compression effectively off), not an out-of-range alarm.
The historian is a pivot, not just a database. Watch for the PI/OSIsoft or Ignition host initiating outbound connections to Level 1/2 (ports 502, 102, 44818, 20000) — it should receive data, never poll PLCs.
How to confirm a hit safely. Validate detections against a non-production PI/Ignition instance: replay recorded archive data, simulate an unauthorized client IP, and test CVE indicators offline. Cross-check every alert against the change/maintenance log before escalating — routine interface restarts and archive backfills mimic the deletion/flatline signatures.
Prerequisites
Historian server inventory (OSIsoft PI, Ignition, GE Proficy, Wonderware InSQL)
Network monitoring on historian network segments (both IT-facing and OT-facing interfaces)
Historian API access for data integrity validation
Baseline of normal historian query patterns (which applications query which tags)
Understanding of historian architecture (data sources, interfaces, client connections)