Detection rules › Kusto

New High Severity Vulnerability Detected Across Multiple Hosts

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

'This creates an incident when a new high severity vulnerability is detected across multilple hosts'

MITRE ATT&CK coverage

TacticTechniques
Initial AccessT1190 Exploit Public-Facing Application

Rule body kusto

id: 6116dc19-475a-4148-84b2-efe89c073e27
name: New High Severity Vulnerability Detected Across Multiple Hosts
description: |
  'This creates an incident when a new high severity vulnerability is detected across multilple hosts'
severity: Medium
status: Available
requiredDataConnectors:
  - connectorId: QualysVMLogsCCPDefinition
    dataTypes:
      - QualysHostDetection
queryFrequency: 1h
queryPeriod: 1h
triggerOperator: gt
triggerThreshold: 0
tactics:
  - InitialAccess
relevantTechniques:
  - T1190
query: |
  let threshold = 10;
  QualysHostDetection
  | extend Status = tostring(Status), Vulnerability = tostring(QID), Severity = tostring(Severity)
  | where Status =~ "New" and Severity == "5"
  | summarize StartTime = min(TimeGenerated), EndTime = max(TimeGenerated), dcount(NetBios) by tostring(QID)
  | where dcount_NetBios >= threshold
  | extend timestamp = StartTime
version: 1.0.2
kind: Scheduled

Stages and Predicates

Parameters

let threshold = 10;

Stage 1: source

QualysHostDetection

Stage 2: extend

| extend Status = tostring(Status), Vulnerability = tostring(QID), Severity = tostring(Severity)

Stage 3: where

| where Status =~ "New" and Severity == "5"

Stage 4: summarize

| summarize StartTime = min(TimeGenerated), EndTime = max(TimeGenerated), dcount(NetBios) by tostring(QID)

Stage 5: where

| where dcount_NetBios >= threshold

Stage 6: extend

| extend timestamp = StartTime

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
Severityeq
  • 5 transforms: cased
Statuseq
  • New
dcount_NetBiosge
  • 10 transforms: cased

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
EndTimesummarize
StartTimesummarize
timestampextend