The cross-harness, self-improving memory layer for AI agents. Join our community: https://discord.com/invite/zdNChS2fBu
Go agent-ai-cliagent-harnessesagent-securitybrowser-extensionciclaude-codecloudcodexcursordetection-engineeringjevknowledge-basememorymobile-device-managementobservabilitysecuritysecurity-information-and-event-managementsecurity-toolstelemetrytraces
feat(sentinel): Arc-free Sentinel path with the bundled Vector
shukieshahb5a197956302
diff --git a/cli/beacon/internal/endpoint/sentinel/pack/README.md b/cli/beacon/internal/endpoint/sentinel/pack/README.mdindex 02eb048a..b4280c36 100644--- a/cli/beacon/internal/endpoint/sentinel/pack/README.md+++ b/cli/beacon/internal/endpoint/sentinel/pack/README.md@@ -83,14 +83,25 @@ the default Beacon recommendation because Beacon events are rich structured JSONwith prompts, tool calls, commands, files, runtime metadata, and optional rawfields. Flattening those events into CEF loses useful context.-## Direct Logs Ingestion API--The Azure Monitor Logs Ingestion API can be useful for a centralized,-customer-managed forwarder, but it should not be configured directly in Beacon-endpoint agent state. Direct API forwarding requires Microsoft Entra-credentials, DCR identifiers, ingestion endpoints, batching, retries, and-network failure handling. Keep those concerns outside Beacon's local endpoint-collector unless you are building a separate managed forwarder.+## Without Azure Monitor Agent: Vector and the Logs Ingestion API++On a machine outside Azure, Azure Monitor Agent needs Azure Arc first, and it+does not run on macOS at all. `vector.toml` is the alternative. The Vector that+ships with Beacon (`/opt/beacon/bin/vector`) posts each line to the Logs+Ingestion API with a Microsoft Entra app registration. It needs no Arc and no+agent extension.++1. Deploy `dcr-logs-ingestion-template.json` with your workspace and Data+ Collection Endpoint resource IDs, and note the `dcrImmutableId` output. It+ runs the same transform into the same `BeaconRuntime_CL` table.+2. Grant your app registration the Monitoring Metrics Publisher role on that DCR.+3. Run Vector with `vector.toml`, setting `BEACON_SENTINEL_DCE_ENDPOINT`,+ `BEACON_SENTINEL_DCR_IMMUTABLE_ID`, `AZURE_TENANT_ID`, `AZURE_CLIENT_ID`, and+ `AZURE_CLIENT_SECRET` in the Vector service's environment.++The host needs outbound HTTPS to `login.microsoftonline.com` and the DCE's+`*.ingest.monitor.azure.com` hostname. The Azure credentials live only in the+Vector service's environment, never in Beacon config.## Content Handlingdiff --git a/cli/beacon/internal/endpoint/sentinel/pack/dcr-logs-ingestion-template.json b/cli/beacon/internal/endpoint/sentinel/pack/dcr-logs-ingestion-template.jsonnew file mode 100644index 00000000..ee8b87cb--- /dev/null+++ b/cli/beacon/internal/endpoint/sentinel/pack/dcr-logs-ingestion-template.json@@ -0,0 +1,71 @@+{+ "$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentTemplate.json#",+ "contentVersion": "1.0.0.0",+ "parameters": {+ "dataCollectionRuleName": {+ "type": "string",+ "defaultValue": "dcr-beacon-runtime-ingestion"+ },+ "workspaceResourceId": {+ "type": "string",+ "metadata": {+ "description": "Resource ID of the Log Analytics workspace enabled for Microsoft Sentinel."+ }+ },+ "dataCollectionEndpointResourceId": {+ "type": "string",+ "metadata": {+ "description": "Resource ID of a Data Collection Endpoint in the workspace's region."+ }+ },+ "location": {+ "type": "string",+ "defaultValue": "[resourceGroup().location]"+ }+ },+ "resources": [+ {+ "type": "Microsoft.Insights/dataCollectionRules",+ "apiVersion": "2023-03-11",+ "name": "[parameters('dataCollectionRuleName')]",+ "location": "[parameters('location')]",+ "properties": {+ "dataCollectionEndpointId": "[parameters('dataCollectionEndpointResourceId')]",+ "streamDeclarations": {+ "Custom-BeaconRuntimeRaw": {+ "columns": [+ { "name": "TimeGenerated", "type": "datetime" },+ { "name": "RawData", "type": "string" }+ ]+ }+ },+ "destinations": {+ "logAnalytics": [+ {+ "workspaceResourceId": "[parameters('workspaceResourceId')]",+ "name": "sentinelWorkspace"+ }+ ]+ },+ "dataFlows": [+ {+ "streams": [+ "Custom-BeaconRuntimeRaw"+ ],+ "destinations": [+ "sentinelWorkspace"+ ],+ "transformKql": "{{DCR_TRANSFORM}}",+ "outputStream": "Custom-BeaconRuntime_CL"+ }+ ]+ }+ }+ ],+ "outputs": {+ "dcrImmutableId": {+ "type": "string",+ "value": "[reference(resourceId('Microsoft.Insights/dataCollectionRules', parameters('dataCollectionRuleName'))).immutableId]"+ }+ }+}diff --git a/cli/beacon/internal/endpoint/sentinel/pack/vector.toml.tmpl b/cli/beacon/internal/endpoint/sentinel/pack/vector.toml.tmplnew file mode 100644index 00000000..fa7a461b--- /dev/null+++ b/cli/beacon/internal/endpoint/sentinel/pack/vector.toml.tmpl@@ -0,0 +1,60 @@+# Beacon Endpoint Agent -> Microsoft Sentinel, through the Azure Monitor Logs Ingestion API+#+# For hosts that cannot run Azure Monitor Agent, which on a machine outside Azure means+# onboarding it to Azure Arc first. Vector posts to a Data Collection Endpoint with a+# Microsoft Entra app registration instead, so no Arc and no agent extension are needed.+# Beacon's Linux packages ship Vector at /opt/beacon/bin/vector.+#+# Each record carries the original Beacon line as RawData. The DCR in+# dcr-logs-ingestion-template.json runs the same transform as the Azure Monitor Agent+# path, so both paths produce identical BeaconRuntime_CL rows.+#+# Set in the Vector service environment, not in Beacon config:+# BEACON_SENTINEL_DCE_ENDPOINT https://<dce>.<region>.ingest.monitor.azure.com+# BEACON_SENTINEL_DCR_IMMUTABLE_ID dcr-... (the DCR's immutableId)+# AZURE_TENANT_ID, AZURE_CLIENT_ID, AZURE_CLIENT_SECRET+# The app registration needs the Monitoring Metrics Publisher role on the DCR.++data_dir = "/var/lib/vector/beacon-sentinel"++[sources.beacon_runtime]+type = "file"+include = ["{{LOG_PATH}}"]+read_from = "end"++[transforms.beacon_raw_record]+type = "remap"+inputs = ["beacon_runtime"]+source = '''+raw = string!(.message)+parsed, err = parse_json(raw)+ts = now()+if err == null && is_object(parsed) {+ ts = parse_timestamp(parsed.timestamp, format: "%+") ?? now()+}+. = {"RawData": raw}+.timestamp = ts+'''++[sinks.beacon_sentinel]+type = "azure_logs_ingestion"+inputs = ["beacon_raw_record"]+endpoint = "${BEACON_SENTINEL_DCE_ENDPOINT}"+dcr_immutable_id = "${BEACON_SENTINEL_DCR_IMMUTABLE_ID}"+stream_name = "Custom-BeaconRuntimeRaw"+timestamp_field = "TimeGenerated"++[sinks.beacon_sentinel.auth]+azure_credential_kind = "client_secret_credential"+azure_tenant_id = "${AZURE_TENANT_ID}"+azure_client_id = "${AZURE_CLIENT_ID}"+azure_client_secret = "${AZURE_CLIENT_SECRET}"++[sinks.beacon_sentinel.batch]+max_events = 1000+timeout_secs = 30++[sinks.beacon_sentinel.request]+retry_attempts = 10+retry_initial_backoff_secs = 1+retry_max_duration_secs = 300diff --git a/cli/beacon/internal/endpoint/sentinel/sentinel.go b/cli/beacon/internal/endpoint/sentinel/sentinel.goindex 437d74f2..dee68e61 100644--- a/cli/beacon/internal/endpoint/sentinel/sentinel.go+++ b/cli/beacon/internal/endpoint/sentinel/sentinel.go@@ -25,7 +25,11 @@ func Files() []siempack.File {{Name: "README.md", Content: mustRead("pack/README.md")},{Name: "dcr-transform.kql", Content: DCRTransform()},{Name: "table-schema.json", Content: mustRead("pack/table-schema.json")},- {Name: "dcr-template.json", Content: renderDCRTemplate(), TemplateLogPath: true, JSONEscape: true},+ {Name: "dcr-template.json", Content: renderDCRTemplate("pack/dcr-template.json"), TemplateLogPath: true, JSONEscape: true},+ // The Logs Ingestion API path, for hosts without Azure Monitor Agent: Vector sends each line+ // as RawData to a DCR that runs the same transform, so both paths fill the same table.+ {Name: "vector.toml", Content: mustRead("pack/vector.toml.tmpl"), TemplateLogPath: true},+ {Name: "dcr-logs-ingestion-template.json", Content: renderDCRTemplate("pack/dcr-logs-ingestion-template.json")},{Name: "queries.kql", Content: mustRead("pack/queries.kql")},{Name: "detections.kql", Content: mustRead("pack/detections.kql")},{Name: "sample-event.jsonl", Content: mustRead("pack/sample-event.jsonl")},@@ -46,8 +50,8 @@ func InstallPack(outputDir, logPath string) error {return siempack.Install(outputDir, Files(), logPath)}-func renderDCRTemplate() string {- tmpl := mustRead("pack/dcr-template.json")+func renderDCRTemplate(path string) string {+ tmpl := mustRead(path)return strings.ReplaceAll(tmpl, "{{DCR_TRANSFORM}}", siempack.JSONEscapeForString(minifyKQL(DCRTransform())))}diff --git a/cli/beacon/internal/endpoint/sentinel/sentinel_test.go b/cli/beacon/internal/endpoint/sentinel/sentinel_test.goindex 3b3e495f..569b6dbe 100644--- a/cli/beacon/internal/endpoint/sentinel/sentinel_test.go+++ b/cli/beacon/internal/endpoint/sentinel/sentinel_test.go@@ -37,6 +37,8 @@ func TestInstallPackWritesExpectedFiles(t *testing.T) {"queries.kql","detections.kql","sample-event.jsonl",+ "vector.toml",+ "dcr-logs-ingestion-template.json",} {if _, err := os.Stat(filepath.Join(dir, name)); err != nil {t.Fatalf("expected %s: %v", name, err)@@ -76,6 +78,7 @@ func TestPackJSONFilesAreValid(t *testing.T) {for _, path := range []string{"pack/table-schema.json","pack/dcr-template.json",+ "pack/dcr-logs-ingestion-template.json",} {var doc map[string]interface{}if err := json.Unmarshal([]byte(mustRead(path)), &doc); err != nil {@@ -85,17 +88,107 @@ func TestPackJSONFilesAreValid(t *testing.T) {}func TestRenderedDCRTemplateContainsTransformFromKQL(t *testing.T) {- rendered := renderDCRTemplate()- if strings.Contains(rendered, "{{DCR_TRANSFORM}}") {- t.Fatal("rendered DCR template still contains {{DCR_TRANSFORM}} placeholder")+ for _, path := range []string{"pack/dcr-template.json", "pack/dcr-logs-ingestion-template.json"} {+ rendered := renderDCRTemplate(path)+ if strings.Contains(rendered, "{{DCR_TRANSFORM}}") {+ t.Fatalf("%s still contains the {{DCR_TRANSFORM}} placeholder", path)+ }+ var doc map[string]interface{}+ if err := json.Unmarshal([]byte(rendered), &doc); err != nil {+ t.Fatalf("rendered %s is not valid JSON: %v", path, err)+ }+ transform := minifyKQL(DCRTransform())+ if !strings.Contains(rendered, transform) {+ t.Fatalf("rendered %s does not contain the minified dcr-transform.kql content", path)+ }}- var doc map[string]interface{}- if err := json.Unmarshal([]byte(rendered), &doc); err != nil {- t.Fatalf("rendered DCR template is not valid JSON: %v", err)+}++// dcrRule is the part of a DCR ARM template the two ingestion paths have to agree on.+type dcrRule struct {+ Resources []struct {+ Properties struct {+ StreamDeclarations map[string]struct {+ Columns []struct {+ Name string `json:"name"`+ Type string `json:"type"`+ } `json:"columns"`+ } `json:"streamDeclarations"`+ DataFlows []struct {+ Streams []string `json:"streams"`+ OutputStream string `json:"outputStream"`+ } `json:"dataFlows"`+ } `json:"properties"`+ } `json:"resources"`+}++func parseDCR(t *testing.T, path string) dcrRule {+ t.Helper()+ var rule dcrRule+ if err := json.Unmarshal([]byte(renderDCRTemplate(path)), &rule); err != nil {+ t.Fatalf("%s: %v", path, err)+ }+ if len(rule.Resources) != 1 || len(rule.Resources[0].Properties.DataFlows) != 1 {+ t.Fatalf("%s: want one DCR with one data flow", path)}- transform := minifyKQL(DCRTransform())- if !strings.Contains(rendered, transform) {- t.Fatalf("rendered DCR template does not contain the minified dcr-transform.kql content")+ return rule+}++// The Logs Ingestion path only works if Vector posts to the stream the DCR declares, with the+// columns the shared transform reads, and the DCR writes to the same table as the Azure Monitor+// Agent path. Nothing in Azure checks any of that until the first record is rejected.+func TestLogsIngestionPathMatchesTheDCRAndTheAgentPath(t *testing.T) {+ vector := mustRead("pack/vector.toml.tmpl")+ ingest := parseDCR(t, "pack/dcr-logs-ingestion-template.json").Resources[0].Properties+ agent := parseDCR(t, "pack/dcr-template.json").Resources[0].Properties++ const stream = "Custom-BeaconRuntimeRaw"+ if !strings.Contains(vector, `stream_name = "`+stream+`"`) {+ t.Errorf("vector.toml does not post to %s", stream)+ }+ decl, ok := ingest.StreamDeclarations[stream]+ if !ok {+ t.Fatalf("the Logs Ingestion DCR does not declare %s", stream)+ }+ columns := map[string]string{}+ for _, c := range decl.Columns {+ columns[c.Name] = c.Type+ }+ if columns["TimeGenerated"] != "datetime" || columns["RawData"] != "string" {+ t.Errorf("%s columns = %v, want TimeGenerated datetime and RawData string", stream, columns)+ }+ if got := ingest.DataFlows[0].Streams; len(got) != 1 || got[0] != stream {+ t.Errorf("the Logs Ingestion data flow reads %v, want %s", got, stream)+ }+ if ingest.DataFlows[0].OutputStream != agent.DataFlows[0].OutputStream {+ t.Errorf("the two paths write to different tables: %q and %q",+ ingest.DataFlows[0].OutputStream, agent.DataFlows[0].OutputStream)+ }+ for _, want := range []string{`type = "azure_logs_ingestion"`, `"RawData": raw`, `timestamp_field = "TimeGenerated"`} {+ if !strings.Contains(vector, want) {+ t.Errorf("vector.toml is missing %s", want)+ }+ }+}++// Credentials come from the Vector service environment, never from the pack.+func TestVectorConfigTakesAzureCredentialsFromTheEnvironment(t *testing.T) {+ vector := mustRead("pack/vector.toml.tmpl")+ for _, key := range []string{"azure_tenant_id", "azure_client_id", "azure_client_secret", "endpoint", "dcr_immutable_id"} {+ found := false+ for _, line := range strings.Split(vector, "\n") {+ line = strings.TrimSpace(line)+ if !strings.HasPrefix(line, key+" =") {+ continue+ }+ found = true+ if !strings.Contains(line, `"${`) {+ t.Errorf("vector.toml sets %s to a literal instead of an environment variable: %s", key, line)+ }+ }+ if !found {+ t.Errorf("vector.toml does not set %s", key)+ }}}@@ -136,7 +229,9 @@ func TestPackREADMEMentionsSentinelSetupAndSecretBoundaries(t *testing.T) {"Content Handling","/var/log/beacon-agent/runtime.jsonl","not in Beacon endpoint configuration",- "Direct Logs Ingestion API",+ "Vector and the Logs Ingestion API",+ "dcr-logs-ingestion-template.json",+ "Monitoring Metrics Publisher","CEF and Syslog",} {if !strings.Contains(readme, want) {diff --git a/docs/log-forwarding/microsoft-sentinel.mdx b/docs/log-forwarding/microsoft-sentinel.mdxindex 5c427aae..853ad61c 100644--- a/docs/log-forwarding/microsoft-sentinel.mdx+++ b/docs/log-forwarding/microsoft-sentinel.mdx@@ -1,11 +1,18 @@---title: "Microsoft Sentinel"-description: "Forward Beacon endpoint events into Microsoft Sentinel with Azure Monitor Agent custom log collection."+description: "Forward Beacon endpoint events into Microsoft Sentinel with Azure Monitor Agent or with Vector and the Logs Ingestion API."---## Forwarding overview-Beacon `v0.0.32` added the [Microsoft Sentinel content pack](/concepts/core-concepts#microsoft-sentinel-content-pack) for teams that want Beacon endpoint events in Log Analytics and Sentinel hunting workflows. Beacon remains the local JSONL producer and writes one source of truth, the active [runtime JSONL log](/concepts/core-concepts#runtime-jsonl-log). Azure Monitor Agent tails that file and sends new records through a Data Collection Rule (DCR) into a custom Log Analytics table.+Beacon `v0.0.32` added the [Microsoft Sentinel content pack](/concepts/core-concepts#microsoft-sentinel-content-pack) for teams that want Beacon endpoint events in Log Analytics and Sentinel hunting workflows. Beacon remains the local JSONL producer and writes one source of truth, the active [runtime JSONL log](/concepts/core-concepts#runtime-jsonl-log). Something on the host tails that file and sends new records through a Data Collection Rule (DCR) into a custom Log Analytics table. There are two ways to do that, and both fill the same `BeaconRuntime_CL` table through the same transform:++| Path | Runs on the host | Needs |+|---|---|---|+| Azure Monitor Agent | AMA | An Azure VM, or [Azure Arc](#azure-monitor-agent-outside-azure) on any other machine |+| Vector | The Vector that ships with Beacon | A Microsoft Entra app registration. No Arc and no agent extension. See [Vector and the Logs Ingestion API](#vector-and-the-logs-ingestion-api) |++On a desktop or server outside Azure, the Vector path is usually simpler.Use this path when you want Sentinel ingestion without storing Azure tenant IDs, client secrets, workspace IDs, DCR identifiers, or ingestion endpoints in Beacon endpoint configuration.@@ -22,9 +29,9 @@ Use system mode for MDM deployments so Azure Monitor Agent can tail `/var/log/be- Beacon endpoint installed and writing local JSONL.- A Log Analytics workspace, with Microsoft Sentinel enabled if you want Sentinel hunting and analytics workflows.-- Azure Monitor Agent installed or deployed to the endpoint.- A custom Log Analytics table named `BeaconRuntime_CL`.-- A Data Collection Rule associated with the endpoint and workspace.+- For the Azure Monitor Agent path: AMA on the endpoint (Azure Arc first, outside Azure) and a DCR associated with it.+- For the Vector path: an Entra app registration, a Data Collection Endpoint, and the Logs Ingestion DCR from the pack.## Install the Sentinel pack@@ -41,6 +48,7 @@ The pack includes:- `README.md` with setup and validation steps- `table-schema.json` for the `BeaconRuntime_CL` custom table- `dcr-template.json` for Azure Monitor Agent custom text log collection+- `dcr-logs-ingestion-template.json` and `vector.toml` for the Vector path- `dcr-transform.kql` for parsing each Beacon JSONL line- `queries.kql` with validation and starter hunting queries- `detections.kql` with example analytics rule logic@@ -133,9 +141,71 @@ The DCR uses Custom Text Logs because Beacon writes newline-delimited JSON. The### 5. Choose the ingestion path-Azure Monitor Agent cannot directly tail Beacon logs from macOS endpoints. For macOS fleets, use a small customer-managed forwarder or relay that reads Beacon JSONL records and posts them to the Azure Monitor Logs Ingestion API.+Azure Monitor Agent does not run on macOS, so Macs use the [Vector path](#vector-and-the-logs-ingestion-api). The signed macOS package installs Vector at `/opt/beacon/bin/vector`, just like the Linux packages.++For Azure Monitor Agent on Windows or Linux, install AMA on the machine, add a custom text log source pointing at the Beacon runtime log (usually `/var/log/beacon-agent/runtime.jsonl`), apply the Beacon DCR transform, route output to `BeaconRuntime_CL`, and associate the DCR with the machine.++### Azure Monitor Agent outside Azure++AMA is an Azure VM extension. On a machine that is not an Azure VM, you have to onboard it to [Azure Arc](https://learn.microsoft.com/en-us/azure/azure-arc/servers/overview) (`azcmagent connect`) before AMA can be installed. That makes every endpoint an Azure resource, running the Connected Machine agent next to AMA. The DCE's logs ingestion endpoint must be in the workspace's region.++A host that cannot reach Azure at all cannot use either path.++## Vector and the Logs Ingestion API++Vector reads `runtime.jsonl` and posts each line to the [Logs Ingestion API](https://learn.microsoft.com/en-us/azure/azure-monitor/logs/logs-ingestion-api-overview) with an Entra app registration. It needs no Arc, no AMA, and no Azure resource per machine. Vector ships with Beacon: the `.deb`, `.rpm`, and macOS package install it at `/opt/beacon/bin/vector`, and the Linux archive carries it as `beacon-vector`.++Each record carries the original Beacon line as `RawData`. The Logs Ingestion DCR runs the same transform as the AMA path, so the rows are identical either way.++### 1. Azure side, once++1. Create the `BeaconRuntime_CL` table and a Data Collection Endpoint in the workspace's region, as in steps 2 and 3 above.+2. Deploy `dcr-logs-ingestion-template.json` with the workspace and DCE resource IDs. Note the `dcrImmutableId` output.+3. Register an app in Microsoft Entra ID and create a client secret for it.+4. On the DCR, grant the app the **Monitoring Metrics Publisher** role.++### 2. Each host++The host needs outbound HTTPS to `login.microsoftonline.com` and to your DCE's `*.ingest.monitor.azure.com` hostname. Nothing else.++```bash title="Install the config and credentials"+sudo mkdir -p /etc/beacon-sentinel+sudo cp beacon-sentinel-pack/vector.toml /etc/beacon-sentinel/vector.toml+sudo install -m 0600 /dev/null /etc/beacon-sentinel/azure.env+sudo tee /etc/beacon-sentinel/azure.env >/dev/null <<'ENV'+BEACON_SENTINEL_DCE_ENDPOINT=https://<dce>.<region>.ingest.monitor.azure.com+BEACON_SENTINEL_DCR_IMMUTABLE_ID=dcr-...+AZURE_TENANT_ID=...+AZURE_CLIENT_ID=...+AZURE_CLIENT_SECRET=...+ENV+```++```ini title="/etc/systemd/system/beacon-sentinel.service"+[Unit]+Description=Vector: Beacon events to Microsoft Sentinel+After=network-online.target+Wants=network-online.target++[Service]+ExecStart=/opt/beacon/bin/vector --config /etc/beacon-sentinel/vector.toml+EnvironmentFile=/etc/beacon-sentinel/azure.env+DynamicUser=yes+StateDirectory=vector/beacon-sentinel+Restart=always++[Install]+WantedBy=multi-user.target+```++```bash title="Start it"+sudo systemctl daemon-reload+sudo systemctl enable --now beacon-sentinel+```++`DynamicUser` runs Vector as an unprivileged user. It can read the runtime log because Beacon writes it world-readable, and systemd reads `azure.env` as root before dropping privileges. `StateDirectory` creates `/var/lib/vector/beacon-sentinel`, where Vector keeps its read position.-For supported Windows or Linux testing, install Azure Monitor Agent on the machine, add a custom text log source pointing to the Beacon runtime log path, usually `/var/log/beacon-agent/runtime.jsonl`, apply the Beacon DCR transform, route output to `BeaconRuntime_CL`, and associate the DCR with the machine.+The pack ships a client secret config. Vector also supports a certificate (`azure_credential_kind = "client_certificate_credential"` with `certificate_path`); see the [`azure_logs_ingestion` sink](https://vector.dev/docs/reference/configuration/sinks/azure_logs_ingestion/).The generated table schema includes columns such as `Vendor`, `Product`, `EventAction`, `Severity`, `HostName`, `UserName`, `HarnessName`, `SessionId`, `ToolName`, `CommandLine`, `Repository`, `Branch`, `Message`, `ContentRetention`, and `RawData`.@@ -163,7 +233,7 @@ BeaconRuntime_CL| order by TimeGenerated desc```-If the validation query does not return data, check the DCR association, Azure Monitor Agent health state, configured file path, and table schema. The target table must exist before the DCR can route transformed records to it.+If the validation query does not return data, check the DCR association, Azure Monitor Agent health state, configured file path, and table schema. On the Vector path, check `journalctl -u beacon-sentinel` for authentication errors and confirm the app has Monitoring Metrics Publisher on the DCR. Role assignments can take several minutes to apply. The target table must exist before the DCR can route transformed records to it.## Hunting content@@ -175,7 +245,7 @@ Use `detections.kql` as example analytics rule logic. Review and tune thresholdsMicrosoft Sentinel can also collect CEF and Syslog through Azure Monitor Agent, but the generated Beacon pack uses custom logs because Beacon events are rich structured JSON with prompts, tool calls, commands, files, runtime metadata, and optional raw fields. Flattening those events into CEF loses useful context.-The Azure Monitor Logs Ingestion API can be useful for a centralized customer-managed forwarder, but it should not be configured directly in Beacon endpoint agent state. Direct API forwarding requires Microsoft Entra credentials, DCR identifiers, ingestion endpoints, batching, retries, and network failure handling. Keep those concerns outside Beacon's local endpoint collector unless you are building a separate managed forwarder.+Beacon's own endpoint config never holds Azure credentials. On the Vector path, the Entra secret, DCR ID, and ingestion endpoint live only in the Vector service's environment file. Vector does the batching and retries.## Content handling