Detection rules › Kusto

ApexOne - Spyware with failed response

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

'Detects spyware with failed response.'

MITRE ATT&CK coverage

TacticTechniques
Initial Access

Rule body

id: c92d9fe4-67b6-11ec-90d6-0242ac120003
name: ApexOne - Spyware with failed response
description: |
  'Detects spyware with failed response.'
severity: High
status: Available
requiredDataConnectors:
  - connectorId: CefAma
    dataTypes:
      - CommonSecurityLog
queryFrequency: 1h
queryPeriod: 1h
triggerOperator: gt
triggerThreshold: 0
tactics:
  - InitialAccess
relevantTechniques:
  - T1190
query: |
  TMApexOneEvent
  | where EventMessage has "Spyware Detected"
  | where ActionResult has_any ("No action", "Unable to")
  | extend IPCustomEntity = SrcIpAddr, AccountCustomEntity = DstUserName
entityMappings:
  - entityType: IP
    fieldMappings:
      - identifier: Address
        columnName: IPCustomEntity
  - entityType: Account
    fieldMappings:
      - identifier: Name
        columnName: AccountCustomEntity
version: 1.0.3
kind: Scheduled

Stages and Predicates

Stage 1: source

TMApexOneEvent

Stage 2: where

| where EventMessage has "Spyware Detected"

Stage 3: where

| where ActionResult has_any ("No action", "Unable to")

Stage 4: extend

| extend IPCustomEntity = SrcIpAddr, AccountCustomEntity = DstUserName

Indicators

These rows show field, operator, and value matches.

FieldKindValuesSearch
ActionResultmatch
  • No action transforms: term
  • Unable to transforms: term
field:"ActionResult" kind:match
EventMessagematch
  • Spyware Detected transforms: term
field:"EventMessage" kind:match value:"Spyware Detected"

Output fields

These fields are emitted when the rule matches.

FieldSource
AccountCustomEntityextend
IPCustomEntityextend