CIS Microsoft Azure Foundations Benchmark v1.4.0/Storage Accounts/40 of 115
3.3Ensure Storage Logging is Enabled for Queue Service for 'Read', 'Write', and 'Delete' requests
Control family: Storage Accounts
Control description
The Storage Queue service stores messages that may be read by any client who has access to the storage account. A queue can contain an unlimited number of messages, each of which can be up to 64KB in size using version 2011-08-18 or newer. 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 queues. 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.
Queues pass work between parts of an application, and the messages can hold sensitive data. Recording every read, write and delete request against the queue service shows who touched which messages, which is what you need when investigating misuse or a breach.
Before you start
The same on every cloud, before the steps in the tabs.
- Decide which storage accounts need queue 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 queue 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 queue reads, writes and deletes
- Sign in to the Azure portal at portal.azure.com and open Storage accounts, then the account.
- Select Monitoring > Diagnostic settings.
- Select the Queue resource, then Add diagnostic setting.
- Name the setting, and under Category details select StorageRead, StorageWrite and StorageDelete.
- Under Destination details, select Send to Log Analytics and choose the security workspace; also archive to a storage account if you keep logs there.
- Select Save.
- Check it: the Queue diagnostic settings list shows the new setting.
Task 2Check that the logs arrive
- Open the Log Analytics workspace and select Logs.
- In the tables list, find StorageQueueLogs and run a query on it for the last hour.
- Confirm entries appear for read, write and delete operations from a test client.
- Set the workspace or table retention to at least the period your logging policy requires.
Evidence
- The Queue diagnostic setting of each storage account, with read, write and delete categories
- Recent entries in the StorageQueueLogs table
Not applicable. This benchmark covers Azure only.
Not applicable. This benchmark covers Azure only.
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.