Detection rules › Kusto
Okta Fast Pass phishing Detection
This query detects cases in which Okta FastPass effectively prevented access to a known phishing website.
MITRE ATT&CK coverage
| Tactic | Techniques |
|---|---|
| Initial Access | T1566 Phishing |
Event coverage
| Provider | Event |
|---|---|
| Okta-user | user.authentication.auth_via_mfa |
Rules detecting the same action
Other rules on this platform that filter on the same API call or operation.
- First Occurrence of Okta User Session Started via Proxy (Elastic)
- MFA Fatigue (OKTA) (Kusto)
- Okta AiTM Phishing Attempt Blocked by FastPass (Panther)
- Okta FastPass Phishing Detection (Sigma)
- Okta FastPass Phishing Detection (Elastic)
- Okta MFA Bruteforce Attack (YARA-L)
- Okta Mismatch Between Source And Response For Verify Push Request (YARA-L)
- Okta Mismatch Between Source and Response for Verify Push Request (Splunk)
Rule body kusto
id: 78d2b06c-8dc0-40e1-91c8-66d916c186f3
name: Okta Fast Pass phishing Detection
description: |
'This query detects cases in which Okta FastPass effectively prevented access to a known phishing website.'
severity: Medium
status: Available
requiredDataConnectors:
- connectorId: OktaSSO
dataTypes:
- Okta_CL
- connectorId: OktaSSOv2
dataTypes:
- OktaSSO
queryFrequency: 1h
queryPeriod: 1h
triggerOperator: gt
triggerThreshold: 0
tactics:
- InitialAccess
relevantTechniques:
- T1566
tags:
- Okta
query: |
OktaSSO
| where eventType_s == 'user.authentication.auth_via_mfa'
| where outcome_result_s == 'FAILURE'
| where outcome_reason_s == 'FastPass declined phishing attempt'
| summarize StartTime = min(TimeGenerated), EndTime = max(TimeGenerated) by actor_alternateId_s, actor_displayName_s, client_userAgent_os_s, client_ipAddress_s, client_geographicalContext_state_s,displayMessage_s, outcome_result_s,
outcome_reason_s, column_ifexists('debugContext_debugData_logOnlySecurityData_s', ""), debugContext_debugData_threatSuspected_s, client_userAgent_rawUserAgent_s,client_userAgent_browser_s, severity_s, client_geographicalContext_city_s, client_geographicalContext_country_s
| extend Location = strcat(client_geographicalContext_city_s, "-", client_geographicalContext_country_s)
entityMappings:
- entityType: Account
fieldMappings:
- identifier: Name
columnName: actor_alternateId_s
- identifier: DisplayName
columnName: actor_displayName_s
- entityType: IP
fieldMappings:
- identifier: Address
columnName: client_ipAddress_s
customDetails:
UserAgent: client_userAgent_rawUserAgent_s
Location: Location
version: 1.1.0
kind: Scheduled
Stages and Predicates
Stage 1: source
OktaSSO
Stage 2: where
| where eventType_s == 'user.authentication.auth_via_mfa'
Stage 3: where
| where outcome_result_s == 'FAILURE'
Stage 4: where
| where outcome_reason_s == 'FastPass declined phishing attempt'
Stage 5: summarize
| summarize StartTime = min(TimeGenerated), EndTime = max(TimeGenerated) by actor_alternateId_s, actor_displayName_s, client_userAgent_os_s, client_ipAddress_s, client_geographicalContext_state_s,displayMessage_s, outcome_result_s,
outcome_reason_s, column_ifexists('debugContext_debugData_logOnlySecurityData_s', ""), debugContext_debugData_threatSuspected_s, client_userAgent_rawUserAgent_s,client_userAgent_browser_s, severity_s, client_geographicalContext_city_s, client_geographicalContext_country_s
Stage 6: extend
| extend Location = strcat(client_geographicalContext_city_s, "-", client_geographicalContext_country_s)
Indicators
Each row is a field, operator, and value that the rule matches. The corpus column counts how many other rules in the catalog look for the same combination: high numbers point to widely-used, community-vetted indicators. Blank or 1 shows that the indicator is specific to this rule.
| Field | Kind | Values |
|---|---|---|
eventType_s | eq |
|
outcome_reason_s | eq |
|
outcome_result_s | eq |
|
Output fields
Fields the rule emits when it matches. Chronicle authors list these in the outcome block; they appear on the detection and $risk_score drives alerting. Sentinel / Defender XDR rules build them up through project / summarize / extend stages. Sentinel maps these into alert fields via entityMappings and customDetails; Defender XDR custom detections surface them as alert fields directly.
| Field | Source |
|---|---|
EndTime | summarize |
StartTime | summarize |
actor_alternateId_s | summarize |
actor_displayName_s | summarize |
client_geographicalContext_city_s | summarize |
client_geographicalContext_country_s | summarize |
client_geographicalContext_state_s | summarize |
client_ipAddress_s | summarize |
client_userAgent_browser_s | summarize |
client_userAgent_os_s | summarize |
client_userAgent_rawUserAgent_s | summarize |
debugContext_debugData_threatSuspected_s | summarize |
displayMessage_s | summarize |
outcome_reason_s | summarize |
outcome_result_s | summarize |
severity_s | summarize |
Location | extend |