Detection rules › Panther
GitHub User Added or Removed from Org
Detects when a user is added or removed from a GitHub Org.
MITRE ATT&CK coverage
| Tactic | Techniques |
|---|---|
| Initial Access | T1195 Supply Chain Compromise |
Rules detecting the same action
Other rules on this platform that filter on the same API call or operation.
- GitHub - User was added to the organization (Kusto)
- Member Removed From GitHub Organization (Elastic)
- New Github Organization Member Added (Sigma)
- New GitHub Owner Added (Elastic)
- New User Added To GitHub Organization (Elastic)
Rule body yaml
AnalysisType: rule
Filename: github_org_modified.py
RuleID: "GitHub.Org.Modified"
DisplayName: "GitHub User Added or Removed from Org"
Enabled: true
LogTypes:
- GitHub.Audit
Tags:
- GitHub
- Initial Access:Supply Chain Compromise
Reports:
MITRE ATT&CK:
- TA0001:T1195
Reference: https://docs.github.com/en/organizations/managing-membership-in-your-organization
Severity: Info
Description: Detects when a user is added or removed from a GitHub Org.
Tests:
- Name: GitHub - Team Deleted
ExpectedResult: false
Log:
{
"actor": "cat",
"action": "team.destroy",
"created_at": 1621305118553,
"data": { "team": "my-org/my-team" },
"org": "my-org",
"p_log_type": "GitHub.Audit",
"repo": "my-org/my-repo",
}
- Name: GitHub - Org - User Added
ExpectedResult: true
Log:
{
"actor": "cat",
"action": "org.add_member",
"created_at": 1621305118553,
"org": "my-org",
"p_log_type": "GitHub.Audit",
"user": "cat",
}
- Name: GitHub - Org - User Removed
ExpectedResult: true
Log:
{
"actor": "cat",
"action": "org.remove_member",
"created_at": 1621305118553,
"org": "my-org",
"p_log_type": "GitHub.Audit",
"user": "bob",
}
Detection logic
Condition
action eq "org.add_member" or action eq "org.remove_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.
| Field | Kind | Values |
|---|---|---|
action | eq |
|
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 |
org |