CommonSecurityLog
CEF-formatted events from firewalls, IDS/IPS, WAFs, and other security appliances. This record covers rows that match no source in shared-table-sources.json
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 worksC5 Network activity
Network activity: firewall, DNS, DHCP, web proxy, flow, load balancer, mail gateway and message flow, web access to internet-facing services
ACSC
- 2. Network device logs
- 8. Cloud platform logging
- 12. Windows DNS server analytic event logs
CISA
- 3. Network device infrastructure3a-3c DNS query and response, DHCP lease information, and firewall logs
MITRE data sources
- Network Traffic: Network Traffic Flow
- Network Traffic: Network Traffic Content
T1 Near-real-time detection
Generic detections need near-real-time matching on single events.
Lake supported in the Azure Monitor table feature matrix
Build the split rule for CommonSecurityLog
A table has one split rule. Select the sources you collect to combine them into one condition. Rows that match stay in Analytics and are mirrored to the data lake. All other rows go to CommonSecurityLog_SPLT.
- CommonSecurityLog retention
- CommonSecurityLog_SPLT retention
Retention is set per table. The values are the highest recommendation among the selected sources on each side. Data lake sources without a split hint keep no rows in Analytics.
Fields detections use
High-value fields
Most used in public rules
DeviceVendor81TimeGenerated68SourceIP58DestinationIP47DeviceProduct47DeviceEventClassID42DeviceAction39Activity29DeviceName25RequestURL25DestinationPort18Message17
Parsers that read this table
CiscoSEGEvent21 rulesPingFederateEvent21 rulesClarotyEvent20 rulesPaloAltoCDLEvent20 rulesTMApexOneEvent20 rulesRadiflowEvent8 rulesInfobloxCDC6 rulesFortiweb3 rulesCrowdStrikeFalconEventStream2 rulesInfobloxCDC_SOCInsights2 rules
Split hints
Rows to keep in Analytics with a split rule. On a shared table, these apply only to rows that match no source.
Keep denied/blocked/alert actions and high-severity events in Analytics
(DeviceAction has "Deny" or DeviceAction has "Block" or DeviceAction has "Drop" or DeviceAction has "Reject" or DeviceAction has "Alert" or DeviceAction has "Reset") or toint(LogSeverity) >= 7Sources 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.