monitoring-scada-modbus-traffic-anomalies

Featured

Monitors Modbus TCP traffic on SCADA and ICS networks to detect anomalous function code usage, unauthorized register writes, and suspicious communication patterns. The analyst uses deep packet inspection with pymodbus, Scapy, and Zeek to baseline normal PLC/RTU communication behavior, then applies statistical and rule-based anomaly detection to identify reconnaissance, parameter manipulation, and denial-of-service attacks targeting Modbus devices on port 502. Activates for requests involving Modbus traffic analysis, SCADA network monitoring, ICS anomaly detection, PLC security monitoring, or OT network threat detection.

AI & Automation 36,355 stars 4443 forks Updated 2 months ago Apache-2.0

Install

View on GitHub

Quality Score: 94/100

Stars 20%
100
Recency 20%
75
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Monitoring SCADA Modbus Traffic Anomalies ## When to Use - Monitoring OT/ICS networks for unauthorized Modbus commands targeting PLCs, RTUs, or HMIs - Detecting reconnaissance activity such as Modbus device enumeration (function code 43, Read Device Identification) - Identifying unauthorized write operations (function codes 05, 06, 15, 16) to coils and holding registers that could alter physical process parameters - Baselining normal Modbus communication patterns and alerting on deviations in function code distribution, register access ranges, or timing intervals - Investigating suspected sabotage or insider threats manipulating SCADA process values through Modbus register writes **Do not use** on networks without authorization from the asset owner, for active injection or fuzzing against production SCADA systems, or as a replacement for safety-instrumented systems (SIS) that provide physical process protection. ## Prerequisites - Network tap or SPAN port on the OT network segment carrying Modbus TCP traffic (port 502) - Python 3.9+ with pymodbus (>=3.6), scapy (>=2.5), and pandas for traffic analysis - Zeek (formerly Bro) installed with the Modbus protocol analyzer enabled for passive traffic logging - Wireshark or tshark for initial packet capture and validation of Modbus frame structure - A baseline period of normal operations (minimum 48-72 hours) to establish communication profiles per device pair - Network diagram identifying Modbus master-slave relationships, de...

Details

Author
mukul975
Repository
mukul975/Anthropic-Cybersecurity-Skills
Created
8 months ago
Last Updated
2 months ago
Language
Python
License
Apache-2.0

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category