New Device/Location sign-in along with critical operation

Status: available
Severity: medium
Time window: 1h
Group by: actor_alternateId_s, actor_displayName_s, authenticationContext_externalSessionId_s, client_device_s, client_geographicalContext_city_s, client_geographicalContext_country_s, client_geographicalContext_geolocation_lat_d, client_geographicalContext_geolocation_lon_d, 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, timekey
Source: github.com/Azure/Azure-Sentinel

This query identifies users seen login from new geo location/country as well as a new device and performing critical operations.

MITRE ATT&CK coverage

Tactic	Techniques
Initial Access	`T1078` Valid Accounts
Persistence	`T1078` Valid Accounts, `T1556` Modify Authentication Process

Event coverage

Provider	Event
Okta-application	application.policy.sign_on.rule.delete
Okta-application	application.policy.sign_on.update
Okta-network-zone	network_zone.rule.disabled
Okta-policy	policy.lifecycle.create
Okta-policy	policy.lifecycle.deactivate
Okta-policy	policy.lifecycle.delete
Okta-policy	policy.lifecycle.update
Okta-policy	policy.rule.deactivate
Okta-policy	policy.rule.delete
Okta-policy	policy.rule.update
Okta-system	system.api_token.create
Okta-system	system.api_token.revoke
Okta-system	system.mfa.factor.deactivate
Okta-user	user.mfa.attempt_bypass
Okta-user	user.mfa.factor.deactivate
Okta-user	user.mfa.factor.reset_all
Okta-user	user.session.start

Rules detecting the same action

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

Attempt to Create Okta API Token (Elastic)
Attempt to Deactivate an Okta Policy (Elastic)
Attempt to Deactivate an Okta Policy Rule (Elastic)
Attempt to Delete an Okta Policy (Elastic)
Attempt to Delete an Okta Policy Rule (Elastic)
Attempt to Modify an Okta Network Zone (Elastic)
Attempt to Modify an Okta Policy (Elastic)
Attempt to Modify an Okta Policy Rule (Elastic)

Rule body kusto

id: 41e843a8-92e7-444d-8d72-638f1145d1e1
name: New Device/Location sign-in along with critical operation
description: |
  'This query identifies users seen login from new geo location/country as well as a new device and performing critical operations.'
severity: Medium
status: Available
requiredDataConnectors:
  - connectorId: OktaSSO
    dataTypes:
      - Okta_CL
  - connectorId: OktaSSOv2
    dataTypes:
      - OktaSSO
queryFrequency: 1h
queryPeriod: 1h
triggerOperator: gt
triggerThreshold: 0
tactics:
  - InitialAccess
  - Persistence
relevantTechniques:
  - T1078
  - T1556
