> 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/compute/appsec-azure-164.md).

# Azure Container Registry (ACR) Isn't Configured to Use Signed/Trusted Images misconfiguration detect

## Azure Container Registry (ACR) Isn't Configured to Use Signed/Trusted Images misconfiguration detected in code

### Rule Details

|                        |                                            |
| ---------------------- | ------------------------------------------ |
| Cortex AppSec Rule ID  | APPSEC\_AZURE\_164                         |
| Category - Subcategory | Public Exposure - Encryption And Protocols |
| Provider               | AZURE                                      |
| Severity               | MEDIUM                                     |
| Framework              | Terraform, Terraform Plan                  |

### Impact

Using signed or trusted images ensures that the images being used in your deployments are verified and not tampered with. Enabling this feature in Azure Container Registry adds a layer of security by ensuring only signed images can be pulled and run.

This rule checks whether Azure Container Registry has trust policy enabled for signed images.

### How to Fix

*Resource:* azurerm\_container\_registry

* *Arguments:* trust\_policy\_enabled \[source,go]

***

resource "azurerm\_container\_registry" "example" { name = "exampleContainerRegistry" resource\_group\_name = azurerm\_resource\_group.example.name location = azurerm\_resource\_group.example.location sku = "Standard" admin\_enabled = false

## If using azurerm version below 4.0

* trust\_policy {
* enabled = true
* }

## If using azurerm version 4.0 and above

* trust\_policy\_enabled = 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/compute/appsec-azure-164.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.