compliance.tf

Storage account Blob services should have Storage logging enabled for read, write, and delete requests

The Storage Blob service provides scalable, cost-efficient objective storage in the cloud. Storage Logging happens server-side and records details for both successful and failed requests. The logs show read, write, and delete operations against the blobs.

What this control checks

Storage account Blob services need Storage logging turned on for read, write, and delete requests

Framework mappings

The clauses this control is mapped to in each framework.

CIS Azure Benchmark v1.5.0

  • 3.13 Ensure Storage logging is Enabled for Blob Service for 'Read', 'Write', and 'Delete' requests

CIS Azure Benchmark v2.0.0

  • 3.13 Ensure Storage logging is Enabled for Blob Service for 'Read', 'Write', and 'Delete' requests

CIS Azure Benchmark v2.1.0

  • 3.13 Ensure Storage logging is Enabled for Blob Service for 'Read', 'Write', and 'Delete' requests

CIS Azure Benchmark v3.0.0

  • 4.13 Ensure Storage logging is Enabled for Blob Service for 'Read', 'Write', and 'Delete' requests

Tool mappings

Use these identifiers to cross-reference this control across tools, reports, and evidence.

  • Compliance.tf Control: storage_account_blob_service_logging_enabled
  • Powerpipe Control: azure_compliance.control.storage_account_blob_service_logging_enabled

Last reviewed: 2026-10-15

View all Azure controls →

On this page

Ask AI about this

Help improve this page