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

# Azure Service Bus Doesn't Use Double Encryption misconfiguration detected in code

## Azure Service Bus Doesn't Use Double Encryption misconfiguration detected in code

### Rule Details

|                        |                           |
| ---------------------- | ------------------------- |
| Cortex AppSec Rule ID  | APPSEC\_AZURE\_199        |
| Category - Subcategory | Storage - Encryption      |
| Provider               | AZURE                     |
| Severity               | MEDIUM                    |
| Framework              | Terraform, Terraform Plan |

### Impact

Azure Service Bus is a fully managed enterprise message broker with message queues and publish-subscribe topics. It offers secure and reliable communication between disparate applications. Ensuring that the Service Bus uses double encryption ensures that your data is encrypted at rest and in transit, providing an additional layer of protection against unauthorized access.

This rule checks that Azure Service Bus namespaces have double encryption enabled.

### How to Fix

*Resource:*

* azurerm\_servicebus\_namespace

*Arguments:*

* customer\_managed\_key/\[0]/infrastructure\_encryption\_enabled \[source,go]

***

resource "azurerm\_servicebus\_namespace" "example" { name = "example-servicebus-namespace"

## ... other configurations ...

customer\_managed\_key {

* infrastructure\_encryption\_enabled = true

## ... other configurations ...

}

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