> 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/analytics-alerts/alerts-by-name/uncommon-azure-cosmos-db-master-key-read-by-identity.md).

# Uncommon Azure Cosmos DB master key read by identity

### Synopsis

| Field                | Value                         |
| -------------------- | ----------------------------- |
| Activation Period    | 14 Days                       |
| Training Period      | 30 Days                       |
| Test Period          | N/A (single event)            |
| Deduplication Period | 1 Day                         |
| Required Data        | Azure Audit Log               |
| Detection Modules    | Cloud                         |
| ATT\&CK Tactic       | Credential Access (TA0006)    |
| ATT\&CK Technique    | Unsecured Credentials (T1552) |
| Severity             | Low                           |

### Description

A cloud identity read master keys from an Azure Cosmos DB account, which is uncommon for this identity.

### Attacker's Goals

Obtain Cosmos DB master keys to gain full access to the database, allowing data exfiltration, modification, or destruction.

### Investigative actions

* Check the identity's actions before and after the key read operation.
* Verify whether the identity is authorized to access Cosmos DB master keys.
* Determine if the retrieved keys were used to access or modify data in the Cosmos DB account.


---

# 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/analytics-alerts/alerts-by-name/uncommon-azure-cosmos-db-master-key-read-by-identity.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.