Run any Skill in Manus with one click

pentest-iot-ot

Stars5

Forks2

UpdatedJune 9, 2026 at 03:59

Embedded / IoT / OT / ICS penetration testing. Use when the user mentions IoT pentest, firmware analysis, OWASP FSTM, binwalk, squashfs, JFFS2, UBIFS, EMBA, FACT, Firmadyne, QEMU emulation, UART, JTAG, SWD, SPI flash, SOIC clip, CH341A, chip-off, JTAGulator, OpenOCD, glitching, ChipWhisperer, U-Boot, BLE GATT, Zigbee, LoRa, Z-Wave, NFC, sub-GHz, HackRF, URH, Modbus, DNP3, S7Comm, EtherNet/IP, BACnet, OPC UA, IEC 61850, Allen-Bradley, Siemens TIA, PLC, HMI, SCADA, engineering workstation, or ATT&CK ICS techniques.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

thau0x01

thau0x01/ai-pentest-kb

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Information Security AnalystsComputer and Mathematical Occupations·SOC 15-1212

SKILL.md

readonly

name

pentest-iot-ot

description

Pentest — IoT / OT

Apply 10-iot-ot/ from the pentest-templates library.

Library root

$PENTEST_LIBRARY — caminho absoluto deste repositório clonado (definido pelo instalador; veja INSTALL.md).

Read 10-iot-ot/00-overview.md first.

Phase order

10-iot-ot/01-firmware-analysis.md — 9 stages of OWASP FSTM applied.
10-iot-ot/02-hardware-attacks.md — UART, JTAG, SWD, SPI/I2C, chip-off, glitching, side-channel, bootloader.
10-iot-ot/03-radio-rf.md — spectrum, modulation, replay, BLE, Zigbee, LoRa, Z-Wave, NFC, sub-GHz.
10-iot-ot/04-iot-app-cloud.md — companion mobile app, cloud backend, MQTT/CoAP/AMQP brokers, provisioning, OTA update.
10-iot-ot/05-ot-ics-recon.md — protocol identification (Modbus, DNP3, S7Comm, EtherNet/IP, BACnet, OPC UA), passive asset inventory.
10-iot-ot/06-ot-ics-attacks.md — protocol abuse, PLC reprogramming, project-file infection, HMI takeover, ATT&CK ICS techniques.

How to operate

Default to passive on OT. Active probing requires explicit ROE per device class. Even nmap version-detection has crashed PLCs.
Firmware path: extract (binwalk v3 / unblob) → filesystem analysis (firmwalker) → emulate (Firmadyne / QEMU) → static + dynamic. EMBA orchestrates this.
Hardware bench order: visual + datasheet → UART → JTAG/SWD → SPI flash dump → glitching/chip-off as last resort.
ICS protocol attacks: identify protocol first (passive), then map device → engineering tooling → project-file path. Engineering workstation compromise is the most common pivot — typically standard Windows compromise.
Companion app uses pentest-mobile; cloud backend uses pentest-cloud and pentest-web-api. Document SIS (Safety Instrumented Systems) architecture as a finding rather than testing the safety path.

When NOT to use

Companion mobile app only → pentest-mobile.
Cloud backend only → pentest-cloud.

Pre-conditions

Physical access to target device (or firmware download).
Hardware bench: bench supply, multimeter, logic analyzer, USB-UART, JTAGulator, OpenOCD-compatible adapter, SOIC clip, CH341A, hot-air rework.
Radio: HackRF One, RTL-SDR, BLE/Zigbee adapters as needed.
ROE explicitly covers permitted operations on PLCs.

OPSEC + Safety

OT systems are fragile and safety-critical. Loss-of-safety is OUT OF SCOPE outside permitted lab environments.
PLCs can crash on unexpected input — treat all active probing as potentially destructive.
Engineering workstation is the typical compromise pivot — Windows EDR considerations apply.

References inside the library

Tooling: tools/install-iot.md, tool-mappings/10-iot-ot-tools.md.
Frameworks: frameworks/owasp-fstm.md, frameworks/owasp-isvs.md, frameworks/mitre-attack-ics.md.
Cross-references: 02-mobile/ (companion app), 01-web-api/ + 06-cloud/ (backend).

More from this repository

same repository

engagement-management

thau0x01/ai-pentest-kb

Engagement-lifecycle management — pre-engagement scoping, ROE drafting, authorisation letters, threat modeling, CVSS scoring, finding write-up, executive summary, technical report, retest scoping, remediation validation. Use when the user mentions scope a pentest, ROE template, rules of engagement, get-out-of-jail letter, authorisation letter, scope statement, communications plan, blackout window, escalation matrix, threat modeling, STRIDE, PASTA, attack tree, threat actor profile, CVSS scoring, finding template, executive summary, technical report, retest, remediation validation, regression coverage, engagement kickoff, or evidence chain of custody.

2026-06-095

engagement-retest

thau0x01/ai-pentest-kb

Plan and execute a pentest retest — re-scope, re-execute the validation steps from prior findings, detect regressions, and write the retest report. Use when the user mentions retest, re-test, remediation validation, regression coverage, "verify the fixes", "validate remediation", retest scoping, retest report, posture trajectory, or compares "before vs after" findings.

2026-06-095

engagement-scoping

thau0x01/ai-pentest-kb

