Detection rules › Panther
GitHub Org IP Allow List modified
Detects changes to a GitHub Org IP Allow List
MITRE ATT&CK coverage
| Tactic | Techniques |
|---|---|
| Persistence | T1098 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_org_ip_allowlist.py
RuleID: "GitHub.Org.IpAllowlist"
DisplayName: "GitHub Org IP Allow List modified"
Enabled: true
LogTypes:
- GitHub.Audit
Tags:
- GitHub
- Persistence:Account Manipulation
Reports:
MITRE ATT&CK:
- TA0003:T1098
Severity: Medium
SummaryAttributes:
- actor
- action
Description: Detects changes to a GitHub Org IP Allow List
Runbook: Verify that the change was authorized and appropriate.
Reference: https://docs.github.com/en/apps/maintaining-github-apps/managing-allowed-ip-addresses-for-a-github-app
Tests:
- Name: GitHub - IP Allow list modified
ExpectedResult: true
Log:
{
"actor": "cat",
"action": "ip_allow_list_entry.create",
"created_at": 1621305118553,
"p_log_type": "GitHub.Audit",
"org": "my-org",
}
- Name: GitHub - IP Allow list disabled
ExpectedResult: true
Log:
{
"actor": "cat",
"action": "ip_allow_list.disable",
"created_at": 1621305118553,
"org": "my-org",
"p_log_type": "GitHub.Audit",
}
- Name: GitHub - Non IP Allow list action
ExpectedResult: false
Log:
{
"actor": "cat",
"action": "org.invite_user",
"created_at": 1621305118553,
"org": "my-org",
"p_log_type": "GitHub.Audit",
}
Detection logic
Condition
action starts_with "ip_allow_list"
action in ["ip_allow_list.enable", "ip_allow_list.disable", "ip_allow_list.enable_for_installed_apps", "ip_allow_list.disable_for_installed_apps", "ip_allow_list_entry.create", "ip_allow_list_entry.update", "ip_allow_list_entry.destroy"]
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.
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 |