Detection rules › Kusto
PaloAlto - Possible attack without response
'Detects possible attack without response.'
MITRE ATT&CK coverage
| Tactic | Techniques |
|---|---|
| Initial Access | T1133 External Remote Services, T1190 Exploit Public-Facing Application |
Rule body kusto
id: b6d54840-51d3-11ec-bf63-0242ac130002
name: PaloAlto - Possible attack without response
description: |
'Detects possible attack without response.'
severity: High
status: Available
requiredDataConnectors:
- connectorId: CefAma
dataTypes:
- CommonSecurityLog
queryFrequency: 1h
queryPeriod: 1h
triggerOperator: gt
triggerThreshold: 0
tactics:
- InitialAccess
relevantTechniques:
- T1190
- T1133
query: |
PaloAltoCDLEvent
| where EventResourceId =~ 'THREAT'
| where DvcAction !has "block" or DvcAction !has "override" or DvcAction !has "deny"
| extend AccountCustomEntity = DstUsername, IPCustomEntity = SrcIpAddr, UrlCustomEntity = Url
entityMappings:
- entityType: Account
fieldMappings:
- identifier: Name
columnName: AccountCustomEntity
- entityType: IP
fieldMappings:
- identifier: Address
columnName: IPCustomEntity
- entityType: URL
fieldMappings:
- identifier: Url
columnName: UrlCustomEntity
version: 1.0.4
kind: Scheduled
Stages and Predicates
Stage 1: source
PaloAltoCDLEvent
Stage 2: where
| where EventResourceId =~ 'THREAT'
Stage 3: where
| where DvcAction !has "block" or DvcAction !has "override" or DvcAction !has "deny"
Stage 4: extend
| extend AccountCustomEntity = DstUsername, IPCustomEntity = SrcIpAddr, UrlCustomEntity = Url
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 |
|---|---|---|
EventResourceId | eq |
|
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 |
|---|---|
AccountCustomEntity | extend |
IPCustomEntity | extend |
UrlCustomEntity | extend |