Control: Ensure Storage logging is enabled for Blob service for read, write, and delete requests
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.
Usage
Run the control in your terminal:
powerpipe control run azure_compliance.control.storage_account_blob_service_logging_enabled
Snapshot and share results via Turbot Pipes:
powerpipe loginpowerpipe control run azure_compliance.control.storage_account_blob_service_logging_enabled --share
SQL
This control uses a named query:
select sa.id as resource, case when not (sa.blob_service_logging ->> 'Read') :: boolean or not (sa.blob_service_logging ->> 'Write') :: boolean or not (sa.blob_service_logging ->> 'Delete') :: boolean then 'alarm' else 'ok' end as status, case when not (sa.blob_service_logging ->> 'Read') :: boolean or not (sa.blob_service_logging ->> 'Write') :: boolean or not (sa.blob_service_logging ->> 'Delete') :: boolean then name || ' blob service logging not enabled for ' || concat_ws(', ', case when not (sa.blob_service_logging ->> 'Write') :: boolean then 'write' end, case when not (sa.blob_service_logging ->> 'Read') :: boolean then 'read' end, case when not (sa.blob_service_logging ->> 'Delete') :: boolean then 'delete' end ) || ' requests.' else name || ' blob service logging enabled for read, write, delete requests.' end as reason , sa.resource_group as resource_group , sub.display_name as subscriptionfrom azure_storage_account sa, azure_subscription subwhere sub.subscription_id = sa.subscription_id;