from logs-okta*
| where
event.dataset == "okta.system" and
not event.action in (
"policy.evaluate_sign_on",
"user.session.start",
"user.authentication.sso"
) and
okta.actor.alternate_id != "system@okta.com" and
okta.actor.alternate_id rlike "[^@\s]+\@[^@\s]+" and
okta.authentication_context.external_session_id != "unknown"
| keep
event.action,
okta.actor.alternate_id,
okta.authentication_context.external_session_id,
okta.debug_context.debug_data.dt_hash
| stats
Esql.okta_debug_context_debug_data_dt_hash_count_distinct = count_distinct(okta.debug_context.debug_data.dt_hash)
by
okta.actor.alternate_id,
okta.authentication_context.external_session_id
| where
Esql.okta_debug_context_debug_data_dt_hash_count_distinct >= 2
| sort
Esql.okta_debug_context_debug_data_dt_hash_count_distinct desc
Install detection rules in Elastic Security
Detect Multiple Device Token Hashes for Single Okta Session in the Elastic Security detection engine by installing this rule into your Elastic Stack.
To setup this rule, check out the installation guide for Prebuilt Security Detection Rules(opens in a new tab or window).