detection.wiki

Detection rules › Panther

GitHub User Role Updated

Severity
high
Log types
GitHub.Audit
Tags
GitHub, Persistence:Account Manipulation
Reference
https://docs.github.com/en/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization
Source
github.com/panther-labs/panther-analysis

Detects when a GitHub user role is upgraded to an admin or downgraded to a member

MITRE ATT&CK coverage

TacticTechniques
PersistenceT1098 Account Manipulation

Rules detecting the same action

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

Rule body yaml

AnalysisType: rule
Filename: github_user_role_updated.py
RuleID: "GitHub.User.RoleUpdated"
DisplayName: "GitHub User Role Updated"
Enabled: true
LogTypes:
  - GitHub.Audit
Tags:
  - GitHub
  - Persistence:Account Manipulation
Reports:
  MITRE ATT&CK:
    - TA0003:T1098
Reference: https://docs.github.com/en/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization
Severity: High
Description: Detects when a GitHub user role is upgraded to an admin or downgraded to a member
Tests:
  - Name: GitHub - Member Updated
    ExpectedResult: true
    Log:
      {
        "actor": "cat",
        "action": "org.update_member",
        "created_at": 1621305118553,
        "p_log_type": "GitHub.Audit",
        "repo": "my-org/my-repo",
        "user": "bob",
      }
  - Name: GitHub - Member Invited
    ExpectedResult: false
    Log:
      {
        "actor": "cat",
        "action": "org.invite_member",
        "created_at": 1621305118553,
        "p_log_type": "GitHub.Audit",
        "repo": "my-org/my-repo",
        "user": "bob",
      }

Detection logic

Condition

action eq "org.update_member"

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
actioneq
  • org.update_member

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
user