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