> 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/appsec2-azure-9.md).

# Azure Virtual Machines does not utilise Managed Disks misconfiguration detected in code

## Rule Details

|                        |                                         |
| ---------------------- | --------------------------------------- |
| Cortex AppSec Rule ID  | APPSEC2\_AZURE\_9                       |
| Category - Subcategory | Compute - Unsanctioned Resource Or Type |
| Provider               | AZURE                                   |
| Severity               | LOW                                     |
| Framework              | Terraform, Terraform Plan               |

## Impact

Migrate BLOB based VHD's to Managed Disks on Virtual Machines to exploit the default features of this configuration. The features include

. Default Disk Encryption

. Resilience as Microsoft will managed the disk storage and move around if underlying hardware goes faulty

. Reduction of costs over storage accounts + Managed disks are by default encrypted on the underlying hardware so no additional encryption is required for basic protection, it is available if additional encryption is required. + Managed disks are by design more resilient that storage accounts. + For ARM deployed Virtual Machines, Azure Adviser will at some point recommend moving VHD's to managed disks both from a security and cost management perspective.

## How to Fix

## *Resource:* azurerm\_virtual\_machine \[source,go]

{ "resource "azurerm\_virtual\_machine" "virtual\_machine\_good" { name = "my-vm" location = "location" resource\_group\_name = "group\_name" network\_interface\_ids = \["1234567"] vm\_size = "Standard\_DS1\_v2"

storage\_image\_reference { publisher = "Canonical" offer = "UbuntuServer" sku = "16.04-LTS" version = "latest" }

storage\_os\_disk { name = "myosdisk1" caching = "ReadWrite" create\_option = "FromImage" managed\_disk\_type = "Standard\_LRS" }

os\_profile { computer\_name = "hostname" admin\_username = "testadmin" admin\_password = "Password1234!" }

os\_profile\_linux\_config { disable\_password\_authentication = false }

tags = { environment = "staging" }

}

## ", }


---

# 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/compute/appsec2-azure-9.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.