M365 Audit: Successful Intune Company Portal login via Cmsi

Flags successful Company Portal (Intune) logins via Cmsi audit events that may indicate Conditional Access bypass attempts.

FreeReviewedSigma · High · v4
Product
m365
Service
audit
Author
Josh Nickels, Marius Rothenbücher (SigmaHQ), DRL 1.1
Published
2025-01-08
Updated
2026-07-31

ATT&CK techniques

Initial Access → Defense Evasion
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Defense Evasion

  6. Cred Access

  7. Discovery

  8. Lateral Movement

  9. Collection

  10. C2

  11. Exfiltration

  12. Impact

What it detects

This rule matches successful UserLoggedIn audit events for the Microsoft Intune Company Portal application when the request type is Cmsi:Cmsi. Such logins may be used to gain access that depends on Conditional Access and Intune device trust state, making them relevant to attacker attempts to bypass policy controls. It relies on M365 audit telemetry fields including Operation, ApplicationId, ResultStatus, RequestType, and the ObjectId filter used to narrow the event scope.

Related detections9 linkedT1078 — drag to rearrange
Suspicious SonicWall NetExtender VPN Command-Line Authentication with Always-Trust (via process_creation)
Suspicious Self-Hosted GitHub Actions Runner Started As Root via Shell (via process_creation)
Suspicious Login Shell Assigned to Service Account games on Linux
Suspicious SSH Daemon Configuration Change Enabling Root Login
Suspicious NTLM Network Logon From Attacker Controlled Workstation Names (via security)
Suspicious dMSA Object Access with Migration AccessMask
Malicious ESX Admins Group Added to Privileged Directory Group
Malicious ESX Admins Group Creation via WinRM Host
Suspicious BrightMetricAgent Remote Tool Execution Associated With Volt Typhoon
M365 Audit: Successful Intune Company Portal login via Cmsi
Pivot detection · T1078 · 9 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.