Detection rules › Kusto

Darktrace AI Analyst

This is a third-party alert feed, not a detection over modeled telemetry. The vendor product raised the finding; this rule forwards it into the SIEM. It is searchable for reference but is excluded from the detection-rule browse and the ATT&CK coverage matrix.

Severity: high
Time window: 5m
Source: github.com/Azure/Azure-Sentinel

'This rule creates Microsoft Sentinel Incidents based on Darktrace AI Analyst Incidents, fetched every 5 minutes.'

Rule body kusto

id: ffa2977f-3077-4bba-b1bf-f3417699cbb0
name: Darktrace AI Analyst 
description: |
  'This rule creates Microsoft Sentinel Incidents based on Darktrace AI Analyst Incidents, fetched every 5 minutes.'
severity: High
requiredDataConnectors:
  - connectorId: DarktraceRESTConnector
    dataTypes:
      - darktrace_model_alerts_CL
queryFrequency: 5m
queryPeriod: 5m 
triggerOperator: gt
triggerThreshold: 0
tactics: [] # no tactics are ingested for AIA events at the moment 
relevantTechniques: []
query: |
  darktrace_model_alerts_CL 
  | where dtProduct_s =="AI Analyst"
  | project-rename  EventStartTime=startTime_s, EventEndTime = endTime_s, NetworkRuleName=title_s, DtCurrentGroup=externalId_g, ThreatCategory=dtProduct_s, ThreatRiskLevel=score_d, SrcHostname=hostname_s, SrcIpAddr=deviceIP_s, DtURL=url_s, DtSummary=summary_s, DtGroupScore=groupScore_d, DtGroupCategory=groupCategory_s, DtSrcDeviceName=bestDeviceName_s, DtIndentifier=identifier_s, ActivityID=activityId_s, DtGroupingID=groupingId_s, DtGroupByActivity=groupByActivity_b, DtSummaryFirstSentence=summaryFirstSentence_s, DtNewEvent=newEvent_b, DtCGLegacy=currentGroup_s, DtGroupPreviousGroups=groupPreviousGroups_s, DtTime=time_s, DtSeverity=Severity, DtLongitude=longitude_d, DtLatitude=latitude_d  
  | extend EventVendor = "Darktrace", EventProduct = "Darktrace DETECT", DtSentinelCategory=DtGroupCategory
  | extend DtSentinelCategory = case (DtGroupCategory == "compliance", "Low", 
                                      DtGroupCategory == "suspicious", "Medium",
                                      "High") //compliance -> low, suspcious -> medium, critical -> high
eventGroupingSettings:
  aggregationKind: AlertPerResult
entityMappings: 
 - entityType: Host
   fieldMappings:
    - identifier: HostName
      columnName: SrcHostname
 - entityType: IP
   fieldMappings:
    - identifier: Address
      columnName: SrcIpAddr
customDetails:
  EventStartTime: EventStartTime
  EventEndTime: EventEndTime
  NetworkRuleName: NetworkRuleName
  DtCurrentGroup: DtCurrentGroup
  ThreatRiskLevel: ThreatRiskLevel
  DtSummary: DtSummary
  DtGroupScore: DtGroupScore
  DtGroupCategory: DtGroupCategory
  DtSentinelCategory: DtSentinelCategory
  DtSrcDeviceName: DtSrcDeviceName
  DtNewEvent: DtNewEvent
  DtSeverity: DtSeverity
alertDetailsOverride: 
  alertDisplayNameFormat: 'Darktrace: {{ThreatRiskLevel}} - {{NetworkRuleName}}'
  alertDescriptionFormat: '{{DtSummary}}'
  alertTacticsColumnName: # leave empty
  alertSeverityColumnName: # leave empty 
  alertDynamicProperties:
    - alertProperty: AlertLink
      value: DtURL
    - alertProperty: ProviderName
      value: EventVendor
    - alertProperty: ProductName
      value: EventProduct
    - alertProperty: ProductComponentName
      value: ThreatCategory
    - alertProperty: Severity
      value: DtSentinelCategory
version: 1.1.0
kind: NRT

Stages and Predicates

Stage 1: `source`

darktrace_model_alerts_CL

Stage 2: `where`

| where dtProduct_s =="AI Analyst"

Stage 3: `project-rename`

| project-rename  EventStartTime=startTime_s, EventEndTime = endTime_s, NetworkRuleName=title_s, DtCurrentGroup=externalId_g, ThreatCategory=dtProduct_s, ThreatRiskLevel=score_d, SrcHostname=hostname_s, SrcIpAddr=deviceIP_s, DtURL=url_s, DtSummary=summary_s, DtGroupScore=groupScore_d, DtGroupCategory=groupCategory_s, DtSrcDeviceName=bestDeviceName_s, DtIndentifier=identifier_s, ActivityID=activityId_s, DtGroupingID=groupingId_s, DtGroupByActivity=groupByActivity_b, DtSummaryFirstSentence=summaryFirstSentence_s, DtNewEvent=newEvent_b, DtCGLegacy=currentGroup_s, DtGroupPreviousGroups=groupPreviousGroups_s, DtTime=time_s, DtSeverity=Severity, DtLongitude=longitude_d, DtLatitude=latitude_d

Stage 4: `extend`

| extend EventVendor = "Darktrace", EventProduct = "Darktrace DETECT", DtSentinelCategory=DtGroupCategory

Stage 5: `extend`

| extend DtSentinelCategory = case (DtGroupCategory == "compliance", "Low", 
                                    DtGroupCategory == "suspicious", "Medium",
                                    "High")

DtSentinelCategory =

ifDtGroupCategory == "compliance""Low"

