Detection rules › Panther

OneLogin User Assumed Another User

Severity
low
Log types
OneLogin.Events
Tags
OneLogin, Lateral Movement:Use Alternate Authentication Material
Reference
https://onelogin.service-now.com/kb_view_customer.do?sysparm_article=KB0010594#:~:text=Prerequisites,Actions%20and%20select%20Assume%20User.
Source
github.com/panther-labs/panther-analysis

User assumed another user account

MITRE ATT&CK coverage

TacticTechniques
Lateral MovementT1550 Use Alternate Authentication Material

Rule body yaml

AnalysisType: rule
Filename: onelogin_user_assumed.py
RuleID: "OneLogin.UserAssumption"
DisplayName: "OneLogin User Assumed Another User"
Enabled: true
LogTypes:
  - OneLogin.Events
Tags:
  - OneLogin
  - Lateral Movement:Use Alternate Authentication Material
Reports:
  MITRE ATT&CK:
    - TA0008:T1550
Severity: Low
Description: User assumed another user account
Reference: https://onelogin.service-now.com/kb_view_customer.do?sysparm_article=KB0010594#:~:text=Prerequisites,Actions%20and%20select%20Assume%20User.
Runbook: >
  Investigate whether this was authorized access.
SummaryAttributes:
  - account_id
  - user_name
  - user_id
Tests:
  - Name: User assumed their own account
    ExpectedResult: false
    Log:
      {
        "event_type_id": "240",
        "actor_user_id": 123456,
        "actor_user_name": "Bob Cat",
        "user_id": 123456,
        "user_name": "Bob Cat",
      }
  - Name: User assumed another user's account
    ExpectedResult: true
    Log:
      {
        "event_type_id": "3",
        "actor_user_id": 654321,
        "actor_user_name": "Mountain Lion",
        "user_id": 123456,
        "user_name": "Bob Cat",
      }

Detection logic

Condition

event_type_id eq "3"
actor_user_id cross_field_compare "user_id"

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
actor_user_idcross_field_compare
  • user_id transforms: op:ne
event_type_ideq
  • 3

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
actor_user_name
user_name