Detection rules › Panther
Carbon Black User Added Outside Org
Detects when a user from a different organization is added to Carbon Black.
MITRE ATT&CK coverage
| Tactic | Techniques |
|---|---|
| Persistence | T1136 Create Account |
Rule body yaml
AnalysisType: rule
RuleID: "CarbonBlack.Audit.User.Added.Outside.Org"
LogTypes:
- CarbonBlack.Audit
Description: "Detects when a user from a different organization is added to Carbon Black."
DisplayName: "Carbon Black User Added Outside Org"
Enabled: true
Filename: cb_audit_user_added_outside_org.py
Severity: High
Tags:
- Persistence
- Create Account
Reports:
MITRE ATT&CK:
- TA0003:T1136
Reference: https://docs.vmware.com/en/VMware-Carbon-Black-Cloud/services/carbon-black-cloud-user-guide/GUID-516BAF8C-A13D-4FC7-AA92-923159C13083.html
Threshold: 1
DedupPeriodMinutes: 60
Tests:
- Name: Outside org
ExpectedResult: true
Log:
{
"clientIp": "12.34.56.78",
"description": "Added user badguy@acme.io to org 12345 (Email Invitation)",
"eventId": "d109e568832111ee8ab2057b240e65f8",
"eventTime": "2023-11-14 19:12:55.917000000",
"flagged": false,
"loginName": "bob.ross@acme.com",
"orgName": "acme.com",
"verbose": false,
}
- Name: Inside org
ExpectedResult: false
Log:
{
"clientIp": "12.34.56.78",
"description": "Added user goodguy@acme.com to org 12345 (Email Invitation)",
"eventId": "d109e568832111ee8ab2057b240e65f8",
"eventTime": "2023-11-14 19:12:55.917000000",
"flagged": false,
"loginName": "bob.ross@acme.com",
"orgName": "acme.com",
"verbose": false,
}
Detection logic
Condition
description starts_with "Added user "
This rule also runs imperative logic the parser cannot express as a filter; the conditions above are the structured part it could extract.
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 |
|---|---|---|
description | starts_with |
|
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 |
|---|
loginName |
clientIp |
description |