Microsoft Cloud App Security: Activity from Microsoft Threat Intelligence Risky IPs

Alert on successful Cloud App Security activity events tied to IPs marked risky by Microsoft Threat Intelligence.

FreeReviewedSigma · Medium · v4
Product
m365
Service
threat_detection
Author
Austin Songer @austinsonger (SigmaHQ), DRL 1.1
Published
2021-08-23
Updated
2026-07-31

ATT&CK techniques

C2
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Priv Esc

  7. Defense Evasion

  8. Cred Access

  9. Discovery

  10. Lateral Movement

  11. Collection

  12. Exfiltration

  13. Impact

What it detects

This rule matches Microsoft Cloud App Security threat detection events indicating successful activity from IP addresses marked as risky by Microsoft Threat Intelligence. Such IPs are associated with malicious infrastructure (for example, botnet command-and-control) and may suggest account compromise or automated abuse. It relies on SecurityComplianceCenter activity telemetry carrying the event name and success status.

Related detections7 linkedT1573 — drag to rearrange
Suspicious Cobalt Strike Download Profile POST to pkg Path
Possible SPECTRALVIPER C2 Communication via Crafted Consent Cookie Values
Malicious OysterLoader C2 Beacon Using WordPressAgent User Agent
Windows curl.exe SOCKS Proxy and .onion Command-Line Execution
Windows PowerShell: Suspicious SslStream Client Certificate Validation in Script Block
Microsoft Cloud App Security: Alerts for Successful Activity from Infrequent Countries
M365 Threat Management: Activity from Anonymous Proxy IP Addresses
Microsoft Cloud App Security: Activity from Microsoft Threat Intelligence Risky IPs
Pivot detection · T1573 · 7 related

Changelog

v4
  1. v4
    Candidate ingested via manual entry.2026-07-31
  2. v3
    Candidate ingested via manual entry.2026-07-31
  3. v2
    Candidate ingested via manual entry.2026-07-31
  4. v1
    No changelog recorded for this version.2026-07-30

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