detection.wiki

Detection rules › Kusto

Fortiweb - WAF Allowed threat

Status
available
Severity
high
Time window
1h
Group by
SrcIpAddr
Source
github.com/Azure/Azure-Sentinel

'Detects WAF "Allowed" action on threat events.'

MITRE ATT&CK coverage

TacticTechniques
Initial AccessT1133 External Remote Services, T1190 Exploit Public-Facing Application

Rule body kusto

id: 86e9409f-b9ea-4e9a-8b72-5132ba43bcae
name: Fortiweb - WAF Allowed threat
description: |
  'Detects WAF "Allowed" action on threat events.'
severity: High
status: Available
requiredDataConnectors:
  - connectorId: FortinetFortiWebAma
    dataTypes:
      - Fortiweb
queryFrequency: 1h
queryPeriod: 1h
triggerOperator: gt
triggerThreshold: 0
tactics:
  - InitialAccess
relevantTechniques:
  - T1190
  - T1133
query: |
  Fortiweb
  | where EventType =~ 'Attack'
  | where DvcAction =~ 'Allow'
  | summarize count() by SrcIpAddr
entityMappings:
  - entityType: IP
    fieldMappings:
      - identifier: Address
        columnName: SrcIpAddr
version: 1.0.2
kind: Scheduled

Stages and Predicates

Stage 1: source

Fortiweb

Stage 2: where

| where EventType =~ 'Attack'

Stage 3: where

| where DvcAction =~ 'Allow'

Stage 4: summarize

| summarize count() by SrcIpAddr

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
DvcActioneq
  • Allow
EventTypeeq
  • Attack

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
SrcIpAddrsummarize