IMPORTANT: No additional bug fixes or documentation updates will be released for this version. For the latest information, see the current release documentation.
« NullSessionPipe Registry Modification Okta Brute Force or Password Spraying Attack »
Elastic Docs ›Elastic Security Solution [7.14] ›Detections and alerts ›Prebuilt rule reference

O365 Excessive Single Sign-On Logon Errors

edit

O365 Excessive Single Sign-On Logon Errors

edit

Identifies accounts with a high number of single sign-on (SSO) logon errors. Excessive logon errors may indicate an attempt to brute force a password or single sign-on token.

Rule type: threshold

Rule indices:

  • filebeat-*
  • logs-o365*

Severity: high

Risk score: 73

Runs every: 5 minutes

Searches indices from: now-20m (Date Math format, see also Additional look-back time)

Maximum alerts per execution: 100

Tags:

  • Elastic
  • Cloud
  • Microsoft 365
  • Continuous Monitoring
  • SecOps
  • Identity and Access

Version: 1

Added (Elastic Stack release): 7.14.0

Rule authors: Elastic, Austin Songer

Rule license: Elastic License v2

Potential false positives

edit

Automated processes that attempt to authenticate using expired credentials and unbounded retries may lead to false positives.

Investigation guide

edit

Config

The Microsoft 365 Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.

Rule query

edit
event.dataset:o365.audit and event.provider:AzureActiveDirectory and
event.category:web and
o365.audit.LogonError:"SsoArtifactInvalidOrExpired"

Threat mapping

edit

Framework: MITRE ATT&CKTM

« NullSessionPipe Registry Modification Okta Brute Force or Password Spraying Attack »