> 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/iam/appsec-azure-176.md).

# Web PubSub Without Managed Identities misconfiguration detected in code

## Rule Details

|                        |                                       |
| ---------------------- | ------------------------------------- |
| Cortex AppSec Rule ID  | APPSEC\_AZURE\_176                    |
| Category - Subcategory | IAM - Authentication Policies         |
| Provider               | AZURE                                 |
| Severity               | MEDIUM                                |
| Framework              | ARM, Bicep, Terraform, Terraform Plan |

## Impact

Azure Managed Identities provides an identity for applications, allowing them to access other Azure resources. It is a secure alternative to using secrets or keys. With Managed Identities, credentials are outside of your code, reducing the risk of them being compromised.

Azure Web PubSub is a real-time web messaging service. For enhanced security, it's recommended to use Azure Managed Identities when Web PubSub accesses other Azure services.

This rule checks to ensure that Azure Web PubSub is configured to use Managed Identities.

## How to Fix

*Resource:* azurerm\_web\_pubsub

* *Arguments:* identity

## Note: The provided example sets the identity to "SystemAssigned". Depending on organizational requirements, "UserAssigned" can be chosen. Ensure that the chosen identity type aligns with security and operational needs. \[source,go]

resource "azurerm\_web\_pubsub" "example" { name = "example-webpubsub" location = azurerm\_resource\_group.example.location resource\_group\_name = azurerm\_resource\_group.example.name

* identity {
* type = "SystemAssigned" # or "UserAssigned" based on the requirement
* }

## tags = { Environment = "production" } }


---

# 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/iam/appsec-azure-176.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.