CIS Microsoft Azure Foundations Benchmark v1.4.0/Storage Accounts/48 of 115
3.11Ensure Storage Logging is Enabled for Table Service for 'Read', 'Write', and 'Delete' Requests
Control family: Storage Accounts
Control description
The Storage Table storage is a service that stores structure NoSQL data in the cloud, providing a key/attribute store with a schema less design. 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 tables. 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.
Table storage holds structured application data. Recording every read, write and delete request against the table service gives an audit trail of who accessed or changed the data, and from where.
Before you start
The same on every cloud, before the steps in the tabs.
- Decide which storage accounts need table logging (all that use Table storage for business data), where logs go and how long they are kept.
- Agree who reviews them.
Evidence
- The storage logging decision: scope, destination and retention
On Azure the tasks send the table 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 table 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 Table 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 Table 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 StorageTableLogs 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 Table diagnostic setting of each storage account, with read, write and delete categories
- Recent entries in the StorageTableLogs 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.