query: |
  let timeframe = 1h;
  let RiskyOperations = dynamic(["policy.rule.update","policy.rule.create","policy.rule.delete", "policy.rule.deactivate", "policy.lifecycle.update", "policy.rule.modify", "policy.lifecycle.create", "policy.lifecycle.delete", "policy.lifecycle.deactivate", "policy.lifecycle.modify", "network_zone.rule.disabled", "system.api_token.create", "system.api_token.revoke", "application.policy.sign_on.update", "application.policy.sign_on.rule.delete","user.mfa.factor.deactivate", "user.mfa.factor.reset_all", "system.mfa.factor.deactivate", "user.mfa.attempt_bypass"]);
  let UserLoginNewCountryDevice = OktaSSO
  | where eventType_s == "user.session.start"
  | where outcome_result_s == "SUCCESS"
  | extend debugContext_debugData_logOnlySecurityData_s = column_ifexists('debugContext_debugData_logOnlySecurityData_s', '{}')
  | where parse_json(tostring(parse_json(debugContext_debugData_logOnlySecurityData_s).behaviors)).["New Country"] == "POSITIVE"
  | where parse_json(tostring(parse_json(debugContext_debugData_logOnlySecurityData_s).behaviors)).["New Geo-Location"] == "POSITIVE"
  | where parse_json(tostring(parse_json(debugContext_debugData_logOnlySecurityData_s).behaviors)).["New Device"] == "POSITIVE"
  | summarize by timekey = bin(TimeGenerated, timeframe), actor_alternateId_s, actor_displayName_s, client_userAgent_os_s, client_userAgent_browser_s, client_device_s, client_userAgent_rawUserAgent_s, client_ipAddress_s, authenticationContext_externalSessionId_s, client_geographicalContext_country_s, client_geographicalContext_city_s, displayMessage_s, outcome_result_s, outcome_reason_s, column_ifexists('debugContext_debugData_logOnlySecurityData_s', ""), debugContext_debugData_threatSuspected_s, client_geographicalContext_geolocation_lat_d, client_geographicalContext_geolocation_lon_d
  | extend Location = strcat(client_geographicalContext_city_s, "-", client_geographicalContext_country_s);
  let RiskyOperationsObserved = OktaSSO
  | where eventType_s in (RiskyOperations)
  | where outcome_result_s == "SUCCESS"
  | summarize by timekey = bin(TimeGenerated, timeframe), actor_alternateId_s, actor_displayName_s, client_userAgent_os_s, client_userAgent_browser_s, client_device_s, client_userAgent_rawUserAgent_s, client_ipAddress_s, authenticationContext_externalSessionId_s, client_geographicalContext_country_s, client_geographicalContext_city_s, displayMessage_s, outcome_result_s, outcome_reason_s, column_ifexists('debugContext_debugData_logOnlySecurityData_s', ""), debugContext_debugData_threatSuspected_s, client_geographicalContext_geolocation_lat_d, client_geographicalContext_geolocation_lon_d;
  UserLoginNewCountryDevice
  | join kind=inner (RiskyOperationsObserved) on timekey, actor_displayName_s, client_ipAddress_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:
  SessionId: authenticationContext_externalSessionId_s
  Location:  Location
alertDetailsOverride:
  alertDisplayNameFormat: New Device/Location {{Location}} sign-in along with critical operation
  alertDescriptionFormat: |
    This query identifies users seen login from new geo location/country {{Location}} as well as a new device and performing critical operations
version: 1.1.1
kind: Scheduled

Stages and Predicates

Parameters

let timeframe = 1h;

Let binding: `RiskyOperations`

let RiskyOperations = dynamic(["policy.rule.update","policy.rule.create","policy.rule.delete", "policy.rule.deactivate", "policy.lifecycle.update", "policy.rule.modify", "policy.lifecycle.create", "policy.lifecycle.delete", "policy.lifecycle.deactivate", "policy.lifecycle.modify", "network_zone.rule.disabled", "system.api_token.create", "system.api_token.revoke", "application.policy.sign_on.update", "application.policy.sign_on.rule.delete","user.mfa.factor.deactivate", "user.mfa.factor.reset_all", "system.mfa.factor.deactivate", "user.mfa.attempt_bypass"]);

Let binding: `RiskyOperationsObserved`

let RiskyOperationsObserved = OktaSSO
| where eventType_s in (RiskyOperations)
| where outcome_result_s == "SUCCESS"
| summarize by timekey = bin(TimeGenerated, timeframe), actor_alternateId_s, actor_displayName_s, client_userAgent_os_s, client_userAgent_browser_s, client_device_s, client_userAgent_rawUserAgent_s, client_ipAddress_s, authenticationContext_externalSessionId_s, client_geographicalContext_country_s, client_geographicalContext_city_s, displayMessage_s, outcome_result_s, outcome_reason_s, column_ifexists('debugContext_debugData_logOnlySecurityData_s', ""), debugContext_debugData_threatSuspected_s, client_geographicalContext_geolocation_lat_d, client_geographicalContext_geolocation_lon_d;

Derived from timeframe, RiskyOperations.

