> 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-132.md).
# Azure Cosmos DB key based authentication is enabled misconfiguration detected in code
## Rule Details
| | |
| ---------------------- | ------------------------------------- |
| Cortex AppSec Rule ID | APPSEC\_AZURE\_132 |
| Category - Subcategory | Storage - Permissions |
| Provider | AZURE |
| Severity | LOW |
| Framework | ARM, Bicep, Terraform, Terraform Plan |
| Mapped CSPM/KSPM Rule | ef14d0a6-8ed0-4f7a-9877-15efa3194737 |
## Impact
In 2019, Microsoft added a feature called Jupyter Notebook to Cosmos DB that lets customers visualize their data and create customized views. The feature was automatically turned on for all Cosmos DBs in February 2021. A series of misconfigurations in the notebook feature opened up a new attack vector - the notebook container allowed for a privilege escalation into other customer notebooks. As a result, an attacker could gain access to customers\`' Cosmos DB primary keys and other highly sensitive secrets such as the notebook blob storage access token. For more details visit - One way to reduce risk is to prevent management plane changes for clients using key based authentication. CosmosDB access keys are mainly used by applications to access data in CosmosDB containers. It is rare for organizations to have use cases where the keys are used to make management changes.
## How to Fix
*Resource:* encryptionOperation
* *Arguments:* EnableEncryption \[source,go]
***
{ "$schema": "", "contentVersion": "1.0.0.0", ... "resources": \[ { "type": "Microsoft.DocumentDB/databaseAccounts", "apiVersion": "2018-07-01", "name": "db", "properties": { ...
* ```
"disableKeyBasedMetadataWriteAccess": true,
}
```
} ] }
***
---
# 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-132.md?ask=&goal=
```
`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.