> 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/monitoring/appsec-azure-163.md).

# Vulnerability Scanning not enabled for Azure Container Registry misconfiguration detected in code

## Rule Details

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

## Impact

Vulnerability scanning for container images is a critical security feature that helps to identify software flaws in your container images. It is highly recommended to enable this feature in Azure Container Registry to identify and fix vulnerabilities before they can be exploited.

This rule checks whether the Azure Container Registry has vulnerability scanning enabled by requiring a SKU of `Standard` or `Premium`.

## How to Fix

*Resource:* azurerm\_container\_registry

* *Arguments:* sku

## // Note: Vulnerability scanning is only available for 'Standard' or 'Premium' SKUs. \[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 }

***


---

# 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/monitoring/appsec-azure-163.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.