detection.wiki

Detection rules › Panther

Carbon Black Admin Role Granted

Severity
high
Log types
CarbonBlack.Audit
Tags
Privilege Escalation, Account Manipulation
Reference
https://docs.vmware.com/en/VMware-Carbon-Black-Cloud/services/carbon-black-cloud-user-guide/GUID-CF5ACD2C-A534-46C8-AE06-E1884DB37B58.html
Source
github.com/panther-labs/panther-analysis

Detects when a user is granted Admin or Super Admin permissions.

MITRE ATT&CK coverage

TacticTechniques
Privilege EscalationT1098 Account Manipulation

Rule body yaml

AnalysisType: rule
RuleID: "CarbonBlack.Audit.Admin.Grant"
LogTypes:
  - CarbonBlack.Audit
Description: "Detects when a user is granted Admin or Super Admin permissions."
DisplayName: "Carbon Black Admin Role Granted"
Enabled: true
Filename: cb_audit_admin_grant.py
Severity: High
Tags:
  - Privilege Escalation
  - Account Manipulation
Reports:
  MITRE ATT&CK:
    - TA0004:T1098
Reference: https://docs.vmware.com/en/VMware-Carbon-Black-Cloud/services/carbon-black-cloud-user-guide/GUID-CF5ACD2C-A534-46C8-AE06-E1884DB37B58.html
Threshold: 1
DedupPeriodMinutes: 60
Tests:
  - Name: Super Admin granted
    ExpectedResult: true
    Log:
      {
        "clientIp": "12.34.56.78",
        "description": "Created grant: psc:cnn:A1234567:BC1234567890 with role Super Admin",
        "eventId": "66443924833011eeac3cb393f3d07f9f",
        "eventTime": "2023-11-14 20:57:19.186000000",
        "flagged": false,
        "loginName": "bob.ross@acme.com",
        "orgName": "acme.com",
        "requestUrl": "/access/v2/orgs/A1234567/grants",
        "verbose": false,
      }
  - Name: Admin granted
    ExpectedResult: true
    Log:
      {
        "clientIp": "12.34.56.78",
        "description": "Created grant: psc:cnn:A1234567:BC1234567890 with role Administrator",
        "eventId": "66443924833011eeac3cb393f3d07f9f",
        "eventTime": "2023-11-14 20:57:19.186000000",
        "flagged": false,
        "loginName": "bob.ross@acme.com",
        "orgName": "acme.com",
        "requestUrl": "/access/v2/orgs/A1234567/grants",
        "verbose": false,
      }
  - Name: Other role granted
    ExpectedResult: false
    Log:
      {
        "clientIp": "12.34.56.78",
        "description": "Created grant: psc:cnn:A1234567:BC1234567890 with role Read Only",
        "eventId": "66443924833011eeac3cb393f3d07f9f",
        "eventTime": "2023-11-14 20:57:19.186000000",
        "flagged": false,
        "loginName": "bob.ross@acme.com",
        "orgName": "acme.com",
        "requestUrl": "/access/v2/orgs/A1234567/grants",
        "verbose": false,
      }

Detection logic

Condition

requestUrl starts_with "/access/"
description starts_with "Updated grant: " or description starts_with "Created grant: "
description contains "Admin"

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.

FieldKindValues
descriptioncontains
  • Admin
descriptionstarts_with
  • Created grant:
  • Updated grant:
requestUrlstarts_with
  • /access/

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