Detection rules › Kusto

PaloAlto - Put and post method request in high risk file type

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

'Detects put and post method request in high risk file type.'

MITRE ATT&CK coverage

Rule body kusto

id: f12e9d10-51ca-11ec-bf63-0242ac130002
name: PaloAlto - Put and post method request in high risk file type
description: |
  'Detects put and post method request in high risk file type.'
severity: High
status: Available
requiredDataConnectors:
  - connectorId: CefAma
    dataTypes:
      - CommonSecurityLog
queryFrequency: 10m
queryPeriod: 10m
triggerOperator: gt
triggerThreshold: 0
tactics:
  - InitialAccess
relevantTechniques:
  - T1190
  - T1133
query: |
  let HighRiskFileType = dynamic(['.exe', '.msi', '.msp', '.jar', '.bat', '.cmd', '.js', '.jse', 'ws', '.ps1', '.ps2', '.msh']);
  PaloAltoCDLEvent
  | where EventResourceId =~ 'THREAT'
  | where EventResult =~ 'file'
  | where HttpRequestMethod has_any ("POST", "PUT")
  | where FileType in (HighRiskFileType)
  | extend FileCustomEntity = SrcFileName
entityMappings:
  - entityType: File
    fieldMappings:
      - identifier: Name
        columnName: FileCustomEntity
version: 1.0.4
kind: Scheduled

Stages and Predicates

Parameters

let HighRiskFileType = dynamic(['.exe', '.msi', '.msp', '.jar', '.bat', '.cmd', '.js', '.jse', 'ws', '.ps1', '.ps2', '.msh']);

Stage 1: source

PaloAltoCDLEvent

Stage 2: where

| where EventResourceId =~ 'THREAT'

Stage 3: where

| where EventResult =~ 'file'

Stage 4: where

| where HttpRequestMethod has_any ("POST", "PUT")

Stage 5: where

| where FileType in (HighRiskFileType)

Stage 6: extend

| extend FileCustomEntity = SrcFileName

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
EventResourceIdeq
  • THREAT
EventResulteq
  • file
FileTypein
  • .bat transforms: cased
  • .cmd transforms: cased
  • .exe transforms: cased
  • .jar transforms: cased
  • .js transforms: cased
  • .jse transforms: cased
  • .msh transforms: cased
  • .msi transforms: cased
  • .msp transforms: cased
  • .ps1 transforms: cased
  • .ps2 transforms: cased
  • ws transforms: cased
HttpRequestMethodmatch
  • POST
  • PUT

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
FileCustomEntityextend