You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
These are hard without some actual logs to base things off of, but we could be generic from the point of looking at the entities it's pulling out (should this incident occur). As such, we could frame it from check the IPs (as per norm), the remediation steps, whether the protocol should be in use with the device, etc.
Remediation would potentially involve blocking the IP(s), adding firewall exclusions, etc.
Alternatively we could put those that we can't yet have confidence in the automation rule into a TBC group?
Related to #20
Unsure how to handle Defender for IoT incidents.
Rule appears to be triggered be creation of multiple other login related incidents/alerts
KQL from https://github.com/Azure/Azure-Sentinel/blob/735a9d926d0feb726ecea6fdcbbab09b43fdbb8f/Solutions/IoTOTThreatMonitoringwithDefenderforIoT/Analytic%20Rules/IoTExcessiveLoginAttempts.yaml#L8
The text was updated successfully, but these errors were encountered: