PAC high severity

Status: available
Severity: high
Time window: 5h
Source: github.com/Azure/Azure-Sentinel

'High severity alerts found by Prancer.'

MITRE ATT&CK coverage

Tactic	Techniques
Reconnaissance	`T1595` Active Scanning

Rule body kusto

id: 7caa1c03-d20b-42f2-ac95-5232f6e570da
name:  PAC high severity
description: |
  'High severity  alerts found by Prancer.'
severity: High
requiredDataConnectors:
- connectorId: PrancerLogData
  dataTypes:
    - prancer_CL
queryFrequency: 5h
queryPeriod: 5h
triggerOperator: gt
triggerThreshold: 0
eventGroupingSettings:
  aggregationKind: SingleAlert
status: Available
tactics:
  - Reconnaissance
relevantTechniques:
  - T1595
query: |
 union prancer_CL
  | where data_data_resourceID_s contains 'Microsoft.Compute' and severity_s == 'High'
  | project
      Name = name_s,
      Severity = severity_s,
      Description = data_alert_description_s,
      URL = data_alert_url_s,
      Resource = data_data_resourceID_s,
      Config_ID = data_data_configId_s,
      Collection = data_data_applicationName_s,
      MITRE = data_alert_mitreId_s,
      Company = companyName_s,
      Solution = data_alert_solution_s,
      WASC_ID = data_alert_wascid_s,
      CWE_ID = data_alert_cweid_s,
      Evidence = data_alert_evidence_s,
      Request_Header = data_data_requestHeader_s,
      Request_Body = data_data_requestBody_s,
      Response_Header = data_data_responseHeader_s,
      Response_Body = data_data_responseBody_s,
      Other_Data = data_alert_other_s
entityMappings:
  - entityType: AzureResource
    fieldMappings:
      - identifier: ResourceId
        columnName: Resource
  - entityType: URL
    fieldMappings:
      - identifier: Url
        columnName: URL
alertDetailsOverride:
  alertDisplayNameFormat: "{{data_data_message_s}}"  
  alertDescriptionFormat: "{{data_data_description_s}}"
  alertSeverityColumnName: "{{data_data_severity_s}}"
  alertDynamicProperties:
    - alertProperty: RemediationSteps
      value: data_data_remediation_description_s
version: 1.0.2
kind: Scheduled

Stages and Predicates

Stage 1: `union`

union

Stage 2: `source`

prancer_CL

Stage 3: `where`

| where data_data_resourceID_s contains 'Microsoft.Compute' and severity_s == 'High'

Stage 4: `project`

| project
     Name = name_s,
     Severity = severity_s,
     Description = data_alert_description_s,
     URL = data_alert_url_s,
     Resource = data_data_resourceID_s,
     Config_ID = data_data_configId_s,
     Collection = data_data_applicationName_s,
     MITRE = data_alert_mitreId_s,
     Company = companyName_s,
     Solution = data_alert_solution_s,
     WASC_ID = data_alert_wascid_s,
     CWE_ID = data_alert_cweid_s,
     Evidence = data_alert_evidence_s,
     Request_Header = data_data_requestHeader_s,
     Request_Body = data_data_requestBody_s,
     Response_Header = data_data_responseHeader_s,
     Response_Body = data_data_responseBody_s,
     Other_Data = data_alert_other_s

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.

Field	Kind	Values
`data_data_resourceID_s`	contains	`Microsoft.Compute`
`severity_s`	eq	`High` 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.

Field	Source
`CWE_ID`	`project`
`Collection`	`project`
`Company`	`project`
`Config_ID`	`project`
`Description`	`project`
`Evidence`	`project`
`MITRE`	`project`
`Name`	`project`
`Other_Data`	`project`
`Request_Body`	`project`
`Request_Header`	`project`
`Resource`	`project`
`Response_Body`	`project`
`Response_Header`	`project`
`Severity`	`project`
`Solution`	`project`
`URL`	`project`
`WASC_ID`	`project`

