> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/appsec-rules/iac-security/logging/appsec-azure-33.md).

# Azure storage account logging for queues is disabled misconfiguration detected in code

## Rule Details

|                        |                                       |
| ---------------------- | ------------------------------------- |
| Cortex AppSec Rule ID  | APPSEC\_AZURE\_33                     |
| Category - Subcategory | Logging - Disabled or missing         |
| Provider               | AZURE                                 |
| Severity               | LOW                                   |
| Framework              | ARM, Bicep, Terraform, Terraform Plan |

## Impact

The *Azure Queue Storage* service stores messages that may be read by any client with access to the storage account. A queue may contain an unlimited number of messages, each of which can be up to 64KB in size when using version 2011-08-18 or newer. *Storage Logging* takes place server-side recording details in the storage account for both successful and failed requests. These logs allow users to see the details of read, write, and delete operations against the queues. *Storage Logging* log entries contain the following information about individual requests: timing information, for example start time, end-to-end latency, server latency, authentication details, concurrency information, and the size of 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 individual requests and to diagnose issues with a storage service. Requests are logged on a best-effort basis. *Storage Analytics* logging is not enabled by default for your storage account.

## How to Fix

*Resource:* azurerm\_storage\_account

* *Arguments:* logging + hour\_metrics + minute\_metrics

## The *logging* field should be enough to enable logging. As Terraform apply might fail, it is recommended to also configure the *hour\_metrics* and *minute\_metrics* fields. \[source,go]

resource "azurerm\_storage\_account" "example" { name = "example" resource\_group\_name = data.azurerm\_resource\_group.example.name location = data.azurerm\_resource\_group.example.location account\_tier = "Standard" account\_replication\_type = "GRS" queue\_properties {

* logging { delete = true read = true write = true version = "1.0" retention\_policy\_days = 10 } } }

***

* hour\_metrics { enabled = true include\_apis = true version = "1.0" retention\_policy\_days = 10 }
* minute\_metrics { enabled = true include\_apis = true version = "1.0" retention\_policy\_days = 10 }

***


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://cortex-docs.paloaltonetworks.com/appsec-rules/iac-security/logging/appsec-azure-33.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.