elifDtGroupCategory == "suspicious""Medium"

else"High"

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
`dtProduct_s`	eq	`AI Analyst` transforms: `cased`

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
`ActivityID`	`project-rename`
`DtCGLegacy`	`project-rename`
`DtCurrentGroup`	`project-rename`
`DtGroupByActivity`	`project-rename`
`DtGroupCategory`	`project-rename`
`DtGroupPreviousGroups`	`project-rename`
`DtGroupScore`	`project-rename`
`DtGroupingID`	`project-rename`
`DtIndentifier`	`project-rename`
`DtLatitude`	`project-rename`
`DtLongitude`	`project-rename`
`DtNewEvent`	`project-rename`
`DtSeverity`	`project-rename`
`DtSrcDeviceName`	`project-rename`
`DtSummary`	`project-rename`
`DtSummaryFirstSentence`	`project-rename`
`DtTime`	`project-rename`
`DtURL`	`project-rename`
`EventEndTime`	`project-rename`
`EventStartTime`	`project-rename`
`NetworkRuleName`	`project-rename`
`SrcHostname`	`project-rename`
`SrcIpAddr`	`project-rename`
`ThreatCategory`	`project-rename`
`ThreatRiskLevel`	`project-rename`
`DtSentinelCategory`	`extend`
`EventProduct`	`extend`
`EventVendor`	`extend`

`j` / `k`	Scroll down / up
`d` / `u`	Half-page down / up
`gg` / `G`	Top / bottom
`h` / `l`	History back / forward
`f`	Follow link (`Shift` = new tab)
`/`	Focus search
`?`	Toggle this help
`↑` / `↓`	Navigate search results
`Enter`	Open highlighted result
`Esc`	Close results / dialog

`type:`	`events` / `rules` / `providers`
`vendor:`	`sigma` / `elastic` / `splunk` / `kusto` / `chronicle` (vendor name alone also works: `sigma:`, `kql:`, `secops:`…)
`tactic:`	TA-id, slug, or name: `credential_access`, `TA0006`
`technique:`	technique or sub-technique ID: `T1003`, `T1003.001` (alias `tech:`)
`severity:`	`critical` / `high` / `medium` / `low` / `informational` (alias `sev:`)
`risk_score`	Numeric comparison on the Elastic risk score (0 to 100): `risk_score>50`, `risk_score<=20`, `risk_score=99` (alias `risk`; Elastic rules only)
`stages:`	Rules with exactly N pipeline stages
`correlation:`	`single_event` / `sequence` / `alternatives` / `alternatives_cross_log` / `all_required` / `correlated`
`with:`	Co-occurrence event-id; stacks (`with:4624 with:4769`) to require all, while a comma list in one occurrence (`with:4624,4769`) is an either-or group. Implies multi-event
`like:`	Structural neighbors of a rule slug (equivalents + subsumption stricter / broader): `like:comsvcs_lsass_memory_dump-splunk-sysmon`
`groupby:`	Entity-grouping substring match against `group_by_keys`: `groupby:user`, `groupby:host`
`uses:`	Rules whose predicate tree touches the field (any kind, any value): `uses:CommandLine`
`excludes:`	Rules with top-level `not()` clauses on the field (FP whitelists): `excludes:ParentImage`
`field:` / `value:`	Predicate search; narrows rule cards to those with a matching leaf and drives the indicator tier. Unquoted = substring, wildcards allowed (`value:mimikatz`)
`indicator:`	Shorthand for `field:F value:V`: `indicator:Image=*\powershell.exe`
`kind:`	Filter by predicate kind. Narrows rule cards to those carrying a matching predicate leaf (`vendor:elastic kind:cidr_match`) and drives the indicator tier: `contains` / `starts_with` / `ends_with` / `regex` / `cidr` / `eq` / `in` … (operator aliases `op:`/`match:`)
`has:` / `no:`	`sample`, `field`, `notes`, `refs`, `trace`, `thirdparty`, `rule`, `pattern`, `timewindow`, `threshold`, `newterms`, `sigma`/`elastic`/`splunk`/`kusto`/`chronicle`
`-op:val`	Exclude matches; works on most operators but not `type:`/`like:`/`has:`/`no:` (use `no:<flag>` to exclude a rule flag): `tactic:execution -vendor:splunk`. Standalone `-kind:`/`-field:`/`-value:` drop every rule carrying a matching predicate leaf (`type:rules -kind:is_null`)
`field:"…"` / `value:"…"`	Quoted value = anchored exact match (also allows spaces): `value:"net user"`
`a,b`	Comma = OR inside one operator (`vendor:sigma,elastic`, `severity:high,critical`); repeating a facet merges the same way. `field:`/`value:` never split (literal commas)
`vendors:` / `stage:`	Singular and plural spellings fold to the canonical operator and value: `tactics:` = `tactic:`, `type:event` = `type:events`, `correlation:sequences` = `correlation:sequence`, `has:thresholds` = `has:threshold`
`"quoted phrase"`	Exact-match a multi-word phrase (free text)

Darktrace AI Analyst

Rule body kusto

Stages and Predicates

Stage 1: `source`

Stage 2: `where`

Stage 3: `project-rename`

Stage 4: `extend`

Stage 5: `extend`

Indicators

Output fields

Keyboard shortcuts

Search operators

Darktrace AI Analyst

Rule body kusto

Stages and Predicates

Stage 1: source

Stage 2: where

Stage 3: project-rename

Stage 4: extend

Stage 5: extend

Indicators

Output fields

Stage 1: `source`

Stage 2: `where`

Stage 3: `project-rename`

Stage 4: `extend`

Stage 5: `extend`