Detection rules › Kusto

Okta Fast Pass phishing Detection

Status
available
Severity
medium
Time window
1h
Group by
actor_alternateId_s, actor_displayName_s, client_geographicalContext_city_s, client_geographicalContext_country_s, client_geographicalContext_state_s, client_ipAddress_s, client_userAgent_browser_s, client_userAgent_os_s, client_userAgent_rawUserAgent_s, debugContext_debugData_threatSuspected_s, displayMessage_s, outcome_reason_s, outcome_result_s, severity_s
Source
github.com/Azure/Azure-Sentinel

This query detects cases in which Okta FastPass effectively prevented access to a known phishing website.

MITRE ATT&CK coverage

TacticTechniques
Initial AccessT1566 Phishing

Event coverage

Rules detecting the same action

Other rules on this platform that filter on the same API call or operation.

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.

FieldKindValues
eventType_seq
  • user.authentication.auth_via_mfa transforms: cased
outcome_reason_seq
  • FastPass declined phishing attempt transforms: cased
outcome_result_seq
  • FAILURE transforms: cased

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.

FieldSource
EndTimesummarize
StartTimesummarize
actor_alternateId_ssummarize
actor_displayName_ssummarize
client_geographicalContext_city_ssummarize
client_geographicalContext_country_ssummarize
client_geographicalContext_state_ssummarize
client_ipAddress_ssummarize
client_userAgent_browser_ssummarize
client_userAgent_os_ssummarize
client_userAgent_rawUserAgent_ssummarize
debugContext_debugData_threatSuspected_ssummarize
displayMessage_ssummarize
outcome_reason_ssummarize
outcome_result_ssummarize
severity_ssummarize
Locationextend