The stages below define let UserLoginNewCountryDevice (the rule's main pipeline source).

Stage 1: `source`

OktaSSO

Stage 2: `where`

| where eventType_s == "user.session.start"

Stage 3: `where`

| where outcome_result_s == "SUCCESS"

Stage 4: `extend`

| extend debugContext_debugData_logOnlySecurityData_s = column_ifexists('debugContext_debugData_logOnlySecurityData_s', '{}')

Stage 5: `where`

| where parse_json(tostring(parse_json(debugContext_debugData_logOnlySecurityData_s).behaviors)).["New Country"] == "POSITIVE"

Stage 6: `where`

| where parse_json(tostring(parse_json(debugContext_debugData_logOnlySecurityData_s).behaviors)).["New Geo-Location"] == "POSITIVE"

Stage 7: `where`

| where parse_json(tostring(parse_json(debugContext_debugData_logOnlySecurityData_s).behaviors)).["New Device"] == "POSITIVE"

Stage 8: `summarize`

| summarize by timekey = bin(TimeGenerated, timeframe), actor_alternateId_s, actor_displayName_s, client_userAgent_os_s, client_userAgent_browser_s, client_device_s, client_userAgent_rawUserAgent_s, client_ipAddress_s, authenticationContext_externalSessionId_s, client_geographicalContext_country_s, client_geographicalContext_city_s, displayMessage_s, outcome_result_s, outcome_reason_s, column_ifexists('debugContext_debugData_logOnlySecurityData_s', ""), debugContext_debugData_threatSuspected_s, client_geographicalContext_geolocation_lat_d, client_geographicalContext_geolocation_lon_d

Stage 9: `extend`

| extend Location = strcat(client_geographicalContext_city_s, "-", client_geographicalContext_country_s)

The stages below run on UserLoginNewCountryDevice (the outer pipeline).

Stage 10: `join`

UserLoginNewCountryDevice
| join kind=inner (RiskyOperationsObserved) on timekey, actor_displayName_s, client_ipAddress_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
`New Country`	eq	`POSITIVE` transforms: `cased`
`New Device`	eq	`POSITIVE` transforms: `cased`
`New Geo-Location`	eq	`POSITIVE` transforms: `cased`
`eventType_s`	eq	`user.session.start` transforms: `cased`
`eventType_s`	in	`application.policy.sign_on.rule.delete` transforms: `cased` `application.policy.sign_on.update` transforms: `cased` `network_zone.rule.disabled` transforms: `cased` `policy.lifecycle.create` transforms: `cased` `policy.lifecycle.deactivate` transforms: `cased` `policy.lifecycle.delete` transforms: `cased` `policy.lifecycle.modify` transforms: `cased` `policy.lifecycle.update` transforms: `cased` `policy.rule.create` transforms: `cased` `policy.rule.deactivate` transforms: `cased` `policy.rule.delete` transforms: `cased` `policy.rule.modify` transforms: `cased` `policy.rule.update` transforms: `cased` `system.api_token.create` transforms: `cased` `system.api_token.revoke` transforms: `cased` `system.mfa.factor.deactivate` transforms: `cased` `user.mfa.attempt_bypass` transforms: `cased` `user.mfa.factor.deactivate` transforms: `cased` `user.mfa.factor.reset_all` transforms: `cased`
`outcome_result_s`	eq	`SUCCESS` 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.

Field	Source
`actor_alternateId_s`	`summarize`
`actor_displayName_s`	`summarize`
`authenticationContext_externalSessionId_s`	`summarize`
`client_device_s`	`summarize`
`client_geographicalContext_city_s`	`summarize`
`client_geographicalContext_country_s`	`summarize`
`client_geographicalContext_geolocation_lat_d`	`summarize`
`client_geographicalContext_geolocation_lon_d`	`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`
`timekey`	`summarize`
`Location`	`extend`

`j` / `k`	Scroll down / up
`d` / `u`	Half-page down / up
`gg` / `G`	Top / bottom
`h` / `l`	History back / forward
`f`	Follow link (`Shift` = new tab)
`/`	Focus search
`?`	Toggle this help
`↑` / `↓`	Navigate search results
`Enter`	Open highlighted result
`Esc`	Close results / dialog

`type:`	`events` / `rules` / `providers`
`vendor:`	`sigma` / `elastic` / `splunk` / `kusto` / `chronicle` (vendor name alone also works: `sigma:`, `kql:`, `secops:`…)
`tactic:`	TA-id, slug, or name: `credential_access`, `TA0006`
`technique:`	technique or sub-technique ID: `T1003`, `T1003.001` (alias `tech:`)
`severity:`	`critical` / `high` / `medium` / `low` / `informational` (alias `sev:`)
`risk_score`	Numeric comparison on the Elastic risk score (0 to 100): `risk_score>50`, `risk_score<=20`, `risk_score=99` (alias `risk`; Elastic rules only)
`stages:`	Rules with exactly N pipeline stages
`correlation:`	`single_event` / `sequence` / `alternatives` / `alternatives_cross_log` / `all_required` / `correlated`
`with:`	Co-occurrence event-id; stacks (`with:4624 with:4769`) to require all, while a comma list in one occurrence (`with:4624,4769`) is an either-or group. Implies multi-event
`like:`	Structural neighbors of a rule slug (equivalents + subsumption stricter / broader): `like:comsvcs_lsass_memory_dump-splunk-sysmon`
`groupby:`	Entity-grouping substring match against `group_by_keys`: `groupby:user`, `groupby:host`
`uses:`	Rules whose predicate tree touches the field (any kind, any value): `uses:CommandLine`
`excludes:`	Rules with top-level `not()` clauses on the field (FP whitelists): `excludes:ParentImage`
`field:` / `value:`	Predicate search; narrows rule cards to those with a matching leaf and drives the indicator tier. Unquoted = substring, wildcards allowed (`value:mimikatz`)
`indicator:`	Shorthand for `field:F value:V`: `indicator:Image=*\powershell.exe`
`kind:`	Filter by predicate kind. Narrows rule cards to those carrying a matching predicate leaf (`vendor:elastic kind:cidr_match`) and drives the indicator tier: `contains` / `starts_with` / `ends_with` / `regex` / `cidr` / `eq` / `in` … (operator aliases `op:`/`match:`)
`has:` / `no:`	`sample`, `field`, `notes`, `refs`, `trace`, `thirdparty`, `rule`, `pattern`, `timewindow`, `threshold`, `newterms`, `sigma`/`elastic`/`splunk`/`kusto`/`chronicle`
`-op:val`	Exclude matches; works on most operators but not `type:`/`like:`/`has:`/`no:` (use `no:<flag>` to exclude a rule flag): `tactic:execution -vendor:splunk`. Standalone `-kind:`/`-field:`/`-value:` drop every rule carrying a matching predicate leaf (`type:rules -kind:is_null`)
`field:"…"` / `value:"…"`	Quoted value = anchored exact match (also allows spaces): `value:"net user"`
`a,b`	Comma = OR inside one operator (`vendor:sigma,elastic`, `severity:high,critical`); repeating a facet merges the same way. `field:`/`value:` never split (literal commas)
`vendors:` / `stage:`	Singular and plural spellings fold to the canonical operator and value: `tactics:` = `tactic:`, `type:event` = `type:events`, `correlation:sequences` = `correlation:sequence`, `has:thresholds` = `has:threshold`
`"quoted phrase"`	Exact-match a multi-word phrase (free text)

New Device/Location sign-in along with critical operation

MITRE ATT&CK coverage

Event coverage

Rules detecting the same action

Rule body kusto

Stages and Predicates

Parameters

Let binding: `RiskyOperations`

Let binding: `RiskyOperationsObserved`

Stage 1: `source`

Stage 2: `where`

Stage 3: `where`

Stage 4: `extend`

Stage 5: `where`

Stage 6: `where`

Stage 7: `where`

Stage 8: `summarize`

Stage 9: `extend`

Stage 10: `join`

Indicators

Output fields

Keyboard shortcuts

Search operators

New Device/Location sign-in along with critical operation

MITRE ATT&CK coverage

Event coverage

Rules detecting the same action

Rule body kusto

Stages and Predicates

Parameters

Let binding: RiskyOperations

Let binding: RiskyOperationsObserved

Stage 1: source

Stage 2: where

Stage 3: where

Stage 4: extend

Stage 5: where

Stage 6: where

Stage 7: where

Stage 8: summarize

Stage 9: extend

Stage 10: join

Indicators

Output fields

Let binding: `RiskyOperations`

Let binding: `RiskyOperationsObserved`

Stage 1: `source`

Stage 2: `where`

Stage 3: `where`

Stage 4: `extend`

Stage 5: `where`

Stage 6: `where`

Stage 7: `where`

Stage 8: `summarize`

Stage 9: `extend`

Stage 10: `join`