# Leakage of sensitive data to ElasticSearch

## Overview

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

## Description

Exposing sensitive data to third-party data tools is a common cause of data leaks and can result in data breaches.

## Remediation Guidelines

* **Do** ensure all sensitive data is removed when logging errors or events to ElasticSearch

## References

* [**Elasticsearch docs**](https://www.elastic.co/guide/en/elasticsearch/client/javascript-api/current/index.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-elasticsearch.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.