compliance.tf

Storage account Table services should have Storage Logging enabled for 'Read', 'Write', and 'Delete' requests

Azure Table storage stores structured NoSQL data. Storage Logging happens server-side and records details for both successful and failed requests. The logs show the details of read, write, and delete operations against the tables.

What this control checks

Storage account Table services must have 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.14 Ensure Storage Logging is Enabled for Table Service for 'Read', 'Write', and 'Delete' Requests

CIS Azure Benchmark v2.0.0

  • 3.14 Ensure Storage Logging is Enabled for Table Service for 'Read', 'Write', and 'Delete' Requests

CIS Azure Benchmark v2.1.0

  • 3.14 Ensure Storage Logging is Enabled for Table Service for 'Read', 'Write', and 'Delete' Requests

CIS Azure Benchmark v3.0.0

  • 4.14 Ensure Storage Logging is Enabled for Table 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_table_service_logging_enabled
  • Powerpipe Control: azure_compliance.control.storage_account_table_service_logging_enabled

Last reviewed: 2026-10-15

View all Azure controls →

On this page

Ask AI about this

Help improve this page