Data Collection Rule Template for Edge Delta
A template for creating a Data Collection Rule when sending logs to Azure Log Analytics and Sentinel.
4 minute read
You can configure Edge Delta agents to prepare log data for downstream processing by Microsoft Sentinel before sending it to Azure. Preparing the telemetry data on the edge for security information and event management (SIEM) ensures uniform data representation for analysis, correlation, and alerting across various types and sources of data.
To send data to Microsoft Sentinel, configure Azure using instructions on this page. Then configure a pipeline with the Microsoft Sentinel destination node and add the Microsoft Sentinel pack. See the packs library for detailed descriptions of the packs. In addition, you feed the Sentinel pack with a relevant pack for the data source, such as the Edge Delta Pipeline Pack for CEF (Common Event Format). The CEF pack routes and processes CEF logs before passing CEL logs to the Sentinel Pack, which creates the mapping from different security sources. The resulting item has attributes in the shape and form required by Sentinel.
Together, the CEF and Sentinel packs process logs as follows, before passing them to the Sentinel Destination node:
{
"_type": "log"
"body": "Dec 16 06:17:49 test-host CEF:1|Vendor234|RUM|v10.678.10-20241010090810|4815|Agent found some errors|9|src=10.0.0.1 dst=2.1.2.2 spt=1232
"
"resource": { • • • }
"timestamp": 1734329869682
}
{
"_type": "log"
"attributes": {
"Activity": "Agent found some errors"
"DestinationIP": "2.1.2.2"
"DeviceProduct": "RUM"
"DeviceVendor": "Vendor234"
"DeviceVersion": "v10.678.10-20241010090810"
"LogSeverity": "9"
"OriginalLogSeverity": "9"
"OriginalTimestamp": 1734329869000
"SourceIP": "10.0.0.1"
"SourcePort": 1232
"type": "CommonSecurityLog"
}
"body": "Dec 16 06:17:49 test-host CEF:1|Vendor234|RUM|v10.678.10-20241010090810|4815|Agent found some errors|9|src=10.0.0.1 dst=2.1.2.2 spt=1232
"
"resource": { • • • }
"timestamp": 1734329869000
}
You need the following objects configured in Azure:
Register Edge Delta as an application.
Cloud Application Administrator
.Edge Delta Sentinel Stream
as the application display name.client_id
parameter, while the Directory (tenant) ID is used for the tenant_id
parameter in the Microsoft Sentinel node.client_secret
parameter in the Microsoft Sentinel node.See the official Azure documentation for more details.
Create the data collection endpoint in Azure Monitor.
Edge-Delta-Stream-Sentinel-Ingestion
as the Endpoint name.data_collection_endpoint
parameter in the Microsoft Sentinel node, and it is used later to create the DCR.See the official Azure documentation for more details.
Create a data collection rule. It defines how data is collected, where it is sent, and the specific transformations applied during ingestion.
First you need the Log Analytics Workspace Resource ID:
Now you can create a DCR using the template:
Edge-Delta-Stream-Ingestion-Rule
.See the official Azure documentation for more details.
Assign rule permissions for the Edge Delta Sentinel Stream app:
data_collection_rule_id
parameter in the Microsoft Sentinel node.streamDeclarations
, for example Custom-CommonSecurityLog
in the following snippet: ...
"properties": {
"immuteableId": "123456789"
"dataCollectionEndpointId": "/subsriptions/123456789/resour...",
"streamDeclarations": {
"Custom-CommonSecurityLog": {
"columns": [{
{...
This value is used for the stream_name
parameter in the Microsoft Sentinel node.
A template for creating a Data Collection Rule when sending logs to Azure Log Analytics and Sentinel.