Try in Splunk Security Cloud

Description

The following analytic identifies an authentication attempt event against an Azure AD tenant that fails during the Multi Factor Authentication challenge. This behavior may represent an adversary trying to authenticate with compromised credentials. In some cases, adversaries may continuously repeat login attempts in order to bombard users with MFA push notifications, SMS messages, and phone calls, potentially resulting in the user finally accepting the authentication request.

  • Type: TTP

  • Product: Splunk Enterprise, Splunk Enterprise Security, Splunk Cloud

  • Last Updated: 2022-07-14
  • Author: Mauricio Velazco, Splunk
  • ID: e62c9c2e-bf51-4719-906c-3074618fcc1c

Annotations

ATT&CK

ATT&CK

ID Technique Tactic
T1078 Valid Accounts Defense Evasion, Persistence, Privilege Escalation, Initial Access
T1078.004 Cloud Accounts Defense Evasion, Persistence, Privilege Escalation, Initial Access
T1621 Multi-Factor Authentication Request Generation Credential Access
Kill Chain Phase
  • Exploitation
NIST
  • DE.CM
CIS20
  • CIS 3
  • CIS 5
  • CIS 16
CVE 


1
2
3
4



 `azuread` body.category=SignInLogs body.properties.status.errorCode=500121 
| rename body.properties.* as * 
| stats values(userPrincipalName) by _time, ipAddress, status.additionalDetails, appDisplayName, userAgent 
| `azure_ad_authentication_failed_during_mfa_challenge_filter`

Macros

The SPL above uses the following Macros:

:information_source: azure_ad_authentication_failed_during_mfa_challenge_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
  • body.category
  • body.properties.status.errorCode
  • body.properties.userPrincipalName
  • body.properties.ipAddress
  • body.properties.status.additionalDetails
  • body.properties.appDisplayName
  • body.properties.userAgent

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. You must be ingesting Azure Active Directory events in your Splunk environment. Specifically, this analytic leverages the RiskyUsers and UserRiskEvents log category.

Known False Positives

Legitimate users may miss to reply the MFA challenge within the time window or deny it by mistake.

Associated Analytic Story

RBA

Risk Score Impact Confidence Message
54.0 60 90 User $body.properties.userPrincipalName$ failed to pass MFA challenge

: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: 1