Try in Splunk Security Cloud

Description

This search detects accounts with high number of Single Sign ON (SSO) logon errors. Excessive logon errors may indicate attempts to bruteforce of password or single sign on token hijack or reuse.

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

  • Last Updated: 2021-01-26
  • Author: Rod Soto, Splunk
  • ID: 8158ccc4-6038-11eb-ae93-0242ac130002

Annotations

ATT&CK
ID Technique Tactic
T1556 Modify Authentication Process Credential Access, Defense Evasion, Persistence
Kill Chain Phase
  • Exploitation
NIST
CIS20
CVE
1
2
3
4
5
6
`o365_management_activity`  Workload=AzureActiveDirectory LogonError=SsoArtifactInvalidOrExpired 
| stats count min(_time) as firstTime max(_time) as lastTime by LogonError ActorIpAddress UserAgent UserId 
| where count > 5 
| `security_content_ctime(firstTime)`
| `security_content_ctime(lastTime)` 
| `o365_excessive_sso_logon_errors_filter`

Macros

The SPL above uses the following Macros:

Note that o365_excessive_sso_logon_errors_filter is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.

Required field

  • _time
  • Workload
  • LogonError
  • ActorIpAddress
  • UserAgent
  • UserId

How To Implement

You must install splunk Microsoft Office 365 add-on. This search works with o365:management:activity

Known False Positives

Logon errors may not be malicious in nature however it may indicate attempts to reuse a token or password obtained via credential access attack.

Associated Analytic story

RBA

Risk Score Impact Confidence Message
64.0 80 80 User $UserId$ has caused excessive number of SSO logon errors from $ActorIpAddress$ using UserAgent $UserAgent$.

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