Detection: Okta Failed SSO Attempts

DEPRECATED DETECTION

This detection has been marked as deprecated by the Splunk Threat Research team. This means that it will no longer be maintained or supported. If you have any questions or concerns, please reach out to us at research@splunk.com.

Updated Date: 2022-09-21 ID: 371a6545-2618-4032-ad84-93386b8698c5 Author: Michael Haag, Rico Valdez, Splunk Type: Anomaly Product: Splunk Enterprise Security

Description

DEPRECATION NOTE - This search has been deprecated and replaced with this detection Okta Unauthorized Access to Application - DM. The following anomaly identifies failed Okta SSO events utilizing the legacy Okta event "unauth app access attempt".

Search

1`okta` eventType=app.generic.unauth_app_access_attempt 
2| stats min(_time) as firstTime max(_time) as lastTime values(app) as Apps count by src_user, result ,displayMessage, src_ip 
3| `security_content_ctime(firstTime)` 
4| `security_content_ctime(lastTime)` 
5| `okta_failed_sso_attempts_filter`

Data Source

Name	Platform	Sourcetype	Source	Supported App
N/A	N/A	N/A	N/A	N/A

Macros Used

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

okta_failed_sso_attempts_filter is an empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.

Annotations

- MITRE ATT&CK

+ Kill Chain Phases

+ NIST

+ CIS

- Threat Actors

ID	Technique	Tactic
T1078	Valid Accounts	Defense Evasion
T1078.001	Default Accounts	Initial Access

KillChainPhase.DELIVERY

KillChainPhase.EXPLOITAITON

KillChainPhase.INSTALLATION

NistCategory.DE_AE

Cis18Value.CIS_10

APT18

APT28

APT29

APT33

APT39

APT41

Akira

Axiom

Carbanak

Chimera

Cinnamon Tempest

Dragonfly

FIN10

FIN4

FIN5

FIN6

FIN7

FIN8

Fox Kitten

GALLIUM

Ke3chang

LAPSUS$

Lazarus Group

Leviathan

OilRig

POLONIUM

PittyTiger

Sandworm Team

Silence

Silent Librarian

Suckfly

Threat Group-3390

Wizard Spider

menuPass

FIN13

Magic Hound

Default Configuration

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

Setting	Value
Disabled	true
Cron Schedule	`0 * * * *`
Earliest Time	`-70m@m`
Latest Time	`-10m@m`
Schedule Window	`auto`
Creates Risk Event	True

This configuration file applies to all detections of type anomaly. These detections will use Risk Based Alerting.

Implementation

This search is specific to Okta and requires Okta logs are being ingested in your Splunk deployment.

Known False Positives

There may be a faulty config preventing legitmate users from accessing apps they should have access to.

Associated Analytic Story

Suspicious Okta Activity

Risk Based Analytics (RBA)

Risk Message	Risk Score	Impact	Confidence
$src_user$ failed SSO authentication to the app.	16	40	40

The Risk Score is calculated by the following formula: Risk Score = (Impact * Confidence/100). Initial Confidence and Impact is set by the analytic author.

References

https://developer.okta.com/docs/reference/api/event-types/?q=app.generic.unauth_app_access_attempt

Detection Testing

Test Type	Status	Dataset	Source	Sourcetype
Validation	Not Applicable	N/A	N/A	N/A
Unit	❌ Failing	N/A	`N/A`	`N/A`
Integration	❌ Failing	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: 3