Drive the pre-engagement scoping conversation and produce the scope statement, Rules of Engagement, authorisation letter, and communications plan. Use when the user mentions kickoff, scoping a pentest, drafting ROE, rules of engagement, scope statement, authorisation letter, get-out-of-jail letter, communications plan, blackout window, escalation matrix, ROE drift, third-party hosting carve-out, social-engineering allowance, time-window restrictions, or evidence-handling rules.

2026-06-095

pentest-active-directory

thau0x01/ai-pentest-kb

Active Directory and hybrid Entra ID penetration testing. Use when the user mentions BloodHound, SharpHound, SOAPHound, AzureHound, RustHound, Kerberoast, AS-REP roast, Golden/Silver/Diamond/Sapphire ticket, DCSync, DCShadow, NTLM relay, ntlmrelayx, ADCS ESC1-ESC15+, EKUwu, Certipy, ACL abuse (GenericAll/WriteDACL/WriteOwner/shadow credentials), GPO abuse, NoPac, ZeroLogon, PetitPotam, DFSCoerce, PrinterBug, krbrelayup, AAD Connect, MSOL_, Pass-Through Auth, Seamless SSO, AdminSDHolder, SID History, krbtgt, or any "domain compromise" task.

2026-06-095

pentest-ai-llm

thau0x01/ai-pentest-kb

LLM-backed application, AI agent, and AI/ML supply-chain penetration testing. Use when the user mentions LLM pentest, AI red team, prompt injection (direct or indirect), jailbreak, DAN, Crescendo, GCG, many-shot jailbreak, system prompt leakage, RAG poisoning, embedding poisoning/inversion, vector DB attack, MCP / Model Context Protocol abuse, tool poisoning, agent excessive agency, function-call abuse, output handling chains (XSS/SSRF/SQLi via LLM output), training-data extraction, membership inference, modelscan/picklescan, Hugging Face poisoned model, garak, PyRIT, promptmap, Augustus, Spikee, OWASP LLM01-LLM10, MITRE ATLAS, or unbounded consumption / cost amplification.

2026-06-095

pentest-cheatsheet

thau0x01/ai-pentest-kb

Surface a one-page pentest cheatsheet for fast field recall. Use when the user asks for a "quick command", "cheatsheet", "one-liner", "what's the syntax for X", "remind me how to do Y", "give me the recon snippets", "AD cheatsheet", "lateral-movement one-liners", "AWS quick commands", "Azure quick commands", "mobile cheatsheet", "initial access cheatsheet", or any request that wants tools/commands without methodology overhead.

2026-06-095

name

pentest-iot-ot

description

Pentest — IoT / OT

Apply 10-iot-ot/ from the pentest-templates library.

Library root

$PENTEST_LIBRARY — caminho absoluto deste repositório clonado (definido pelo instalador; veja INSTALL.md).

Read 10-iot-ot/00-overview.md first.

Phase order

10-iot-ot/01-firmware-analysis.md — 9 stages of OWASP FSTM applied.
10-iot-ot/02-hardware-attacks.md — UART, JTAG, SWD, SPI/I2C, chip-off, glitching, side-channel, bootloader.
10-iot-ot/03-radio-rf.md — spectrum, modulation, replay, BLE, Zigbee, LoRa, Z-Wave, NFC, sub-GHz.
10-iot-ot/04-iot-app-cloud.md — companion mobile app, cloud backend, MQTT/CoAP/AMQP brokers, provisioning, OTA update.
10-iot-ot/05-ot-ics-recon.md — protocol identification (Modbus, DNP3, S7Comm, EtherNet/IP, BACnet, OPC UA), passive asset inventory.
10-iot-ot/06-ot-ics-attacks.md — protocol abuse, PLC reprogramming, project-file infection, HMI takeover, ATT&CK ICS techniques.

How to operate

Default to passive on OT. Active probing requires explicit ROE per device class. Even nmap version-detection has crashed PLCs.
Firmware path: extract (binwalk v3 / unblob) → filesystem analysis (firmwalker) → emulate (Firmadyne / QEMU) → static + dynamic. EMBA orchestrates this.
Hardware bench order: visual + datasheet → UART → JTAG/SWD → SPI flash dump → glitching/chip-off as last resort.
ICS protocol attacks: identify protocol first (passive), then map device → engineering tooling → project-file path. Engineering workstation compromise is the most common pivot — typically standard Windows compromise.
Companion app uses pentest-mobile; cloud backend uses pentest-cloud and pentest-web-api. Document SIS (Safety Instrumented Systems) architecture as a finding rather than testing the safety path.

When NOT to use

Companion mobile app only → pentest-mobile.
Cloud backend only → pentest-cloud.

Pre-conditions

Physical access to target device (or firmware download).
Hardware bench: bench supply, multimeter, logic analyzer, USB-UART, JTAGulator, OpenOCD-compatible adapter, SOIC clip, CH341A, hot-air rework.
Radio: HackRF One, RTL-SDR, BLE/Zigbee adapters as needed.
ROE explicitly covers permitted operations on PLCs.

OPSEC + Safety

OT systems are fragile and safety-critical. Loss-of-safety is OUT OF SCOPE outside permitted lab environments.
PLCs can crash on unexpected input — treat all active probing as potentially destructive.
Engineering workstation is the typical compromise pivot — Windows EDR considerations apply.

References inside the library

Tooling: tools/install-iot.md, tool-mappings/10-iot-ot-tools.md.
Frameworks: frameworks/owasp-fstm.md, frameworks/owasp-isvs.md, frameworks/mitre-attack-ics.md.
Cross-references: 02-mobile/ (companion app), 01-web-api/ + 06-cloud/ (backend).