IMPORTANT: No additional bug fixes or documentation updates will be released for this version. For the latest information, see the current release documentation.
« Possible FIN7 DGA Command and Control Behavior Potential Abuse of Repeated MFA Push Notifications »
Elastic Docs ›Elastic Security Solution [8.2] ›Detections and alerts ›Prebuilt rule reference

Possible Okta DoS Attack

edit

Possible Okta DoS Attack

edit

Detects possible Denial of Service (DoS) attacks against an Okta organization. An adversary may attempt to disrupt an organization’s business operations by performing a DoS attack against its Okta service.

Rule type: query

Rule indices:

  • filebeat-*
  • logs-okta*

Severity: medium

Risk score: 47

Runs every: 5 minutes

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

Maximum alerts per execution: 100

References:

Tags:

  • Elastic
  • Identity
  • Okta
  • Continuous Monitoring
  • SecOps
  • Monitoring

Version: 6 (version history)

Added (Elastic Stack release): 7.9.0

Last modified (Elastic Stack release): 7.13.0

Rule authors: Elastic

Rule license: Elastic License v2

Investigation guide

edit
## Config

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

Rule query

edit
event.dataset:okta.system and
event.action:(application.integration.rate_limit_exceeded or
system.org.rate_limit.warning or system.org.rate_limit.violation or
core.concurrency.org.limit.violation)

Threat mapping

edit

Framework: MITRE ATT&CKTM

Rule version history

edit
Version 6 (7.13.0 release)
  • Formatting only
Version 5 (7.12.0 release)
  • Formatting only
Version 4 (7.11.2 release)
  • Formatting only
Version 3 (7.11.0 release)
  • Formatting only
Version 2 (7.10.0 release)

  • Updated query, changed from:

    event.module:okta and event.dataset:okta.system and
event.action:(application.integration.rate_limit_exceeded or
system.org.rate_limit.warning or system.org.rate_limit.violation or
core.concurrency.org.limit.violation)
« Possible FIN7 DGA Command and Control Behavior Potential Abuse of Repeated MFA Push Notifications »