Security operations / Alert
SecurityIncident
Sentinel incidents created from correlated alerts and manual escalation
Recommendation
High-value events that need near-real-time detection, low-volume join targets, or high-value tables the lake cannot hold.
How the matrix worksC1 Detections and findings
Detections, alerts, incidents, security findings (vulnerability and posture findings), and detection pipeline health
ACSC
- 1. Endpoint detection and response (EDR) logsEDR detections
- 2. Network device logsIDS/IPS alerts
- Risk considerationsCheck the health of priority sources
CISA
No event type
MITRE data sources
None recorded
T1 Near-real-time detection
Generic detections need near-real-time matching on single events.
Lake supported in the Azure Monitor table feature matrix
Fields detections use
High-value fields
Most used in public rules
Classification2IncidentName2IncidentNumber2Labels2Severity2Status2TimeGenerated2IncidentUrl1LastModifiedTime1Title1
Sources for this recommendation
- Log Horizon classification baseline Initial per-table classifications, recommendations, lifecycle state, and descriptive metadata migrated without semantic changes.
- Log Baseline volume model Judgment-based volume driver and relative volume class per table. Not measured tenant volume.
- 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.
- Azure Monitor Logs and Microsoft Sentinel billing Free data sources and billing behavior used for isFree.