Try in Splunk Security Cloud

Description

The following analytic detects the registration of a new Multi-Factor Authentication (MFA) method for a user account in Azure Active Directory. It leverages Azure AD audit logs to identify changes in MFA configurations. This activity is significant because adding a new MFA method can indicate an attacker's attempt to maintain persistence on a compromised account. If confirmed malicious, the attacker could bypass existing security measures, solidify their access, and potentially escalate privileges, access sensitive data, or make unauthorized changes. Immediate verification and remediation are required to secure the affected account.

  • Type: TTP
  • Product: Splunk Enterprise, Splunk Enterprise Security, Splunk Cloud
  • Datamodel: Authentication
  • Last Updated: 2024-05-16
  • Author: Mauricio Velazco, Splunk
  • ID: 0488e814-eb81-42c3-9f1f-b2244973e3a3

Annotations

ATT&CK

ATT&CK

ID Technique Tactic
T1098 Account Manipulation Persistence, Privilege Escalation
T1098.005 Device Registration Persistence, Privilege Escalation
Kill Chain Phase
  • Installation
  • Exploitation
NIST
  • DE.CM
CIS20
  • CIS 10
CVE 


1
2
3
4
5
6
7
8
9
10
11
12
13
14



`azure_monitor_aad`  operationName="Update user" 
| rename properties.* as *  
| eval propertyName = mvindex('targetResources{}.modifiedProperties{}.displayName', 0) 
| search propertyName = StrongAuthenticationMethod 
| eval oldvalue = mvindex('targetResources{}.modifiedProperties{}.oldValue',0) 
| eval newvalue = mvindex('targetResources{}.modifiedProperties{}.newValue',0) 
| rex field=newvalue max_match=0 "(?i)(?<new_method_type>\"MethodType\")" 
| rex field=oldvalue max_match=0 "(?i)(?<old_method_type>\"MethodType\")" 
| eval count_new_method_type = coalesce(mvcount(new_method_type), 0) 
| eval count_old_method_type = coalesce(mvcount(old_method_type), 0) 
| stats earliest(_time) as firstTime latest(_time) as lastTime values(propertyName) by user newvalue oldvalue 
| `security_content_ctime(firstTime)` 
| `security_content_ctime(lastTime)` 
| `azure_ad_new_mfa_method_registered_filter`

Macros

The SPL above uses the following Macros:

:information_source: azure_ad_new_mfa_method_registered_filter is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.

Required fields

List of fields required to use this analytic.

  • _time
  • operationName
  • properties.targetResources{}.modifiedProperties{}.displayName
  • properties.targetResources{}.modifiedProperties{}.oldValue
  • properties.targetResources{}.modifiedProperties{}.newValue
  • user

How To Implement

You must install the latest version of Splunk Add-on for Microsoft Cloud Services from Splunkbase (https://splunkbase.splunk.com/app/3110/#/details). You must be ingesting Azure Active Directory events into your Splunk environment through an EventHub. This analytic was written to be used with the azure:monitor:aad sourcetype leveraging the AuditLog log category.

Known False Positives

Users may register MFA methods legitimally, investigate and filter as needed.

Associated Analytic Story

RBA

Risk Score Impact Confidence Message
30.0 60 50 A new MFA method was registered for user $user$

:information_source: The Risk Score is calculated by the following formula: Risk Score = (Impact * Confidence/100). Initial Confidence and Impact is set by the analytic author.

Reference

Test Dataset

Replay any dataset to Splunk Enterprise by using our replay.py tool or the UI. Alternatively you can replay a dataset into a Splunk Attack Range

source | version: 3