Try in Splunk Security Cloud

Description

The following analytic identifies a successful authentication event against Azure Active Directory for an account without Multi-Factor Authentication enabled. This could be evidence of a missconfiguration, a policy violation or an account take over attempt that should be investigated

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

  • Last Updated: 2022-07-12
  • Author: Mauricio Velazco, Splunk
  • ID: a560e7f6-1711-4353-885b-40be53101fcd

Annotations

ATT&CK

ATT&CK

ID Technique Tactic
T1586 Compromise Accounts Resource Development
T1586.003 Cloud Accounts Resource Development
T1078 Valid Accounts Defense Evasion, Persistence, Privilege Escalation, Initial Access
T1078.004 Cloud Accounts Defense Evasion, Persistence, Privilege Escalation, Initial 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.authenticationRequirement=singleFactorAuthentication body.properties.authenticationDetails{}.succeeded=true 
| rename body.properties.* as * 
|  stats values(userPrincipalName) by _time, ipAddress, appDisplayName, authenticationRequirement 
| `azure_ad_successful_single_factor_authentication_filter`

Macros

The SPL above uses the following Macros:

:information_source: azure_ad_successful_single-factor_authentication_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.authenticationRequirement
  • body.properties.authenticationDetails
  • body.properties.userPrincipalName
  • body.properties.ipAddress
  • body.properties.appDisplayName

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 in your Splunk environment. Specifically, this analytic leverages the SignInLogs log category.

Known False Positives

Although not recommended, certain users may be required without multi-factor authentication. Filter as needed

Associated Analytic Story

RBA

Risk Score Impact Confidence Message
45.0 50 90 Successful authentication for user $body.properties.userPrincipalName$ without MFA

: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