Skip to content

Commit c427e23

Browse files
committed
updates
1 parent e6392ad commit c427e23

2 files changed

Lines changed: 24 additions & 14 deletions

File tree

articles/sentinel/TOC.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -809,7 +809,7 @@
809809
href: manage-table-tiers-retention.md
810810
displayName: table management, tiers, retention, tables
811811
- name: What to ingest into the data lake?
812-
href: datalake/what-to-inget-to-data-lake.md
812+
href: datalake/what-to-ingest-to-data-lake.md
813813
displayName: data lake ingestion
814814

815815
- name: SOC optimizations

articles/sentinel/datalake/what-to-inget-to-data-lake.md renamed to articles/sentinel/datalake/what-to-ingest-to-data-lake.md

Lines changed: 23 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -1,37 +1,40 @@
11
---
2-
title: What to ingest into the data lake
2+
title: Which logs should you ingest into the data lake
33
description: How to choose which log sources to ingest into your Microsoft Sentinel data lake.
44
ms.topic: conceptual
55
ms.date: 01/29/2026
66
author: EdB-MSFT
77
ms.author: edbaynash
88
ms.service: microsoft-sentinel
99
ms.subservice: sentinel-graph
10+
11+
# Customer intent: As a security architect, I want to decide which log sources belong in the Sentinel data lake so that I balance cost and visibility.
12+
1013
---
1114

1215

1316

14-
# What to ingest into the data lake
17+
# Which logs should you ingest into the data lake?
1518

16-
After onboarding to Microsoft Sentinel data lake, you can decide which logs to ingest into the data lake.
19+
After onboarding to Microsoft Sentinel data lake, decide which logs to ingest into the data lake.
1720

18-
The analytics tier in Sentinel provides real-time analysis and alerting capabilities using log data ingested into Sentinel workspaces. The analytics tier supports the following use cases:
19-
+ **Real-time detection and correlation**: Immediate alerting on critical events, such as endpoints, identity, cloud security, perimeter.
21+
The analytics tier in Sentinel provides real-time analysis and alerting capabilities by using log data ingested into Sentinel workspaces. The analytics tier supports the following use cases:
22+
+ **Real-time detection and correlation**: Immediate alerting on critical events such as endpoints, identity, cloud security, perimeter.
2023
+ **Rapid investigation**: Live searches for active incidents and threat responses.
2124
+ **High-fidelity, actionable logs**: Focus on sources with direct security value, such as EDR signals, privileged access, authentication, threat alerts.
2225

23-
The data lake tier in Sentinel provides large-scale, long term storage and advanced analytics capabilities. The data lake supports the following use cases:
24-
+ **High-volume, lower-priority logs**: Sources that are valuable for deep forensics, analysis of past incidents to understand attack vectors and impacts, or periodic hunts but costly to keep the analytics tier.
26+
The data lake tier in Sentinel provides large-scale, long-term storage and advanced analytics capabilities. The data lake supports the following use cases:
27+
+ **High-volume, lower-priority logs**: Sources that are valuable for deep forensics, analysis of past incidents to understand attack vectors and impacts, or periodic hunts but are costly to keep in the analytics tier.
2528
+ **Analytics and threat hunting**: Cross-log searching, long-term trend analysis, and proactive exploration of historical data to identify hidden threats and patterns.
26-
+ **Batch analytics and summarization**: Use Spark, KQL, or similar tools to enrich, correlate, or summarize data before forwarding only the high-risk signals to the analytics tier for active monitoring.
29+
+ **Batch analytics and summarization**: Use Spark, KQL, or similar tools to enrich, correlate, or summarize data before forwarding only high-risk signals to the analytics tier.
2730
+ **Advanced analytics and machine learning**: Use big data techniques to uncover complex relationships and trends.
2831

29-
Depending on your organization's security needs, you may choose to ingest different log sources into the data
30-
lake. Store high volume logs that are less critical for real-time detection but valuable for deep analysis and forensics in the lake and retain only high-value logs in the analytics tier.
32+
Depending on your organization's security needs, you might choose to ingest different log sources into the data
33+
lake. Store high-volume logs that are less critical for real-time detection but valuable for deep analysis and forensics in the lake, and retain only high-value logs in the analytics tier.
3134

32-
The following table provides guidance on common log source types, their typical log volume, and their value for different security use cases. Use this information to help determine which log sources to ingest into your data lake based on your organization's specific needs and priorities.
35+
Use the following table to prioritize which sources belong in the data lake versus the analytics tier.
3336

34-
| Log source type | Typical Log Volume |Value for real-time threat detection/alerting | Value for threat hunting | Value for incident investigation/forensics | Ingest to data lake |
37+
| Log source type | Typical log volume | Value for real-time threat detection and alerting | Value for threat hunting | Value for incident investigation and forensics | Ingest to data lake |
3538
|-------------------------------------------------|--------------------|-------------------------------------|----------------|-----------------------------------|-----------------------|
3639
| AAA (TACACS/Radius) | Medium | High | High | High | Yes |
3740
| Active Directory (on-premises) | High | High | High | High | No |
@@ -92,4 +95,11 @@ The following table provides guidance on common log source types, their typical
9295
| Web Application Firewall (WAF) Logs | Medium | High | High | High | Yes |
9396
| Windows Server Events | High | High | High | High | No |
9497
| XDR Source Logs (Defender: Office, Identity, Endpoint, CloudApp) | Medium | High | High | High | No |
95-
| Zoom Meeting Logs | Low-Medium | Low | Low | Medium | Yes |
98+
| Zoom Meeting Logs | Low-Medium | Low | Low | Medium | Yes |
99+
100+
101+
## Related articles
102+
103+
- [Manage data tiers and retention in Microsoft Sentinel](../manage-data-overview.md)
104+
- [Configure table settings in Microsoft Sentinel](../manage-table-tiers-retention.md)
105+
- [Set up connectors for the Microsoft Sentinel data lake](../datalake/sentinel-lake-connectors.md)

0 commit comments

Comments
 (0)