> 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-206.md).

# Azure Storage Accounts Without Proper Replication misconfiguration detected in code

## Azure Storage Accounts Without Proper Replication misconfiguration detected in code

### Rule Details

|                        |                                       |
| ---------------------- | ------------------------------------- |
| Cortex AppSec Rule ID  | APPSEC\_AZURE\_206                    |
| Category - Subcategory | Storage - Replication                 |
| Provider               | AZURE                                 |
| Severity               | LOW                                   |
| Framework              | ARM, Bicep, Terraform, Terraform Plan |

### Impact

Azure Storage Account provides scalable and secure storage for a wide range of data solutions. A key feature of the Storage Account service is its ability to replicate data, ensuring data durability and availability. Replication copies your data, either within the same data center, to a second data center, or across regions, providing protection against unexpected hardware failures, datacenter outages, or even large-scale events like natural disasters.

The following replication types are recommended for ensuring high durability and availability of data:

* GRS (Geo-Redundant Storage): Cross-regional replication to protect against regional unavailability.
* RAGRS (Read-Access Geo-Redundant Storage): Similar to GRS, but also provides read-only access to the data in the secondary location.
* GZRS (Geo-Zone-Redundant Storage): Combines the high availability provided by replication across availability zones with protection from regional outages.
* RAGZRS (Read-Access Geo-Zone-Redundant Storage): Provides read-only access to the data in the secondary location, and combines the advantages of GZRS.

This rule ensures that Azure Storage Accounts are configured to use one of the recommended replication methods, safeguarding your data against local and regional disruptions.

### How to Fix

*Resource:*

* azurerm\_storage\_account

*Arguments:*

* account\_replication\_type \[source,go]

***

resource "azurerm\_storage\_account" "example" { name = "examplestoracc"

## ... other configurations ...

* account\_replication\_type = "GRS" # Or use RAGRS, GZRS, or RAGZRS as per your requirement.

## ... 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

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

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.