1200kmSECURITY RESEARCH

1200KM / sigma-rule

Change to Authentication Method — Sigma Rule

Sigma rule 4d78a000-ab52-4564-88a5-7ab5242b20c7. Change to Authentication Method — Sigma Rule. Change to authentication method could be an indicator of an attacker adding an auth method to the account so they can have continued access.

Rule metadata and linked tags

Author: AlertIQ. Source status: test; severity: medium. Source dates: 2021-10-10 / 2022-12-25.

Original logsource
{
  "product": "azure",
  "service": "auditlogs"
}

Pinned original Sigma rule · Detection Rule License 1.1

Source SHA-256: b5f0dda93aa123d14cb73c0f5bf81be94be2b4df18a1bba211db8db4e16eb662

Detection logic

Original source YAML. Source-tag agreement is not proof of complete semantic coverage. This rule has not been compiled for a SIEM backend or validated against live telemetry here.

Original Sigma rule YAML, scroll horizontally if needed
title: Change to Authentication Method
id: 4d78a000-ab52-4564-88a5-7ab5242b20c7
status: test
description: Change to authentication method could be an indicator of an attacker adding an auth method to the account so they can have continued access.
references:
    - https://learn.microsoft.com/en-us/entra/architecture/security-operations-privileged-accounts
author: AlertIQ
date: 2021-10-10
modified: 2022-12-25
tags:
    - attack.privilege-escalation
    - attack.credential-access
    - attack.defense-impairment
    - attack.t1556
    - attack.persistence
    - attack.t1098
logsource:
    product: azure
    service: auditlogs
detection:
    selection:
        LoggedByService: 'Authentication Methods'
        Category: 'UserManagement'
        OperationName: 'User registered security info'
    condition: selection
falsepositives:
    - Unknown
level: medium

Original YAML and metadata in JSON

False positives

  • Unknown

Source references

Connected ecosystem references

Exact source-tagged techniques

Telemetry review

Read the original logsource above, then inspect the linked detection workspaces for technique-level sensor context. No per-rule telemetry equivalence is inferred.

Pinned research references. No browser attack runner or production-validated detector is asserted. Imported procedures remain unvalidated; any bounded lab evidence has its own scope. ATT&CK / Atomic provenance · Detection provenance.