↳ GitHub sourceAnalytics ruleHigh

ApexOne - Spyware with failed response

View on GitHub ↗Original file ↗

Description

'Detects spyware with failed response.'

Rule type: Scheduled
Version: 1.0.3
Declared status: Available
Query frequency: 1h
Query period: 1h
Trigger: gt 0

Declared MITRE coverage

InitialAccess T1190

Declared sources

Metadata from the source file. No dependencies inferred from KQL.

Connectors

CefAma

Data types

CommonSecurityLog

KQL query

Original query, unchanged.

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

Declared entities

IPAccount

Source provenance

GitHub

Displayed values come from files in Azure/Azure-Sentinel. They describe the published template, not your workspace configuration.

File: Solutions/Trend Micro Apex One/Analytic Rules/TMApexOneSpywareWithFailedResponse.yaml ↗
Commit: 9800e51 ↗
Source identifier: c92d9fe4-67b6-11ec-90d6-0242ac120003

Additional source files 2

Solutions/Trend Micro Apex One/Analytic Rules/TMApexOneSpywareWithFailedResponse.yamlsource ↗Solutions/Trend Micro Apex One/Data/Solution_Trend Micro Apex One.jsonsolution-membership ↗

GSTEP / CATALOG TRACKING

Added to catalog : 16 Sept 2026 · 05:49 UTC
Last change observed : 16 Sept 2026 · 05:49 UTC

GSTEP sync dates, separate from the source content’s publication dates.