opentide

VMware Carbon Black Cloud (`platform::carbon_black_cloud::1.0`)

`configurations.carbon_black_cloud` is a Carbon Black Cloud Enterprise EDR watchlist report. The detection text is a Lucene query stored as an IOC. Query validation is supported. The IOC id is the Tide rule's `metadata.uuid`. The report is matched by title inside a watchlist that must already exist on the console.

Shared fields are defined in platforms.

Requirements

  • Static validation MUST require a non-blank query.
  • organizations, watchlist, report, and tags MAY be omitted and still validate.
  • Registry load MUST accept organization as an alias of organizations.
  • Deploy MUST collapse newlines in query to spaces.
  • Deploy MUST refuse to create a report on a watchlist that does not already exist.
  • Legacy external-id keys are invalid. rule_id_bundle, rule_id, and rule_id::<tenant> fail external_id_in_rule. Migration removes them as external_id_unused; the IOC remains addressed by metadata.uuid and the report by title.
  • Severity MUST be taken from response.alert_severity. The block has no severity field.

Definition

Block

FieldTypeRequiredDefaultDescription
querystringyes—Lucene query. Multiline in YAML. Deploy joins lines with spaces.
organizationslist[string]optionalnullAccepted, including the loader alias organization. The current deployer targets the tenant the run selects and does not filter on this list.
watchliststringoptionalnullWatchlist name. Deploy uses the tenant watchlist when omitted. The watchlist must already exist.
reportstringoptionalnullReport title. Deploy uses the Tide rule name when omitted.
tagslist[string]optionalnullExtra report tags, appended after the tags opentide always writes.

Report tags and severity

Deploy always tags the report with:

  1. The block status, stringified. An omitted status is the string None.
  2. When the rule has detection_model: that UUID (an objective, or a signal under one), then the ATT&CK technique ids resolved from it.
  3. tags from this block.

Severity is the Carbon Black report score for response.alert_severity:

response.alert_severityReport severity
Informational1
Low3
Medium6
High8
Critical10

When response is missing, deploy uses Low (score 3). An unmapped severity fails deploy.

Deploy

The report description is the Tide rule description.

Block status strategyCarbon Black result
DISABLEMENT or DELETIONThe report is deleted when its title is the rule name. When the report title is a shared report (report names something else) the IOC is removed, and the report is deleted only if that IOC was the last one.
any otherIOC upserted. A missing report is created and attached to the watchlist. An existing report whose title is the Tide rule name is updated, and its severity is replaced whenever the mapped score differs. A shared report (the report title is not the rule name) is updated too, but its severity rises only when the new score is higher.

metadata.uuid is the IOC id, so a later deploy replaces that IOC instead of adding a second one.

Relationships

Defaults & overrides

FieldDefault
watchlisttenant setup watchlist
reportTide rule name
Severityresponse.alert_severity, else Low
IOC idmetadata.uuid

Examples

configurations:
  carbon_black_cloud:
    enabled: true
    schema: platform::carbon_black_cloud::1.0
    status: STAGING
    query: process_name:cmd.exe
    watchlist: opentide
    report: Suspicious command processor
    tags:
      - windows
      - execution

Fixture: fixtures/platforms/carbon-black-cloud.yaml.

History

VersionDateNotes
1.02026-09-30Initial field contract from the Carbon Black configuration model, loader, and deployer.
1.12026-10-16rule_id_bundle is removed. Legacy external-id keys fail external_id_in_rule, and migration removes them as external_id_unused (RFC 0010). Identity stays metadata.uuid for the IOC and the title for the report. Schema id unchanged.

On this page