ApexOne - Spyware with failed response

Back


Id	c92d9fe4-67b6-11ec-90d6-0242ac120003
Rulename	ApexOne - Spyware with failed response
Description	Detects spyware with failed response.
Severity	High
Tactics	InitialAccess
Techniques	T1190
Required data connectors	CefAma
Kind	Scheduled
Query frequency	1h
Query period	1h
Trigger threshold	0
Trigger operator	gt
Source Uri	https://github.com/Azure/Azure-Sentinel/blob/master/Solutions/Trend Micro Apex One/Analytic Rules/TMApexOneSpywareWithFailedResponse.yaml
Version	1.0.3
Arm template	c92d9fe4-67b6-11ec-90d6-0242ac120003.json

KQL

TMApexOneEvent
| where EventMessage has "Spyware Detected"
| where ActionResult has_any ("No action", "Unable to")
| extend IPCustomEntity = SrcIpAddr, AccountCustomEntity = DstUserName

YAML

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

ARM