> 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/2-java/leakage-of-sensitive-data-to-elasticsearch.md).

# Leakage of Sensitive Data to ElasticSearch

## Overview

* **Rule ID**: `java_third_parties_elasticsearch`
* **Applicable Languages**: Java
* **Weakness ID**: CWE-201

## Description

Leaking sensitive data to third-party loggers like ElasticSearch is a common cause of data breaches.

## Remediation Guidelines

* **Ensure** that all sensitive data is removed before sending it to third-party services like ElasticSearch.

## References

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