Azure Audit Logs: User registered security info (authentication method change)

Flags Azure AD audit events where a user registers new authentication security info.

FreeReviewedSigma · Medium · v5
Product
azure
Service
auditlogs
Author
AlertIQ (SigmaHQ), DRL 1.1
Published
2021-10-10
Updated
2026-07-31

ATT&CK techniques

Persistence → Cred Access
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Discovery

  6. Lateral Movement

  7. Collection

  8. C2

  9. Exfiltration

  10. Impact

What it detects

This rule flags Azure audit log events where a user registers security info under the Authentication Methods service for UserManagement. Attackers may add or change authentication methods to maintain or extend access after initial compromise. Detection relies on Azure Audit Logs entries with LoggedByService set to Authentication Methods, along with the matching UserManagement category and operation name 'User registered security info'.

Related detections9 linkedT1098 — drag to rearrange
Suspicious AWS SAML Identity Provider Creation
Suspicious Okta Sign-On Policy Lifecycle Modification
Possible Shadow Credentials Abuse via msDS-KeyCredentialLink Modification
Suspicious Route53 Domain Transfer Lock Disabled via Scattered Spider Technique
Suspicious Domain Admin Account Creation via net (via process_creation)
Suspicious Guest Account Privilege Escalation (via process_creation)
Suspicious Login Shell Assigned to Service Account games on Linux
Suspicious NTLM Network Logon From Attacker Controlled Workstation Names (via security)
Suspicious dMSA Object Access with Migration AccessMask
Azure Audit Logs: User registered security info (authentication method change)
Pivot detection · T1098 · 9 related

Changelog

v5
  1. v5
    Candidate ingested via manual entry.2026-07-31
  2. v4
    Candidate ingested via manual entry.2026-07-31
  3. v3
    Candidate ingested via manual entry.2026-07-31
  4. v2
    Candidate ingested via manual entry.2026-07-31
  5. 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.