Detection rules › Panther
Anthropic Integration Connected
Tracks when a user connects an external integration (e.g., GitHub, Google Drive) to their Anthropic account. Logged for compliance visibility into external data pathways. The integration_type field identifies which service was connected.
MITRE ATT&CK coverage
| Tactic | Techniques |
|---|---|
| Collection | T1530 Data from Cloud Storage |
Rule body yaml
AnalysisType: rule
RuleID: Anthropic.Activity.Integration.Connected
DisplayName: "Anthropic Integration Connected"
Enabled: true
Filename: anthropic_integration_connected.py
LogTypes:
- Anthropic.Activity
Severity: Info
Description: >
Tracks when a user connects an external integration (e.g., GitHub, Google Drive)
to their Anthropic account. Logged for compliance visibility into external data
pathways. The integration_type field identifies which service was connected.
Runbook: |
1. Find all Anthropic.Activity events by actor:email_address in the 1 hour before and after the alert to understand the context of the integration connection
2. Check if actor:email_address has connected other integrations in the past 30 days to identify unusual patterns
3. Check if actor:ip_address matches previously seen IP addresses for this actor
Tags:
- Anthropic
- Compliance
- Integrations
Reports:
MITRE ATT&CK:
- TA0009:T1530 # Data from Cloud Storage
Tests:
- Name: GitHub integration connected
ExpectedResult: true
Log:
{
"id": "activity_01ABC123",
"created_at": "2026-05-06T17:38:28Z",
"organization_id": "org_01XYZ",
"type": "integration_user_connected",
"integration_type": "github",
"actor": {
"type": "user_actor",
"email_address": "user@example.com",
"user_id": "user_01ABC",
"ip_address": "10.0.0.1",
"user_agent": "Mozilla/5.0"
}
}
- Name: Non-matching event type
ExpectedResult: false
Log:
{
"id": "activity_01DEF456",
"created_at": "2026-05-06T17:38:28Z",
"organization_id": "org_01XYZ",
"type": "claude_chat_created",
"actor": {
"type": "user_actor",
"email_address": "user@example.com",
"user_id": "user_01DEF",
"ip_address": "10.0.0.2"
}
}
Detection logic
Condition
type eq "integration_user_connected"
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 |
integration_type |