> 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/public-exposure/appsec-azure-215.md).

# Backend of the API management system does not utilize HTTPS misconfiguration detected in code

## Rule Details

|                        |                           |
| ---------------------- | ------------------------- |
| Cortex AppSec Rule ID  | APPSEC\_AZURE\_215        |
| Category - Subcategory | Public Exposure - APIs    |
| Provider               | AZURE                     |
| Severity               | HIGH                      |
| Framework              | Terraform, Terraform Plan |

## Impact

This rule, identified by APPSEC\_AZURE\_215, falls under the category of encryption checks. It is verifying that the API management backend is using HTTPS protocol for communication and connectivity.

Why is this important? HTTPS ensures that all data communication between the client and server is encrypted and secure. Using unsecured protocols like HTTP can expose sensitive data to potential eavesdropping, manipulation, or cyberattacks. Implementing HTTPS is a basic yet essential step in maintaining security and safeguarding data in transit, hence non-compliance with this policy might lead to potential security risks.

## How to Fix

*Resource:* azurerm\_api\_management\_backend

* *Arguments:* url

## To fix this issue, ensure that your API Management Backend uses HTTPS as defined in your Terraform configuration. \[source,go]

## resource "azurerm\_api\_management\_backend" "example" { resource\_group\_name = azurerm\_resource\_group.example.name api\_management\_name = azurerm\_api\_management.example.name title = "example" url = "<https://example.com>" }


---

# 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/public-exposure/appsec-azure-215.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.