Rethinking Threat ID: 31671 (SCADA ICCP Unauthorized COTP Connection) — Is This Really Malicious?

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Rethinking Threat ID: 31671 (SCADA ICCP Unauthorized COTP Connection) — Is This Really Malicious?

L0 Member

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.

0 REPLIES 0
  • 31 Views
  • 0 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

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!