> 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/secrets-security/appsec-secret-116.md).

# MongoDB Atlas Keys Secret detected in code

## Rule Details

|                       |                      |
| --------------------- | -------------------- |
| Cortex AppSec Rule ID | APPSEC\_SECRET\_116  |
| Category              | Database Credentials |
| Severity              | HIGH                 |
| Framework             | Git                  |

## Impact

The MongoDB Atlas Keys Secret grants server-to-server access to cloud resources.

Exposure allows unauthorized access to databases, potentially leading to data exfiltration, modification, or deletion. This is a Critical Risk causing operational disruption and financial loss.

## How to Fix

To remediate exposed Database credentials:

1. Log in to your database administration tool or console.
2. Identify the database user associated with the exposed connection string.
3. Rotate the password for that specific database user immediately.
4. Update the connection strings in your application configuration or secrets manager.
5. Restart your application instances if necessary to apply the new connection string.

Next, remove the secret from your codebase:

1. Locate the exposed connection string in your codebase.
2. Replace the hardcoded value with a secure variable or reference.

Finally, clean your version control history:

1. Permanently remove the sensitive data from your version control history to ensure it cannot be retrieved.


---

# 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/secrets-security/appsec-secret-116.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.