Suspicious Sign-In via Legacy Authentication Protocol (via signinlogs)

PremiumReviewedSigma · Medium · v1
Product
azure
Service
signinlogs
Author
HuntRule
Published
2026-11-06
Updated
2026-11-06

ATT&CK techniques

Initial Access → Defense Evasion
  1. Recon

  2. Resource Dev

  3. Execution

  4. Cred Access

  5. Discovery

  6. Lateral Movement

  7. Collection

  8. C2

  9. Exfiltration

  10. Impact

What it detects

This rule detects successful Azure AD sign-ins over legacy authentication clients such as IMAP, POP, SMTP or other basic-auth endpoints, which cannot enforce multifactor authentication and are targeted to bypass conditional-access controls. Legacy-auth abuse is tracked in the Red Canary Threat Detection Report cloud coverage. Detecting these sign-ins surfaces an MFA-evading access path.

Related detections9 linkedT1078.004 — drag to rearrange
Malicious Context.ai OAuth Service Principal by App Owner Organization (via azure)
Suspicious ECS ExecuteCommand Lateral Movement via SSM in AWS CloudTrail (via cloudtrail)
Suspicious AWS SES CreateEmailIdentity Following Key Compromise (Cloud Email Abuse)
Malicious Bapak AWS EKS CreateCluster With Known Cluster Name via CloudTrail
Malicious AWS IAM User Creation With Known Threat Actor Names
Suspicious AWS API Activity From S3 Browser Client User-Agent
Suspicious AWS API Activity From WinSCP Client User-Agent
Suspicious EKS Access Entry Creation via CloudTrail
Suspicious Azure CLI Service Principal Login with Inline Secret
Suspicious Sign-In via Legacy Authentication Protocol (via signinlogs)
Pivot detection · T1078.004 · 9 related

Detection content is published as a reviewed draft. Tune thresholds and exclusions against your own telemetry before enabling this rule for alerting.