3.10 Ensure Storage logging is enabled for Blob service for read, write, and delete requests

Warning! Audit Deprecated

This audit has been deprecated and will be removed in a future update.

View Next Audit Version

Information

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.

Rationale:

Storage Analytics logs contain detailed information about successful and failed requests to a storage service. This information can be used to monitor individual requests and to diagnose issues with a storage service. Requests are logged on a best-effort basis.

Impact:

Enabling storage account blob service logging does have a cost implication.

NOTE: Nessus has not performed this check. Please review the benchmark to ensure target compliance.

Solution

From Azure Console:

Go to Storage Accounts.

Select the specific Storage Account.

Click the Diagnostics settings (classic) blade from Monitoring (classic) section.

Set the Status to On, if set to Off.

Select Blob properties.

Select Read, Write and Delete options under the Loggingsection to enable Storage Logging for Blob service.

Using Azure Command Line Interface:
Use the below command to enable the Storage Logging for Blob service.

az storage logging update --account-name <storageAccountName> --account-key <storageAccountKey> --services b --log rwd --retention 90

Default Value:

By default, storage account blob service logging is disabled for read, write, an delete operations

See Also

https://workbench.cisecurity.org/files/3459