Try in Splunk Security Cloud

Description

This analytic detects the registration of a new Multi-Factor Authentication (MFA) method associated with a user account within Azure Active Directory by monitoring Azure AD audit logs and configurations. While adding a new MFA method can be a routine and legitimate action, it can also be indicative of an attacker's attempt to maintain persistence on a compromised account. By registering a new MFA method, attackers can potentially bypass existing security measures, allowing them to authenticate using stolen credentials without raising alarms. Monitoring for such changes is crucial, especially if the addition is not preceded by a user request or if it deviates from typical user behavior. If an attacker successfully registers a new MFA method on a compromised account, they can solidify their access, making it harder for legitimate users to regain control. The attacker can then operate with the privileges of the compromised account, potentially accessing sensitive data, making unauthorized changes, or even escalating their privileges further. Immediate action would be required to verify the legitimacy of the MFA change and, if malicious, to remediate and secure the affected account.

  • Type: TTP
  • Product: Splunk Enterprise, Splunk Enterprise Security, Splunk Cloud
  • Datamodel: Authentication
  • Last Updated: 2023-12-20
  • 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: 2