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

# Azure Container Registry (ACR) Doesn't Have a Retention Policy Set misconfiguration detected in code

## Azure Container Registry (ACR) Doesn't Have a Retention Policy Set misconfiguration detected in code

### Rule Details

|                        |                           |
| ---------------------- | ------------------------- |
| Cortex AppSec Rule ID  | APPSEC\_AZURE\_167        |
| Category - Subcategory | Storage - Backups         |
| Provider               | AZURE                     |
| Severity               | LOW                       |
| Framework              | Terraform, Terraform Plan |

### Impact

Azure Container Registry retention policies help to manage image storage by automatically deleting untagged manifests. Enabling this policy ensures efficient usage of storage and removes potential vulnerabilities associated with stale or unused images.

This rule checks if the retention policy is enabled for Azure Container Registry, ensuring that untagged manifests are automatically deleted.

### How to Fix

*Resource:* azurerm\_container\_registry

* *Arguments:* retention\_policy \[source,go]

***

resource "azurerm\_container\_registry" "example" { ...

## If using azurerm version below 4.0

* retention\_policy {
* enabled = true
* days = 7
* }

## If using azurerm version 4.0 and above

* retention\_policy\_in\_days = 7 }

***


---

# 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-167.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.