# Leakage of sensitive data to Datadog RUM

## Overview

* **Rule ID**: `javascript_third_parties_datadog_browser`
* **Applicable Languages**: Javascript
* **Weakness ID**: CWE-201

## Description

Sensitive and private data on your pages may be sent to Datadog to identify elements with which a user interacted.

## Remediation Guidelines

* Control the information sent to Datadog by either manually setting an action name or applying a global scrubbing rule in the Datadog Browser SDK for RUM.

## References

* [**Datadog docs**](https://docs.datadoghq.com/)
* [**Scrubbing data**](https://docs.datadoghq.com/tracing/configure_data_security/?tab=mongodb#scrub-sensitive-data-from-your-spans)
* [**OWASP logging cheat sheet**](https://cheatsheetseries.owasp.org/cheatsheets/Logging_Cheat_Sheet.html)
* [**CWE-201: Insertion of Sensitive Information Into Sent Data**](https://cwe.mitre.org/data/definitions/201.html)
* [**OWASP Top 10: A01:2021 - Broken Access Control**](https://owasp.org/Top10/A01_2021-Broken_Access_Control/)

## Configuration

To omit this rule during a scan, and to provide you with continuous 24/7 code-level scanning, you can employ our [**SAST TOOL**](https://scopy.sec1.io/login)


---

# Agent Instructions: 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:

```
GET https://docs.sec1.io/user-docs/4-sast/3-javascript/leakage-of-sensitive-data-to-datadog-rum-browser.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.