Share via

Defender for IoT devices custom security alerts

  • Article

Defender for IoT continuously analyzes your IoT solution using advanced analytics and threat intelligence to alert you to malicious activity.

We encourage you to create custom alerts based on your knowledge of expected device behavior to ensure alerts act as the most efficient indicators of potential compromise in your unique organizational deployment and landscape.

The following lists of Defender for IoT alerts are definable by you based on your expected IoT device behavior. For more information about how to customize each alert, see create custom alerts.

Agent-based security custom alerts

Severity Alert name Data source Description Suggested remediation
Low Custom alert - The number of active connections is outside the allowed range Legacy Defender-IoT-micro-agent, Eclipse ThreadX Number of active connections within a specific time window is outside the currently configured and allowable range. Investigate the device logs. Learn where the connection originated and determine if it's benign or malicious. If malicious, remove possible malware and understand source. If benign, add the source to the allowed connection list.
Low Custom alert - The outbound connection created to an IP that isn't allowed Legacy Defender-IoT-micro-agent, Eclipse ThreadX An outbound connection was created to an IP that is outside your allowed IP list. Investigate the device logs. Learn where the connection originated and determine if it's benign or malicious. If malicious, remove possible malware and understand source. If benign, add the source to the allowed IP list.
Low Custom alert - The number of failed local logins is outside the allowed range Legacy Defender-IoT-micro-agent, Eclipse ThreadX The number of failed local logins within a specific time window is outside the currently configured and allowable range.
Low Custom alert - The sign in of a user that isn't on the allowed user list Legacy Defender-IoT-micro-agent, Eclipse ThreadX A local user outside your allowed user list, logged in to the device. If you're saving raw data, navigate to your log analytics account and use the data to investigate the device, identify the source, and then fix the allow/block list for those settings. If you aren't currently saving raw data, go to the device and fix the allow/block list for those settings.
Low Custom alert - A process was executed that isn't allowed Legacy Defender-IoT-micro-agent, Eclipse ThreadX A process that isn't allowed was executed on the device. If you're saving raw data, navigate to your log analytics account and use the data to investigate the device, identify the source, and then fix the allow/block list for those settings. If you aren't currently saving raw data, go to the device and fix the allow/block list for those settings.

Next steps