Detection: Investigate User Activities In Okta

REMOVED DETECTION

This detection has been removed from the Splunk Threat Research content library and is no longer maintained or supported.

Reason: As of Splunk Enterprise Security version 8.0, Splunk Enterprise Security no longer supports Investigations. As such, all Investigations have been deprecated in ES Content Update.

Removed in version: 5.2.0

If you have any questions or concerns, please reach out to us at research@splunk.com.

Updated Date: 2026-05-13 ID: 24ff145d-4d16-420a-b047-480f2a51c403 Author: Rico Valdez, Splunk Type: Investigation Product: Splunk Enterprise Security

Description

This search returns all okta events by a specific user

Search

1`okta` user=$user$ 
2| rename client.geographicalContext.country as country, client.geographicalContext.state as state, client.geographicalContext.city as city 
3| table _time, user, displayMessage, app, src_ip, state, city, result, outcome.reason

Data Source

No data sources specified for this detection.

Macros Used

Name	Value
okta	`eventtype=okta_log OR sourcetype = "OktaIM2:log"`

Annotations

- MITRE ATT&CK

+ Kill Chain Phases

+ NIST

+ CIS

- Threat Actors

ID	Technique	Tactic

Default Configuration

This detection is configured by default in Splunk Enterprise Security to run with the following settings:

Setting	Value
Disabled	true
Cron Schedule	`N/A`
Earliest Time	`N/A`
Latest Time	`N/A`
Schedule Window	`N/A`
Creates Finding (Notable)	No
Creates Intermediate Finding (Risk Event)	No

Implementation

You must be ingesting Okta logs

Known False Positives

Associated Analytic Story

Suspicious Okta Activity

Detection Testing

Test Type	Status	Dataset	Source	Sourcetype
Validation	Not Applicable	N/A	N/A	N/A
Unit	Not Applicable	N/A	`N/A`	`N/A`
Integration	Not Applicable	N/A	`N/A`	`N/A`

Replay any dataset to Splunk Enterprise by using our replay.py tool or the UI. Alternatively you can replay a dataset into a Splunk Attack Range

Source: GitHub |

Version: 1