> 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/public-exposure/appsec-azure-35.md).

# Azure Storage Account default network access is set to 'Allow' misconfiguration detected in code

## Rule Details

|                        |                                       |
| ---------------------- | ------------------------------------- |
| Cortex AppSec Rule ID  | APPSEC\_AZURE\_35                     |
| Category - Subcategory | Public Exposure - Storage Buckets     |
| Provider               | AZURE                                 |
| Severity               | LOW                                   |
| Framework              | ARM, Bicep, Terraform, Terraform Plan |
| Mapped CSPM/KSPM Rule  | 0c8ba0ca-2414-4d62-897c-4b57a291ae2b  |

## Impact

Restricting default network access helps to provide an additional layer of security. By default, storage accounts accept connections from clients on any network. To limit access to selected networks, the default action must be changed. We recommend you configure storage accounts to *deny* access to traffic from all networks, including internet traffic. At an appropriate time, access can be granted to traffic from specific Azure Virtual networks, allowing a secure network boundary for specific applications to be built. Access can also be granted to public internet IP address ranges enabling connections from specific internet or on-premises clients. When network rules are configured only applications from allowed networks can access a storage account. When calling from an allowed network applications continue to require authorization, such as a valid access key or SAS token, to access the storage account.

## How to Fix

*Resource:* azurerm\_storage\_account\_network\_rules

* *Arguments:* default\_action

In a Storage Account:

*Suppression Advice*

## This can trigger incorrectly on *azurerm\_storage\_account* when using correctly configured *azurerm\_storage\_account\_network\_rules*, if this occurs suppression is reasonable. \[source,go]

resource "azurerm\_storage\_account\_network\_rules" "test" { resource\_group\_name = azurerm\_resource\_group.test.name storage\_account\_name = azurerm\_storage\_account.test.name

* default\_action = "Deny" }

***

resource "azurerm\_storage\_account" "test" { name = var.watcher resource\_group\_name = azurerm\_resource\_group.test.name location = azurerm\_resource\_group.test.location

* network\_rules {
* default\_action="Deny"
* }

## account\_tier = "Standard" account\_kind = "StorageV2" account\_replication\_type = "LRS" enable\_https\_traffic\_only = true }


---

# 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/public-exposure/appsec-azure-35.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.