Elastic low stable kql
Multiple Okta User Authentication Events with Same Device Token Hash
Detects when a high number of Okta user authentication events are reported for multiple users in a short time frame. Adversaries may attempt to launch a credential stuffing or password spraying attack from the same device by using a list of known usernames and passwords to gain unauthorized access to user accounts.
Detection Logic
from logs-okta*
| where
data_stream.dataset == "okta.system" and
(event.action like "user.authentication.*" or event.action == "user.session.start") and
okta.debug_context.debug_data.dt_hash != "-" and
okta.outcome.reason == "INVALID_CREDENTIALS"
| keep
event.action,
okta.debug_context.debug_data.dt_hash,
okta.actor.id,
okta.actor.alternate_id,
okta.outcome.reason
| stats
Esql.okta_actor_id_count_distinct = count_distinct(okta.actor.id)
by
okta.debug_context.debug_data.dt_hash,
okta.actor.alternate_id
| where
Esql.okta_actor_id_count_distinct > 20
| sort
Esql.okta_actor_id_count_distinct desc False Positives
- ⚠ Users may share an endpoint related to work or personal use in which separate Okta accounts are used.
- ⚠ Shared systems such as Kiosks and conference room computers may be used by multiple users.
Field Validations
Loading…
Comments (0)
Loading comments...