TECH NEWS

Speaking Siemens S7comm: Protocol Mechanics and Security Boundaries

https://hackernoon.imgix.net/images/PMUKGjUIQmgkJbHTCnFk64jn7ds1-c9d2ath.png

S7comm is one of those protocols that looks simple until you start following the conversation all the way down. At first, there is just a TCP connection to port 102, then TPKT appears, then COTP, then Siemens-specific connection parameters, then the S7comm session has its own negotiation, then a memory address becomes meaningful, then a single function code can turn a packet from a read request into a write operation. That was exactly what I wanted to investigate.

After working through Modbus TCP, EtherNet/IP, DNP3, BACnet, OPC UA, IEC 104, IEC 61850, and PROFINET, S7comm felt like the right protocol to finish this part of the research with. The laboratory target was a Snap7 server exposing a Siemens S7-style communication interface on TCP/102. I built the research client myself, constructed the protocol messages, captured the exchanges, and then started deliberately deviating from the expected conversation, and that ended up being...

Copyright of this story solely belongs to hackernoon.com. To see the full text click HERE

Read more

https://www.reuters.com/resizer/v2/JBJ4CBBSQFOF3AIWU54BZ5CG3A.jpg?auth=20a95c7d39f738bcb2ddc30ebce249900d9b76acde0304cdaad76d9d2cc34fc9&height=1005&width=1920&quality=80&smart=true

A Delaware jury awards Qualcomm $2 in nominal damages after finding Arm breached its architectural license agreement and sought to disrupt Qualcomm's business

Featured Podcasts Training Data: David Silver and Lasse Espeholt of Ineffable Intelligence: A Superlearner for the Age of Experience Sequoia Capital partners host conversations with leading AI builders and researchers to develop a deeper understanding of the evolving technologies and their implications. Subscribe to Training Data. Invest Like the Best: