Detection rules › Kusto

Apache - Command in URI

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

'Detects command in URI'

MITRE ATT&CK coverage

Rule body kusto

id: 54da6a42-3b00-11ec-8d3d-0242ac130003
name: Apache - Command in URI
description: |
  'Detects command in URI'
severity: High
status: Available
requiredDataConnectors:
  - connectorId: CustomLogsAma
    datatypes:
      - ApacheHTTPServer_CL
queryFrequency: 15m
queryPeriod: 15m
triggerOperator: gt
triggerThreshold: 0
tactics:
  - InitialAccess
relevantTechniques:
  - T1190
  - T1133
query: |
  let cmd_list = dynamic(['whoami', 'dpkg', 'useradd', 'sudo', 'cat']);
  ApacheHTTPServer
  | where UrlOriginal has_any (cmd_list)
  | extend UrlCustomEntity = UrlOriginal
entityMappings:
  - entityType: URL
    fieldMappings:
      - identifier: Url
        columnName: UrlCustomEntity
version: 1.0.3
kind: Scheduled

Stages and Predicates

Parameters

let cmd_list = dynamic(['whoami', 'dpkg', 'useradd', 'sudo', 'cat']);

Stage 1: source

ApacheHTTPServer

Stage 2: where

| where UrlOriginal has_any (cmd_list)

Stage 3: extend

| extend UrlCustomEntity = UrlOriginal

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
UrlOriginalmatch
  • cat
  • dpkg
  • sudo
  • useradd
  • whoami

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
UrlCustomEntityextend