> 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-segment.md).

# Leakage of sensitive data to Segment

## Overview

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

## Description

Exposing sensitive data to third-party loggers such as Segment is a frequent cause of data leaks and can result in data breaches.

## Remediation Guidelines

* **Make sure that all sensitive data is removed** before sending information to third-party analytics libraries like Segment.

## References

* [**Segment Node.js docs**](https://segment.com/docs/connections/sources/catalog/libraries/server/node/)
* [**Segment JavaScript docs**](https://segment.com/docs/connections/sources/catalog/libraries/website/javascript/)
* [**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)