detection.wiki

Detection rules › Kusto

Trend Micro CAS - DLP violation

Status
available
Severity
high
Time window
15m
Source
github.com/Azure/Azure-Sentinel

'Detects when DLP policy violation occurs.'

MITRE ATT&CK coverage

TacticTechniques
ExfiltrationT1048 Exfiltration Over Alternative Protocol

Rule body kusto

id: 1ddeb8ad-cad9-4db4-b074-f9da003ca3ed
name: Trend Micro CAS - DLP violation
description: |
  'Detects when DLP policy violation occurs.'
severity: High
status: Available
requiredDataConnectors:
  - connectorId: TrendMicroCAS
    dataTypes:
      - TrendMicroCAS
queryFrequency: 15m
queryPeriod: 15m
triggerOperator: gt
triggerThreshold: 0
tactics:
  - Exfiltration
relevantTechniques:
  - T1048
query: |
  TrendMicroCAS
  | where isnotempty(TriggeredDlpTemplate)
  | extend AccountCustomEntity = DstUserName
entityMappings:
  - entityType: Account
    fieldMappings:
      - identifier: Name
        columnName: AccountCustomEntity
version: 1.0.1
kind: Scheduled

Stages and Predicates

Stage 1: source

TrendMicroCAS

Stage 2: where

| where isnotempty(TriggeredDlpTemplate)

Stage 3: extend

| extend AccountCustomEntity = DstUserName

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
TriggeredDlpTemplateis_not_null
  • (no value, null check)

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.

FieldSource
AccountCustomEntityextend