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

# Azure Event Grid Topic Local Authentication Enabled misconfiguration detected in code

## Azure Event Grid Topic Local Authentication Enabled misconfiguration detected in code

### Rule Details

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

### Impact

Azure Event Grid is a managed event routing service based on the publish-subscribe protocol. Event publishers send events to a topic, which then routes events to all subscribed event handlers. When building systems that react to the changes happening in Azure resources, Azure Event Grid can help to streamline and simplify the design and scalability of such systems.

However, for security purposes, it is recommended to avoid using local authentication mechanisms. These mechanisms can be less secure than managed or cloud-based mechanisms, potentially exposing the system to threats.

This rule ensures that local authentication for Azure Event Grid Topics is disabled.

### How to Fix

*Resource:*

* azurerm\_eventgrid\_topic

*Arguments:*

* local\_auth\_enabled \[source,go]

***

resource "azurerm\_eventgrid\_topic" "example" { name = "example-topic" location = azurerm\_resource\_group.example.location resource\_group\_name = azurerm\_resource\_group.example.name

## ... other configurations ...

* local\_auth\_enabled = false

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