> For the complete documentation index, see [llms.txt](https://docs.sec1.io/user-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sec1.io/user-docs/4-sast/3-javascript/leakage-of-sensitive-data-to-datadog-rum-browser.md).

# 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)