Compliancemanzill.com
CIS Microsoft Azure Foundations Benchmark v1.4.0

CIS Microsoft Azure Foundations Benchmark v1.4.0/Storage Accounts/47 of 115

3.10Ensure Storage logging is Enabled for Blob Service for 'Read', 'Write', and 'Delete' requests

Control family: Storage Accounts

Control description

The Storage Blob service provides scalable, cost-efficient objective storage in the cloud. Storage Logging happens server-side and allows details for both successful and failed requests to be recorded in the storage account. These logs allow users to see the details of read, write, and delete operations against the blobs. Storage Logging log entries contain the following information about individual requests: Timing information such as start time, end-to-end latency, and server latency, authentication details , concurrency information and the sizes of the request and response messages.

How to implement

ResponsibilityCustomerYou configure and operate this in your own cloud accounts.

Blob storage often holds an organization's most sensitive files. Recording every read, write and delete request against the blob service shows who accessed or changed what, including failed attempts, which is the basis of any investigation into data theft.

Before you start

The same on every cloud, before the steps in the tabs.

  • Decide which storage accounts need blob logging (all that hold business data), where logs go and how long they are kept.
  • Agree who reviews them and how they are used in investigations.

Evidence

  • The storage logging decision: scope, destination and retention

On Azure the tasks send the blob service's read, write and delete logs to a Log Analytics workspace with a diagnostic setting on the storage account, then check the logs arrive.

Task 1Log blob reads, writes and deletes

  1. Sign in to the Azure portal at portal.azure.com and open Storage accounts, then the account.
  2. Select Monitoring > Diagnostic settings.
  3. Select the Blob resource, then Add diagnostic setting.
  4. Name the setting, and under Category details select StorageRead, StorageWrite and StorageDelete.
  5. Under Destination details, select Send to Log Analytics and choose the security workspace; also archive to a storage account if you keep logs there.
  6. Select Save.
  7. Check it: the Blob diagnostic settings list shows the new setting.

Task 2Check that the logs arrive

  1. Open the Log Analytics workspace and select Logs.
  2. In the tables list, find StorageBlobLogs and run a query on it for the last hour.
  3. Confirm entries appear for read, write and delete operations from a test client.
  4. Set the workspace or table retention to at least the period your logging policy requires.

Evidence

  • The Blob diagnostic setting of each storage account, with read, write and delete categories
  • Recent entries in the StorageBlobLogs table

Console steps as of 5 November 2026. Not every step has been confirmed in a live console yet, and menus and labels can move between releases, so look for the nearest match if one has changed.