Individual skill

hardware-ot-ics

Assess OT/ICS environments — PLC, SCADA, DCS, HMI — safely and passive-first: Purdue-model zoning, industrial protocol discovery (Modbus, S7, DNP3, EtherNet/IP), mirrored-traffic analysis, and read-only verification. Load for an authorized engagement touching industrial control networks, engineering workstations, historians, or IT/OT boundaries. Signals: ports 502, 102, 44818, 20000; Modbus/S7comm banners; PLC/RTU inventory requests.

skills/hardware/hardware-ot-ics/SKILL.md

Read pinned source

Source commit ee0e0c50d2f6d941a14b73dd85a2b470d0ab976e

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Not checked yet
Last checked
Nov 7, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
27
Repository last updated
Oct 14, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# OT / ICS security assessment (passive-first)

## When it applies
The engagement touches an industrial environment — PLC/RTU controllers, SCADA/DCS, HMIs,
engineering workstations, historians, jump hosts, or the IT/OT boundary (firewall rules, data
diodes). **A misstep here can cause physical harm, not just downtime.** Load `tradecraft-scope-roe`
and require the written authorization to spell out: the site and network segments, whether active
scanning is allowed, and whether writing coils/registers is allowed — **the default for both is
NO**. Work passive-first; nothing touches a PLC's state until the scope explicitly says so.

## Why it works
Industrial protocols (Modbus, S7comm, DNP3, EtherNet/IP) predate hostile networks: they run in
cleartext with no authentication (`CWE-306`), so anyone who can reach the port can read process
state — and usually write it. That's exactly why the assessment itself is the risk: a high-rate
Back to top