`j` / `k`	Scroll down / up
`d` / `u`	Half-page down / up
`gg` / `G`	Top / bottom
`h` / `l`	History back / forward
`f`	Follow link (`Shift` = new tab)
`/`	Focus search
`?`	Toggle this help
`↑` / `↓`	Navigate search results
`Enter`	Open highlighted result
`Esc`	Close results / dialog

`type:`	`events` / `rules` / `providers`
`vendor:`	`sigma` / `elastic` / `splunk` / `kusto` / `chronicle` (vendor name alone also works: `sigma:`, `kql:`, `secops:`…)
`tactic:`	TA-id, slug, or name: `credential_access`, `TA0006`
`technique:`	technique or sub-technique ID: `T1003`, `T1003.001` (alias `tech:`)
`severity:`	`critical` / `high` / `medium` / `low` / `informational` (alias `sev:`)
`risk_score`	Numeric comparison on the Elastic risk score (0 to 100): `risk_score>50`, `risk_score<=20`, `risk_score=99` (alias `risk`; Elastic rules only)
`stages:`	Rules with exactly N pipeline stages
`correlation:`	`single_event` / `sequence` / `alternatives` / `alternatives_cross_log` / `all_required` / `correlated`
`with:`	Co-occurrence event-id; stacks (`with:4624 with:4769`) to require all, while a comma list in one occurrence (`with:4624,4769`) is an either-or group. Implies multi-event
`like:`	Structural neighbors of a rule slug (equivalents + subsumption stricter / broader): `like:comsvcs_lsass_memory_dump-splunk-sysmon`
`groupby:`	Entity-grouping substring match against `group_by_keys`: `groupby:user`, `groupby:host`
`uses:`	Rules whose predicate tree touches the field (any kind, any value): `uses:CommandLine`
`excludes:`	Rules with top-level `not()` clauses on the field (FP whitelists): `excludes:ParentImage`
`field:` / `value:`	Predicate search; narrows rule cards to those with a matching leaf and drives the indicator tier. Unquoted = substring, wildcards allowed (`value:mimikatz`)
`indicator:`	Shorthand for `field:F value:V`: `indicator:Image=*\powershell.exe`
`kind:`	Filter by predicate kind. Narrows rule cards to those carrying a matching predicate leaf (`vendor:elastic kind:cidr_match`) and drives the indicator tier: `contains` / `starts_with` / `ends_with` / `regex` / `cidr` / `eq` / `in` … (operator aliases `op:`/`match:`)
`has:` / `no:`	`sample`, `field`, `notes`, `refs`, `trace`, `thirdparty`, `rule`, `pattern`, `timewindow`, `threshold`, `newterms`, `sigma`/`elastic`/`splunk`/`kusto`/`chronicle`
`-op:val`	Exclude matches; works on most operators but not `type:`/`like:`/`has:`/`no:` (use `no:<flag>` to exclude a rule flag): `tactic:execution -vendor:splunk`. Standalone `-kind:`/`-field:`/`-value:` drop every rule carrying a matching predicate leaf (`type:rules -kind:is_null`)
`field:"…"` / `value:"…"`	Quoted value = anchored exact match (also allows spaces): `value:"net user"`
`a,b`	Comma = OR inside one operator (`vendor:sigma,elastic`, `severity:high,critical`); repeating a facet merges the same way. `field:`/`value:` never split (literal commas)
`vendors:` / `stage:`	Singular and plural spellings fold to the canonical operator and value: `tactics:` = `tactic:`, `type:event` = `type:events`, `correlation:sequences` = `correlation:sequence`, `has:thresholds` = `has:threshold`
`"quoted phrase"`	Exact-match a multi-word phrase (free text)

PAC high severity

MITRE ATT&CK coverage

Rule body kusto

Stages and Predicates

Stage 1: `union`

Stage 2: `source`

Stage 3: `where`

Stage 4: `project`

Indicators

Output fields

Keyboard shortcuts

Search operators

PAC high severity

MITRE ATT&CK coverage

Rule body kusto

Stages and Predicates

Stage 1: union

Stage 2: source

Stage 3: where

Stage 4: project

Indicators

Output fields

Stage 1: `union`

Stage 2: `source`

Stage 3: `where`

Stage 4: `project`