IMPORTANT: No additional bug fixes or documentation updates
will be released for this version. For the latest information, see the
current release documentation.
Possible Okta DoS Attack
editPossible Okta DoS Attack
editAn adversary may attempt to disrupt an organization’s business operations by performing a denial of service (DoS) attack against its Okta infrastructure.
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: 4 (version history)
Added (Elastic Stack release): 7.9.0
Last modified (Elastic Stack release): 7.11.2
Rule authors: Elastic
Rule license: Elastic License
Investigation guide
editThe Okta Filebeat module must be enabled to use this rule.
Rule query
editevent.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
editFramework: MITRE ATT&CKTM
-
Tactic:
- Name: Impact
- ID: TA0040
- Reference URL: https://attack.mitre.org/tactics/TA0040/
-
Technique:
- Name: Network Denial of Service
- ID: T1498
- Reference URL: https://attack.mitre.org/techniques/T1498/
Rule version history
edit- 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)
-