Pipeline: 4.13 Ensure Storage logging is Enabled for Blob Service for 'Read', 'Write', and 'Delete' requests
Description
The Storage Blob service provides scalable, cost-efficient object 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.
Storage Analytics logs contain detailed information about successful and failed requests to a storage service. This information can be used to monitor each individual request to a storage service for increased security or diagnostics. Requests are logged on a best-effort basis.
Storage Analytics logging is not enabled by default for your storage account.
Remediation
From Azure Portal
- Go to
Storage Accounts
. - For each storage account, under
Monitoring
, clickDiagnostics settings
. - Select the
blob
tab indented below the storage account. - To create a new diagnostic setting, click
+ Add diagnostic setting
. To update an existing diagnostic setting, clickEdit setting
on the diagnostic setting. - Check the boxes next to
StorageRead
,StorageWrite
, andStorageDelete
. - Select an appropriate destination.
- Click
Save
.
From Azure CLI
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, and delete operations.
Run the pipeline
To run this pipeline from your terminal:
flowpipe pipeline run azure_cis.pipeline.cis_v300_4_13
Use this pipeline
To call this pipeline from your pipeline, use a step:
step "pipeline" "step_name" { pipeline = azure_cis.pipeline.cis_v300_4_13 }
Params
Name | Type | Required | Description | Default |
---|---|---|---|---|
database | connection.steampipe | Yes | Database connection string. | connection.steampipe.default |
notifier | notifier | Yes | The name of the notifier to use for sending notification messages. | notifier.default |
notification_level | string | Yes | The verbosity level of notification messages to send. Valid options are 'verbose', 'info', 'error'. | info |
approvers | list(notifier) | Yes | List of notifiers to be used for obtaining action/approval decisions. | notifier.default |
Outputs
This pipeline has no outputs.