> 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/appsec2-azure-21.md).

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

## Rule Details

|                        |                               |
| ---------------------- | ----------------------------- |
| Cortex AppSec Rule ID  | APPSEC2\_AZURE\_21            |
| Category - Subcategory | Logging - Disabled or missing |
| Provider               | AZURE                         |
| Severity               | LOW                           |
| Framework              | Terraform, Terraform Plan     |

## Impact

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. 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. We recommend that you ensure Storage Logging is enabled for Blob Service for Read Requests

## How to Fix

## *Resource:* azurerm\_resource\_group, azurerm\_log\_analytics\_workspace, azurerm\_storage\_account, azurerm\_log\_analytics\_storage\_insights,azurerm\_storage\_container \[source,go]

{ "resource "azurerm\_resource\_group" "resource\_group\_ok" { name = "example-resources" location = "West Europe" }

resource "azurerm\_log\_analytics\_workspace" "analytics\_workspace\_ok" { name = "exampleworkspace" location = azurerm\_resource\_group.resource\_group\_ok.location resource\_group\_name = azurerm\_resource\_group.resource\_group\_ok.name sku = "PerGB2018" retention\_in\_days = 30 }

resource "azurerm\_storage\_account" "storage\_account\_ok" { name = "examplestoracc" resource\_group\_name = azurerm\_resource\_group.resource\_group\_ok.name location = azurerm\_resource\_group.resource\_group\_ok.location account\_tier = "Standard" account\_replication\_type = "LRS" }

resource "azurerm\_log\_analytics\_storage\_insights" "analytics\_storage\_insights\_ok" { name = "example-storageinsightconfig" resource\_group\_name = azurerm\_resource\_group.resource\_group\_ok.name workspace\_id = azurerm\_log\_analytics\_workspace.analytics\_workspace\_ok.id

storage\_account\_id = azurerm\_storage\_account.storage\_account\_ok.id storage\_account\_key = azurerm\_storage\_account.storage\_account\_ok.primary\_access\_key blob\_container\_names= \["blobExample\_ok"] }

resource "azurerm\_storage\_container" "storage\_container\_ok" { name = "my-awesome-content.zip" storage\_account\_name = azurerm\_storage\_account.storage\_account\_ok.name storage\_container\_name = azurerm\_storage\_container.storage\_container\_ok.name container\_access\_type = "blob" }

## ", }


---

# 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/appsec2-azure-21.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.