liveBook · Manning

Log Analytics

As explained in Azure Security

A Log Analytics workspace is an Azure Monitor data store and query environment for collecting, retaining, and analyzing telemetry and security data.

A Log Analytics workspace (LAW) is an Azure Monitor destination for collected telemetry and security data. Agents send VM data to a workspace, where Defender for Cloud can use it to identify VM weaknesses and misconfigurations. Workspace choice affects management, data separation, retention, and potentially cost. section 6.2.1 section 9.1.4

Defender for Cloud can create a default workspace during subscription onboarding, generally one per applicable region. A default workspace is convenient, but a custom centralized workspace can better fit organizational management requirements. For OS collection, Azure Monitor Agent (AMA) succeeds the Log Analytics agent and can route performance and security events to different workspaces through data collection rules. section 6.2.1 section 9.1.4

Use a workspace as a security-data destination in several ways:

  • Export Defender for Cloud recommendations, secure score data, security alerts, and regulatory compliance data while keeping that data in Azure. section 7.5.1
  • Enable Microsoft Sentinel on a selected workspace to begin collecting data for security operations. section 8.2.2
  • Separate performance data from security events when Sentinel ingestion charges make a single destination less useful for security monitoring. section 9.1.4

Retain higher-severity Defender for Cloud data

Configure continuous export for a subscription to send medium- and high-severity security alerts and recommendations to a selected workspace. Enable both streaming updates and weekly snapshots. Changed alerts are stored in the SecurityAlert table; recommendations are stored in SecurityRecommendation, where they can be analyzed. The configuration requires Security Admin or Owner access on the resource group, plus workspace permissions appropriate to its solution state. section 7.5.2 section 7.5.1

Table 9.3 Prerequisites for installing AMA on your Azure VMs (view table figure)

Permissions

Networking

Authentication

The Virtual Machine Contributor role on VMs

The Azure Connected Machine Resource Administrator role on VMs

The Log Analytics Contributor role on your VMs (or any other role that includes the action Microsoft .Resources/deployments/*)

The VMs must have access to the following HTTPS endpoints:

  • global.handler.control.monitor.azure.com
  • <your-VMs-region-name>.handler.control.monitor.azure.com
  • <log-analytics-workspace-id>.ods.opinsights.azure.com

Managed identities must be enabled on your VMs.

You can use either a user- or system-assigned managed identity.

Before installing AMA on Azure VMs that will send data to a workspace, verify required VM roles, HTTPS access to the workspace endpoint, and a managed identity. section 9.1.4

How Azure Security covers it

How deep it goes
Explains workspace selection, data export, multihoming, tables, permissions, and agent prerequisites without detailing query construction.
Examples
Walks through exporting medium- and high-severity alerts and recommendations with streaming updates and weekly snapshots to a workspace.
What it assumes
Assumes Azure portal access and relevant subscription, resource-group, VM, and workspace permissions while explaining required roles and connectivity.
What you can do after
Operate/configure a workspace destination for Defender for Cloud exports, Sentinel collection, and separated VM telemetry flows.
How it connects
Connects Azure Monitor Agent, Log Analytics agent, Microsoft Defender for Cloud, Microsoft Sentinel, Event Hub, and data collection rules.

Also explained in

Compare how 3 books explain Log Analytics →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Azure Security. The section links point to the parts of the book it draws on.