> 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/storage/appsec-azure-3.md).

# Azure Storage Account without Secure transfer enabled misconfiguration detected in code

## Azure Storage Account without Secure transfer enabled misconfiguration detected in code

### Rule Details

|                        |                                       |
| ---------------------- | ------------------------------------- |
| Cortex AppSec Rule ID  | APPSEC\_AZURE\_3                      |
| Category - Subcategory | Storage - Encryption                  |
| Provider               | AZURE                                 |
| Severity               | LOW                                   |
| Framework              | ARM, Bicep, Terraform, Terraform Plan |
| Mapped CSPM/KSPM Rule  | 4a6a7642-06f0-4e51-aa79-a7c06afffdc5  |

### Impact

Azure Storage Accounts provide the capability to store a variety of data types, including blobs, files, queues, tables, and disks. Ensuring the secure transport of this data is crucial to prevent potential eavesdropping and man-in-the-middle attacks.

This rule ensures that the 'supportsHttpsTrafficOnly' property for Azure Storage Accounts is set to 'true'. By setting this property to 'true', only HTTPS traffic is allowed to the storage service. Notably, since the API version 2019-04-01, the default value for 'supportsHttpsTrafficOnly' has been set to 'true'. However, it's important to verify this for Storage Accounts, especially those created before this API version.

HTTPS ensures that the data between the client and server is encrypted, adding a layer of security for data in transit.

### How to Fix

*Resources:*

* azurerm\_storage\_account

*Arguments:*

* enable\_https\_traffic\_only

*Azure Resource Manager (ARM)*

*Resources:*

* Microsoft.Storage/storageAccounts

*Arguments:*

* properties/supportsHttpsTrafficOnly \[source,go]

***

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

* enable\_https\_traffic\_only = true # Ensure only HTTPS traffic is allowed. }

***

{ "type": "Microsoft.Storage/storageAccounts", "apiVersion": "2020-08-01-preview", "name": "mystorageaccount", "location": "westus", "properties": {

* "supportsHttpsTrafficOnly": true # Ensure the storage service allows HTTPS traffic only.

## ... other configurations ...

### } }


---

# 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/storage/appsec-azure-3.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.