Source inside CommonSecurityLog
Trend Micro Apex Central (CEF)
Trend Micro Apex One endpoint detections managed by Apex Central
Recommendation
High-value events that need near-real-time detection, low-volume join targets, or high-value tables the lake cannot hold.
Retention is set per table, so the retention for this source is advisory.
How the matrix worksC1 Detections and findings
Detections, alerts, incidents, security findings (vulnerability and posture findings), and detection pipeline health
T1 Near-real-time detection
Generic detections need near-real-time matching on single events.
Rows that belong to this source
DeviceVendor =~ "Trend Micro" and DeviceProduct =~ "Apex Central"Rules query these rows through the TMApexOneEvent parser.
Sources for this recommendation
- Azure-Sentinel public content corpus Table identity and usage evidence from public analytics rules, hunting queries, parsers, and solution content. Classification, tier, retention, and billing recommendations require human review.
- Log Baseline classification rules Value rules C1-C9 mapped to ASD and CISA guidance, and tier rules T1-T5 including plan support. Stored per table as valueRule and tierRule.
- Log Baseline volume model Judgment-based volume driver and relative volume class per table. Not measured tenant volume.
- ASD ACSC Priority logs for SIEM ingestion: Practitioner guidance Loosely prioritized log categories (EDR, network devices, domain controllers, Windows, virtualisation, cloud, containers, databases, MDM, DNS, Linux, macOS) used by the classification rules. Collection priority, not storage tier.
- CISA Guidance for Implementing M-21-31 Prioritized event types for collection and storage (ICAM, operating systems, network infrastructure, cloud, AWS, Azure, Microsoft 365, GCP) used by the classification rules. Collection priority, not storage tier.