- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
08-19-2026 10:13 PM
When reviewing security alerts, context is everything. Take Threat ID: 31671 ("SCADA ICCP Unauthorized COTP Connection Established"), for instance. The current description simply states: "This alert indicates that an ICCP client has successfully connected using OSI Connection Oriented Transport Protocol."
While seeing a successful connection pop up in an alert is certainly helpful for asset visibility, the description leaves a massive gap: it fails to explain what actually makes the event malicious or risky. A successful COTP (Connection-Oriented Transport Protocol) handshake on its own is just a normal network event—it happens every time legitimate control systems communicate. Without additional context—such as whether the source IP address is unauthorized, if the connection violates segmentation policies, or if it deviates from established baseline behavior—this alert risks becoming just another piece of alert fatigue.
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!

