ics-protocols-s7comm
Ics Ics Protocols S7Comm.
- License 许可
- MIT
- 最近更新
- 2026-09-01
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- ics-protocols-s7comm
- domain
- cybersecurity
- description
- Ics Ics Protocols S7Comm.
02 资源文件 5
- 参考文档index.json1.1 KB
- 参考文档references/api-reference.md2.3 KB
- 参考文档references/index.json84 B
- 脚本scripts/agent.py6.1 KB
- 脚本scripts/index.json84 B
03 SKILL.md 正文
| | S7comm | Siemens proprietary protocol for communication with SIMATIC S7 PLCs over TCP port 102, layered on COTP/TPKT | | S7CommPlus | Enhanced version of S7comm used by S7-1200/1500 with integrity protection mechanisms | | ROSCTR | Remote Operating Service Control field in S7comm header indicating PDU type (Job, Ack, Ack_Data, Userdata) | | TIA Portal | Totally Integrated Automation Portal -- Siemens engineering software for programming S7 PLCs | | CPU Stop (0x29) | S7comm function that halts PLC program execution, a critical denial-of-service operation | | Program Download (0x1A) | S7comm function initiating transfer of new control logic to a PLC, representing the highest risk operation |
Common Scenarios
Scenario: Unauthorized PLC Program Modification
Context: A Dragos sensor alerts on S7comm program download traffic from an IP address that is not the authorized TIA Portal engineering workstation.
Approach:
- Capture the complete S7comm session for forensic analysis
- Identify the source host and determine if it is compromised or rogue
- Compare the current PLC program against the last known-good backup
- Check if the PLC CPU mode was changed (RUN to STOP to PROGRAM)
- If the program was modified, restore from verified backup
- Investigate the attack chain -- how did the attacker reach the S7comm network segment
- Implement S7comm access protection (know-how protection, access passwords) on all PLCs
Pitfalls: S7-300/400 PLCs have no cryptographic integrity protection -- any device that can reach TCP port 102 can send commands. Do not rely solely on PLC passwords as they are transmitted in cleartext in S7comm (not S7CommPlus). Network segmentation is the primary defense.
Output Format
S7COMM SECURITY ANALYSIS REPORT
===================================
Date: YYYY-MM-DD
Scope: [Network segments analyzed]
SESSION INVENTORY:
Engineering stations: [count and IPs]
PLCs communicating: [count and IPs]
Unauthorized sources: [count]
CRITICAL FINDINGS:
CPU Stop commands: [count]
Program downloads: [count from unauthorized sources]
Replay attack potential: [assessment]
VULNERABILITY ASSESSMENT:
S7-300/400 (no integrity): [count of affected PLCs]
S7-1200/1500 (S7CommPlus): [firmware assessment]
Known CVEs applicable: [list]
RECOMMENDATIONS:
1. [Highest priority remediation]
2. [Network segmentation improvement]
3. [Monitoring enhancement]
04 同仓库更多 Skills
services-wmi-persistence-detect
Detect WMI event subscription persistence by enumerating ActiveScriptEventConsumer, CommandLineEventConsumer, and permanent subscriptions in the WMI repository.
services-wmi-exec-exploit
Perform lateral movement across Windows networks using WMI-based remote execution techniques including Impacket wmiexec.py, CrackMapExec, and native WMI commands for stealthy post-exploitation during red team engagements.
registry-artifact-extract
Extract and analyze Windows Registry hives to uncover user activity, installed software, autostart entries, and evidence of system compromise.
processes-token-impersonate-detect
Detect Windows token impersonation and privilege abuse including SeImpersonatePrivilege exploitation via Potato attacks and token stealing techniques.
processes-thread-injection-detect
Detect Windows thread injection techniques including CreateRemoteThread, QueueUserAPC, NtCreateThreadEx, and thread hijacking via process memory analysis.
processes-hollow-technique-detect
Detect process hollowing (RunPE) by identifying processes with mismatched image paths between PEB and VAD tree, or unmapped PE headers in memory.