For the complete documentation index, see llms.txt. This page is also available as Markdown.

First SSO access from ASN for user

Synopsis

Field
Value

Activation Period

14 Days

Training Period

30 Days

Test Period

N/A (single event)

Deduplication Period

1 Day

Required Data

Requires one of the following data sources: AzureAD OR Azure SignIn Log OR Idira OR Duo OR Google Workspace Authentication OR Okta OR OneLogin OR PingOne

Detection Modules

Identity Analytics

ATT&CK Tactic

Initial Access (TA0001)

ATT&CK Technique

Valid Accounts: Domain Accounts (T1078.002)

Severity

Informational

Description

A user successfully authenticated via SSO with a new ASN.

Attacker's Goals

Use an account that was possibly compromised to gain access to the network.

Investigative actions

  • Confirm that the activity is benign (e.g. the user has switched locations and providers).

  • Verify if the ASN is an approved ASN to authenticate from.

  • Follow further actions done by the user.

Variations

First SSO access from ASN for user - suspicious characteristics detected

Synopsis

Field
Value

ATT&CK Tactic

Initial Access (TA0001)

ATT&CK Technique

Valid Accounts: Domain Accounts (T1078.002)

Severity

Low

Description

First SSO access from ASN for user that shows suspicious characteristics.

Attacker's Goals

Use an account that was possibly compromised to gain access to the network.

Investigative actions

  • Confirm that the activity is benign (e.g. the user has switched locations and providers).

  • Verify if the ASN is an approved ASN to authenticate from.

  • Follow further actions done by the user.

Google Workspace - First SSO access from ASN for user

Synopsis

Field
Value

ATT&CK Tactic

Initial Access (TA0001)

ATT&CK Technique

Valid Accounts: Domain Accounts (T1078.002)

Severity

Informational

Description

A user successfully authenticated via SSO with a new ASN.

Attacker's Goals

Use an account that was possibly compromised to gain access to the network.

Investigative actions

  • Confirm that the activity is benign (e.g. the user has switched locations and providers).

  • Verify if the ASN is an approved ASN to authenticate from.

  • Follow further actions done by the user.

Was this helpful?