detection.wiki

Detection rules › Panther

OneLogin Unauthorized Access

Severity
medium
Log types
OneLogin.Events
Tags
OneLogin, Lateral Movement:Use Alternate Authentication Material
Reference
https://onelogin.service-now.com/kb_view_customer.do?sysparm_article=KB0010420
Source
github.com/panther-labs/panther-analysis

A OneLogin user was denied access to an app more times than the configured threshold.

MITRE ATT&CK coverage

TacticTechniques
Lateral MovementT1550 Use Alternate Authentication Material

Rule body yaml

AnalysisType: rule
Filename: onelogin_unauthorized_access.py
RuleID: "OneLogin.UnauthorizedAccess"
DisplayName: "OneLogin Unauthorized Access"
Enabled: true
LogTypes:
  - OneLogin.Events
Tags:
  - OneLogin
  - Lateral Movement:Use Alternate Authentication Material
Reports:
  MITRE ATT&CK:
    - TA0008:T1550
Severity: Medium
Description: A OneLogin user was denied access to an app more times than the configured threshold.
Threshold: 10
DedupPeriodMinutes: 10
Reference: https://onelogin.service-now.com/kb_view_customer.do?sysparm_article=KB0010420
Runbook: Analyze the user activity and actions.
SummaryAttributes:
  - account_id
  - user_name
  - user_id
  - app_name
Tests:
  - Name: Normal Event
    ExpectedResult: false
    Log:
      {
        "event_type_id": "8",
        "user_id": 123456,
        "user_name": "Bob Cat",
        "app_name": "confluence",
      }
  - Name: User Unauthorized Access Event
    ExpectedResult: true
    Log:
      {
        "event_type_id": "90",
        "user_id": 123456,
        "user_name": "Bob Cat",
        "app_name": "confluence",
      }

Detection logic

Condition

event_type_id eq "90"

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
event_type_ideq
  • 90

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
user_name