Detection rules › Kusto

Imperva - Forbidden HTTP request method in request

Status
available
Severity
medium
Time window
1h
Source
github.com/Azure/Azure-Sentinel

'Detects connections with unexpected HTTP request method.'

MITRE ATT&CK coverage

Rule body

id: 7ebc9e24-319c-4786-9151-c898240463bc
name: Imperva - Forbidden HTTP request method in request
description: |
  'Detects connections with unexpected HTTP request method.'
severity: Medium
status: Available
requiredDataConnectors:
  - connectorId: ImpervaWAFCloudAPI
    dataTypes:
      - ImpervaWAFCloud
queryFrequency: 1h
queryPeriod: 1h
triggerOperator: gt
triggerThreshold: 0
tactics:
  - InitialAccess
relevantTechniques:
  - T1190
  - T1133
query: |
  let bl_http_methods = dynamic(['PUT', 'HEAD', 'OPTIONS', 'TRACE', 'POST']);
  ImpervaWAFCloud
  | where HttpRequestMethod in~ (bl_http_methods)
  | extend IPCustomEntity = SrcIpAddr, UrlCustomEntity = UrlOriginal
entityMappings:
  - entityType: IP
    fieldMappings:
      - identifier: Address
        columnName: IPCustomEntity
  - entityType: URL
    fieldMappings:
      - identifier: Url
        columnName: UrlCustomEntity
version: 1.0.0
kind: Scheduled

Stages and Predicates

Parameters

let bl_http_methods = dynamic(['PUT', 'HEAD', 'OPTIONS', 'TRACE', 'POST']);

Stage 1: source

ImpervaWAFCloud

Stage 2: where

| where HttpRequestMethod in~ (bl_http_methods)

Stage 3: extend

| extend IPCustomEntity = SrcIpAddr, UrlCustomEntity = UrlOriginal

Indicators

These rows show field, operator, and value matches.

FieldKindValuesSearch
HttpRequestMethodin
  • HEAD
  • OPTIONS
  • POST
  • PUT
  • TRACE
field:"HttpRequestMethod" kind:in

Output fields

These fields are emitted when the rule matches.

FieldSource
IPCustomEntityextend
UrlCustomEntityextend