performing-iot-security-assessment

Featured

Performs comprehensive security assessments of IoT devices and their ecosystems by testing hardware interfaces, firmware, network communications, cloud APIs, and companion mobile applications. The tester uses firmware extraction and analysis, hardware debugging via UART and JTAG, network protocol analysis, and runtime exploitation to identify vulnerabilities across all layers of the IoT stack. Activates for requests involving IoT security testing, embedded device assessment, firmware security analysis, or smart device penetration testing.

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

# Performing IoT Security Assessment ## When to Use - Evaluating the security of IoT devices before deployment in enterprise or critical infrastructure environments - Assessing consumer IoT products for security vulnerabilities as part of product security review or certification - Testing industrial IoT (IIoT) devices for vulnerabilities that could affect operational technology environments - Analyzing firmware for backdoors, hardcoded credentials, and known vulnerabilities in embedded components - Evaluating the security of the complete IoT ecosystem including device, cloud backend, and mobile companion app **Do not use** against IoT devices without written authorization, for modifying firmware on devices you do not own, or against medical devices or safety-critical systems without specific medical device testing authorization and safety protocols. ## Prerequisites - Physical access to the target IoT device(s) for hardware analysis and testing - Hardware tools: USB-to-UART adapter (FTDI), Bus Pirate, logic analyzer, JTAG debugger (Segger J-Link), SPI flash programmer (CH341A) - Firmware analysis tools: Binwalk, Firmwalker, Firmware Analysis Toolkit (FAT), Ghidra, QEMU for emulation - Network analysis: Wireshark, tcpdump, Bluetooth tools (Ubertooth, nRF Connect), Zigbee tools (KillerBee) - Soldering equipment for accessing hardware debug points if needed ## Workflow ### Step 1: Device Reconnaissance and Hardware Analysis Examine the physical device and identify attack...

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

Data & Documents Listed

offensive-iot

IoT and embedded device security testing methodology. Covers hardware reconnaissance (UART, JTAG, SWD, SPI flash, I2C EEPROM, eMMC chip-off), firmware acquisition (vendor portals, OTA capture, flash dump, binwalk extraction), firmware analysis (filesystem mounting, binary triage, hardcoded secrets, default credential discovery), bootloader attacks (U-Boot console, secure-boot bypass, fault injection), runtime attacks on embedded Linux/RTOS (busybox CVEs, MTD writes, /dev/mem), wireless protocol attacks (Zigbee, BLE, Z-Wave, LoRaWAN, Thread/Matter, sub-GHz), MQTT/CoAP/Modbus/BACnet/OPC-UA exploitation, mobile companion app analysis, cloud-IoT API abuse, and side-channel/glitching basics. Use for IoT pentest, smart-home assessment, ICS/OT testing, or embedded vulnerability research.

719 Updated 3 months ago
0xwilliamortiz
Data & Documents Featured

offensive-iot

IoT and embedded device security testing methodology. Covers hardware reconnaissance (UART, JTAG, SWD, SPI flash, I2C EEPROM, eMMC chip-off), firmware acquisition (vendor portals, OTA capture, flash dump, binwalk extraction), firmware analysis (filesystem mounting, binary triage, hardcoded secrets, default credential discovery), bootloader attacks (U-Boot console, secure-boot bypass, fault injection), runtime attacks on embedded Linux/RTOS (busybox CVEs, MTD writes, /dev/mem), wireless protocol attacks (Zigbee, BLE, Z-Wave, LoRaWAN, Thread/Matter, sub-GHz), MQTT/CoAP/Modbus/BACnet/OPC-UA exploitation, mobile companion app analysis, cloud-IoT API abuse, and side-channel/glitching basics. Use for IoT pentest, smart-home assessment, ICS/OT testing, or embedded vulnerability research.

11,204 Updated yesterday
SnailSploit
AI & Automation Listed

harden-iot

Harden IoT and embedded devices against firmware tampering, hardware-interface abuse, and RTOS/ICS compromise: firmware replacement, root shells on open UART or JTAG/SWD ports, unlocked bootloader consoles, default credentials, and unauthorized commands or program downloads over Modbus, DNP3, S7comm, and MQTT (MITRE ATT&CK T1542, T1542.001, T1495, T1200, T1078.001; ICS T1693.001, T1693.002, T1694.001, T0843, T1692.001, T0848). Signals: firmware and boot telemetry (verified boot, OTA signature checks, TPM attestation), device console syslog, OT network monitoring (Zeek, Mosquitto), and Microsoft Defender for IoT alerts. Gives a hunt and a hardening plan mapped to ISO 27001, NIST CSF, and the Essential Eight. Use when hardening an IoT or embedded fleet, locking down debug ports and bootloader consoles, enforcing signed firmware and secure boot, hunting unauthorized PLC program downloads or rogue Modbus writes, or triaging Defender for IoT alerts.

0 Updated 5 days ago
umbrasec-labs