Detection rules › Panther
Anthropic IP Restriction Deleted
Detects when an organization IP restriction is deleted. IP restrictions are a critical network-level access control — removing them allows access from any IP address, which could indicate an attacker widening the attack surface after gaining admin access.
MITRE ATT&CK coverage
| Tactic | Techniques |
|---|---|
| Stealth | T1562.001 Impair Defenses: Disable or Modify Tools |
Rule body yaml
AnalysisType: rule
RuleID: Anthropic.Activity.IP.Restriction.Deleted
DisplayName: "Anthropic IP Restriction Deleted"
Enabled: true
Filename: anthropic_ip_restriction_deleted.py
LogTypes:
- Anthropic.Activity
Severity: High
Description: >
Detects when an organization IP restriction is deleted. IP restrictions
are a critical network-level access control — removing them allows access
from any IP address, which could indicate an attacker widening the attack
surface after gaining admin access.
Runbook: |
1. Find all Anthropic.Activity events by actor:email_address in the 24 hours before the alert to identify any suspicious activity leading up to the IP restriction change
2. Check if actor:ip_address matches previously seen IP addresses for this actor in the past 30 days to detect potential account compromise
3. Check if other org_ip_restriction events (created, updated) occurred in the 1 hour around the alert to determine if this is a policy replacement or a standalone deletion
Tags:
- Anthropic
- Network Security
- Defense Evasion
Reports:
MITRE ATT&CK:
- TA0005:T1562.001 # Impair Defenses: Disable or Modify Tools
Tests:
- Name: IP restriction deleted
ExpectedResult: true
Log:
{
"id": "activity_01ABC123",
"created_at": "2026-05-07T10:00:00Z",
"organization_id": "org_01XYZ",
"type": "org_ip_restriction_deleted",
"actor": {
"type": "user_actor",
"email_address": "admin@example.com",
"user_id": "user_01ABC",
"ip_address": "10.0.0.1",
"user_agent": "Mozilla/5.0"
}
}
- Name: IP restriction created - not a match
ExpectedResult: false
Log:
{
"id": "activity_01DEF456",
"created_at": "2026-05-07T10:00:00Z",
"organization_id": "org_01XYZ",
"type": "org_ip_restriction_created",
"actor": {
"type": "user_actor",
"email_address": "admin@example.com",
"user_id": "user_01ABC",
"ip_address": "10.0.0.1"
}
}
Detection logic
Condition
type eq "org_ip_restriction_deleted"
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 |
|---|---|---|
type | 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 | Source |
|---|---|
event_type | type |
actor_type | actor.type |
actor_email | actor.email_address |
actor_user_id | actor.user_id |
ip_address | actor.ip_address |
user_agent | actor.user_agent |
api_key_id | actor.api_key_id |
organization_id | |
ips | p_any_ip_addresses |