Detection rules › Kusto

Web sites blocked by Eset

Status
available
Severity
low
Time window
5m
Source
github.com/Azure/Azure-Sentinel

'Create alert on web sites blocked by Eset.'

MITRE ATT&CK coverage

Rule body kusto

id: 84ad2f8a-b64c-49bc-b669-bdb4fd3071e9
name: Web sites blocked by Eset
description: |
  'Create alert on web sites blocked by Eset.'
severity: Low
status: Available
requiredDataConnectors:
  - connectorId: EsetSMC
    dataTypes:
      - eset_CL
queryFrequency: 5m
queryPeriod: 5m
triggerOperator: gt
triggerThreshold: 0
tactics:
  - Exfiltration
  - CommandAndControl
  - InitialAccess
relevantTechniques:
  - T1189
  - T1567
  - T1071.001
query: |
  eset_CL
  | where event_type_s == 'FilteredWebsites_Event'
  | extend AccountCustomEntity = username_s, URLCustomEntity = object_uri_s, HostCustomEntity = hostname_s, IPCustomEntity = ipv4_s
entityMappings:
  - entityType: Account
    fieldMappings:
      - identifier: FullName
        columnName: AccountCustomEntity
  - entityType: Host
    fieldMappings:
      - identifier: FullName
        columnName: HostCustomEntity
  - entityType: IP
    fieldMappings:
      - identifier: Address
        columnName: IPCustomEntity
  - entityType: URL
    fieldMappings:
      - identifier: Url
        columnName: URLCustomEntity
version: 1.0.1
kind: Scheduled

Stages and Predicates

Stage 1: source

eset_CL

Stage 2: where

| where event_type_s == 'FilteredWebsites_Event'

Stage 3: extend

| extend AccountCustomEntity = username_s, URLCustomEntity = object_uri_s, HostCustomEntity = hostname_s, IPCustomEntity = ipv4_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.

FieldKindValues
event_type_seq
  • FilteredWebsites_Event 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
AccountCustomEntityextend
HostCustomEntityextend
IPCustomEntityextend
URLCustomEntityextend